The manual method using websockets still works. You can connect your Eve device to the Sky Connect Stick with it. If you need help, just reply here.
2 Likes
I’d be interested in the manual method.
You need bluetooth on your homeassistant server. Either an integrated chip or a Bluetooth stick. Do you have bluetooth on your server?
We need bluetooth just for the pairing process
Hello all
Today I was able to add my Eve Motion sensor in Home Assistant.
My setup is HA with skyconnect dongle for thread + matter server + OTBR router ( “OTBR firewall” deactivated and “NAT64” activated)
I had previously the same error than you.
But on another forum I found the solution.
I followed this :
- Before you can add Matter-based Thread devices, your phone needs to know the credentials of your newly created Thread network.
- To share the credentials with your Android phone, open the Home Assistant Companion app.
- In the Companion app, go to Settings > Companion app > Troubleshooting, then select Sync Thread credentials.
- Follow the instructions on screen.
- Result: You will see a confirmation stating that Thread credentials from Home Assistant have been added to this device.
1 Like
After trying for multiple hours and borrowing an android phone from a friend, it finally works using this method!
This same option in the companion app is also there in the ios app, but you just get a blank screen.
1 Like
Thanks, you browser/websocket version works for me!
Eve Energy Matter
Sonoff Thread Stick
It is important to deactivate the Bluetooth integration and restart everything.
Hello after lot of hour to try install my eve motion on my Freebox VM, I decided to install on RPI 4 with h my skyconnect
It works fine now.
I enable discovering on my Bluetooth is it a prerequisites?
Can I synch my eve motion with multiprocole?And have ZigBee in same time?
jube
I suspect it’s crucial for the system to access the Bluetooth chip, particularly its Bluetooth Low Energy function. One method to ensure this is by deactivating the integration and rebooting the system.
Ludomatador
Where did you enable Bluetooth discovery? Which settings did you use?
My Eve motion works seamlessly with multiprotocol.
I use Zigbee at the same time as the Skyconnect stick.
I m not sure that why it’s ok on my raspberry and ko on my Freebox VM. I active passive search in device and service, Bluetooth and configure. I translate maybe little different.
Ok good news for multiprocol, thread device or so expensive.
I just need install multiprocol , then add it in border router and pairing with open thread border api?
Before I will clone my SD card to be sure.
I spend lot of time on my Freebox VM. But with RPI ok after 3 times
i am using proxmox and i pass the bluetooth chip as a hardware device to my haos vm.
i still dont understand what “active passive search” is. Maybe share a screenshot of your process?
I just need install multiprocol , then add it in border router and pairing with open thread border api? → Perhaps it gets added automatically.
This is what I change but maybe nothing to see with my old VM issue
I will try activate multiprocol further.
Anybody know how set motion sensivity, my Eve motion is outdoor and detect too much movement with the wind
Thanks! Updating the credentials in the HA App actually did the trick!
hello, I managed to connect my eve motion with raspberry 4 and skyconnect.
I encounter a problem it goes every one or two days unavailable for a while, then when it comes back available only the lux is ok and refreshes.
while the motion remains frozen.
if I ping via parameter/device/matter eve motion/ping it’s ok.
if I re-interrogate and move at the same time the value remains frozen on detected. the only way to resolve and remove the batteries from the eve motion.
reboot and re-query several times.
how to analyze solve this problem?
eve motion is out but brightness updates correctly after being unavailable.
I move move eve motion next to the door and now it s ok
Sometimes the waves must have had difficulty to join raspberry.
That strange the brightness resynchronized well but not the motion
These console commands previously worked for me a few months ago. Today, I can’t seem to open the websocket. Connection fails. Is this code still working for you?
- Other users reported that they successfully commissioned a device with their Android phone.
- The Silicon Labs Multiprotocol addon no longer exposes the websocket port. However, we can delve deeper into the system and use the port. The port is only open to the Docker container with the ‘host’ network.
docker network ls
NETWORK ID NAME DRIVER SCOPE
a5719e2ed26c bridge bridge local
817ca3a4f2b7 hassio bridge local
8c7ebd2b3c19 host host local
2a24e7559ea0 none null local
So, we create a new container with this network. I named it ‘websocket’.
docker run -d --network host --name websocket node tail -f /dev/null
We access the ‘websocket’ container and navigate to the home directory where we create an ‘app’ folder. There, we initialize npm and install the websocket package ‘ws’. Now, we just type ‘node’ and a console similar to the one from my Firefox browser (F11) opens. There, I can enter the commands previously posted by me.
This sounds complicated. Is the android method really not working for you? If you would like to use my method and need help, you can simply contact me here.
cd home/node
mkdir app
cd app
npm init -y
npm i ws
node
Thank you @KolBusa for sharing this nice steps!
I also tried them with my Nuki Lock 4.0 Pro. Rasperry Pi 3+ (Bluetooth is available in HA). Smlight SLZB-06M Stick for Thread Border Router.
My Matter Code looks like this:
I tried only with first line, and also with second line, but with both got an error:
Invalid string length and Integrity check failed
So I used the whole string, which was accepted:
6380-730-71004957-001-77-2
Matter was activated in Nuki iOS app.
- Request
{
"message_id": "1",
"command": "set_thread_dataset",
"args": {
"dataset": "0e08...0f7f8"
}
- Result
{
"fabric_id": 2,
"compressed_fabric_id": 12693754281838381060,
"schema_version": 8,
"min_supported_schema_version": 5,
"sdk_version": "2024.5.0",
"wifi_credentials_set": false,
"thread_credentials_set": false
}
- Request
{
"message_id": "2",
"command": "commission_with_code",
"args": {
"code": "6380-730-71004957-001-77-2"
}
}
- Result
{
"message_id": "2",
"error_code": 1,
"details": "Commission with code failed for node x."
}
But I always got the error. (Devices are very near to each other.)
Commission with code failed for node x.
Logs:
Matter Server:
2024-05-30 17:26:34.535 (MainThread) INFO [matter_server.server.device_controller] Starting Matter commissioning with code using Node ID 35 (attempt 1/3).
2024-05-30 17:26:35.089 (Dummy-2) CHIP_ERROR [chip.native.SPL] Failed decoding base10. Input length 10 was not expected length 20
2024-05-30 17:26:35.121 (Dummy-2) CHIP_ERROR [chip.native.DL] Long dispatch time: 327 ms, for event type 2
2024-05-30 17:26:35.166 (MainThread) ERROR [matter_server.server.client_handler] [548280855056] Error while handling: commission_with_code: src/setup_payload/ManualSetupPayloadParser.cpp:62: CHIP Error 0x0000001E: Invalid string length
2024-05-30 17:27:01.303 (MainThread) INFO [matter_server.server.device_controller] Starting Matter commissioning with code using Node ID 36 (attempt 1/3).
2024-05-30 17:27:01.338 (MainThread) ERROR [matter_server.server.client_handler] [548280855056] Error while handling: commission_with_code: src/setup_payload/ManualSetupPayloadParser.cpp:49: CHIP Error 0x00000013: Integrity check failed
2024-05-30 17:27:07.271 (MainThread) INFO [matter_server.server.device_controller] Starting Matter commissioning with code using Node ID 37 (attempt 1/3).
2024-05-30 17:27:07.456 (Dummy-2) CHIP_ERROR [chip.native.DL] Long dispatch time: 123 ms, for event type 3
2024-05-30 17:27:08.124 (Dummy-3) CHIP_ERROR [chip.native.DL] FAIL: ConnectDevice: GDBus.Error:org.bluez.Error.Failed: le-connection-abort-by-local (36)
2024-05-30 17:27:14.843 (Dummy-2) CHIP_ERROR [chip.native.DL] Long dispatch time: 127 ms, for event type 16389
2024-05-30 17:27:15.592 (Dummy-2) INFO [root] Established secure session with Device
2024-05-30 17:27:20.305 (Dummy-2) CHIP_ERROR [chip.native.DL] Long dispatch time: 159 ms, for event type 16389
2024-05-30 17:27:22.937 (Dummy-2) CHIP_ERROR [chip.native.CTL] Required network information not provided in commissioning parameters
2024-05-30 17:27:22.939 (Dummy-2) CHIP_ERROR [chip.native.CTL] Parameters supplied: wifi (no) thread (no)
2024-05-30 17:27:22.940 (Dummy-2) CHIP_ERROR [chip.native.CTL] Device supports: wifi (no) thread(yes)
2024-05-30 17:27:42.414 (Dummy-2) WARNING [root] Failed to commission: src/controller/AutoCommissioner.cpp:313: CHIP Error 0x0000002F: Invalid argument
2024-05-30 17:27:42.419 (Dummy-2) CHIP_ERROR [chip.native.BLE] no endpoint for unsub complete
2024-05-30 17:27:47.428 (MainThread) INFO [matter_server.server.device_controller] Starting Matter commissioning with code using Node ID 37 (attempt 2/3).
2024-05-30 17:27:49.139 (Dummy-2) CHIP_ERROR [chip.native.DL] Long dispatch time: 109 ms, for event type 16389
2024-05-30 17:27:49.872 (Dummy-2) INFO [root] Established secure session with Device
2024-05-30 17:27:54.461 (Dummy-2) CHIP_ERROR [chip.native.DL] Long dispatch time: 106 ms, for event type 16389
2024-05-30 17:27:57.072 (Dummy-2) CHIP_ERROR [chip.native.CTL] Required network information not provided in commissioning parameters
2024-05-30 17:27:57.073 (Dummy-2) CHIP_ERROR [chip.native.CTL] Parameters supplied: wifi (no) thread (no)
2024-05-30 17:27:57.074 (Dummy-2) CHIP_ERROR [chip.native.CTL] Device supports: wifi (no) thread(yes)
2024-05-30 17:28:16.407 (Dummy-2) WARNING [root] Failed to commission: src/controller/AutoCommissioner.cpp:313: CHIP Error 0x0000002F: Invalid argument
2024-05-30 17:28:16.409 (Dummy-2) CHIP_ERROR [chip.native.BLE] no endpoint for unsub complete
2024-05-30 17:28:21.414 (MainThread) INFO [matter_server.server.device_controller] Starting Matter commissioning with code using Node ID 37 (attempt 3/3).
2024-05-30 17:28:23.095 (Dummy-2) CHIP_ERROR [chip.native.DL] Long dispatch time: 110 ms, for event type 16389
2024-05-30 17:28:23.827 (Dummy-2) INFO [root] Established secure session with Device
2024-05-30 17:28:28.402 (Dummy-2) CHIP_ERROR [chip.native.DL] Long dispatch time: 107 ms, for event type 16389
2024-05-30 17:28:31.028 (Dummy-2) CHIP_ERROR [chip.native.CTL] Required network information not provided in commissioning parameters
2024-05-30 17:28:31.029 (Dummy-2) CHIP_ERROR [chip.native.CTL] Parameters supplied: wifi (no) thread (no)
2024-05-30 17:28:31.031 (Dummy-2) CHIP_ERROR [chip.native.CTL] Device supports: wifi (no) thread(yes)
2024-05-30 17:28:50.408 (Dummy-2) WARNING [root] Failed to commission: src/controller/AutoCommissioner.cpp:313: CHIP Error 0x0000002F: Invalid argument
2024-05-30 17:28:50.410 (Dummy-2) CHIP_ERROR [chip.native.BLE] no endpoint for unsub complete
2024-05-30 17:28:50.415 (MainThread) ERROR [matter_server.server.client_handler] [548280855056] Error while handling: commission_with_code: Commission with code failed for node 37.
Border router:
s6-rc: info: service banner: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
[20:40:09] INFO: Starting mDNS Responder...
s6-rc: info: service legacy-cont-init successfully started
Default: mDNSResponder (Engineering Build) (Apr 26 2024 10:06:25) starting
[20:40:10] INFO: Starting socat TCP client for OTBR daemon...
s6-rc: info: service socat-otbr-tcp successfully started
-----------------------------------------------------------
Add-on: OpenThread Border Router
OpenThread Border Router add-on
-----------------------------------------------------------
Add-on version: 2.6.0
You are running the latest version of this add-on.
System: Home Assistant OS 12.3 (aarch64 / raspberrypi3-64)
Home Assistant Core: 2024.5.3
Home Assistant Supervisor: 2024.05.1
-----------------------------------------------------------
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service banner successfully started
s6-rc: info: service universal-silabs-flasher: starting
[20:40:14] INFO: Flashing firmware is disabled
s6-rc: info: service universal-silabs-flasher successfully started
s6-rc: info: service otbr-agent: starting
[20:40:18] INFO: Setup OTBR firewall...
[20:40:20] INFO: Starting otbr-agent...
otbr-agent[189]: [NOTE]-AGENT---: Running 0.3.0-2279c02-dirty
otbr-agent[189]: [NOTE]-AGENT---: Thread version: 1.3.0
otbr-agent[189]: [NOTE]-AGENT---: Thread interface: wpan0
otbr-agent[189]: [NOTE]-AGENT---: Radio URL: spinel+hdlc+uart:///tmp/ttyOTBR?uart-baudrate=460800
otbr-agent[189]: [NOTE]-AGENT---: Radio URL: trel://enu1u1u1
otbr-agent[189]: [NOTE]-ILS-----: Infra link selected: enu1u1u1
otbr-agent[189]: 00:00:00.126 [N] RoutingManager: No valid /48 BR ULA prefix found in settings, generating new one
otbr-agent[189]: 00:00:00.169 [N] RoutingManager: BR ULA prefix: fd39:a69b:b2bc::/48 (generated)
otbr-agent[189]: 00:00:00.170 [N] RoutingManager: Local on-link prefix: fdde:ad00:beef:cafe::/64
otbr-agent[189]: 00:00:00.274 [W] Platform------: [netif] Failed to process request#2: No such process
s6-rc: info: service otbr-agent successfully started
s6-rc: info: service otbr-agent-rest-discovery: starting
s6-rc: info: service otbr-agent-configure: starting
Done
s6-rc: info: service otbr-agent-configure successfully started
otbr-agent[189]: 00:00:02.948 [N] RoutingManager: Local on-link prefix: fde3:24de:2a02:6ab2::/64
otbr-agent[189]: 00:00:02.985 [N] Mle-----------: Role disabled -> detached
otbr-agent[189]: 00:00:03.033 [N] Platform------: [netif] Changing interface state to up.
otbr-agent[189]: 00:00:03.067 [W] Platform------: [netif] ADD [U] fe80:0:0:0:64f4:296b:887:8619 failed (InvalidArgs)
otbr-agent[189]: 00:00:03.067 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[189]: 00:00:03.071 [W] Platform------: [netif] ADD [U] fd41:13e5:1b22:c5f:913f:a8b9:a829:22db failed (InvalidArgs)
otbr-agent[189]: 00:00:03.072 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[189]: 00:00:03.076 [W] Platform------: [netif] Failed to process request#5: No such process
otbr-agent[189]: 00:00:03.137 [N] Mle-----------: Attach attempt 1, AnyPartition reattaching with Active Dataset
[20:40:23] 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[189]: 00:00:09.637 [N] RouterTable---: Allocate router id 12
otbr-agent[189]: 00:00:09.638 [N] Mle-----------: RLOC16 fffe -> 3000
otbr-agent[189]: 00:00:09.644 [N] Mle-----------: Role detached -> leader
otbr-agent[189]: 00:00:09.645 [N] Mle-----------: Partition ID 0x65edda5c
otbr-agent[189]: 00:00:09.716 [W] Platform------: [netif] ADD [U] fd41:13e5:1b22:c5f:0:ff:fe00:3000 failed (InvalidArgs)
otbr-agent[189]: 00:00:09.716 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[189]: 00:00:09.718 [W] Platform------: [netif] ADD [U] fd41:13e5:1b22:c5f:0:ff:fe00:fc00 failed (InvalidArgs)
otbr-agent[189]: 00:00:09.718 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[189]: [NOTE]-BBA-----: BackboneAgent: Backbone Router becomes Primary!
otbr-agent[189]: 00:00:09.899 [W] Platform------: [netif] ADD [U] fd41:13e5:1b22:c5f:0:ff:fe00:fc38 failed (InvalidArgs)
otbr-agent[189]: 00:00:09.900 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[189]: 00:00:09.900 [W] Platform------: [netif] ADD [U] fd41:13e5:1b22:c5f:0:ff:fe00:fc10 failed (InvalidArgs)
otbr-agent[189]: 00:00:09.901 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[189]: 00:00:10.275 [W] Platform------: [netif] ADD [U] fd39:a69b:b2bc:1:ddbe:229f:76b5:abb0 failed (InvalidArgs)
otbr-agent[189]: 00:00:10.275 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[189]: 00:00:20.033 [W] Platform------: [netif] ADD [U] fd41:13e5:1b22:c5f:0:ff:fe00:fc11 failed (InvalidArgs)
otbr-agent[189]: 00:00:20.033 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::1466:8eff:fe17:e861/veth5875df9/48
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::1466:8eff:fe17:e861/veth5875df9/48
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::1466:8eff:fe17:e861/veth5875df9/48
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::1466:8eff:fe17:e861/veth5875df9/48
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::1466:8eff:fe17:e861/veth5875df9/48
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::fc27:6bff:febf:d829/veth5bd362b/50
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::fc27:6bff:febf:d829/veth5bd362b/50
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::fc27:6bff:febf:d829/veth5bd362b/50
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::fc27:6bff:febf:d829/veth5bd362b/50
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::fc27:6bff:febf:d829/veth5bd362b/50
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::fc27:6bff:febf:d829/veth5bd362b/50
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::fc27:6bff:febf:d829/veth5bd362b/50
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::fc27:6bff:febf:d829/veth5bd362b/50
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::9426:84ff:fe71:fd44/veth0c870dc/52
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::9426:84ff:fe71:fd44/veth0c870dc/52
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::9426:84ff:fe71:fd44/veth0c870dc/52
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::9426:84ff:fe71:fd44/veth0c870dc/52
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::9426:84ff:fe71:fd44/veth0c870dc/52
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::9426:84ff:fe71:fd44/veth0c870dc/52
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::505d:d7ff:fe70:ca3b/veth1532c3c/54
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::505d:d7ff:fe70:ca3b/veth1532c3c/54
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::505d:d7ff:fe70:ca3b/veth1532c3c/54
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::505d:d7ff:fe70:ca3b/veth1532c3c/54
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::505d:d7ff:fe70:ca3b/veth1532c3c/54
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::505d:d7ff:fe70:ca3b/veth1532c3c/54
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::505d:d7ff:fe70:ca3b/veth1532c3c/54
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::505d:d7ff:fe70:ca3b/veth1532c3c/54
Do you need more information? Any ideas what I could do/change?
{
"fabric_id": 2,
"compressed_fabric_id": 12693754281838381060,
"schema_version": 8,
"min_supported_schema_version": 5,
"sdk_version": "2024.5.0",
"wifi_credentials_set": false,
"thread_credentials_set": false
}
Why is the variable thread_credentials_set set to false? Did you used correct dataset value?
Edit:
Does Homeassistant Matter already support Locks?
Can you connect a thread-matter bulb or something like the eve motion?
Is Bluetooth working?
I used the value from here for the args.dataset, is this not the correct one?
Should I change something else to have thread_credentials_set: true?
I did not find any information that locks are not supported with Matter: The State of Matter - Home Assistant, Matter (BETA) - Home Assistant.
Till now I do not have any other matter device, but I will order one. What would you recommend to be cheap and should work for sure?
Bluetooth is shown in HA:
Raspberry Pi Foundation bcm43438-bt (B8:27:EB:77:83:FE) 1 Gerät
Is there a way to test the Bluetooth connection?
I’m not sure where the issue lies. First, let’s verify that we’re using the correct dataset. Could you log the commissioning process using both your dataset and an invalid dataset? If the log outputs are identical, we’ll know the problem is with your dataset.
edit: can you just run this code? And post the output here?
var socket = new WebSocket("ws://localhost:5580/ws");
socket.addEventListener("message", (event) => {
console.log("Message from server ", event.data);
});
edit2: Your “Border Router” log looks quite different.
Here is mine:
2024-05-30 08:47:16.182 homeassistant universal_silabs_flasher.flash INFO Extracted GBL metadata: NabuCasaMetadata(metadata_version=1, sdk_version='4.3.1', ezsp_version='7.3.1.0', ot_rcp_version='SL-OPENTHREAD/2.3.1.0_GitHub-e6df00dd6' (2.3.1.0), cpc_version='4.3.1-4f7f9e99-dirty-de58d93e' (4.3.1), fw_type=<FirmwareImageType.RCP_UART_802154: 'rcp-uart-802154'>, baudrate=460800)
2024-05-30 08:47:16.182 homeassistant universal_silabs_flasher.flasher INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud
2024-05-30 08:47:18.193 homeassistant universal_silabs_flasher.flasher INFO Probing ApplicationType.CPC at 460800 baud
2024-05-30 08:47:18.210 homeassistant universal_silabs_flasher.flasher INFO Detected ApplicationType.CPC, version '4.3.1-4f7f9e99-dirty-de58d93e' (4.3.1) at 460800 baudrate (bootloader baudrate None)
2024-05-30 08:47:18.210 homeassistant universal_silabs_flasher.flash INFO Firmware version '4.3.1-4f7f9e99-dirty-de58d93e' (4.3.1) is flashed, not re-installing
s6-rc: info: service universal-silabs-flasher successfully started
s6-rc: info: service cpcd-config: starting
[08:47:18] INFO: Using known baudrate of 460800 for cpcd!
[08:47:18] INFO: Generating cpcd configuration.
s6-rc: info: service cpcd-config successfully started
s6-rc: info: service cpcd: starting
[08:47:18] INFO: Starting cpcd...
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.
s6-rc: info: service cpcd successfully started
s6-rc: info: service zigbeed: starting
s6-rc: info: service otbr-agent: starting
s6-rc: info: service zigbeed successfully started
[08:47:19] INFO: Starting zigbeed...
[08:47:19] INFO: Setup OTBR firewall...
[08:47:19] INFO: Starting otbr-agent...
otbr-agent[304]: [NOTE]-AGENT---: Running 0.3.0
otbr-agent[304]: [NOTE]-AGENT---: Thread version: 1.3.0
otbr-agent[304]: [NOTE]-AGENT---: Thread interface: wpan0
otbr-agent[304]: [NOTE]-AGENT---: Radio URL: spinel+cpc://cpcd_0?iid=2&iid-list=0
otbr-agent[304]: [NOTE]-ILS-----: Infra link selected: enp0s18
otbr-agent[304]: 54d.01:43:17.005 [C] Platform------: mCpcBusSpeed = 115200
[08:47:18:818688] Info : [CPCd v4.3.1.0] [Library API v3] [RCP Protocol v4]
[08:47:18:818743] Info : Git commit: 133b29678b3d0bc7578e098d2f46b4d5bcd2ebb4 / branch:
[08:47:18:818745] Info : Sources hash: ff8300587e7e4ab1def7a89a272c0baef32f9eb3bff9b0ba06b94e655d652367
[08:47:18:818747] 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.
[08:47:18:818853] Info : Reading cli arguments
[08:47:18:818859] Info : /usr/local/bin/cpcd
[08:47:18:821091] Info : Reading configuration
[08:47:18:821097] Info : file_path = /usr/local/etc/cpcd.conf
[08:47:18:821098] Info : instance_name = cpcd_0
[08:47:18:821099] Info : socket_folder = /dev/shm
[08:47:18:821100] Info : operation_mode = MODE_NORMAL
[08:47:18:821100] Info : use_encryption = false
[08:47:18:821101] Info : binding_key_file = /etc/binding-key.key
[08:47:18:821102] Info : stdout_tracing = false
[08:47:18:821102] Info : file_tracing = false
[08:47:18:821103] Info : lttng_tracing = false
[08:47:18:821104] Info : enable_frame_trace = false
[08:47:18:821104] Info : traces_folder = /dev/shm/cpcd-traces
[08:47:18:821105] Info : bus = UART
[08:47:18:821105] Info : uart_baudrate = 460800
[08:47:18:821106] Info : uart_hardflow = true
[08:47:18:821106] Info : uart_file = /dev/ttyUSB0
[08:47:18:821107] Info : fu_recovery_pins_enabled = false
[08:47:18:821108] Info : fu_connect_to_bootloader = false
[08:47:18:821108] Info : fu_enter_bootloader = false
[08:47:18:821109] Info : restart_cpcd = false
[08:47:18:821109] Info : application_version_validation = false
[08:47:18:821110] Info : print_secondary_versions_and_exit = false
[08:47:18:821111] Info : use_noop_keep_alive = false
[08:47:18:821111] Info : reset_sequence = true
[08:47:18:821112] Info : stats_interval = 0
[08:47:18:821112] Info : rlimit_nofile = 2000
[08:47:18:821113] Info : ENCRYPTION IS DISABLED
[08:47:18:821114] Info : Starting daemon in normal mode
[08:47:18:832879] Info : Connecting to Secondary...
[08:47:18:912272] Info : RX capability is 256 bytes
[08:47:18:912288] Info : Connected to Secondary
[08:47:18:915973] Info : Secondary Protocol v4
[08:47:18:923059] Info : Secondary CPC v4.3.1
[08:47:18:926435] Info : Secondary bus bitrate is 460800
[08:47:18:933914] Info : Secondary APP v4.3.1-4f7f9e99-dirty-de58d93e
[08:47:18:934012] Info : Daemon startup was successful. Waiting for client connections
[08:47:19:394819] Info : New client connection using library v4.3.1.0
[08:47:19:398847] Info : Opened connection socket for ep#12
[08:47:19:398978] Info : Endpoint socket #12: Client connected. 1 connections
[08:47:20:198211] Info : New client connection using library v4.3.1.0
[08:47:20:203355] Info : Endpoint socket #12: Client connected. 2 connections
otbr-agent[304]: 00:00:00.132 [N] RoutingManager: BR ULA prefix: fde7:c1df:f22e::/48 (loaded)
otbr-agent[304]: 00:00:00.132 [N] RoutingManager: Local on-link prefix: fd23:890f:d24a:fb3d::/64
otbr-agent[304]: 00:00:00.161 [N] Mle-----------: Role disabled -> detached
otbr-agent[304]: 00:00:00.168 [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
s6-rc: info: service otbr-web: starting
s6-rc: info: service otbr-web successfully started
[08:47:21] INFO: Starting otbr-web...
otbr-web[389]: [INFO]-WEB-----: Running 0.3.0
otbr-web[389]: [INFO]-WEB-----: Border router web started on wpan0
[08:47:22] 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
Listening on port 9999 for connection...
Accepting connection.
Accepted connection 7.
otbr-agent[304]: 00:00:27.788 [N] Mle-----------: RLOC16 3400 -> fffe
otbr-agent[304]: 00:00:27.792 [W] Platform------: [netif] Failed to process request#5: Unknown error -95
otbr-agent[304]: 00:00:28.465 [N] Mle-----------: Attach attempt 1, AnyPartition reattaching with Active Dataset
otbr-agent[304]: 00:00:34.965 [N] RouterTable---: Allocate router id 13
otbr-agent[304]: 00:00:34.965 [N] Mle-----------: RLOC16 fffe -> 3400
otbr-agent[304]: 00:00:34.969 [N] Mle-----------: Role detached -> leader
otbr-agent[304]: 00:00:34.970 [N] Mle-----------: Partition ID 0x6f8d3315
otbr-agent[304]: 00:00:34.973 [C] Platform------: Failed to bind UDP socket: Address already in use
otbr-agent[304]: 00:00:34.984 [W] Platform------: [netif] Failed to process request#6: Unknown error -17
otbr-agent[304]: [NOTE]-BBA-----: BackboneAgent: Backbone Router becomes Primary!
I am using the Silicon Labs Multiprotocol Addon.