Skip to content

Zigbee devices went off and the SkyConnect Multi-PAN doesn't find the tools #144808

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

Open
turcsi801021 opened this issue May 13, 2025 · 0 comments

Comments

@turcsi801021
Copy link

The problem

My problem is that all my Zigbee devices are unavailable after upgra 2025.5.0 and 2025.5.1. I can not restore the HA. Is this the problem only in my HA or has anyone encountered a similar error in the last 2 days?
I don't knonw what is the next step. Now all my Zigbee devices are reachless. Nothing works.
I tried to reset, downgrade... everything. The device appears to exist, but it doesn't seem to communicate with any devices.

The adapter is SkyConnect. Here you can see the configuration of it (is it ok or should i change something)?

Device:
/dev/serial/by-id/usb-Nabu_Casa_SkyConnect_v1.0_86e48a96ee8cec118cd868e883c5466d-if00-port0

Baudrate:
115200

I can see in the log the following:

[10:31:26:238776] Info : Reading cli arguments
[10:31:26:238783] Info : /usr/local/bin/cpcd
[10:31:26:243951] Info : Reading configuration
[10:31:26:243965] Info : file_path = /usr/local/etc/cpcd.conf
[10:31:26:243967] Info : instance_name = cpcd_0
[10:31:26:243969] Info : socket_folder = /dev/shm
[10:31:26:243972] Info : operation_mode = MODE_NORMAL
[10:31:26:243974] Info : use_encryption = false
[10:31:26:243976] Info : binding_key_file = /etc/binding-key.key
[10:31:26:243978] Info : stdout_tracing = false
[10:31:26:243980] Info : file_tracing = false
[10:31:26:243982] Info : lttng_tracing = false
[10:31:26:243984] Info : enable_frame_trace = false
[10:31:26:243986] Info : traces_folder = /dev/shm/cpcd-traces
[10:31:26:243988] Info : bus = UART
[10:31:26:243990] Info : uart_baudrate = 460800
[10:31:26:243992] Info : uart_hardflow = true
[10:31:26:243994] Info : uart_file = /dev/ttyUSB1
[10:31:26:243997] Info : fu_recovery_pins_enabled = false
[10:31:26:243999] Info : fu_connect_to_bootloader = false
[10:31:26:244001] Info : fu_enter_bootloader = false
[10:31:26:244003] Info : restart_cpcd = false
[10:31:26:244005] Info : application_version_validation = false
[10:31:26:244007] Info : print_secondary_versions_and_exit = false
[10:31:26:244009] Info : use_noop_keep_alive = false
[10:31:26:244011] Info : reset_sequence = true
[10:31:26:244013] Info : stats_interval = 0
[10:31:26:244015] Info : rlimit_nofile = 2000
[10:31:26:244017] Info : ENCRYPTION IS DISABLED

[10:28:48:812577] Info : Starting daemon in normal mode
[10:28:48:829229] Info : Connecting to Secondary...
[10:28:50:829700] Info : Failed to connect, secondary seems unresponsive
[10:28:50:829833] Info : Connecting to Secondary...
[10:28:52:829997] Info : Failed to connect, secondary seems unresponsive
[10:28:52:830022] Info : Connecting to Secondary...
[10:28:54:830185] Info : Failed to connect, secondary seems unresponsive
[10:28:54:830221] Info : Connecting to Secondary...
[10:28:56:830420] Info : Failed to connect, secondary seems unresponsive
[10:28:56:830455] Info : Connecting to Secondary...
[10:28:58:830721] Info : Failed to connect, secondary seems unresponsive
[10:28:58:830758] Info : Connecting to Secondary...
[10:29:00:830967] Info : Failed to connect, secondary seems unresponsive
[10:29:00:831002] Info : Connecting to Secondary...
[10:29:02:831231] Info : Failed to connect, secondary seems unresponsive
[10:29:02:831268] Info : Connecting to Secondary...

I am not a programmer, but this looks very interesting:

WARNING in function 'main' in file /usr/src/cpc-daemon/main.c at line #186 : Running CPCd as 'root' is not recommended. Proceed at your own risk.
FATAL in function 'prevent_device_collision' in file /usr/src/cpc-daemon/misc/config.c at line #843 : The device "/dev/ttyUSB1" is locked by another cpcd instance

What does it mean? could you please explain me what to do as a not programmer?

[11:02:01] INFO: Setup OTBR firewall...
[11:02:01] INFO: Starting otbr-agent...
otbr-agent[346]: [NOTE]-AGENT---: Running 0.3.0
otbr-agent[346]: [NOTE]-AGENT---: Thread version: 1.3.0
otbr-agent[346]: [NOTE]-AGENT---: Thread interface: wpan0
otbr-agent[346]: [NOTE]-AGENT---: Radio URL: spinel+cpc://cpcd_0?iid=2&iid-list=0
otbr-agent[346]: [NOTE]-ILS-----: Infra link selected: end0
otbr-agent[346]: 49d.18:12:36.015 [C] Platform------: mCpcBusSpeed = 115200
[11:02:01:709134] Info : New client connection using library v4.3.1.0
[11:02:01:712848] Info : Opened connection socket for ep#12
[11:02:01:712970] Info : Endpoint socket #12: Client connected. 1 connections
[11:02:02:167349] Info : New client connection using library v4.3.1.0
[11:02:02:171796] Info : Endpoint socket #12: Client connected. 2 connections
otbr-agent[346]: 00:00:00.113 [N] RoutingManager: BR ULA prefix: fd58:9f5e:e7ff::/48 (loaded)
otbr-agent[346]: 00:00:00.113 [N] RoutingManager: Local on-link prefix: fd36:58ad:ae47:d948::/64
otbr-agent[346]: 00:00:00.156 [N] Mle-----------: Role disabled -> detached
otbr-agent[346]: 00:00:00.171 [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.
[11:02:05] 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
otbr-agent[346]: 00:00:26.658 [N] Mle-----------: RLOC16 7800 -> fffe
otbr-agent[346]: 00:00:26.662 [W] Platform------: [netif] Failed to process request#5: Unknown error -95
otbr-agent[346]: 00:00:27.279 [N] Mle-----------: Attach attempt 1, AnyPartition reattaching with Active Dataset
otbr-agent[346]: 00:00:33.784 [N] RouterTable---: Allocate router id 30
otbr-agent[346]: 00:00:33.785 [N] Mle-----------: RLOC16 fffe -> 7800
otbr-agent[346]: 00:00:33.788 [N] Mle-----------: Role detached -> leader
otbr-agent[346]: 00:00:33.789 [N] Mle-----------: Partition ID 0x523aab7e
otbr-agent[346]: 00:00:33.832 [W] Platform------: [netif] Failed to process request#6: Unknown error -17
otbr-agent[346]: [NOTE]-BBA-----: BackboneAgent: Backbone Router becomes Primary!
Accepted connection 7.
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::7850:64ff:fea9:fcb7/vetha19b438/68
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::7850:64ff:fea9:fcb7/vetha19b438/68
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::7850:64ff:fea9:fcb7/vetha19b438/68
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::7850:64ff:fea9:fcb7/vetha19b438/68
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::7850:64ff:fea9:fcb7/vetha19b438/68
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::7850:64ff:fea9:fcb7/vetha19b438/68

Thank you for your help in advance.

What version of Home Assistant Core has the issue?

2025.05.01

What was the last working version of Home Assistant Core?

What type of installation are you running?

Home Assistant OS

Integration causing the issue

No response

Link to integration documentation on our website

No response

Diagnostics information

The adapter is SkyConnect. Here you can see the configuration of it (is it ok or should i change something)?

Device:
/dev/serial/by-id/usb-Nabu_Casa_SkyConnect_v1.0_86e48a96ee8cec118cd868e883c5466d-if00-port0

Baudrate:
115200

I can see in the log the following:

[10:31:26:238776] Info : Reading cli arguments
[10:31:26:238783] Info : /usr/local/bin/cpcd
[10:31:26:243951] Info : Reading configuration
[10:31:26:243965] Info : file_path = /usr/local/etc/cpcd.conf
[10:31:26:243967] Info : instance_name = cpcd_0
[10:31:26:243969] Info : socket_folder = /dev/shm
[10:31:26:243972] Info : operation_mode = MODE_NORMAL
[10:31:26:243974] Info : use_encryption = false
[10:31:26:243976] Info : binding_key_file = /etc/binding-key.key
[10:31:26:243978] Info : stdout_tracing = false
[10:31:26:243980] Info : file_tracing = false
[10:31:26:243982] Info : lttng_tracing = false
[10:31:26:243984] Info : enable_frame_trace = false
[10:31:26:243986] Info : traces_folder = /dev/shm/cpcd-traces
[10:31:26:243988] Info : bus = UART
[10:31:26:243990] Info : uart_baudrate = 460800
[10:31:26:243992] Info : uart_hardflow = true
[10:31:26:243994] Info : uart_file = /dev/ttyUSB1
[10:31:26:243997] Info : fu_recovery_pins_enabled = false
[10:31:26:243999] Info : fu_connect_to_bootloader = false
[10:31:26:244001] Info : fu_enter_bootloader = false
[10:31:26:244003] Info : restart_cpcd = false
[10:31:26:244005] Info : application_version_validation = false
[10:31:26:244007] Info : print_secondary_versions_and_exit = false
[10:31:26:244009] Info : use_noop_keep_alive = false
[10:31:26:244011] Info : reset_sequence = true
[10:31:26:244013] Info : stats_interval = 0
[10:31:26:244015] Info : rlimit_nofile = 2000
[10:31:26:244017] Info : ENCRYPTION IS DISABLED

[10:28:48:812577] Info : Starting daemon in normal mode
[10:28:48:829229] Info : Connecting to Secondary...
[10:28:50:829700] Info : Failed to connect, secondary seems unresponsive
[10:28:50:829833] Info : Connecting to Secondary...
[10:28:52:829997] Info : Failed to connect, secondary seems unresponsive
[10:28:52:830022] Info : Connecting to Secondary...
[10:28:54:830185] Info : Failed to connect, secondary seems unresponsive
[10:28:54:830221] Info : Connecting to Secondary...
[10:28:56:830420] Info : Failed to connect, secondary seems unresponsive
[10:28:56:830455] Info : Connecting to Secondary...
[10:28:58:830721] Info : Failed to connect, secondary seems unresponsive
[10:28:58:830758] Info : Connecting to Secondary...
[10:29:00:830967] Info : Failed to connect, secondary seems unresponsive
[10:29:00:831002] Info : Connecting to Secondary...
[10:29:02:831231] Info : Failed to connect, secondary seems unresponsive
[10:29:02:831268] Info : Connecting to Secondary...

[11:02:01] INFO: Setup OTBR firewall...
[11:02:01] INFO: Starting otbr-agent...
otbr-agent[346]: [NOTE]-AGENT---: Running 0.3.0
otbr-agent[346]: [NOTE]-AGENT---: Thread version: 1.3.0
otbr-agent[346]: [NOTE]-AGENT---: Thread interface: wpan0
otbr-agent[346]: [NOTE]-AGENT---: Radio URL: spinel+cpc://cpcd_0?iid=2&iid-list=0
otbr-agent[346]: [NOTE]-ILS-----: Infra link selected: end0
otbr-agent[346]: 49d.18:12:36.015 [C] Platform------: mCpcBusSpeed = 115200
[11:02:01:709134] Info : New client connection using library v4.3.1.0
[11:02:01:712848] Info : Opened connection socket for ep#12
[11:02:01:712970] Info : Endpoint socket #12: Client connected. 1 connections
[11:02:02:167349] Info : New client connection using library v4.3.1.0
[11:02:02:171796] Info : Endpoint socket #12: Client connected. 2 connections
otbr-agent[346]: 00:00:00.113 [N] RoutingManager: BR ULA prefix: fd58:9f5e:e7ff::/48 (loaded)
otbr-agent[346]: 00:00:00.113 [N] RoutingManager: Local on-link prefix: fd36:58ad:ae47:d948::/64
otbr-agent[346]: 00:00:00.156 [N] Mle-----------: Role disabled -> detached
otbr-agent[346]: 00:00:00.171 [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.
[11:02:05] 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
otbr-agent[346]: 00:00:26.658 [N] Mle-----------: RLOC16 7800 -> fffe
otbr-agent[346]: 00:00:26.662 [W] Platform------: [netif] Failed to process request#5: Unknown error -95
otbr-agent[346]: 00:00:27.279 [N] Mle-----------: Attach attempt 1, AnyPartition reattaching with Active Dataset
otbr-agent[346]: 00:00:33.784 [N] RouterTable---: Allocate router id 30
otbr-agent[346]: 00:00:33.785 [N] Mle-----------: RLOC16 fffe -> 7800
otbr-agent[346]: 00:00:33.788 [N] Mle-----------: Role detached -> leader
otbr-agent[346]: 00:00:33.789 [N] Mle-----------: Partition ID 0x523aab7e
otbr-agent[346]: 00:00:33.832 [W] Platform------: [netif] Failed to process request#6: Unknown error -17
otbr-agent[346]: [NOTE]-BBA-----: BackboneAgent: Backbone Router becomes Primary!
Accepted connection 7.
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::7850:64ff:fea9:fcb7/vetha19b438/68
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::7850:64ff:fea9:fcb7/vetha19b438/68
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::7850:64ff:fea9:fcb7/vetha19b438/68
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::7850:64ff:fea9:fcb7/vetha19b438/68
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::7850:64ff:fea9:fcb7/vetha19b438/68
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::7850:64ff:fea9:fcb7/vetha19b438/68

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

@turcsi801021 turcsi801021 changed the title Zgibee devices went off and the SkyConnect Multi-PAN doesn't find them Zigbee devices went off and the SkyConnect Multi-PAN doesn't find them May 13, 2025
@turcsi801021 turcsi801021 changed the title Zigbee devices went off and the SkyConnect Multi-PAN doesn't find them Zigbee devices went off and the SkyConnect Multi-PAN doesn't find the tools May 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant