-
Notifications
You must be signed in to change notification settings - Fork 299
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
ZiGate implementation #242
Comments
Does #241 and Koenkk/zigbee2mqtt#4737 being merged mean that zigbee-herdsman and zigbee2mqtt now works with all modules with ZiGate firmware including original ones from https://zigate.fr by the @fairecasoimeme project from Frédéric Dubois? Do not own a ZiGate or other NXP Zigbee coordinator myself but know it is supported by ZHA for Home Assistant via zigpy-zigate Known working Zigbee radio modules
|
Also related to #150 |
These changes are all available in Zigbee2MQTT 1.16.0 but it's unclear for me how stable it is. |
Update supported adapters with ZiGate USB-TTL. Experimental as per Koenkk/zigbee-herdsman#242
* Update supported adapters with ZiGate USB-TTL Update supported adapters with ZiGate USB-TTL. Experimental as per Koenkk/zigbee-herdsman#242 * Update supported adapters with ZiGate USB-TTL * Mention ZiGate USB-TTL hardware specification Mention ZiGate USB-TTL hardware specification * Update supported_adapters.md Co-authored-by: Koen Kanters <koenkanters94@gmail.com>
FYI, Koenkk/zigbee2mqtt.io#474 has updated Zigbee2MQTT website documentation to list ZiGate USB-TTL as a supported adapter: PS: Other ZiGate adapters not yet listed there, include ZiGate USB-DIN, PiZiGate, and ZiGate WiFi Pack -> https://zigate.fr/boutique/ Thanks and headsup to @fairecasoimeme @G1K @kirovilya @devbis @lenz |
Hi everybody, I'm trying to add my PiZiGate to Zigbee2MQTT, but i have errors:
This is my configuration.yaml:
I use docker-compose:
/dev/ttyS0 is working, i used it before with ZHA in HA. Thanks ! |
Hey @Kalypox Does the baudrate for your zigate adapter is equal to the one in herdsman? You should try to set the baudrate in the config file. The second approach is to upgrade the firmware. It heavily relies on the raw Zigbee mode that is under development since 3.1c. |
Hi @devbis,
Have a nice day ! |
Note! ZiGate 3.1d firmware or later is recommended for all ZiGate hardware is it contains an important bug-fix https://zigate.fr/tag/firmware/ https://zigate.fr/2020/10/12/maj-firmware-zigate-version-3-1d/ Also updated docs recommend upgrading to ZiGate Zigbee coordinator firmware version 3.1d or later: https://www.zigbee2mqtt.io/information/supported_adapters.html |
Added Roadmap to start post Described current problems in #252 (comment) related to #285 |
Most of the points from the roadmap are closed, but there is a problem with the stability of the module firmware when using raw mode in both directions. Perhaps they will be resolved, but for now I recommend trying to work with the firmware from this repository. And it supports advanced logging, which can help in finalizing the adapter |
I do not have devices to check OTA, but in the sniffer, I see the correct communication that there is no update for the device. If anyone tests please write here. |
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 |
The latest improvements from the end of January are available in the 1.18 release |
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 |
@Koenkk Maybe re-open this issue for tracking and leave open even if no activity as ZiGate support is still listed as experimental? |
hmm, why does github-actions bot close this? |
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 |
Maybe permanently remove the stale label somehow? |
Most likely, you need to add the closing issue exempt-issue-labels to the action settings, specify a list of labels in it that do not need to be marked as obsolete. and for issue to use such a label https://github.com/actions/stale#exempt-issue-labels zigbee-herdsman/.github/workflows/stale.yml Lines 11 to 18 in ff26225
|
@Koenkk Maybe add dont-stale label to this issue as well as it should probably also be keep open for the same reason as EZSP? https://github.com/Koenkk/zigbee-herdsman/issues?q=is%3Aissue+is%3Aopen+label%3Adont-stale |
Could you clarify which firmware should be use on a ZiGate V1 to act as a coordinator |
@pipiche38 But Zigate V1 firmware has seemed to be corrected and work as it should. The only problem that strongly interferes is the absence of PDM backup and periodically the chip reports that after rebooting it is Factory reseted In the firmware Realized raw PDM backup memory of NXP JN516x zigbee chip and recovery. Those who wish can try. |
I'll put it on my todo list, this looks promising and could be a good alternative to the zigate firmware |
Does anyone have any more updates or news on the backup and restore features for the zigate adapter in zigbee-herdsman? PS: This question is directly related to this discussion about Z2M migration across Zigbee stacks -> Koenkk/zigbee2mqtt#16478 |
Discussion of the implementation of a new adapter based on the NXP chip JN516x ( JN5168 / JN5169 )
#241
What you can try as a coordinator
Xiaomi gateway DGNWG05LM, ZHWG11LM
End devices from xiaomi JN5169 https://github.com/Jerome-PS/JN516xSniffer
Ready modules https://www.seeedstudio.com/Mesh-Bee-Open-Source-Zigbee-Pro-Module-with-MCU-JN516-p-1751.html
DIY module + TTL adapter
E75-2G4M10S Zigbee JN5169 aliexpress.com/item/32973411720.html
Road map
supported GP - (requires stable firmware with GreenPower support and 242 endpoint ) What is being assembled now limits the resources of the APDU or does not start after the firmwareIf you have the opportunity, please join the development and testing. I don't have much development experience especially with uart and ZiGate
Perhaps this will solve the requests
Koenkk/zigbee2mqtt#743
Koenkk/zigbee2mqtt#409
The text was updated successfully, but these errors were encountered: