Closed HFeenstra closed 7 months ago
Extra input: log file after restoring backup from 10 days ago: (see also: #108927 of general issues)
18:43:20:265404] Info : uart_hardflow = true [18:43:20:265406] Info : uart_file = /dev/ttyUSB0 [18:43:20:265408] Info : fu_recovery_pins_enabled = false [18:43:20:265410] Info : fu_connect_to_bootloader = false [18:43:20:265412] Info : fu_enter_bootloader = false [18:43:20:265414] Info : restart_cpcd = false [18:43:20:265415] Info : application_version_validation = false [18:43:20:265417] Info : print_secondary_versions_and_exit = false [18:43:20:265418] Info : use_noop_keep_alive = false [18:43:20:265420] Info : reset_sequence = true [18:43:20:265421] Info : stats_interval = 0 [18:43:20:265423] Info : rlimit_nofile = 2000 [18:43:20:265425] Info : ENCRYPTION IS DISABLED [18:43:20:265427] Info : Starting daemon in normal mode [18:43:20:276993] Info : Connecting to Secondary... [18:43:20:355303] Info : RX capability is 256 bytes [18:43:20:355342] Info : Connected to Secondary [18:43:20:358581] Info : Secondary Protocol v4 [18:43:20:365426] Info : Secondary CPC v4.3.1 [18:43:20:368663] Info : Secondary bus bitrate is 460800 [18:43:20:375782] Info : Secondary APP v4.3.1-4f7f9e99-dirty-de58d93e [18:43:20:375914] Info : Daemon startup was successful. Waiting for client connections [18:43:21] INFO: Setup OTBR firewall... [18:43:21] INFO: Starting otbr-agent... otbr-agent[313]: [NOTE]-AGENT---: Running 0.3.0 otbr-agent[313]: [NOTE]-AGENT---: Thread version: 1.3.0 otbr-agent[313]: [NOTE]-AGENT---: Thread interface: wpan0 otbr-agent[313]: [NOTE]-AGENT---: Radio URL: spinel+cpc://cpcd_0?iid=2&iid-list=0 otbr-agent[313]: [NOTE]-ILS-----: Infra link selected: end0 otbr-agent[313]: 51d.18:53:27.982 [C] Platform------: mCpcBusSpeed = 115200 [18:43:22:046127] Info : New client connection using library v4.3.1.0 [18:43:22:049971] Info : Opened connection socket for ep#12 [18:43:22:050065] Info : Endpoint socket #12: Client connected. 1 connections [18:43:22:166739] Info : New client connection using library v4.3.1.0 [18:43:22:170697] Info : Endpoint socket #12: Client connected. 2 connections otbr-agent[313]: 00:00:00.114 [N] RoutingManager: BR ULA prefix: fd2d:c636:28fb::/48 (loaded) otbr-agent[313]: 00:00:00.114 [N] RoutingManager: Local on-link prefix: fd50:c023:1930:580c::/64 otbr-agent[313]: 00:00:00.202 [N] Mle-----------: Role disabled -> detached otbr-agent[313]: 00:00:00.219 [N] Platform------: [netif] Changing interface state to up. s6-rc: info: service otbr-agent successfully started s6-rc: info: service otbr-agent-rest-discovery: starting Listening on port 9999 for connection... Accepting connection. [18:43:25] INFO: Successfully sent discovery information to Home Assistant. s6-rc: info: service otbr-agent-rest-discovery successfully started s6-rc: info: service legacy-services: starting s6-rc: info: service legacy-services successfully started Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::9849:75ff:fec8:120f/veth632547c/82 Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::9849:75ff:fec8:120f/veth632547c/82 Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::9849:75ff:fec8:120f/veth632547c/82 Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::9849:75ff:fec8:120f/veth632547c/82 Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::9849:75ff:fec8:120f/veth632547c/82 Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::c1f:95ff:fe23:ef42/veth798ffb3/84 Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::9849:75ff:fec8:120f/veth632547c/82 Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::c1f:95ff:fe23:ef42/veth798ffb3/84 Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::c1f:95ff:fe23:ef42/veth798ffb3/84 Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::c1f:95ff:fe23:ef42/veth798ffb3/84 Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::c1f:95ff:fe23:ef42/veth798ffb3/84 Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::c0f8:baff:fe08:bac9/vethcbbff60/86 Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::c0f8:baff:fe08:bac9/vethcbbff60/86 Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::c0f8:baff:fe08:bac9/vethcbbff60/86 Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::c0f8:baff:fe08:bac9/vethcbbff60/86 Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::c0f8:baff:fe08:bac9/vethcbbff60/86 Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::9406:83ff:fe40:ae63/veth3ccf3be/88 Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::c0f8:baff:fe08:bac9/vethcbbff60/86 Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::9406:83ff:fe40:ae63/veth3ccf3be/88 Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::9406:83ff:fe40:ae63/veth3ccf3be/88 Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::9406:83ff:fe40:ae63/veth3ccf3be/88 Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::9406:83ff:fe40:ae63/veth3ccf3be/88 Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::540b:86ff:fe82:5db/vethf0de868/90 Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::540b:86ff:fe82:5db/vethf0de868/90 Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::540b:86ff:fe82:5db/vethf0de868/90 Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::540b:86ff:fe82:5db/vethf0de868/90 Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::540b:86ff:fe82:5db/vethf0de868/90 Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::540b:86ff:fe82:5db/vethf0de868/90 otbr-agent[313]: 00:00:28.207 [N] Mle-----------: RLOC16 2c00 -> fffe otbr-agent[313]: 00:00:28.211 [W] Platform------: [netif] Failed to process request#5: Unknown error -95 otbr-agent[313]: 00:00:28.409 [N] Mle-----------: Attach attempt 1, AnyPartition reattaching with Active Dataset Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::f03c:68ff:fe4f:d806/veth707b170/92 Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::f03c:68ff:fe4f:d806/veth707b170/92 Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::f03c:68ff:fe4f:d806/veth707b170/92 Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::f03c:68ff:fe4f:d806/veth707b170/92 Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::f03c:68ff:fe4f:d806/veth707b170/92 Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::f03c:68ff:fe4f:d806/veth707b170/92 otbr-agent[313]: 00:00:34.910 [N] RouterTable---: Allocate router id 11 otbr-agent[313]: 00:00:34.911 [N] Mle-----------: RLOC16 fffe -> 2c00 otbr-agent[313]: 00:00:34.916 [N] Mle-----------: Role detached -> leader otbr-agent[313]: 00:00:34.917 [N] Mle-----------: Partition ID 0xc68edcf otbr-agent[313]: 00:00:35.015 [W] Platform------: [netif] Failed to process request#6: Unknown error -17 otbr-agent[313]: [NOTE]-BBA-----: BackboneAgent: Backbone Router becomes Primary! Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::a4b7:cfff:fed4:ec01/vethe19fe5c/94 Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::a4b7:cfff:fed4:ec01/vethe19fe5c/94 Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::a4b7:cfff:fed4:ec01/vethe19fe5c/94 Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::a4b7:cfff:fed4:ec01/vethe19fe5c/94 Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::a4b7:cfff:fed4:ec01/vethe19fe5c/94 Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::a4b7:cfff:fed4:ec01/vethe19fe5c/94 Accepted connection 7. otbr-agent[313]: 01:08:57.527 [W] Platform------: Error processing result: InvalidState otbr-agent[313]: 01:08:57.533 [W] Platform------: Error waiting response: InvalidState otbr-agent[313]: 01:08:57.533 [W] SubMac--------: RadioReceive() failed, error: InvalidState
Update/Work around: As mentioned in other tickets regarding SkyConnect and Multiprotocol I have now turned off Multiprotocol and had to completely setup again all the devices, some of them came up again, but overall I had to reconnect/readd them. This has just been 1.5 hours up till now and still all devices are working properly. Hope devs will figure out what makes that SkyConnect is losing connection/Multiprotocol is some what interferring?
Read in other tickets this seems to have been reported as of 2023.12.x
Rolling back to 2.4.2 seemed to fix it for now. Looks like somethings wrong in the latest vesion
Thanks for the reply. I ended up disabling the Multiprotocol of the Skyconnect and reconfigure the whole ZHA interface and devices.
Same issue here. Seems restore to 2.4.2 and complete reboot (shutdown, power off, power on) fix the issue of 2.4.4 :( for now.
How can I install version 2.4.2? I don't find a link where I can download older versions.
Typically if you upgrade a backup is created and you can revert back to the backup.
Unfortunately - a have to say - for me after the 2.4.4 version reverting back to 2.4.2 didn't do the trick 100%. After a while it started to fail. Maybe there was also a fw update with 2.4.4, I don't know. I decided to try 2.4.4 again and my light switches disappeared (I just didn't realized it first) and I wasn't able to reconfigure it. :(
I ended up to disable the OpenThread Border Router and firewall as I don't have any Matter device.
Now Zigbee seems to work...
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Describe the issue you are experiencing
added or tweaked. Running an Home Assistant Blue, 2024.1.3 with Skyconnect, 2.4.2 Sillicon lab firmware, looks like it started when upgrading to 2.4.4 (firmware as of 26-1-2024). Have ZHA integration and was working perfectly until this interruption.
What did I do: Restore backup before this issue, then reboot the whole system including hardware, then it works for 15 min and gives these issues in logbook.
Odd it disconnects and starts a new session..? ZHA doesn’t give an error. All entities I see, try to switch a light, gives a failed send request error in RED.
Restored from backup now twice no success thus far. Who has more info, steps to resolve??
What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Home Assistant Operating System
Which add-on are you reporting an issue with?
Silicon Labs Multiprotocol
What is the version of the add-on?
2.4.2
Steps to reproduce the issue
...
System Health information
System Information
Home Assistant Community Store
GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 4996 Installed Version | 1.34.0 Stage | running Available Repositories | 1381 Downloaded Repositories | 51Home Assistant Cloud
logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okHome Assistant Supervisor
host_os | Home Assistant OS 11.4 -- | -- update_channel | stable supervisor_version | supervisor-2023.12.1 agent_version | 1.6.0 docker_version | 24.0.7 disk_total | 113.9 GB disk_used | 20.2 GB healthy | true supported | true board | odroid-n2 supervisor_api | ok version_api | ok installed_addons | AdGuard Home (5.0.2), Node-RED (17.0.3), Genie (3.0.0), Samba share (12.2.0), Mosquitto broker (6.4.0), AirSonos (4.2.0), Studio Code Server (5.15.0), Advanced SSH & Web Terminal (17.0.4), TasmoAdmin (0.29.1), Grocy (0.21.0), ESPHome (2023.12.9), Silicon Labs Multiprotocol (2.4.2), Matter Server (5.0.4), Piper (1.4.0), Whisper (1.0.2), Simple Scheduler (2.2.1), Home Assistant Google Drive Backup (0.112.1), openWakeWord (1.8.2), Z-Wave JS (0.4.3), Cloudflared (5.1.1)Dashboards
dashboards | 9 -- | -- resources | 36 views | 22 mode | storageRecorder
oldest_recorder_run | 18 januari 2024 om 05:04 -- | -- current_recorder_run | 28 januari 2024 om 17:34 estimated_db_size | 400.93 MiB database_engine | sqlite database_version | 3.41.2Spotify
api_endpoint_reachable | ok -- | --Anything in the Supervisor logs that might be useful for us?
Anything in the add-on logs that might be useful for us?
Additional information
Everything is in description