-
Notifications
You must be signed in to change notification settings - Fork 682
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
[Device Support Request] ZLinky_TIC (French Linky electricity meter) #1146
Comments
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. |
Still waiting on firmware update to unblock PR #1165 |
Hello, |
FYI, there is some news about new quirk code for ZHA Device Handlers now as well as a new firmware needed for it, see -> #1165 fairecasoimeme as the manufacturer of ZLinky_TIC has also posted there mentioning that he released new pre-release (beta) Zigbee firmware for this device which is supposed to fix or address at least some of the issues seen in ZHA, so guess they are looking for experienced ZHA Zigbee users to test it, see: Originally posted by @fairecasoimeme in #1165 (comment)
|
FYI, you still need to manually update ZLinky TIC firmware but at least quirk code has now been merged into ZHA Device Handlers: Another problem with Lixee ZLinky TIC needing firmware update now instead really becomes a user experience problem as now the first impression without a such Zigbee OTA Provider code firmware for ZLinky TIC is that it can not be updated automatically with the ZHA integration so users who can pair/join it will still not be able to use it until they manually updated the firmware on ZLinky TIC via other means. Would now be great if someone with the necessary skills and interest would consider submitting a pull request to zigpy with ZLinky TIC Zigbee OTA Provider code now that ZHA Device Handlers support for your Lixee ZLinky TIC has now been merged into the zha-quirks package that will likely be added around the time that the next upcoming major Home Assistant core version is released. See details in related feature request for zigpy which is Zigbee library Home Assistant ZHA depends on -> zigpy/zigpy#1060 |
Sorry, but I think it's not a ZLinky problem but a zigpy-zigate problem. I think you can update ZLinky with OTA with other compatible coordinator than ZiGate. |
I guess @Hedda means adding Lixee to the list of OTA supported manufacturers here: https://www.home-assistant.io/integrations/zha/#ota-firmware-updates In the mean time, people can use @mdeweerd's excellent https://github.com/mdeweerd/zha-toolkit to download OTA updates from Koenkk/zigbee-OTA and install them automatically without having to manipulate file by hand. One issue that needs to be addressed in 100% automated mode is how to select the router / non-router OTA firmware. |
OK, |
Yes, for that in practice zigpy needs to get a downloader code as an LiXee/ZLinky firmware Zigbee OTA provider added to it here: https://github.com/zigpy/zigpy/blob/dev/zigpy/ota/provider.py I do not think you need to change anything in the zigpy-zigate radio library code as the OTA provided is only in the zigpy code: https://github.com/zigpy/zigpy/blob/dev/zigpy/ota/ Anyway, ZHA only supports automatic OTA firmware update for Zigbee OTA providers that is available in the zigpy code there. See: zigpy library is the Zigbee framework library that the ZHA integration component that Home Assistant core depends on, and Home Assistant is not alone in depending on it as zigpy is partially also used by Jeedom Zigbee Plugin and Domoticz Zigbee Plugin (which I believe both are also very popular in France). https://www.home-assistant.io/integrations/zha https://www.domoticz.com/wiki/ZigbeeForDomoticz https://doc.jeedom.com/en_US/plugins/automation%20protocol/zigbee/ So there is a very large userbase of Zigbee users that is indirectly using the zigpy library and by default only get its OTA providers. PS: It is believed that ZHA userbase alone is now over 150,000 users so that might motivate manufacturers to add OTA providers: |
@fairecasoimeme Regarding managing router or non-router firmware; could you not make unified firmware that is configurable remotely by modifying the custom ZHA Device Handler (quirk) for ZHA or custom zigbee-herdsman converter for Zigbee2MQTT? I do not know much about Zigbee application firmware development but read that for example, the "premium version" of PTVO Zigbee Configurable Firmware is configurable so that you can control the RF transmit power output dBm as "signal level " remotely in run-time, see an explanation of that feature here with instruction on how to use change that signal level "remotely via a custom converter (a.k.a. quirk) for Zigbee2MQTT -> https://ptvo.info/zigbee-configurable-firmware-features/rf-signal-level-control/ |
not possible because non router and router mode have differents flash structures. :( |
Rather than updating ZHA specific settings, I still strongly believe that it is better to maintain a central open list such as Koenkk/zigbee-OTA. Maybe that list does need some extra info such as:
Regarding ZLinky: I think it should create two "models" so that the versions and updates apply to only one "branch" of the software versions. Which implies that in the future the end user should be able to choose an apparently not compatible FW update for his device. |
Interesting ideas but such new zigpy OTA feature ideas probably instead belong in a more general zigpy discussion about OTA features and functions so therefor suggest starting a new discussion about that here -> https://github.com/zigpy/zigpy/discussions Or alternatively, if the ideas are specifically related to Zigbee OTA for fairecasoimeme ZLinky TIC device then in that existing zigpy feature request here -> zigpy/zigpy#1060 There is also an existing feature request for zigpy that is specifically about getting OTA files from Koenkk/zigbee-OTA repository here -> zigpy/zigpy#535 |
@fairecasoimeme May I suggest that you re-post that comment as reply to that zigpy feature request here -> zigpy/zigpy#1060 |
I was "reminding" my view because of the comment:
|
Please also see the related discussion in zigbee-herdsman-converters repo which have the same OTA firmware image selection dilemma with there being two firmware with the same "Zigbee Device Signature" -> Koenkk/zigbee-herdsman-converters#4785 |
Is your feature request related to a problem? Please describe.
Add support for ZLinky_TIC, an add-on to transmit all data from the French Linky electricity meter.
Firmware for this device is open source, and clusters are documented at https://github.com/fairecasoimeme/Zlinky_TIC
Describe the solution you'd like
I'd like to be able to query the manufacturer specific cluster attributes:
Device signature
Additional context
Device is distributed directly by its independent French manufacturer at https://lixee.fr/produits/37-zigate-usb-ttl-3770014375148.html
The text was updated successfully, but these errors were encountered: