-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
constantly broadcasting to find devices........ #26
Comments
I am having the exact same issue. |
I have the same problem. |
I have the same issue. I traced it down to a scanInterval parameter. For whatever reason, Twinkly plugin is constantly scanning for new devices. I think this should be done once at startup but there's probably a reason the developer choose to make it loop. As a workaroud, you can increase the scanInterval to something bigger. By default it's 60 seconds (60000 ms). Bump it up to once a day (86400000ms) and that will reduce the messages significantly. Just add it to your config.json like so:
|
Sorry, I'm dumb. Where do I put that on the config? |
It's under the platforms array. You should see an existing one with twinkly. |
I've created a nice update for this: https://github.com/vanHoesel/homebridge-twinkly-plus and delivers colour change too! |
Is there any way to stop this from happening non stop?
[20/11/2021, 18:30:44] [Twinkly] Found known device: XXX @ 192.168.1.XXX (XXX)
[20/11/2021, 18:31:44] [Twinkly] Broadcasting to find devices...
[20/11/2021, 18:31:44] [Twinkly] GET http://XXX/xled/v1/gestalt
[20/11/2021, 18:31:44] [Twinkly] Found known device: XXXE @ 192.168.1.XXX (Twinkly_XXX)
[20/11/2021, 18:32:44] [Twinkly] Broadcasting to find devices...
[20/11/2021, 18:32:44] [Twinkly] GET http://192.168.1.XXX/xled/v1/gestalt
[20/11/2021, 18:32:44] [Twinkly] Found known device: XXX @ XXX (Twinkly_XXX)
[20/11/2021, 18:33:44] [Twinkly] Broadcasting to find devices...
[20/11/2021, 18:33:44] [Twinkly] GET http://192.168.1.XXX/xled/v1/gestalt
[20/11/2021, 18:33:45] [Twinkly] Found known device: XXX @ 192.168.1.XXX (Twinkly_XXX)
[20/11/2021, 18:34:44] [Twinkly] Broadcasting to find devices...
[20/11/2021, 18:34:44] [Twinkly] GET http://192.168.1.XXX/xled/v1/gestalt
[20/11/2021, 18:34:44] [Twinkly] Found known device: XXX @ 192.168.1.XXX (Twinkly_XXX)
[20/11/2021, 18:35:44] [Twinkly] Broadcasting to find devices...
[20/11/2021, 18:35:44] [Twinkly] GET http://192.168.1.XXX/xled/v1/gestalt
[20/11/2021, 18:35:44] [Twinkly] Found known device: XXXE @ 192.168.1.XXX (Twinkly_XXX)
[20/11/2021, 18:36:44] [Twinkly] Broadcasting to find devices...
[20/11/2021, 18:36:44] [Twinkly] GET http://192.168.1.XXX/xled/v1/gestalt
[20/11/2021, 18:36:44] [Twinkly] Found known device: XXX @ 192.168.1.XXX (Twinkly_XXX)
[20/11/2021, 18:37:44] [Twinkly] Broadcasting to find devices...
[20/11/2021, 18:37:44] [Twinkly] GET http://192.168.1.XXX/xled/v1/gestalt
[20/11/2021, 18:37:46] [Twinkly] Found known device: XXX @ 192.168.1.XXX (Twinkly_XXX)
[20/11/2021, 18:38:44] [Twinkly] Broadcasting to find devices...
[20/11/2021, 18:38:44] [Twinkly] GET http://192.168.1.XXX/xled/v1/gestalt
[20/11/2021, 18:38:44] [Twinkly] Found known device: XXX @ 192.168.1.XXX (Twinkly_XXX)
[20/11/2021, 18:39:44] [Twinkly] Broadcasting to find devices...
[20/11/2021, 18:39:44] [Twinkly] GET http://192.168.1.XXX/xled/v1/gestalt
[20/11/2021, 18:39:44] [Twinkly] Found known device: XXX @ 192.168.1.XXX (Twinkly_XXX)
The text was updated successfully, but these errors were encountered: