-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Müller Licht bulbs constantly request OTAs #16371
Comments
Normally Zigbee2MQTT should respond to these requests: zigbee2mqtt/lib/extension/otaUpdate.ts Line 124 in 1402139
See https://www.zigbee2mqtt.io/guide/usage/debug.html on how to enable the herdsman debug logging. Note that this is only logged to STDOUT and not to log files. |
Well, while I wasn't able to transfer it to the internal log file, I did a grab with putty.
I hope this helps. |
It is a bit hard to see in this log, I've improved the logging, the herdsman debug logging is not needed anymore, just the normal z2m debug logging is enough. After each Changes will be available in the dev branch in a few hours from now. (https://www.zigbee2mqtt.io/advanced/more/switch-to-dev-branch.html) |
Yep now it is easier:
|
Changes will be available in the dev branch in a few hours from now. (https://www.zigbee2mqtt.io/advanced/more/switch-to-dev-branch.html) |
I can confirm this changes and reduces the spamming with OTA requests. The bulbs now fire the OTA request roughly every minute (one minute + at least one second). Before it was every 15 plus x seconds. That takes some pressure from the network, but is still not nice. It has already been suspected before that the firmware in these kinds of lamps are incorrectly in a developer mode. So I think that is kind of the best we can get (maybe I get in touch with the company to ask for an updated firmware). I will now dig deeper into #16278, @ASNNetworks there already suggested that the bulbs react with flickering when pairing mode "all" is activated (so far confirmed from my side). So it seems to be kind of developer mode, too. Maybe you can give some hints in the other thread what to look for in the logs.
|
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days |
What happened?
I noticed that my Müller-Licht bulbs request an OTA update very often and Zigbee2MQTT seems to not react to it at all.
What did you expect to happen?
Maybe Z2M can tell devices that there's no OTA available, if they are not yet supported with firmware updates, to give them a response to that and back off with their requests?
How to reproduce it (minimal and precise)
Use Müller Licht bulbs in a Zigbee Network with Z2M/zStack as coordinator
Zigbee2MQTT version
1.29.2
Adapter firmware version
20221102
Adapter
Slaesh's CC2652RB stick
Debug log
ota_log.txt
See also
#16278
The text was updated successfully, but these errors were encountered: