-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
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 |
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. |
Yep same issue after updating to Ember |
same here |
Impacted as well
|
Same issue here after migrating to ember from ezsp. |
Another affected over here - |
How can we figure out which device is "41954"? ROUTE_ERROR_MANY_TO_ONE_ROUTE_FAILURE for "41954". |
Same issue here, using |
Convert 41954 to hexadecimal (A3E2) and then search for it in your IEEE Address list in the devices page of your Zigbee2MQTT installation |
Same issue, disappointing to see thread is closed |
FYI / PSA: Two months ago, they released firmware version 7.4.3. I personally updated to this, and the ROUTE_ERROR_MANY_TO_ONE_ROUTE_FAILURE has gone away. I suggest giving this a try while backing up your existing setup. |
Try monitoring your logs longer. It does seem to reduce it abit, but sit there longer at the zb2mqtt page and it comes back |
Has anyone resolved this issue? I cannot connect ledvance light bulb after forced delete, it joined z2m, but interview failed. Is there anything I can try? Already turned on and off the addon and ha, tried switching sonoff dongle-e firmware to previous releases and even going back to ezsp, but nothing seems to work. I’m thinking about uninstaling z2m addon and repairing every device again, but I’m afraid that it would just brake other devices…. |
Your issue seems to be unrelated to this topic. Just keep retrying, I had a similar issue months ago with a Philips Hue lightbulb. Make sure to try to reset the bulb itself as well. Might help you! |
I'm actually running 7.4.3 and experiencing these issues. I ran Hope it helps for anyone else as well. So, in summary: |
Thanks! Unfortunately it didn't work. I bought another zigbee device and after pairing it I could finally pair the broken one! |
What does this have to do with the Z2M? |
Same error but trying to update some Hue Ambiance Lightstrips when trying to update via OTA:
I'm on ember also, Dongle-E, 7.4.3 |
HA yellow, same issue here. according to my latest debuging, Affected devices: |
since i removed the lonsoho (tuya) ledstripe drivers i did not recieve the issue anymore. took a few hours for the devices to reroute before the issue stopped appearing did only affect this lonsoho rgb zigbee led stripe controllers, not the identical looking "YSRSAI mini Dimmer" https://www.zigbee2mqtt.io/supported-devices/#v=YSRSAI) therefore i guess it has to do with the rgb part of the converter |
Same here: EmberZNet 7.4.1 [GA] End devices: 86 |
From yesterday to today 4 ZBMINI-L2 stopped communicating. I can see them
on the devices list, but I receive "ROUTE_ERROR_SOURCE_ROUTE_FAILURE"
messages. All others are OK. I did nothing around z2m or zigbee, there was
only a restart of the whole system due to a HACS thermostat integration
update.
CoderJoeyMoment ***@***.***> ezt írta (időpont: 2024. okt.
6., V, 16:08):
… Same here:
EmberZNet 7.4.1 [GA]
slzb-06m
End devices: 86
Router: 43
—
Reply to this email directly, view it on GitHub
<#22516 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALN3C2WJJAMWJ77WSEINMKTZ2E763AVCNFSM6AAAAABHKKVYNOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJVGQ2TIMRSGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Sounds like they routed using one out of the 5 and since it broke, others didn't catch up connectivity from some other source.
Is it possible that there are not many other router (ac powered) zb devices around?
________________________________
From: major328 ***@***.***>
Sent: Monday, October 7, 2024 8:56:02 AM
To: Koenkk/zigbee2mqtt ***@***.***>
Cc: senna1992 ***@***.***>; Comment ***@***.***>
Subject: Re: [Koenkk/zigbee2mqtt] Ember driver warings (Issue #22516)
From yesterday to today 4 ZBMINI-L2 stopped communicating. I can see them
on the devices list, but I receive "ROUTE_ERROR_SOURCE_ROUTE_FAILURE"
messages. All others are OK. I did nothing around z2m or zigbee, there was
only a restart of the whole system due to a HACS thermostat integration
update.
CoderJoeyMoment ***@***.***> ezt írta (időpont: 2024. okt.
6., V, 16:08):
Same here:
EmberZNet 7.4.1 [GA]
slzb-06m
End devices: 86
Router: 43
—
Reply to this email directly, view it on GitHub
<#22516 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALN3C2WJJAMWJ77WSEINMKTZ2E763AVCNFSM6AAAAABHKKVYNOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJVGQ2TIMRSGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
—
Reply to this email directly, view it on GitHub<#22516 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BDT5STZABF3VGONFBQILY2LZ2IWAFAVCNFSM6AAAAABHKKVYNOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJWGA3DANJRGA>.
You are receiving this because you commented.Message ID: ***@***.***>
|
around these units (means inside the garage where these units are
installed) I have 2 other AC powered routers working properly. One ZBMINI
and one Xiaomi Zigbee plug, and near I have other 2 ZBMINIs. This lost
group was seen by Z2M 12 hours before, which is the time when I restarted
the HomeAssistant.
senna1992 ***@***.***> ezt írta (időpont: 2024. okt. 7., H,
9:02):
… Sounds like they routed using one out of the 5 and since it broke, others
didn't catch up connectivity from some other source.
Is it possible that there are not many other router (ac powered) zb
devices around?
________________________________
From: major328 ***@***.***>
Sent: Monday, October 7, 2024 8:56:02 AM
To: Koenkk/zigbee2mqtt ***@***.***>
Cc: senna1992 ***@***.***>; Comment ***@***.***>
Subject: Re: [Koenkk/zigbee2mqtt] Ember driver warings (Issue #22516)
From yesterday to today 4 ZBMINI-L2 stopped communicating. I can see them
on the devices list, but I receive "ROUTE_ERROR_SOURCE_ROUTE_FAILURE"
messages. All others are OK. I did nothing around z2m or zigbee, there was
only a restart of the whole system due to a HACS thermostat integration
update.
CoderJoeyMoment ***@***.***> ezt írta (időpont: 2024. okt.
6., V, 16:08):
> Same here:
>
> EmberZNet 7.4.1 [GA]
> slzb-06m
>
> End devices: 86
> Router: 43
>
> —
> Reply to this email directly, view it on GitHub
> <
#22516 (comment)>,
> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/ALN3C2WJJAMWJ77WSEINMKTZ2E763AVCNFSM6AAAAABHKKVYNOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJVGQ2TIMRSGE>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
—
Reply to this email directly, view it on GitHub<
#22516 (comment)>,
or unsubscribe<
https://github.com/notifications/unsubscribe-auth/BDT5STZABF3VGONFBQILY2LZ2IWAFAVCNFSM6AAAAABHKKVYNOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJWGA3DANJRGA>.
You are receiving this because you commented.Message ID: ***@***.***>
—
Reply to this email directly, view it on GitHub
<#22516 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALN3C2S6AIAHK3Q6BCDT4D3Z2IWY5AVCNFSM6AAAAABHKKVYNOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJWGA3TQMBQGY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
But as I know these units has no routing functionality. ZBMINI-L2 is only
an phase powered switch, not a router , but maybe I'm wrong.
senna1992 ***@***.***> ezt írta (időpont: 2024. okt. 7., H,
9:02):
… Sounds like they routed using one out of the 5 and since it broke, others
didn't catch up connectivity from some other source.
Is it possible that there are not many other router (ac powered) zb
devices around?
________________________________
From: major328 ***@***.***>
Sent: Monday, October 7, 2024 8:56:02 AM
To: Koenkk/zigbee2mqtt ***@***.***>
Cc: senna1992 ***@***.***>; Comment ***@***.***>
Subject: Re: [Koenkk/zigbee2mqtt] Ember driver warings (Issue #22516)
From yesterday to today 4 ZBMINI-L2 stopped communicating. I can see them
on the devices list, but I receive "ROUTE_ERROR_SOURCE_ROUTE_FAILURE"
messages. All others are OK. I did nothing around z2m or zigbee, there was
only a restart of the whole system due to a HACS thermostat integration
update.
CoderJoeyMoment ***@***.***> ezt írta (időpont: 2024. okt.
6., V, 16:08):
> Same here:
>
> EmberZNet 7.4.1 [GA]
> slzb-06m
>
> End devices: 86
> Router: 43
>
> —
> Reply to this email directly, view it on GitHub
> <
#22516 (comment)>,
> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/ALN3C2WJJAMWJ77WSEINMKTZ2E763AVCNFSM6AAAAABHKKVYNOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJVGQ2TIMRSGE>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
—
Reply to this email directly, view it on GitHub<
#22516 (comment)>,
or unsubscribe<
https://github.com/notifications/unsubscribe-auth/BDT5STZABF3VGONFBQILY2LZ2IWAFAVCNFSM6AAAAABHKKVYNOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJWGA3DANJRGA>.
You are receiving this because you commented.Message ID: ***@***.***>
—
Reply to this email directly, view it on GitHub
<#22516 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALN3C2S6AIAHK3Q6BCDT4D3Z2IWY5AVCNFSM6AAAAABHKKVYNOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJWGA3TQMBQGY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I've switched off the AC power and after a half minute switched on and all
are communicating again
Major Ákos ***@***.***> ezt írta (időpont: 2024. okt. 7., H, 9:12):
… But as I know these units has no routing functionality. ZBMINI-L2 is only
an phase powered switch, not a router , but maybe I'm wrong.
senna1992 ***@***.***> ezt írta (időpont: 2024. okt. 7., H,
9:02):
> Sounds like they routed using one out of the 5 and since it broke, others
> didn't catch up connectivity from some other source.
>
>
> Is it possible that there are not many other router (ac powered) zb
> devices around?
>
>
>
>
> ________________________________
> From: major328 ***@***.***>
> Sent: Monday, October 7, 2024 8:56:02 AM
> To: Koenkk/zigbee2mqtt ***@***.***>
> Cc: senna1992 ***@***.***>; Comment ***@***.***>
> Subject: Re: [Koenkk/zigbee2mqtt] Ember driver warings (Issue #22516)
>
>
> From yesterday to today 4 ZBMINI-L2 stopped communicating. I can see them
> on the devices list, but I receive "ROUTE_ERROR_SOURCE_ROUTE_FAILURE"
> messages. All others are OK. I did nothing around z2m or zigbee, there
> was
> only a restart of the whole system due to a HACS thermostat integration
> update.
>
> CoderJoeyMoment ***@***.***> ezt írta (időpont: 2024. okt.
> 6., V, 16:08):
>
> > Same here:
> >
> > EmberZNet 7.4.1 [GA]
> > slzb-06m
> >
> > End devices: 86
> > Router: 43
> >
> > —
> > Reply to this email directly, view it on GitHub
> > <
> #22516 (comment)>,
>
> > or unsubscribe
> > <
> https://github.com/notifications/unsubscribe-auth/ALN3C2WJJAMWJ77WSEINMKTZ2E763AVCNFSM6AAAAABHKKVYNOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJVGQ2TIMRSGE>
>
> > .
> > You are receiving this because you were mentioned.Message ID:
> > ***@***.***>
> >
>
> —
> Reply to this email directly, view it on GitHub<
> #22516 (comment)>,
> or unsubscribe<
> https://github.com/notifications/unsubscribe-auth/BDT5STZABF3VGONFBQILY2LZ2IWAFAVCNFSM6AAAAABHKKVYNOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJWGA3DANJRGA>.
>
> You are receiving this because you commented.Message ID: ***@***.***>
>
> —
> Reply to this email directly, view it on GitHub
> <#22516 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ALN3C2S6AIAHK3Q6BCDT4D3Z2IWY5AVCNFSM6AAAAABHKKVYNOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJWGA3TQMBQGY>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
|
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: