derjayjay / homebridge-keylights Goto Github PK

View Code? Open in Web Editor NEW

44.0 2.0 4.0 873 KB

Yet another Homebridge plugin for Elgato Key Light and Key Light Air. https://homebridge.io

License: MIT License

TypeScript 100.00%

homebridge-plugin homebridge key-lights homekit elgato elgato-key-light

homebridge-keylights's People

Contributors

Stargazers

Watchers

Forkers

lumaxis abstrctn marcocanc mpash

homebridge-keylights's Issues

"Discovered accessory on network" but "Could not register accessory, skipping"

I have 4 key lights in my office, 2 at my computer, and 2 at my writing desk.

All 4 are seen, but cannot be registered.

This is what I see in the HB log:

[3/3/2022, 7:18:54 AM] [Elgato Key Lights] Discovered accessory on network: Elgato Key Light Air 70D3
[3/3/2022, 7:18:54 AM] [Elgato Key Lights] Could not register accessory, skipping Elgato Key Light Air 70D3

[3/3/2022, 7:18:54 AM] [Elgato Key Lights] Discovered accessory on network: Writing Desk Left
[3/3/2022, 7:18:54 AM] [Elgato Key Lights] Could not register accessory, skipping Writing Desk Left

[3/3/2022, 7:18:54 AM] [Elgato Key Lights] Discovered accessory on network: Elgato Key Light Air Left
[3/3/2022, 7:18:54 AM] [Elgato Key Lights] Could not register accessory, skipping Elgato Key Light Air Left

[3/3/2022, 7:18:54 AM] [Elgato Key Lights] Discovered accessory on network: Writing Desk Right
[3/3/2022, 7:18:54 AM] [Elgato Key Lights] Could not register accessory, skipping Writing Desk Right

I have rebooted HomeKit.

I have rebooted the key lights and made sure they are on the latest firmware.

I can access them via "http://ip.address.of.keylight:9123"

I installed Homebridge specifically for this. Any help would be appreciated.

Support "Elgato Ring Light"

Hey,

is it possible also to use the new "Elgato Ring Light"?

"Could not register accessory, skipping…"

Hi there,
I have the same behaviour described here, systematically:
[4/23/2021, 9:50:45 PM] [Elgato Key Lights] Discovered accessory on network: Elgato Key Light Air 2B20
[4/23/2021, 9:50:45 PM] [Elgato Key Lights] Discovered accessory on network: Elgato Key Light Air 2997
[4/23/2021, 9:50:45 PM] [Elgato Key Lights] Could not register accessory, skipping Elgato Key Light Air 2B20
[4/23/2021, 9:50:45 PM] [Elgato Key Lights] Could not register accessory, skipping Elgato Key Light Air 2997

I tried to switch off and on the Key Lights, then restarting Homebridge, or uninstalling and reinstalling the plugin, ticking "Use IP address instead of hostname" in the Advanced setting, or creating a virtual dedicated bridge with this plugin: nothing works. But the official Elgato app works like a charm.

Any help there?

Multiple Keylights - how to config?

How do I configure more than one Keylight?

Keylights occasionally become unresponsive

Not sure if this is just a Keylight behavior issue, but the Keylights occasionally become unresponsive in Homebridge. I have to powercycle the keylight to get it responsive again. This behavior is new since I've set up the homebridge-keylights plugin, it was working fine via Elgato Control Center before.

Not sure if the plugin is sending commands, not closing connections, etc. that could cause the device to hang?

HOOBS 3.2.9, Node 12.16.3, Keylights 1.2.0.

Keylight or LightStrip color temperature warning

Either the Keylight or LightStrip is throwing an error:

[9/20/2022, 3:42:32 PM] [homebridge-keylights] This plugin generated a warning from the characteristic 'Color Temperature': characteristic was supplied illegal value: number 0 exceeded minimum of 140. See https://homebridge.io/w/JtMGR for more info.

spread-the-word - extremely chatty

Hi there - first off much thanks for this plugin. I've been using it for almost a year now and it has been wonderfully convenient to access and control the Key Lights through HomeKit.

I recently ran Homebridge debug with * to look into some other issue, but discovered the logs flooded with activity from spread-the-word. I haven't looked deeply yet into the library but figured I'd start here since it's a transitive dep and could be a configuration issue in how it's initialized. Sample of the logs that is pretty much non-stop:

2022-11-03T20:49:05.198Z SpreadTheWord:Server response from 192.168.1.1
2022-11-03T20:49:05.198Z SpreadTheWord:Server added 4 records
2022-11-03T20:49:05.199Z SpreadTheWord:Listener querying unresolved record openthread.thread.home.arpa
2022-11-03T20:49:05.199Z SpreadTheWord:Listener querying unresolved record _dacp._tcp.local
2022-11-03T20:49:05.200Z SpreadTheWord:Server query from 172.21.147.128
2022-11-03T20:49:05.200Z SpreadTheWord:Server question: openthread.thread.home.arpa ANY
2022-11-03T20:49:05.200Z SpreadTheWord:Server answer all
2022-11-03T20:49:05.200Z SpreadTheWord:Server question: _dacp._tcp.local ANY
2022-11-03T20:49:05.200Z SpreadTheWord:Server answer all
2022-11-03T20:49:05.261Z SpreadTheWord:TXT parse <Buffer 06 63 23 3d 31 39 39 04 66 66 3d 30 14 69 64 3d 30 45 3a 45 45 3a 33 41 3a 36 39 3a 41 31 3a 38 36 0d 6d 64 3d 68 6f 6d 65 62 72 69 64 67 65 06 70 76 ... 31 more bytes> { binary: undefined }
2022-11-03T20:49:05.261Z SpreadTheWord:TXT parse output {
  'c#': '199',
  ff: '0',
  id: '0E:EE:3A:69:A1:86',
  md: 'homebridge',
  pv: '1.1',
  's#': '1',
  sf: '0',
  ci: '2',
  sh: 'MPJecA=='
} { binary: undefined }
2022-11-03T20:49:05.261Z SpreadTheWord:TXT parse <Buffer 04 63 23 3d 32 04 66 66 3d 30 14 69 64 3d 30 45 3a 31 33 3a 30 36 3a 30 33 3a 30 42 3a 33 33 0d 6d 64 3d 68 6f 6d 65 62 72 69 64 67 65 06 70 76 3d 31 ... 29 more bytes> { binary: undefined }
2022-11-03T20:49:05.262Z SpreadTheWord:TXT parse output {
  'c#': '2',
  ff: '0',
  id: '0E:13:06:03:0B:33',
  md: 'homebridge',
  pv: '1.1',
  's#': '1',
  sf: '0',
  ci: '2',
  sh: 'cmYnqA=='
} { binary: undefined }
2022-11-03T20:49:05.262Z SpreadTheWord:TXT parse <Buffer 04 63 23 3d 37 04 66 66 3d 30 14 69 64 3d 30 45 3a 44 37 3a 35 44 3a 38 44 3a 37 39 3a 38 31 0d 6d 64 3d 68 6f 6d 65 62 72 69 64 67 65 06 70 76 3d 31 ... 29 more bytes> { binary: undefined }
2022-11-03T20:49:05.262Z SpreadTheWord:TXT parse output {
  'c#': '7',
  ff: '0',
  id: '0E:D7:5D:8D:79:81',
  md: 'homebridge',
  pv: '1.1',
  's#': '1',
  sf: '0',
  ci: '2',
  sh: 'QMGQsg=='
} { binary: undefined }
2022-11-03T20:49:05.263Z SpreadTheWord:TXT parse <Buffer 06 63 23 3d 31 34 32 04 66 66 3d 30 14 69 64 3d 30 45 3a 37 35 3a 39 44 3a 43 38 3a 39 35 3a 31 38 0d 6d 64 3d 68 6f 6d 65 62 72 69 64 67 65 06 70 76 ... 31 more bytes> { binary: undefined }
2022-11-03T20:49:05.263Z SpreadTheWord:TXT parse output {
  'c#': '142',
  ff: '0',
  id: '0E:75:9D:C8:95:18',
  md: 'homebridge',
  pv: '1.1',
  's#': '1',
  sf: '0',
  ci: '2',
  sh: 'ZGu2Gg=='
} { binary: undefined }
2022-11-03T20:49:05.264Z SpreadTheWord:TXT parse <Buffer 04 63 23 3d 33 04 66 66 3d 30 14 69 64 3d 30 45 3a 33 36 3a 43 33 3a 38 32 3a 43 36 3a 35 44 0d 6d 64 3d 68 6f 6d 65 62 72 69 64 67 65 06 70 76 3d 31 ... 29 more bytes> { binary: undefined }
2022-11-03T20:49:05.265Z SpreadTheWord:TXT parse output {
  'c#': '3',
  ff: '0',
  id: '0E:36:C3:82:C6:5D',
  md: 'homebridge',
  pv: '1.1',
  's#': '1',
  sf: '0',
  ci: '2',
  sh: '06IqCQ=='
} { binary: undefined }
2022-11-03T20:49:05.267Z SpreadTheWord:TXT parse <Buffer 04 63 23 3d 33 04 66 66 3d 30 14 69 64 3d 30 45 3a 35 41 3a 43 44 3a 35 44 3a 42 35 3a 45 41 0d 6d 64 3d 68 6f 6d 65 62 72 69 64 67 65 06 70 76 3d 31 ... 29 more bytes> { binary: undefined }
2022-11-03T20:49:05.267Z SpreadTheWord:TXT parse output {
  'c#': '3',
  ff: '0',
  id: '0E:5A:CD:5D:B5:EA',
  md: 'homebridge',
  pv: '1.1',
  's#': '1',
  sf: '0',
  ci: '2',
  sh: 'yza0kQ=='
} { binary: undefined }
2022-11-03T20:49:05.268Z SpreadTheWord:Server response from 192.168.1.102
2022-11-03T20:49:05.270Z SpreadTheWord:Server added 20 records
2022-11-03T20:49:05.272Z SpreadTheWord:Listener querying unresolved record openthread.thread.home.arpa
2022-11-03T20:49:05.273Z SpreadTheWord:Listener querying unresolved record _dacp._tcp.local
2022-11-03T20:49:05.274Z SpreadTheWord:Server query from 172.21.147.128
2022-11-03T20:49:05.275Z SpreadTheWord:Server question: openthread.thread.home.arpa ANY
2022-11-03T20:49:05.275Z SpreadTheWord:Server answer all
2022-11-03T20:49:05.276Z SpreadTheWord:Server question: _dacp._tcp.local ANY
2022-11-03T20:49:05.276Z SpreadTheWord:Server answer all
2022-11-03T20:49:05.312Z SpreadTheWord:TXT parse <Buffer 0b 73 68 3d 6b 32 44 73 50 67 3d 3d 05 63 69 3d 31 30 04 73 66 3d 30 05 73 23 3d 34 35 06 70 76 3d 31 2e 31 08 6d 64 3d 43 47 44 4e 31 14 69 64 3d 37 ... 26 more bytes> { binary: undefined }
2022-11-03T20:49:05.313Z SpreadTheWord:TXT parse output {
  sh: 'k2DsPg==',
  ci: '10',
  sf: '0',
  's#': '45',
  pv: '1.1',
  md: 'CGDN1',
  id: '7A:67:15:8D:D4:D7',
  ff: '1',
  'c#': '3'
} { binary: undefined }
2022-11-03T20:49:05.315Z SpreadTheWord:Server response from 192.168.1.1
2022-11-03T20:49:05.316Z SpreadTheWord:Server added 4 records
2022-11-03T20:49:05.317Z SpreadTheWord:Listener querying unresolved record openthread.thread.home.arpa
2022-11-03T20:49:05.318Z SpreadTheWord:Listener querying unresolved record _dacp._tcp.local
2022-11-03T20:49:05.320Z SpreadTheWord:Server query from 172.21.147.128
2022-11-03T20:49:05.320Z SpreadTheWord:Server question: openthread.thread.home.arpa ANY
2022-11-03T20:49:05.322Z SpreadTheWord:Server answer all
2022-11-03T20:49:05.323Z SpreadTheWord:Server question: _dacp._tcp.local ANY
2022-11-03T20:49:05.324Z SpreadTheWord:Server answer all
2022-11-03T20:49:05.367Z SpreadTheWord:TXT parse <Buffer 09 6d 66 3d 45 6c 67 61 74 6f 06 64 74 3d 32 30 30 14 69 64 3d 33 43 3a 36 41 3a 39 44 3a 31 39 3a 31 41 3a 33 41 21 6d 64 3d 45 6c 67 61 74 6f 20 4b ... 29 more bytes> { binary: undefined }
2022-11-03T20:49:05.367Z SpreadTheWord:TXT parse output {
  mf: 'Elgato',
  dt: '200',
  id: '3C:6A:9D:19:1A:3A',
  md: 'Elgato Key Light Air XXXXXXXXX',
  pv: '1.0'
} { binary: undefined }

I'm running Homebridge in a container with bridged networking; in this case 172.21.147.128 refers to the Homebridge instance. All the other 192.* addresses are local devices on the network.

Based on my understanding of the plugin, I'm expecting discovery to happen at start, but then it should be pretty quiet once accessories are initialized. I've seen some chatter around HomePods flooding the network with openthread.thread.home.arpa queries, but my expectation is that this plugin wouldn't (shouldn't?) care once the accessories have been initialized. Is this expected behavior based of stw based on the needs of this plugin?

skipping Elgato Key Light Air

Hi, thanks to the nice code, but I have some issue to connect my keylight air, could you help? Thanks!
it shows:
[6/3/2021, 3:57:56 PM] [Elgato Key Lights] Discovered accessory on network: Elgato Key Light Air 384B
[6/3/2021, 3:57:56 PM] [Elgato Key Lights] Could not register accessory, skipping Elgato Key Light Air 384B

After plugin and HOOBS reinstall, Plugin can't control the lights

I had an unfortunate situation (note to self: never upgrade node just for the heck of it) that required a complete in-place reinstall of HOOBS and all plugins. Upon reinstalling, the Keylight plugin picked up the cached accessory for my Keylight, however, it's unable to control the Keylight at all.

Any suggestions on how to completely blow away the cached settings for the plugin so it can start re-discovery from scratch?

12/1/2020, 9:10:42 AM [Elgato Key Lights] Loading accessory from cache: Elgato Key Light 6F41
12/1/2020, 9:10:43 AM [Elgato Key Lights] Discovered accessory on network: Elgato Key Light 6F41
12/1/2020, 9:10:51 AM [Elgato Key Lights] Restoring existing accessory from cache: Elgato Key Light 6F41 as Elgato Key Light 6F41

Key Lights found by plugin, homekit says no response

I have two Key Lights - Both are found by homebridge and I can toggle them on and off via the web interface. They also appear in Homekit but don't work, with the message No Response.

Deleting and re-adding homebridge, restarting the lights, restarting the router, nothing has worked. Using the new homekit architecture, could that have something to do with it?

Infinite loop in spread the word

It's definitely an issue in module stw but not sure how it's being triggered

(node:2263) UnhandledPromiseRejectionWarning: RangeError: Maximum call stack size exceeded
    at RecordRegistry.tracePTR (/homebridge/node_modules/homebridge-keylights/node_modules/spread-the-word/dist/RecordRegistry.js:54:13)
    at RecordRegistry.tracePTR (/homebridge/node_modules/homebridge-keylights/node_modules/spread-the-word/dist/RecordRegistry.js:59:57)
    at RecordRegistry.tracePTR (/homebridge/node_modules/homebridge-keylights/node_modules/spread-the-word/dist/RecordRegistry.js:59:57)
    at RecordRegistry.tracePTR (/homebridge/node_modules/homebridge-keylights/node_modules/spread-the-word/dist/RecordRegistry.js:59:57)
    at RecordRegistry.tracePTR (/homebridge/node_modules/homebridge-keylights/node_modules/spread-the-word/dist/RecordRegistry.js:59:57)
    at RecordRegistry.tracePTR (/homebridge/node_modules/homebridge-keylights/node_modules/spread-the-word/dist/RecordRegistry.js:59:57)
    at RecordRegistry.tracePTR (/homebridge/node_modules/homebridge-keylights/node_modules/spread-the-word/dist/RecordRegistry.js:59:57)
    at RecordRegistry.tracePTR (/homebridge/node_modules/homebridge-keylights/node_modules/spread-the-word/dist/RecordRegistry.js:59:57)
    at RecordRegistry.tracePTR (/homebridge/node_modules/homebridge-keylights/node_modules/spread-the-word/dist/RecordRegistry.js:59:57)
    at RecordRegistry.tracePTR (/homebridge/node_modules/homebridge-keylights/node_modules/spread-the-word/dist/RecordRegistry.js:59:57)

Fix should go to upstream but the module seems not maintained anymore.

Could not register accessory, skipping

[8/21/2020, 10:10:41 AM] [Elgato Key Lights] Discovered accessory on network: Elgato Key Light Air ****
...
[8/21/2020, 10:12:53 AM] [Elgato Key Lights] Could not register accessory, skipping Elgato Key Light Air ****

Not sure if this might be because I had another key light plugin, nextcart’s, installed? Uninstalled before adding yours. That one connected and worked somewhat reliably.

Add homekit adaptive lighting support

Great Plugin! Really nice to control the lights with Apple HomeKit too. Do yo think it would be possible to add homekit adaptive lighting support for the non-streaming times?

Thanks!

"Could not register accessory" homebridge in docker

I'm wondering if this is because I'm running it in docker on my Synology NAS, but I was able to fix this issue by checking the useIP button. I'm wondering if .local addresses can't resolve correctly when requested from within docker. Regardless, it's working now.

Thank you so much for this simple solution! Much appreciated!

Light Keeps Turning on at 60%

I have just installed the keylights plugin which works fine except the brightness continually defaults to 60% regardless of what is set in the config.

I have tried all variations of the power-on settings none of which seem to make any difference, the light simply powers on at 60%.

Add Key Light Mini

There's a new battery-driven Key Light that has a few new configuration options (whether to bypass the battery aka "studio mode", take certain actions when the battery is low. Would it be possible to add support for this? It shows up in Homebridge with this plugin, but I can't seem to get it to rename within the Homebridge / HomeKit config, and having some of the additional settings available in the plugin would save me having to switch apps.

Thanks.

Add support for Elgato Light Strip

That would be nice to have for support for the light strip.
When we add one with this plug-in, the light strip "transforms" into a key light and we loose the ability to control colour.

Extremely frequent DNS queries from HomeBridge; some incorrectly formed

Yesterday I noticed that my key light integration wasn't working. I unplugged and re-plugged in the key light, and it started working again.

As part of troubleshooting I also looked at the HomeBridge logs, which indicated frequent DNS queries for the key light. I then looked at my DNS server (a Pi-Hole) and was surprised to find that almost all of my DNS query traffic was HomeBridge querying for my key light.

It appears that HomeBridge (or the Keylight plugin for HomeBridge) is querying for A and AAAA records for the discovered key light, every second, and is ALSO appending the local domain name (.local) and querying both again, every second.

So the problem is query volume. Querying once per second for multiple records is kind of overkill.

The second problem is that it's also appending the domain name when it already has an FQDN, and making multiple queries per second with names that cannot possibly work.

derjayjay / homebridge-keylights Goto Github PK

homebridge-keylights's People

Contributors

Stargazers

Watchers

Forkers

homebridge-keylights's Issues

Recommend Projects

Recommend Topics

Recommend Org

Jobs