too much log / polling interval
Closed this issue · 3 comments
There is too much log and a small interval in my opinion
Feb 27 21:07:35 rpi-speaker1 homebridge[7655]: [2019-2-27 21:07:35] [Yeelight] doing a round of proactive search for known devices.
Feb 27 21:07:35 rpi-speaker1 homebridge[7655]: [2019-2-27 21:07:35] [Yeelight] received advertisement from e061b8.
Feb 27 21:07:36 rpi-speaker1 homebridge[7655]: [2019-2-27 21:07:36] [Yeelight] received advertisement from 6eca50.
Feb 27 21:07:36 rpi-speaker1 homebridge[7655]: [2019-2-27 21:07:36] [Yeelight] received advertisement from 6eca50.
Feb 27 21:07:36 rpi-speaker1 homebridge[7655]: [2019-2-27 21:07:36] [Yeelight] received advertisement from 360572.
Feb 27 21:07:36 rpi-speaker1 homebridge[7655]: [2019-2-27 21:07:36] [Yeelight] received advertisement from e061b8.
Feb 27 21:07:36 rpi-speaker1 homebridge[7655]: [2019-2-27 21:07:36] [Yeelight] received advertisement from 360572.
Feb 27 21:07:50 rpi-speaker1 homebridge[7655]: [2019-2-27 21:07:50] [Yeelight] doing a round of proactive search for known devices.
Feb 27 21:07:50 rpi-speaker1 homebridge[7655]: [2019-2-27 21:07:50] [Yeelight] received advertisement from e061b8.
Feb 27 21:07:50 rpi-speaker1 homebridge[7655]: [2019-2-27 21:07:50] [Yeelight] received advertisement from e061b8.
Feb 27 21:07:50 rpi-speaker1 homebridge[7655]: [2019-2-27 21:07:50] [Yeelight] received advertisement from 360572.
Feb 27 21:07:50 rpi-speaker1 homebridge[7655]: [2019-2-27 21:07:50] [Yeelight] received advertisement from 6eca50.
Feb 27 21:07:50 rpi-speaker1 homebridge[7655]: [2019-2-27 21:07:50] [Yeelight] received advertisement from 6eca50.
Feb 27 21:07:50 rpi-speaker1 homebridge[7655]: [2019-2-27 21:07:50] [Yeelight] received advertisement from 360572.
Feb 27 21:08:05 rpi-speaker1 homebridge[7655]: [2019-2-27 21:08:05] [Yeelight] doing a round of proactive search for known devices.
Feb 27 21:08:06 rpi-speaker1 homebridge[7655]: [2019-2-27 21:08:06] [Yeelight] received advertisement from 6eca50.
Feb 27 21:08:06 rpi-speaker1 homebridge[7655]: [2019-2-27 21:08:06] [Yeelight] received advertisement from 6eca50.
Feb 27 21:08:06 rpi-speaker1 homebridge[7655]: [2019-2-27 21:08:06] [Yeelight] received advertisement from e061b8.
Feb 27 21:08:06 rpi-speaker1 homebridge[7655]: [2019-2-27 21:08:06] [Yeelight] received advertisement from 360572.
Feb 27 21:08:06 rpi-speaker1 homebridge[7655]: [2019-2-27 21:08:06] [Yeelight] received advertisement from e061b8.
Feb 27 21:08:06 rpi-speaker1 homebridge[7655]: [2019-2-27 21:08:06] [Yeelight] received advertisement from 360572.
is there a way to increase interval using a config variable?
is there a way to disable logging of the polling?
Thank you.
Hello @ageorgios,
This polling should only happen when you start until all known Yeelights are found at which point it stops.
Do you have any device offline? I should probably implement a reasonable timeout after which it just gives up on the missing devices...
I am pretty sure there in no offline Yeelight on my network.
I haven't explicitly specified the yeelights and I let your code discover the devices with this configuration:
"platforms": [{
"platform": "yeelight",
"name": "Yeelight",
}]
It would be great if you implemented a stop on this search after 1-2 minutes!
Thanks
actually I had a yeelight offline... but what should I do if i decide to remove a bulb?