Ember driver warings #22516
Comments
|
Same to me. Also random devices emit intermittently the following: BTW, it's annoying that the device address is in base-10 on these messages but hex in UI. Many to one for me seems to be related to network scan. I have the same versions and same zb-stick as @major328 |
|
Zigbee2MQTT version [1.37.0] Network By device type
By vendor
By model
after switching to ember, I have a lot of messages of this type in the logs: I also noticed that the stability of the network has become worse, the reaction time is longer. |
This all began when I changed from ezsp to ember. I started noticing this error after my Tuya Smart plug (with power monitoring by polling) stopped reporting power. Instead of showing any values, anything related to power (Power, Current, Voltage, Energy) shows "N/A" in zb2mqtt. However, the other functions, such as on/off state, power outage memory and indicator mode for said plug in zb2mqtt worked fine. I could remotely control the plug, but there was no power monitoring. After removing and attempting to readd the smart plug to my network, the ROUTE_ERROR_MANY_TO_ONE_ROUTE_FAILURE appeared, although the plug got added to my zb network just fine, leading me to believe it has something to do with the smart plug. I attempted to troubleshoot by removing the smartplug, then instead of permit join all, i selected routers that were closer to the smart plug. I started getting another error that the device was blacklisted. Then I took the smart plug, moved it closer to my coordinator and permit join on the coordinator only. The ROUTE_ERROR_MANY_TO_ONE_ROUTE_FAILURE appeared, the smart plug joined my network and the power values still show N/A. I switched back to ezsp. The errors stopped appearing, and my smartplug now works normally with the power reporting values instead of N/A. I conclude that ember has some kind of compatibility issue with this smartplug. Zigbee Model |
|
|
|
@thewan056 Can you open a new issue for that device with missing power monitoring and provide a |
Nerivec
added
ember
In my network of 39 switches, temperature sensors, smoke alarms and some end-device-switches, I've now used Ember for 24 hours and it seems to work better than ezsp ever did and all devices are reachable and they seem to work. I see 2900 ROUTE_ERROR_SOURCE_ROUTE_FAILURE messages in the log for 26 different devices. They seem to occur in bursts of 3 to 6 messages all for same device. Each burst takes a second or two and the bursts take place every couple minutes. |
|
The majority of the messages are for random end device sensors like TS0201 but also router devices like TS011F_plug_1 are there. The odd one for ZBMINIL2 end-device single wire relay also occurs. |
|
@rinne Do you have the complete log file for those ~24h? I'll take a look, see if I can spot something. |
|
Same problem, I updated to the ember driver, flashed the ncp-uart-hw-v7.4.1.0-zbdonglee-115200 firmware (because in my case if I use subsequent zigbee2mqtt firmware it doesn't start at all). With normal ezsp driver, no problem, except the warnings to update the driver to ember |
Indeed I have. |
|
Just to be clear: Network/route errors are not necessarily a "problem". They happened with @rinne Your network relies heavily on Tuya routers, which are know to be subpar in a lot of cases. Maybe try to add a "good" router next time you need a new device. If you want recommendations, check the zigbee2mqtt discord. Definitely avoid Aqara though. |
But they have so nice form factor and cost next to nothing. I do see your point though :). |
@Nerivec any chance to change the device id in the log to hex? (or add hex in addition to decimal) |
|
I will try to find time to reproduce this because this involves making my parents house zigbee network "unreliable" temporarily so that I can get logs. At that time I was just thinking of making the network stable again (it was being less responsive than usual) so the only thing on my mind back then was getting back to normal first. Also for those that criticize me and others buying tuya or tuya based products rebranded by others, we have no choice. For example the smart plug socket stated above. Unlike US or EU plug sockets, UK plug sockets for zigbee are really hard to find. On top of that where we live, the only other options for zigbee UK plug sockets besides tuya and tuya rebrands are Sonoff and Ikea. Both Sonoff and Ikea plugs have impractical shape and size to fit in to certain areas of the house. And the Sonoff in particular is known to be not reliable and lacking functionality like restoring state after a power outage. And yes I have both Ikea and Sonoff sockets so I know their advantages and disadvantages first hand. Many other smart products that are zigbee based only tuya and their rebrands exist in our market, both locally and online internationally. As a 3rd world developing country, we can only hope that we get the newer versions of products, like the newer ikea socket that has a more compact shape, that may or may never reach our shores. So we have no choice and make do with what we have. If we encounter problems we report them and if it is not fixable, then fine. We are not complaining, thats just the reality we live with. |
|
Router: SLZB-06M Updated to latest driver which switches from EZSP to ember |
|
@RaceNJason Please create a new issue and provide a debug log of the pairing process with ember. I'm closing this to avoid unrelated issues getting lost in this "generic" thread. |
What happened?
After switched to ember driver I got this messages:
"[2024-05-04 20:51:28] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_MANY_TO_ONE_ROUTE_FAILURE for "14594".
[2024-05-04 20:51:43] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_MANY_TO_ONE_ROUTE_FAILURE for "17127"."
What did you expect to happen?
information how to fix this
How to reproduce it (minimal and precise)
switched from ezsp to ember driver
Zigbee2MQTT version
1.37.0
Adapter firmware version
7.4.1.0 build 0
Adapter
Sonoff ZBDongle-E
Setup
Add-on on HomeAssistant
Debug log
No response
The text was updated successfully, but these errors were encountered: