OK. Was looking at moving to Z2M but might stick with ZHA if its a higher probability of working with ZigBee and Thread in the future.
I would not recommend updating the ESP firmware or the zigbee chip firmware if you dont have a very specific need to. It was a pain reflashing everything multiple times and after all is said and done my network went from rock solid to having my devices become non responsive in a matter of days or a week and require a restart of the z2m addon or the coordinator itself. I have no idea if I messed something up continously removing and re-installing the board into the case, some part of the flashing or what but there is no current benefit to updating.
please reach out over email or DM if you want to trouble shoot some.
I now am advising against updating to the 20221226 Z-Stack FW just too many issues popping up, even if itās just for a few people, seems more trouble than itās worth right now.
Hey mate,
Trying to get Z2M going, and it starts up and runs fine. but i cannot change the channel at all, or change any of the panID or networkID. Its like its sticking with the old values and not changing. Is that a known issue? Or am i doing something wrong?
I fresh install, change the channel to 25, restart the Z2M container. The logs tell me to delete the backup file, so I do. Then restarting again, i get this:
Blockquote
Zigbee2MQTT:error 2023-02-28 14:35:40: Configuration is not consistent with adapter state/backup!
Zigbee2MQTT:error 2023-02-28 14:35:40: - PAN ID: configured=59907, adapter=6754
Zigbee2MQTT:error 2023-02-28 14:35:40: - Extended PAN ID: configured=00124b00237ba736, adapter=00124b00237ba736
Zigbee2MQTT:error 2023-02-28 14:35:40: - Network Key: configured=f7d44b96b5c8f35deb3fdb9782ada460, adapter=01030507090b0d0f00020406080a0c0d
Zigbee2MQTT:error 2023-02-28 14:35:40: - Channel List: configured=25, adapter=11
Zigbee2MQTT:error 2023-02-28 14:35:40: Please update configuration to prevent further issues.
Zigbee2MQTT:error 2023-02-28 14:35:40: If you wish to re-commission your network, please remove coordinator backup at /config/zigbee2mqtt/coordinator_backup.json.
Zigbee2MQTT:error 2023-02-28 14:35:40: Re-commissioning your network will require re-pairing of all devices!
Zigbee2MQTT:error 2023-02-28 14:35:40: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2023-02-28 14:35:40: Failed to start zigbee
Zigbee2MQTT:error 2023-02-28 14:35:40: Check Zigbee2MQTT fails to start | Zigbee2MQTT for possible solutions
Zigbee2MQTT:error 2023-02-28 14:35:40: Exitingā¦
Zigbee2MQTT:error 2023-02-28 14:35:40: Error: startup failed - configuration-adapter mismatch - see logs above for more information
Here are my Z2M settings:
Hmmm. maybe someone with more z2m knowledge can comment.
If you have deleted the backup json file I believe z2m should start with the new settings, but it is acting like the backup is still there.
If you want to start fresh, wouldnāt it be safer to
- backup your .json and .yaml files somewhere (using SCP, or via SSH)
- delete the add-on
- make sure the /config/zigbee2mqtt folder is deleted
- reinstall the add-on
- make sure the /config/zigbee2mqtt folder is empty
- do the config from scratch
Having a look through some other issues, it looks like I might need to go through and reset the NVRAM.
Iāll have that a go later in the week.
It works fine as long as Iām not trying to change anything from default
I have done all these steps, itās like any previous setting on the ZigBee device are not being overwritten. I see some others in this thread with similar issues, and so Iāll try reset the NVRAM on the gateway to see if that resolves it
the zigpy-znp tools.md has a really good guide for getting it installed on any platform, and commands:
https://github.com/zigpy/zigpy-znp/blob/9b959dcf021b665e02d36d38c9141d31d9824254/TOOLS.md
Just closing the loop on this one - resetting the NVRAM fixed my issue with changing channel. That guide worked perfectly. Did a channel scan and there was 100% interference on channel 25, apparently wifi channel 13 lines up perfectly with zigbee 25, so went with channel 20 instead.
Loving the switch to Z2M. Firmware updates are a breeze, and trigger entities make life so much easier
2 Likes
Hey there,
upgrading my cc2652p2 coordinator did not solve my issue, that z2m is not finding the coordinator from time to time (and then stops the addon).
Although itās reachable through the web GUIā¦
Do you know by any chance the python command to restart the coordinator like the command on the web GUI does?
Thanks!
There should be a restart button with the latest esphome builds exposed in HA under the esphome device. check that itās enabled under the configuration entities on the device page.
Just one thing need to be mentioned here: EFR32MG21 does not support multithread. Means that this chip canāt handle Zigbee and Thread/Matter at the same time. This relates to all EFR32MG21 based devices including well known usb adapters SkyConnect, ZBdongle-E etc.
With the multi pan enabled rcp fw, the efr32 just forwards the data to a daemon on the host -cpcd and it directs the the packets tagged with the thread is to openthread and the packets tagged with zigbee is to zigbeed which is the ncp running on the host.
SI Labs does have an alpha/beta of rcp and ncp running on the efr32 as well.
The multipan rcp support is now a PR in the main openthread repo (again after it was rebased in the si labs branch) I believe this will add multipan support to any radio openthread supports.
I just purchased the TubeZB Zigbee Router/Repeater to increase the footprint of my Zigbee network since none of my mains powered devices have a router function. The new router paired fine with my HA Sonoff Zigbee 3.0 USB Dongle Plus but no devices appeared to route through it. When I moved it to a location that should have been well within range of the coordinator, it appeared offline and I lost control of many of my existing bulbs. They appeared to be online, but I was not able to control them.
Where should I look next?
It takes time. But some end devices wont do it on their own also, so you need to repair them via the repeater. Thatās how it works with my mains powered devices.
Iām expecting my first repeater to be delivered to me today so eagerly awaiting a reduction in red lines on the ZHA visualisation.
1 Like
Thanks Sarg. I left it overnight and it didnāt seem to reconnect to HA (Iām using ZHA), route any devices and the visualization still shows it offline.
Ahh okay yeah that doesnāt seem right.
Iāll be able to compare with you once mine is delivered but iād expect it to be online. My coordinator is a tubez one.
Are you using ZHA or Z2M?
Also what are your mains powered non-routing devices?
if it doesnāt come back online by itās self you can power cycle it.
Iām using ZHA and the bulbs are all Sengled, who has a policy of non routing on devices that can be switched off, like bulbs.
FYI, I tried a SONOFF S40 Lite as a router and it would disconnect from the coordinator after just a few minutes. The Visualization show it online, but never any connecting line.