Closed mospaeda closed 7 months ago
Can you pull up the device, manage clusters > OTA and then under Cluster Attributes > "current_file_version" and do a "Get Zigbee Attribute" and check what that reports?
Detail is as below :
Ota (Endpoint id: 1, Id: 0x0019, Type: out) current_file_version (id: 0x0002) Value : 1
So value is 1
For referece, have you now flashed the "ZLinky_router_v9.0.ota" or the "ZLinky_router_v9.0_no_route.ota" OTA firmware image file?
https://github.com/fairecasoimeme/Zlinky_TIC/releases
Also suggest edit and changing subject title of this issue to refect that this is an issue with LiXee ZLinky_TIC Router v9.0 firmware.
_[BUG] LiXee ZLinky_TIC Router v9.0 firmware version is reported as "Firmware: 0x00000001" in Home Assistant ZHA_
Maybe you should also report as issue to https://github.com/fairecasoimeme/Zlinky_TIC/issues for attention of @fairecasoimeme?
Update: Ah, see that @mospaeda also reported this issue there too -> https://github.com/fairecasoimeme/Zlinky_TIC/issues/115
For record I received the LiXee ZLinky_TIC already with the firmware 9 installed I didn't update the received Zlinky by OTA to version 9
Basic -Endpoint id: 1, Id: 0x0000 - Value is 9 Basic - sw_build_id (id: 0x4000) - Value is 4000-0009 Basic - date_code (id: 0x0006) - Value is 20220930.
For some reason, the OTA - current_file_version is reported as 1
@codyhackw Can you confirm the cluster used for firmware version ?
https://github.com/fairecasoimeme/Zlinky_TIC/issues/115#issuecomment-1286718366
I didn't know that on ZHA the firmware version was related to the OTA cluster For me the version firmware is in Basic not in OTA I'll see to update also the version in OTA cluster That would be fixed in next version ...
I know it uses the OTA cluster with other devices, which is why I asked you to check there. Not certain if that's only the case if/when the OTA cluster is used or how the determination is made though.
Edit - Note that the recommended OTA file version definition is defined Here
Not sure if this can be fixed on the zha-device-handlers or zigpy side without the user updating device firmware?
For reference, the workaround, for now at least, is for the user to update ZLinky TIC v13.0 device firmware (or later)
https://github.com/fairecasoimeme/Zlinky_TIC
https://github.com/fairecasoimeme/Zlinky_TIC/releases/tag/v13.0
https://github.com/fairecasoimeme/Zlinky_TIC/issues
ZLinky TIC v13.0 firmware is supported in the upcoming Home Assistant 2023.3 release as it will have zha-device-handlers v0.0.93:
https://github.com/zigpy/zha-device-handlers/releases/tag/0.0.93
Noted, now I need to find a way to upgrade to firmware version 13+
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Not possible in my case to update to firmware 13. I seem something is missing or not working (Zigate and Zlinky on Home assistant latest version ) Still need to investigate why (and especilally if Zigate can push update)
Not possible in my case to update to firmware 13. I seem something is missing or not working (Zigate and Zlinky on Home assistant latest version ) Still need to investigate why (and especilally if Zigate can push update)
I do not own one but believe that there are two types of firmware variants with different modes from them and you can only perform Zigbee OTA update if the mode of the OTA file is the same as the previous one.
https://github.com/fairecasoimeme/Zlinky_TIC/blob/master/README.md#ota
That means you can not change flash an image over OTA that has a different mode, so if you want to change mode then you must update the firmware manually by flashing via a TTL Serial to USB adapter or similar, see "Non OTA" section in their readme file:
https://github.com/fairecasoimeme/Zlinky_TIC/blob/master/README.md#non-ota
https://zigate.fr/documentation/mise-a-jour-de-la-zigate-2/
Regardless, suggest that you ask them for help with all firmware upgrade methods issues as that discussion does not really here:
https://github.com/fairecasoimeme/Zlinky_TIC/issues
and/or here:
PS: Off-topic but related, also check out feature request asking for a LiXee ZLinky TIC Zigbee OTA Provider in zigpy (inc. in ZHA);
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Describe the bug In home assistant, the firmware seems reported wrong in the display ZLinky_TIC par LiXee Connecté via [Zigbee Coordinator] Firmware: 0x00000001 I don't know from where the value 0x00000001 is coming but it is probably not pointing to right register
To Reproduce Steps to reproduce the behavior: go the ZHA device page : LiXee ZLinky_TIC look at the firmware version : Firmware: 0x00000001
But From the cluster details it seems that it is different (in my case firmware 9 as I received last week) reference from offcial doc : https://github.com/fairecasoimeme/Zlinky_TIC#clusters
Basic (Endpoint id: 1, Id: 0x0000, Type: in) Valeur 9
sw_build_id (id: 0x4000) 4000-0009 date_code (id: 0x0006) 20220930
Expected behavior Should be Firmware: 0x00000009
Diagnostic information
```yaml Paste the diagnostic information here. Don't remove the extra line breaks outside the ``` marks. ```Additional logs
``` Paste any additional debug logs here. Don't remove the extra line breaks outside the ``` marks. ```Additional context Add any other context about the problem here.