-
Notifications
You must be signed in to change notification settings - Fork 200
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
New FW for Namrom 1402769 dimmer #565
Conversation
The file 1402769-Firmware-35.ota downloaded from vendor somehow was put into EcoDim folder for manufacturerCode 4714 instead. Also after running script shows up a few more files I did not change. I'm a noob at this, sorry if I did something wrong!
"manufacturerCode": 4107, | ||
"imageType": 260, | ||
"sha512": "eb9e81b28ea8128831c0f656e65be2821b6d06207bd44adbc31b050ed41e3656edc10e1c0a27cf73a2817c257208f9002c3e219913903ecdaacf7857f799b001", | ||
"url": "https://otau.meethue.com/storage/ZGB_100B_0104/33cbfd3d-3b58-43e2-a6a0-1e6fe50f2bee/ConnectedLamp-Atmel-Target_0012.sbl-ota" | ||
"sha512": "d2bf330b9a23114efb6a613ccefce691e4a67a98175033e65d3eaf6841312b5a542bd538ae19c06c3804aa06224d35acc184f4b37a6198b457df2a173a490f21", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why did this entity change?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I really don't know. I just added the file in a fresh fork (uploaded it, since url gave error 403 Forbidden), run node scripts/add.js PATH_TO_OTA_FILE and then run node scripts/updateall.js and these changes showed up. I did not touch anything else.
I can start all over again and see if I get another result?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
updateall.js
shouldn't be needed, only `add.js
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Damn, I did not read the instructions properly..
I will redo it from scratch, but before we begin I thougt I should test if it works since add.js generates a code with wrong manufacturer ID. So I added firmware in local OTA index and tried with different settings without anything seem to work. I tested added another firmware (for a OTA working device) and by modifying the "file version" it responded with a available upgrade so I know the local index is working.
But, a question, when a device does not show up in the OTA tab of z2m, is that because it does not support OTA at all? Comparing to another supported device from the same vendor I could not se any difference in clusters.
Thanks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's because the definition is missing ota: ota.zigbeeOTA
(example)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I found it.. so I played around a bit and made my own external definition for this model. I have 6 ones that is working perfect, and 5 that is not working as intended.
When I enable OTA i get updates for the ones that is working (without adding the firmware file locally) and no update for the test unit that I want to upgrade..
[14-10-242024 01:16:12] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Testdimmer', payload '{"brightness":254,"linkquality":58,"power_on_behavior":null,"state":"OFF","update":{"installed_version":1,"latest_version":1,"state":"idle"},"update_available":null}'
Old/new version is 1
[14-10-242024 01:16:11] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Soverom master', payload '{"brightness":35,"level_config":{"on_level":53},"linkquality":134,"power_on_behavior":null,"state":"ON","update":{"installed_version":2,"latest_version":4,"state":"available"},"update_available":null}'
The working one is on version 2 and can update to 4.. I have no idea what file that's made available as there should not be a firmware for this in zigbee-OTA and the one I have downloaded from manufacturer is version 2. Any idea?
They seem to be identical except from the date code, all with the latest date code is workin, all with the 2022 datecode is failing (does not report back status when using the dimmer wheel, at least for ZHA, since they did not work I replaced them so the test unit does not have a load connected, was trying to make them work.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
{ "fileVersion": 4, "fileSize": 286646, "manufacturerCode": 4714, "imageType": 1000, "sha512": "9b7835e32ef5af35385710332838099c5dce99a398ae04a1a769d67935fb0752ca4da58892f13bc842cbf8f9ae20516142fe9b66eff3e8ebef6577a71a1d9b0b", "url": "https://github.com/Koenkk/zigbee-OTA/raw/master/images/EcoDim/ZB21S3_HZC_Dimmer1_EcoDim-Zigbee%203.0_1.01_20230908.ota", "path": "images/EcoDim/ZB21S3_HZC_Dimmer1_EcoDim-Zigbee 3.0_1.01_20230908.ota" },
Could maybe be this one.. 1 of 3 with fileVersion 4 in the index. It's placed under EcoDim just as the file I uploaded. I would love to try updating one but I'm afraid I'll destroy one that's working so best to leave it...
Added FW file for Namron dimmer. Should been under Namron, not EcoDim - or both?
Changes related to Jennic/Osram was initiated by the script.