New Edge not starting anymore with ezsp 7.4.0 #20827
Comments
|
|
The version from 13.1 is working without problems. |
Nerivec
added a commit
to Nerivec/zigbee-herdsman
that referenced
this issue
Jan 15, 2024
|
I unfortunately don't have test equipment at the moment... |
|
@Nerivec otherwise i will restore the backup from yesterday because right now z2m isn’t usable for me and with the edge version I can’t back. (Need the edge version because auf the 7.4.0 firmware) |
|
If you haven't deleted the old latest-dev image: |
Koenkk
pushed a commit
to Koenkk/zigbee-herdsman
that referenced
this issue
Jan 16, 2024
|
Should be fixed now! Changes will be available in the dev branch in a few hours from now. |
|
Ok updated it and now it seem to work. |
|
@Nerivec For example: |
|
@wastez thats not because of the EZSP adapter, seems the device just doesn't respond. |
|
Yes but since this changes I have it with every device. |
|
@wastez looks like an issue in the EZSP firmware, did you already try downgrading it? |
|
Yes could be and of course I could downgrade. |
|
Here much more about it: |
|
But looks it only happens after a fresh start of z2m |
|
Can you capture one with herdsman debug ON? |
|
Ok here it is: |
|
Can you include the stuff before |
|
Do you search for that: |
|
I'm looking for the lines like you had in your first log, |
|
Sorry less cuted it: |
|
@kirovilya Could this be a side-effect of the removal of https://docs.silabs.com/d/zigbee-stack-api/7.4.0/message#ember-incoming-route-error-handler
If I understand this correctly, the default timeout starts at 3sec, and can increase up to 30s, so after having failed a few times, the timeout has increased internally on its own, and it stops failing, which would explain the reported behavior (on start)... |
|
@Nerivec I'm not sure if this is the reason, but anything is possible. if these commands are sent to a sleeping sensor, then of course they will not reach - you need to wake up the sensor |
|
@kirovilya |
|
@kirovilya |
|
@wastez "Failed to configure" - means that the device has not yet been configured (perhaps it was not configured when the device was added) - which means it needs to be woken up for configuration. |
|
@kirovilya |
|
@wastez One of the possible reasons is that previously this device did not have a “configure” code, but now it does, and therefore it needs to be executed. |
|
@kirovilya |
|
@wastez I don’t know why this happened... try waking up one of the sensors and performing configuration (you can force the button at the bottom of the sensor page) - the error for this sensor should disappear. |
|
@kirovilya |
|
@wastez Just a side note from what I read over time since you mentioned them: |
|
Hmmmmmm.... |
|
I have the same issue... does not start on boot... using a RESTART and it then works.. I am using EDGE (23/11/2024) on HA and the latest ezsp multiprotocol. This is a new install with No sensors attached yet.
|
|
@RichardPar do you have any more logs (try starting with herdsman debug ON)? This config ID assertion is not an issue per say, it's just not supported anymore, the code needs cleanup; anyway, it does not prevent startup. |
It hangs after a boot at this point.. it however starts when I do a RESTART. I will add Herdsmen debug this evening (when I get home in an hour) ''[16:26:15] INFO: Preparing to start... |
|
"Assertion failed" - not a critical situation for ezsp adapter. I can hide them or put them in debug logs. |
|
It's good to have them as |
|
It hangs on Boot :D There has to be a race condition with something else.. but to clarify - it does not start at all on first boot..
As to how to enable debug, where would herdsman be set? I added under the Socat stanza - didnt seem to do anything
|
|
Check the |
|
You have to change to yaml edit in the right upper corner. (And not enter it in the socat section) |
|
Its looping |
|
Looks like it can't connect to the port of the multiprotocol addon. Can you access it via telnet? To see if the port is reachable. |
If I click restart on the Z2MQTT plugin, it immidiately connects. Its there and running (as my THREAD devices are online) |
|
Maybee z2m try's connect to early while the multiprotocol addon isn't already up and ready for connections. |
|
Can you check the logs of the silabs addon? You might find some more information there... |
I'll dig for some more debug.. Silabs is listening Z2MQTT looks like its connecting to something.. (below is the same small logs from Silabs Multiprotocol) SiLabs Multiprotocol |
|
Something bring the multiprotocol to crash and restart the port. |
Why when I restart Z2MQTT it all works fine? (Multiprotocol is not restarted) I have reproduced on 3 differenent installs too. |
|
@RichardPar Can you try again once 0.33.2 is available to update and let me know if the behavior is better? If it's an underlaying issue with socket or silabs, of course, that won't fix the problem, but at least Z2M should handle the fail properly now. Well, hopefully anyway... |
Installed and ran+connectesd first time ... I will put it through more paces and see how it purrs. |
|
This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 30 days |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
It doesn’t start anymore.
no error message, just writing „starting“ in the logs.
the gui doesn’t get available.
What did you expect to happen?
No response
How to reproduce it (minimal and precise)
No response
Zigbee2MQTT version
latest edge
Adapter firmware version
7.4.0
Adapter
EZSP Sonoff Dongle E
Setup
Proxmox
Debug log
No response
The text was updated successfully, but these errors were encountered: