Assertion failed: Command (setConfigurationValue) returned unexpected state: [object Object] #19168
Comments
|
Same "problem" with a Skyconnect Dongle ! |
|
|
|
1.33.1 starts too, I wrote that everything works fine with the only exception of the assertion failed entry in the log |
|
Sometime i have the exception of the assertion and z2m won't start. Then I have to launch z2m in debug mode (1 time). |
|
I also appear to have the same error with the kyconnect Dongle : [22:15:39] INFO: Preparing to start... |
|
UPDATE: now it's randomly happening while the addon is working too, not only in the start phase |
|
Maybe a similar issue here: It should restart automatically but it doesn't. After this, if I restart the container manually, its fine and everything works as expected. I'm using the Zigbee Dongle-E with multipan fw, if I remember correctly 4.3.1 fw version, configuration.yaml relevant part: |
|
Same problem. Is there a way to downgrade addon? |
|
Enabling debug, the error appears to occur when configuring the buffer count to Editing the assertion to be more verbose I got: |
|
Seems to be related to this addon issue |
|
Some news ?
With Skyconnect / Silicon Labs Multiprotocol |
|
[12:17:22] INFO: Preparing to start... |
|
I got this error (for the first time) after upgrade to 1.35.01. my hardware is skyconnect, multipan firmwore on ha supervised/vmware. Reverted to prior version, what worked |
|
@dierochade which version works for you? Here are my thoughts on this:
I'm not sure if this is related with z2m or related with the Zigbee-herdsman library. I don't know how is responsible of the coordinator initialisation in the code. I believe it could be considered a WARNING only. This message shouldn't block the coordinator to work ok at all. |
I have the same hardware and the same configuration (supervised, but on a Khadas) and I already had the problem with previous versions (and it continues with version 1.35). |
OK but I think that in previous versions of Z2M (<1.35) this error message was blocking. |
z2m
I use this firmware too As it works for me at the moment I cannot say anything additional. |
|
Just started seeing this on my side as well with the latest zigbee2mqtt, multipan firmware on a dongle E. |
|
Also facing this bug with SkyConnect and latest upgrade of the Z2M addon... but Z2M don't work anymore. |
|
Same issues here :( |
|
Same issue here with latest zigbee2mqtt version ( 1.35.0-1 ), multipan firmware (2.4.0)on a dongle E. |
|
Same issue with zigbee2mqtt version ( 1.35.0-1 ), multipan firmware (2.4.0)on a dongle E. |
|
I have the same problem now. Sky connect and multiprozocol enabled. |
In my case, I downgrade Silicon Labs Multiprotocol addon from 2.4.0 to 2.3.2 by restoring a backup : addon_core_silabs_multiprotocol_2.3.2 (System > Backup >addon_core_silabs_multiprotocol_2.3.2 >restore) |
|
Same here since this morning. After upgrading HA to the latest version. Edit: Downgrading Silicon Labs Multiprotocol addon from 2.4.0 to 2.3.2 by restoring a backup did the trick! |
Worked also for me. After downgrade und restart of Home assistant it works again. That was an easy fix. Edit: |
Easy fix but one hour without services. All is OK now. |
Yep, same here, commands fail (multipan firmware, E dongle) |
How to downgrade to version 2.3.2, without having to reconfigure everything, when you don't have a backup of the previous version? |
|
countered the same issue and ended up coming here by searching the log. Downgrade the multiprotocol addon did help |
|
I had the same problem a view days ago. You have to downgrade the silicon labs protocol add-on |
|
@noobzilla81 : Don't you read the previous posts before writing something? |
|
Trying to setup z2m today, so I don't have a backup since I just installed it... Any ideas for how to get around this or do I just need to wait for now? |
This might be helpful. But I am not sure if it has flashed incompatible firmware too. So I just moved all Zigbee devices back to their gateway, connecting them to HA again and wait. https://community.home-assistant.io/t/hass-io-api-specify-version-for-add-on-install/144340/6 |
|
Having the same issue here... Please help, I can't get it to work 👎🏻
|
I switched to the Edge version and it works now, thanks for the link though |
|
Hi Folks, I'm new to HA and installed the silicon lab multiprotocol version 2.4.3 (only one available). I have the same issues with s2m. So i dont have a backup and i cant revert/downgrade to version 2.4.3. Log: What can i do? Please help/advise (thnx) |
Install Edge version in add-on store |
@MondoGao : Thank you very much for your response/advice. Keep up da good work! Installing Edge version results in: Log zigbee: Log Silicon: Installation: Zigbee config for serial: Please bear with me |
|
Someone has tested Silicon Labs Multiprotocol version 2.4.4 with Z2M ? |
Same Problem, Z2M doesn't work |
Ok, thanks. |
|
It seems that Z2M 1.35.2-1 fixes the problems with SLM 2.4.4, doesn't it? |
|
Is someone brave enough to try this? |
|
Didn't they reverted back to 2.3.x due to instability of 2.4.4 anyway?
Wysłano z programu Outlook dla systemu Android<https://aka.ms/AAb9ysg>
…________________________________
From: aLimp86 ***@***.***>
Sent: Thursday, February 1, 2024 10:45:56 PM
To: Koenkk/zigbee2mqtt ***@***.***>
Cc: kurdybanek ***@***.***>; Comment ***@***.***>
Subject: Re: [Koenkk/zigbee2mqtt] Assertion failed: Command (setConfigurationValue) returned unexpected state: [object Object] (Issue #19168)
Is someone brave enough to try this?
—
Reply to this email directly, view it on GitHub<#19168 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AZSO56XU4I2U34G7RJJNSADYRQEJJAVCNFSM6AAAAAA5S3O636VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRSGMYDEMBXGE>.
You are receiving this because you commented.Message ID: ***@***.***>
|
|
I don't know - I simply gave up and am waiting for this Z2M bug to be fixed. In the meantime, I've gotten used to restarting z2m as soon as everything freezes. I made a serious mistake switching to the Silabs dongle, but now I'm too lazy to reconnect everything. |
The problem doesn't seem to be the dongle but the firmware that enables multiprotocol. I think that with the simple Zigbee firmware, it's more stable. But I'm also fed up of having to reassociate everything (some of my devices aren't very accessible, for example in the post of my electric gate...). |
|
For me it works pretty stable after the fixed version of silabs multiprotocol was released. I noticed some delays in operation from time to time for several devices (mostly those which are at the edge of the range,so it doesn't have to be firmware related), but nothing like at total freeze
Wysłano z programu Outlook dla systemu Android<https://aka.ms/AAb9ysg>
…________________________________
From: merlinpimpim ***@***.***>
Sent: Friday, February 2, 2024 11:36:32 AM
To: Koenkk/zigbee2mqtt ***@***.***>
Cc: kurdybanek ***@***.***>; Comment ***@***.***>
Subject: Re: [Koenkk/zigbee2mqtt] Assertion failed: Command (setConfigurationValue) returned unexpected state: [object Object] (Issue #19168)
I don't know - I simply gave up and am waiting for this Z2M bug to be fixed. In the meantime, I've gotten used to restarting z2m as soon as everything freezes. I made a serious mistake switching to the Silabs dongle, but now I'm too lazy to reconnect everything.
The problem doesn't seem to be the dongle but the firmware that enables multiprotocol. I think that with the simple Zigbee firmware, it's more stable. But I'm also fed up of having to reassociate everything (some of my devices aren't very accessible, for example in the post of my electric gate...).
—
Reply to this email directly, view it on GitHub<#19168 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AZSO56WQ25FRLCXNKGYNIJTYRS6TBAVCNFSM6AAAAAA5S3O636VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRTGUZTCNBWGE>.
You are receiving this because you commented.Message ID: ***@***.***>
|
Are you talking about version 2.4.4? |
|
Yes, 2.4.4 of silabs multiprotocol and 1.35.1 (yesterday upgraded to 1.35.2) of Z2MQTT
Wysłano z programu Outlook dla systemu Android<https://aka.ms/AAb9ysg>
…________________________________
From: merlinpimpim ***@***.***>
Sent: Friday, February 2, 2024 11:47:07 AM
To: Koenkk/zigbee2mqtt ***@***.***>
Cc: kurdybanek ***@***.***>; Comment ***@***.***>
Subject: Re: [Koenkk/zigbee2mqtt] Assertion failed: Command (setConfigurationValue) returned unexpected state: [object Object] (Issue #19168)
For me it works pretty stable after the fixed version of silabs multiprotocol was released. I noticed some delays in operation from time to time for several devices (mostly those which are at the edge of the range,so it doesn't have to be firmware related), but nothing like at total freeze Wysłano z programu Outlook dla systemu Androidhttps://aka.ms/AAb9ysg
…
________________________________ From: merlinpimpim @.> Sent: Friday, February 2, 2024 11:36:32 AM To: Koenkk/zigbee2mqtt @.> Cc: kurdybanek @.>; Comment @.> Subject: Re: [Koenkk/zigbee2mqtt] Assertion failed: Command (setConfigurationValue) returned unexpected state: [object Object] (Issue #19168<#19168>) I don't know - I simply gave up and am waiting for this Z2M bug to be fixed. In the meantime, I've gotten used to restarting z2m as soon as everything freezes. I made a serious mistake switching to the Silabs dongle, but now I'm too lazy to reconnect everything. The problem doesn't seem to be the dongle but the firmware that enables multiprotocol. I think that with the simple Zigbee firmware, it's more stable. But I'm also fed up of having to reassociate everything (some of my devices aren't very accessible, for example in the post of my electric gate...). — Reply to this email directly, view it on GitHub<#19168 (comment)<#19168 (comment)>>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AZSO56WQ25FRLCXNKGYNIJTYRS6TBAVCNFSM6AAAAAA5S3O636VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRTGUZTCNBWGE. You are receiving this because you commented.Message ID: @.***>
Are you talking about version 2.4.4?
—
Reply to this email directly, view it on GitHub<#19168 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AZSO56UA7RTITZ55GX2XMPTYRS72XAVCNFSM6AAAAAA5S3O636VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRTGU2DQMZVGQ>.
You are receiving this because you commented.Message ID: ***@***.***>
|
|
Successfully updated to 2.4.4 😀 On the other hand, there's always an error of this type in the Z2m logs (but it doesn't seem to be blocking):
|
|
Same problem with Skyconnect flashed in RCP 4.3.1, SLM addon in 2.4.4 (which uses 4.3.1 firmware if my understanding is good) and Z2M in 1.36.0-1 (the latest when I wrote this line). The exact error is: If there is a combination that works I will be able to test it.
It seems I have the same config, but it is blocking on my side. No Zigbee devices are found. Can you please tell me your firmware release on the Skyconnect and the Z2M release ? |
|
|
Thank you @merlinpimpim, where did you find this informations, I cannot find the equivalent on my system ? I search for Coordinator type and revision 7.3.1.0 which I don't understand. I flash the Skyconnect with RCP 4.3.1 firmware. It doesn't to have any 7.3.1.0 firmware release for RCP. 7.3.1 looks more like a EZSP firmware (https://github.com/NabuCasa/silabs-firmware). And my understanding is good, this cannot works for Thread and Matter. I'm certainly confused with all this release and try to find a working combinaison. |
I doubt that you are on the right track with this error message if your system is not working. this kinda strange error 55 message shows up for some people for quite a while but does not seem to impair functionality (as far as I can see/at least for me). all the posts in this thread with people that had actual problems were with wrong firmware and totally unrelated to the error message (did post here anyway, confusing). |
|
@merlinpimpim, my problems occurs with the RCP 4.3.1. So I already have tried with it. Than you anyway for the tips. |
|
As someone newly setting up Zigbee2MQTT with a new Sonoff Zigbee 3.0 Dongle Plus V2 Model E with MultiPan firmware - what's my best route to get set-up? I'm getting the above error: |
and others
What happened?
Hi all,
I've a question about a log entry: I've just completed the setup of the addon that uses a SONOFF E Dongle. It seems that everything is woking fine (I've paired just one device at the moment), but every time I start the the zigbee2mqtt, in the log tab of the addon page in Home Assistant, I have an assertion failed entry.
Looking at the log int the /config/zigbee2mqtt/log/ folder, the Assertion Failed entry in not present.
Do you know which is the meaning of this entry and if it represents a potential problem? Considering that I've just paired just one device, I'm still in time to switch to ZHA.
Any help will be really appreciated.
Have a nice day.
What did you expect to happen?
Have a log with no errors
How to reproduce it (minimal and precise)
Just start
Zigbee2MQTT version
1.33.1
Adapter firmware version
7.3.1.0 build 176
Adapter
Sonoff Zigbee 3.0 USB Dongle Plus V2 model "ZBDongle-E"
Debug log
Zigbee2MQTT:info 2023-10-04 11:41:23: Starting Zigbee2MQTT version 1.33.1 (commit #unknown)
Zigbee2MQTT:info 2023-10-04 11:41:23: Starting zigbee-herdsman (0.19.0)
Zigbee2MQTT:debug 2023-10-04 11:41:23: Using zigbee-herdsman with settings: '{"adapter":{"concurrent":null,"delay":null,"disableLED":false},"backupPath":"/config/zigbee2mqtt/coordinator_backup.json","databaseBackupPath":"/config/zigbee2mqtt/database.db.backup","databasePath":"/config/zigbee2mqtt/database.db","network":{"channelList":[XX],"extendedPanID":[XXX,XXX,XX,XXX,X,XXX,XXX,XXX],"networkKey":"HIDDEN","panID":XXXX},"serialPort":{"adapter":"ezsp","path":"/dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_XXXXXXXXXXXXXX-XXXX"}}'
Assertion failed: Command (setConfigurationValue) returned unexpected state: [object Object]
Zigbee2MQTT:info 2023-10-04 11:41:27: zigbee-herdsman started (resumed)
The text was updated successfully, but these errors were encountered: