-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
OTA: Firmware on (SNZB-06P) #22071
Comments
I'm seeing the same problem myself |
I am experiencing the same problem as well. |
1 similar comment
I am experiencing the same problem as well. |
I'm having the same issue. The device came with version 1.0.6 and can't be configured properly because of Is there a way to flash an earlier version? |
I am struggeling about the same thing. I just received two units, one with 1.03 which I could update to 1.05 working quite well now. |
What happened?
is:open OTA: Firmware "0x0ceff6fffe5e086d" (SNZB-06P) is newer than the latest firmware available online.
The latest firmware available online = 1.0.5
What did you expect to happen?
Update firmware SNZB-06P to firmware 1.0.5
How to reproduce it (minimal and precise)
zigbee2mqtt > OTA > SNZB-06P Check for updates
Zigbee2MQTT version
1.36.1
Adapter firmware version
1.0.6
Adapter
SNZB-06P
Setup
home asisstant intel mini pc
Debug log
Info 2024-04-04 12:58:56Checking if update available for 'SNZB-06P'
Warning 2024-04-04 12:58:59OTA: Firmware on '0x0ceff6fffe5e086d' (SNZB-06P) is newer than latest firmware online.
Info 2024-04-04 12:58:59No update available for 'SNZB-06P'
Info 2024-04-04 12:58:59MQTT publish: topic 'zigbee2mqtt/SNZB-06P', payload '{"illumination":"bright","linkquality":180,"occupancy":false,"occupancy_sensitivity":"high","occupancy_timeout":30,"update":{"installed_version":4102,"latest_version":4101,"state":"idle"},"update_available":null}'
Info 2024-04-04 12:58:59MQTT publish: topic 'zigbee2mqtt/bridge/response/device/ota_update/check', payload '{"data":{"id":"SNZB-06P-K","updateAvailable":false},"status":"ok","transaction":"r2muf-3"}'
The text was updated successfully, but these errors were encountered: