Where do i get my own dataset?
Thanks
Here (See my screenshot):
Hello beautiful people, i just added my Eve Energy (updated to Matter) in Home Assistant.
UPDATE Eve Energy to Matter :
Use Eve iphone App, go in the Eve Energy Device settings, and the Eve app will propose you to upgrade Eve Energy to Matter. Save new Matter QR Code needed later to add it in the Apple Home.
Once updated to Matter, go in the Apple Home app > add new device > scan new QR Code > your Eve Energy is added to Apple Home.
Next how to add it to Home Assistant :
WORKED WELL :
1/ Apple Home app on iphone - enable pairing mode
Select Eve Energy device > settings (in the bottom of the page) > Turn On Pairing Mode
2/ Home Assitant on iPhone
It did not work on the PC but worked well from the iPhone Home Assistant App (because Bluetooth involved at some point ?).
Home Assitant on iPhone > Integrations > Add Integration blue button > Add Matter device > Eve Energy is detected and proposed > next > next > next : it’s added.
Now you see your device in the Matter section in Home Assistant.
DID NOT WORK :
I have my Apple TVs and HomePods in the Thread section with message " You don’t have a preferred network yet." and the button “Add an open thread border router”.
But there is no need to do anything in the Thread section to make your Matter Eve Energy work in Home Assistant.
Also i tryed first ADD ENTRY button in the Matter section from the wab page on PC, but it does not work like this. You must use iPhone Home Assistant app to add your Matter devices as described above.
IPV6 WARNING with Matter :
Because i have two internet boxes (fiber + cellular when fiber breaks) i have router with dual wan,
i discovered that matter uses ipv6 and when my fiber fails and i am on the cellular box, ipv6 doesn’t work so all Matter devices are “Unawalable” in Apple Home and Apple devices can not reach internet because i have static ipv6 setup to my fiber router (via my GT-AXE16000 asus router).
So Matter adds new problems linked to ipv6, and you should not go matter if you could have ipv6 issues at home.
Best regards 
Hello!
I’m trying to get my feet wet with matter via thread and purchased a SkyConnect as well as an eve Motion (Matter) sensor. I followed the instructions listed here:
https://skyconnect.home-assistant.io/procedures/enable-multiprotocol/
… and everything looks like it does in the screenshots.
But when I try to add my eve device using the iOS app as described here:
I get from this screen:
to this screen:
… unless I reset the eve sensor (by using a pin to hold down the reset button for 10 seconds). Then, I get this result:
… As far as I can tell everything is configured correctly. Can anyone tell me what I’m doing wrong?
I read above about websockets and the like but that goes well beyond my skill level. I feel like I’m close to getting it working, no?
Any help would be greatly appreciated!
Best regards,
Andrew
You don’t need a high skill level. I can can assist you. Does your Homeassistant server have Bluetooth?
Thanks KolBusa for your swift response. It’s a Home Assistant Yellow, I believe the RPi CM4 that powers it has Bluetooth…
Ok, if your raspi has wlan it will also support bluetooth.
First, we need to access the thread dataset value from the thread integration.
Settings → devices & services → Thread → Configure → little i
How do you get the pairing code which need to provide in the second step? I see the label on my eve devices (homekit code, qr and some long letter and numbers), but none of them works. I don’t have apple device with thread to migrate my devices to matter in eve app
1 Like
Now step 2:
We need:
- our locl homeassistant network address. (my: 192.168.2.130)
- A Browser browsing our homeassistant (my: 192.168.2.130:8123). This tab is focussed
- On this page we open the development tools of the browser (key F12) and switch to “console” tab in the development tools
- there we can start with step 2: Talking to the matter server and sending it the thread dateset via websocket. Therefore you can paste this into the console. Please change network address and thread dataset. And post here a screenshot of your result.
var socket = new WebSocket("ws://192.168.2.130:5580/ws");
socket.addEventListener("message", (event) => {
console.log("Message from server ", event.data);
});
socket.addEventListener("open", (event) => {
console.log("WebSocket is open");
var message = {
"message_id": "1",
"command": "set_thread_dataset",
"args": {
"dataset": "0e080000000000010000000300000b35060004001fffe0020823890fd24ab1fb3d0708fd32b595bafdd8d30510d4b788583c85b27e2463f14f248fe94b030e686f6d652d617373697374616e74010263e30410bbe3fea1a3a4db87a91b276b3aba21ca0c0402a0f7f8"
}
};
socket.send(JSON.stringify(message));
});
1 Like
For step 3 we need the pairing code. My eve motion device has on the bottom a sticker with four things:
- matter logo with “matter”
- qr code
- paring code (my: 3084-602-3139) ← we need this
- another code
Method 1:
Sell your device and buy a matter-ready eve device.
Method 2:
Buy an iphone and a homepod so you can apply the matter update to your eve device. Alternative visit a friend with this setup and do it there.
1 Like
Edit:
Your value of thread_credentials_set is false. Maybe this will be a problem…
Good!
Bring the eve device in range of the bluetooth signal of your rapsi. And we hope, that your bluetooth is working…
In step 3 you will commission the matter server with the eve device matter pairing code, like this (just change the network address and post result here with a screenshot):
var socket = new WebSocket("ws://192.168.2.130:5580/ws");
socket.addEventListener("message", (event) => {
console.log("Message from server ", event.data);
});
socket.addEventListener("open", (event) => {
console.log("WebSocket is open");
var message = {
"message_id": "2",
"command": "commission_with_code",
"args": {
"code": "33976113343"
}
};
socket.send(JSON.stringify(message));
});
3 Likes
Done:
thread_credentials_set is now true.
… but a few seconds later, this appeared:
… I assume the CM4 is w/o wireless/BT. 
I was sure that I had BlueTooth since I paired some flic-buttons to my HA, but I know remember that this was using a different Pi as a Bluetooth-proxy.
I have several other Pis flying around. Could I run this procedure on a different instance of HA? Or I could purchase a bluetooth dongle (USB)…? Or maybe using an ESP32 as bluetooth proxy via esphome?
Best regards,
Andrew
Bluetooth dongle should work. You could also borrow one from a neighbor, because you need it only for commission. I haven’t tried the other methods (ESP32, Bluetooth-Proxy).
You can go to http://192.168.2.130:8123/config/hardware (change to your network address) and click “ALL HARDWARE”. There you can search for “blue”. This is my result:
So I know that Bluetooth is running on my Homeassistant server.
Thanks! I did that and my system does not have Bluetooth. I will get a BT dongle and try again.
I too am struggling with the “Thread Border Router Required” message. I’m running Home Assistant OS on a RPi 4 with the SkyConnect dongle. Home Assistant seems to be working fine, except I can’t get any Thread devices to connect.
First of all, can someone confirm I’ve set this up properly?
-I’m currently running Silicon Labs Multiprotocol Add-on, not OpenThread Border Router (I shouldn’t be running both simultaneously, right?). Though I have tested OpenThread Border Router as well. (I don’t need Zigbee, so either would be fine for me)
-I have configured the “Device” to the SkyConnect device, and left all other options as their default. I should NOT configure the network ports (e.g. 8080 and 8081), correct?
-Open Thread Border Router shows up under integrations, and shows “Home Assistant SkyConnect (Silicon Labs Multiprotocol)” when clicked.
-When I configure the Thread integration, it shows Preferred network “home-assistant”, 1 border router, and “Silicon Labs Multiprotocol”.
-Under the Preferred network, I have clicked “Used for Android + iOS credentials”
My Home Assistant is connected to my network over WiFi, though I’ve also attempted to plug in using Ethernet with the same results. I’ve also confirmed my interfaces have IPv6 (under IP Information in Network settings). I’ve also tested that Matter over WiFi devices work, so the Matter Server seems OK. I don’t have any other Thread Border Routers (or devices) on my network.
I’ve attempted to add the devices using the Home Assistant app on both an iPhone X and iPhone 8, which typically give the “Thread Border Router Required” error, but occasionally I get an “Unable To Pair”, “Pairing Failed” error. I’ve also tried the WebSocket as described above using the Firefox console. Unfortunately, I always get the “Commission with code failed” error. All devices are physically within a couple feet of each other.
Some other things I tried:
I have an nRF52840 dongle, so I flashed that with the OpenThread RCP, and attempted to use it with the OpenThread Border Router Add-on, with the same results. As mentioned above, I’ve also tried that Add-on with the SkyConnect dongle.
I enabled the networking ports (8080 and 8081) and attempted to form a new thread network, etc. but again, made no difference.
I’ve tried a few different Thread devices to make sure I didn’t simply have a defective device, but all of them do the same thing.
I feel like I’m just banging my head on a wall at this point - does anyone see anything wrong in my current setup, or have ideas/thoughts on troubleshooting? Thanks!
1 Like
Maybe you get the “Commission with code failed” error because you dont have bluetooth on your raspi or the distance between your eve device and the raspi is too large.
Edit: Can you post your matter and/or thread log?
Thanks for the reply… I’m running a standard Raspberry Pi 4 4GB, which should have Bluetooth (it shows up under devices). I’ve also tried deleting the Bluetooth integration as was mentioned above, in case it somehow blocked access (which made no difference). It came back when I rebooted, so this most recent test had it enabled. All devices are all sitting next to each other on my desk (<1 ft. from each other), so nothing should be out of range.
Below are the logs following my attempt to manually add through the console. The common theme in these logs seems to be mDNS. Do you think that’s related, and any ideas on troubleshooting? Thanks!
Matter:
[1695918587.400953][125:125] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_config.ini
[1695918587.405835][125:125] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_counters.ini
[1695918587.408530][125:125] CHIP:DL: writing settings to file (/data/chip_counters.ini-pRvtkC)
[1695918587.414860][125:125] CHIP:DL: renamed tmp file to file (/data/chip_counters.ini)
[1695918587.414946][125:125] CHIP:DL: NVS set: chip-counters/reboot-count = 4 (0x4)
[1695918587.416358][125:125] CHIP:DL: Got Ethernet interface: eth0
[1695918587.416960][125:125] CHIP:DL: Found the primary Ethernet interface:eth0
[1695918587.417724][125:125] CHIP:DL: Got WiFi interface: wlan0
[1695918587.424020][125:125] CHIP:DL: Found the primary WiFi interface:wlan0
2023-09-28 12:29:47 core-matter-server PersistentStorage[125] WARNING Initializing persistent storage from file: /data/chip.json
2023-09-28 12:29:47 core-matter-server PersistentStorage[125] WARNING Loading configuration from /data/chip.json...
2023-09-28 12:29:47 core-matter-server PersistentStorage[125] INFO SetSdkKey: g/gcc = b'\xa0\x0f\x00\x00'
2023-09-28 12:29:47 core-matter-server PersistentStorage[125] INFO Committing...
2023-09-28 12:29:47 core-matter-server PersistentStorage[125] INFO SetSdkKey: g/gdc = b'\xa0\x0f\x00\x00'
2023-09-28 12:29:47 core-matter-server PersistentStorage[125] INFO Committing...
2023-09-28 12:29:47 core-matter-server chip.DL[125] ERROR MDNS failed to join multicast group on eth0 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:764: Inet Error 0x00000110: Address not found
2023-09-28 12:29:47 core-matter-server chip.DL[125] ERROR MDNS failed to join multicast group on vethdeec44d for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:764: Inet Error 0x00000110: Address not found
2023-09-28 12:29:47 core-matter-server chip.DL[125] ERROR MDNS failed to join multicast group on veth2099766 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:764: Inet Error 0x00000110: Address not found
2023-09-28 12:29:47 core-matter-server chip.DL[125] ERROR MDNS failed to join multicast group on veth57c873e for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:764: Inet Error 0x00000110: Address not found
2023-09-28 12:29:47 core-matter-server chip.DL[125] ERROR MDNS failed to join multicast group on vethf74de18 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:764: Inet Error 0x00000110: Address not found
2023-09-28 12:29:47 core-matter-server chip.DL[125] ERROR MDNS failed to join multicast group on veth2b3a0f8 for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:764: Inet Error 0x00000110: Address not found
2023-09-28 12:29:47 core-matter-server chip.DL[125] ERROR MDNS failed to join multicast group on veth639bfcb for address type IPv4: src/inet/UDPEndPointImplSockets.cpp:764: Inet Error 0x00000110: Address not found
2023-09-28 12:29:47 core-matter-server CertificateAuthorityManager[125] WARNING Loading certificate authorities from storage...
2023-09-28 12:29:47 core-matter-server CertificateAuthority[125] WARNING New CertificateAuthority at index 1
2023-09-28 12:29:47 core-matter-server CertificateAuthority[125] WARNING Loading fabric admins from storage...
2023-09-28 12:29:47 core-matter-server FabricAdmin[125] WARNING New FabricAdmin: FabricId: 0x0000000000000002, VendorId = 0x134B
2023-09-28 12:29:47 core-matter-server PersistentStorage[125] INFO SetReplKey: caList = {'1': [{'fabricId': 2, 'vendorId': 4939}]}
2023-09-28 12:29:47 core-matter-server PersistentStorage[125] INFO Committing...
2023-09-28 12:29:47 core-matter-server matter_server.server.stack[125] INFO CHIP Controller Stack initialized.
2023-09-28 12:29:48 core-matter-server matter_server.server.server[125] INFO Starting the Matter Server...
2023-09-28 12:29:48 core-matter-server matter_server.server.helpers.paa_certificates[125] INFO Fetching the latest PAA root certificates from DCL.
/usr/local/lib/python3.11/site-packages/matter_server/server/helpers/paa_certificates.py:46: CryptographyDeprecationWarning: The parsed certificate contains a NULL parameter value in its signature algorithm parameters. This is invalid and will be rejected in a future version of cryptography. If this certificate was created via Java, please upgrade to JDK16+ or the latest JDK11 once a fix is issued. If this certificate was created in some other fashion please report the issue to the cryptography issue tracker. See https://github.com/pyca/cryptography/issues/8996 for more details.
pem_certificate = x509.load_pem_x509_certificate(certificate.encode())
2023-09-28 12:29:57 core-matter-server matter_server.server.helpers.paa_certificates[125] INFO Fetched 108 PAA root certificates from DCL.
2023-09-28 12:29:57 core-matter-server matter_server.server.helpers.paa_certificates[125] INFO Fetching the latest PAA root certificates from Git.
2023-09-28 12:29:58 core-matter-server matter_server.server.helpers.paa_certificates[125] INFO Fetched 2 PAA root certificates from Git.
2023-09-28 12:29:58 core-matter-server FabricAdmin[125] WARNING Allocating new controller with CaIndex: 1, FabricId: 0x0000000000000002, NodeId: 0x000000000001B669, CatTags: []
2023-09-28 12:29:59 core-matter-server PersistentStorage[125] INFO SetSdkKey: g/fs/c = b'\x15$\x00\x01(\x01\x18'
2023-09-28 12:29:59 core-matter-server PersistentStorage[125] INFO Committing...
2023-09-28 12:29:59 core-matter-server PersistentStorage[125] INFO SetSdkKey: f/1/m = b'\x15%\x00K\x13,\x01\x00\x18'
2023-09-28 12:29:59 core-matter-server PersistentStorage[125] INFO Committing...
2023-09-28 12:29:59 core-matter-server PersistentStorage[125] INFO SetSdkKey: f/1/n = b'\x150\x01\x01\x01$\x02\x017\x03$\x13\x02\x18&\x04\x80"\x81\'&\x05\x80%M:7\x06$\x15\x02&\x11i\xb6\x01\x00\x18$\x07\x01$\x08\x010\tA\x042\xfeF\xe2\xb8\x17\xa6xL\x9c\x0e;\xa7\x9c\xb1H*\xd3\n\nM\x03\xbeD\xd7\xb1G/W\x07K[\x0b\x106\x0cA\xa3\xdbs\xea$\x1c\xc6Sd\x1a9\x9c\xc3\xd2\x9f\xd7\x0ba\x14\x1c\x13\xbaHT,m\xd07\n5\x01(\x01\x18$\x02\x016\x03\x04\x02\x04\x01\x180\x04\x14\xf2\x06\xa8\x859\x15\xfc*\xbaF\xcd\x8f\xa5\xed\xe6R\x11u\xad\xf50\x05\x14\xb2\r\x12[y+\x16$7\xac\x1e\xdf\t\x9f\xdb\x88\x13x9l\x180\x0b@f\xf1\x83g\xbf{\'\xb6\xa7\xf1\x1d\x8fF\x9a\xb1\x13\xfd\xa1\xbck\r?Q\xa94d\x9f\xba\xf5\x91\xcb:\xe0j\xb3\xf7\x1f\xd8\xe3-\xc9k\x9fA\x0e\x9f\xd2\xaf\x02\x975\x00\x85\x83\xe2\xd7dw\xe7\x8d*\xd9S\xae\x18'
2023-09-28 12:29:59 core-matter-server PersistentStorage[125] INFO Committing...
2023-09-28 12:29:59 core-matter-server PersistentStorage[125] INFO SetSdkKey: f/1/i = b'\x150\x01\x01\x01$\x02\x017\x03$\x14\x01\x18&\x04\x80"\x81\'&\x05\x80%M:7\x06$\x13\x02\x18$\x07\x01$\x08\x010\tA\x04\xf3\xf2\xef\x8c\x81_\xc3\xfb! l\xc6U\x11\x8c\x98%\xba\xe3M\x11\x99\xd0\x1d\xab\xe6\xb2%0#\xd6F\xd6\x92\xd1U\xad\t\x80\x94]\xcegpw~|\x16l2\x1d\xf9\x0f|F\xa6\x91\x1f\xf9\x0f\x1c\xda\xbf,7\n5\x01)\x01\x18$\x02`0\x04\x14\xb2\r\x12[y+\x16$7\xac\x1e\xdf\t\x9f\xdb\x88\x13x9l0\x05\x14\xf2\xf2\xe8\xbcrC\x9a\xb1\x88\t\x03u:\xf0AA\x90sl<\x180\x0b@y\xd8u\x9d\xb8\xd1\xef}\tp?\xc2\xb3\x15\x89\x84\xea#\x1a\x9e^\xf5\xe1^(\xce|\xf5^\xe2\x01\xda\xf1\xb4\xa5\x96\x8f\xcdVE\xb1\x97u\x0b\xd5B\xcc(\x8a\n\x1fy\x8b\x1fR\xb3\xbf\x16\xebp:\xbee\xa0\x18'
2023-09-28 12:29:59 core-matter-server PersistentStorage[125] INFO Committing...
2023-09-28 12:29:59 core-matter-server PersistentStorage[125] INFO SetSdkKey: g/lkgt = b'\x15&\x00\r\x80\x0c,\x18'
2023-09-28 12:29:59 core-matter-server PersistentStorage[125] INFO Committing...
2023-09-28 12:29:59 core-matter-server PersistentStorage[125] INFO DeleteSdkKey: g/fs/c
2023-09-28 12:29:59 core-matter-server PersistentStorage[125] INFO Committing...
2023-09-28 12:29:59 core-matter-server PersistentStorage[125] INFO SetSdkKey: f/1/k/0 = b'\x15$\x01\x00$\x02\x016\x03\x15$\x04\x00%\x05\x12\x8d0\x06\x10\xb1&\xe1\xe8\x1f3m\x86\x88\xb2\x88\xee\xf0\xdeD\x1d\x18\x15$\x04\x00$\x05\x000\x06\x10\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x18\x15$\x04\x00$\x05\x000\x06\x10\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x18\x18%\x07\xff\xff\x18'
2023-09-28 12:29:59 core-matter-server PersistentStorage[125] INFO Committing...
2023-09-28 12:29:59 core-matter-server chip.DL[125] ERROR Long dispatch time: 144 ms, for event type 2
2023-09-28 12:29:59 core-matter-server matter_server.server.vendor_info[125] INFO Loading vendor info from storage.
2023-09-28 12:29:59 core-matter-server matter_server.server.vendor_info[125] INFO Loaded 100 vendors from storage.
2023-09-28 12:29:59 core-matter-server matter_server.server.vendor_info[125] INFO Fetching the latest vendor info from DCL.
2023-09-28 12:29:59 core-matter-server matter_server.server.vendor_info[125] INFO Fetched 100 vendors from DCL.
2023-09-28 12:29:59 core-matter-server matter_server.server.vendor_info[125] INFO Saving vendor info to storage.
2023-09-28 12:30:30 core-matter-server chip.DIS[125] ERROR Timeout waiting for mDNS resolution.
2023-09-28 12:30:44 core-matter-server chip.DIS[125] ERROR OperationalSessionSetup[1:0000000000000001]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:114: CHIP Error 0x00000032: Timeout
2023-09-28 12:31:15 core-matter-server chip.DIS[125] ERROR Timeout waiting for mDNS resolution.
2023-09-28 12:31:29 core-matter-server chip.DIS[125] ERROR OperationalSessionSetup[1:0000000000000001]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:114: CHIP Error 0x00000032: Timeout
2023-09-28 12:32:00 core-matter-server chip.DIS[125] ERROR Timeout waiting for mDNS resolution.
2023-09-28 12:32:14 core-matter-server chip.DIS[125] ERROR OperationalSessionSetup[1:0000000000000001]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:114: CHIP Error 0x00000032: Timeout
2023-09-28 12:32:14 core-matter-server matter_server.server.device_controller[125] WARNING Unable to subscribe to Node 1 as it is unavailable, will retry later in the background.
2023-09-28 12:33:15 core-matter-server chip.DIS[125] ERROR Timeout waiting for mDNS resolution.
2023-09-28 12:33:29 core-matter-server chip.DIS[125] ERROR OperationalSessionSetup[1:0000000000000001]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:114: CHIP Error 0x00000032: Timeout
2023-09-28 12:34:00 core-matter-server chip.DIS[125] ERROR Timeout waiting for mDNS resolution.
2023-09-28 12:34:14 core-matter-server chip.DIS[125] ERROR OperationalSessionSetup[1:0000000000000001]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:114: CHIP Error 0x00000032: Timeout
2023-09-28 12:34:45 core-matter-server chip.DIS[125] ERROR Timeout waiting for mDNS resolution.
2023-09-28 12:34:59 core-matter-server chip.DIS[125] ERROR OperationalSessionSetup[1:0000000000000001]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:114: CHIP Error 0x00000032: Timeout
2023-09-28 12:34:59 core-matter-server matter_server.server.device_controller[125] WARNING Unable to subscribe to Node 1 as it is unavailable, will retry later in the background.
2023-09-28 12:35:51 core-matter-server matter_server.server.helpers.paa_certificates[125] INFO Fetching the latest PAA root certificates from DCL.
2023-09-28 12:35:52 core-matter-server matter_server.server.helpers.paa_certificates[125] INFO Fetched 0 PAA root certificates from DCL.
2023-09-28 12:35:52 core-matter-server matter_server.server.helpers.paa_certificates[125] INFO Fetching the latest PAA root certificates from Git.
2023-09-28 12:35:52 core-matter-server matter_server.server.helpers.paa_certificates[125] INFO Fetched 0 PAA root certificates from Git.
2023-09-28 12:35:52 core-matter-server chip.DL[125] ERROR Long dispatch time: 102 ms, for event type 2
2023-09-28 12:36:02 core-matter-server chip.BLE[125] ERROR BLE scan error: src/platform/Linux/bluez/ChipDeviceScanner.cpp:154: CHIP Error 0x00000032: Timeout
2023-09-28 12:36:05 core-matter-server chip.DL[125] ERROR FAIL: ConnectDevice : Operation was cancelled (19)
2023-09-28 12:36:05 core-matter-server chip.CTL[125] ERROR Commissioning discovery over BLE failed: src/platform/Linux/bluez/Helper.cpp:1761: CHIP Error 0x000000AC: Internal error
2023-09-28 12:36:05 core-matter-server chip.-[125] ERROR src/platform/Linux/bluez/Helper.cpp:1761: CHIP Error 0x000000AC: Internal error at src/controller/SetUpCodePairer.cpp:299
2023-09-28 12:36:10 core-matter-server chip.DIS[125] ERROR Timeout waiting for mDNS resolution.
2023-09-28 12:36:22 core-matter-server chip.CTL[125] ERROR Discovery timed out
2023-09-28 12:36:22 core-matter-server chip.ZCL[125] ERROR Secure Pairing Failed
2023-09-28 12:36:22 core-matter-server matter_server.server.client_handler[125] ERROR [548147418192] Error handling message: CommandMessage(message_id='2', command='commission_with_code', args={'code': '24503012203'})
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/matter_server/server/client_handler.py", line 188, in _run_handler
result = await result
^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/matter_server/server/device_controller.py", line 171, in commission_with_code
raise NodeCommissionFailed(
matter_server.common.errors.NodeCommissionFailed: Commission with code failed for node 33
2023-09-28 12:36:23 core-matter-server chip.DIS[125] ERROR Timeout waiting for mDNS resolution.
2023-09-28 12:36:24 core-matter-server chip.DIS[125] ERROR OperationalSessionSetup[1:0000000000000001]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:114: CHIP Error 0x00000032: Timeout
2023-09-28 12:36:55 core-matter-server chip.DIS[125] ERROR Timeout waiting for mDNS resolution.
2023-09-28 12:37:09 core-matter-server chip.DIS[125] ERROR OperationalSessionSetup[1:0000000000000001]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:114: CHIP Error 0x00000032: Timeout
2023-09-28 12:37:40 core-matter-server chip.DIS[125] ERROR Timeout waiting for mDNS resolution.
2023-09-28 12:37:54 core-matter-server chip.DIS[125] ERROR OperationalSessionSetup[1:0000000000000001]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:114: CHIP Error 0x00000032: Timeout
2023-09-28 12:37:54 core-matter-server matter_server.server.device_controller[125] WARNING Unable to subscribe to Node 1 as it is unavailable, will retry later in the background.
2023-09-28 12:39:15 core-matter-server chip.DIS[125] ERROR Timeout waiting for mDNS resolution.
2023-09-28 12:39:29 core-matter-server chip.DIS[125] ERROR OperationalSessionSetup[1:0000000000000001]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:114: CHIP Error 0x00000032: Timeout
OpenThread Border Router (Silicon Labs Multiprotocol):
2023-09-28 12:29:40 homeassistant universal_silabs_flasher.flash[187] INFO Extracted GBL metadata: NabuCasaMetadata(metadata_version=1, sdk_version='4.3.1', ezsp_version=None, ot_rcp_version=None, fw_type=<FirmwareImageType.RCP_UART_802154: 'rcp-uart-802154'>, baudrate=460800)
2023-09-28 12:29:40 homeassistant universal_silabs_flasher.flasher[187] INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud
2023-09-28 12:29:43 homeassistant universal_silabs_flasher.flasher[187] INFO Probing ApplicationType.CPC at 460800 baud
2023-09-28 12:29:43 homeassistant universal_silabs_flasher.flasher[187] INFO Detected ApplicationType.CPC, version '4.3.1' at 460800 baudrate (bootloader baudrate None)
2023-09-28 12:29:43 homeassistant universal_silabs_flasher.flash[187] INFO Firmware version '4.3.1' is flashed, not re-installing
s6-rc: info: service universal-silabs-flasher successfully started
s6-rc: info: service cpcd-config: starting
[12:29:46] INFO: Using known baudrate of 460800 for cpcd!
[12:29:47] INFO: Generating cpcd configuration.
s6-rc: info: service cpcd-config successfully started
s6-rc: info: service cpcd: starting
[12:29:49] 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
[12:29:49:096408] Info : [CPCd v4.3.1.0] [Library API v3] [RCP Protocol v4]
[12:29:49:096589] Info : Git commit: 133b29678b3d0bc7578e098d2f46b4d5bcd2ebb4 / branch:
[12:29:49:096593] Info : Sources hash: ff8300587e7e4ab1def7a89a272c0baef32f9eb3bff9b0ba06b94e655d652367
[12:29:49:096601] 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.
[12:29:49:096635] Info : Reading cli arguments
[12:29:49:096644] Info : /usr/local/bin/cpcd
[12:29:49:101916] Info : Reading configuration
[12:29:49:101936] Info : file_path = /usr/local/etc/cpcd.conf
[12:29:49:101939] Info : instance_name = cpcd_0
[12:29:49:101941] Info : socket_folder = /dev/shm
[12:29:49:101943] Info : operation_mode = MODE_NORMAL
[12:29:49:101945] Info : use_encryption = false
[12:29:49:101947] Info : binding_key_file = /etc/binding-key.key
[12:29:49:101949] Info : stdout_tracing = false
[12:29:49:101951] Info : file_tracing = false
[12:29:49:101953] Info : lttng_tracing = false
[12:29:49:101955] Info : enable_frame_trace = false
[12:29:49:101957] Info : traces_folder = /dev/shm/cpcd-traces
[12:29:49:101959] Info : bus = UART
[12:29:49:101960] Info : uart_baudrate = 460800
[12:29:49:101963] Info : uart_hardflow = true
[12:29:49:101965] Info : uart_file = /dev/ttyUSB0
[12:29:49:101967] Info : fu_recovery_pins_enabled = false
[12:29:49:101971] Info : fu_connect_to_bootloader = false
[12:29:49:101973] Info : fu_enter_bootloader = false
[12:29:49:101975] Info : restart_cpcd = false
[12:29:49:101976] Info : application_version_validation = false
[12:29:49:101978] Info : print_secondary_versions_and_exit = false
[12:29:49:101980] Info : use_noop_keep_alive = false
[12:29:49:101982] Info : reset_sequence = true
[12:29:49:101983] Info : stats_interval = 0
[12:29:49:101985] Info : rlimit_nofile = 2000
[12:29:49:101987] Info : ENCRYPTION IS DISABLED
[12:29:49:101989] Info : Starting daemon in normal mode
[12:29:49:119761] Info : Connecting to Secondary...
[12:29:49:201056] Info : RX capability is 256 bytes
[12:29:49:201089] Info : Connected to Secondary
[12:29:49:204521] Info : Secondary Protocol v4
[12:29:49:211818] Info : Secondary CPC v4.3.1
[12:29:49:215781] Info : Secondary bus bitrate is 460800
[12:29:49:222933] Info : Secondary APP vUNDEFINED
[12:29:49:223217] Info : Daemon startup was successful. Waiting for client connections
[12:29:50] INFO: Starting zigbeed...
[12:29:51] INFO: Setup OTBR firewall...
[12:29:52] INFO: Starting otbr-agent...
[12:29:51:503277] Info : New client connection using library v4.3.1.0
[12:29:51:507751] Info : Opened connection socket for ep#12
[12:29:51:508449] Info : Endpoint socket #12: Client connected. 1 connections
otbr-agent[314]: [NOTE]-AGENT---: Running 0.3.0
otbr-agent[314]: [NOTE]-AGENT---: Thread version: 1.3.0
otbr-agent[314]: [NOTE]-AGENT---: Thread interface: wpan0
otbr-agent[314]: [NOTE]-AGENT---: Radio URL: spinel+cpc://cpcd_0?iid=2&iid-list=0
otbr-agent[314]: [NOTE]-ILS-----: Infra link selected: wlan0
otbr-agent[314]: 49d.17:06:53.421 [C] Platform------: mCpcBusSpeed = 115200
[12:29:52:205322] Info : New client connection using library v4.3.1.0
[12:29:52:209813] Info : Endpoint socket #12: Client connected. 2 connections
otbr-agent[314]: 00:00:00.172 [N] RoutingManager: BR ULA prefix: fd78:dd61:dfa4::/48 (loaded)
otbr-agent[314]: 00:00:00.172 [N] RoutingManager: Local on-link prefix: fd52:b8bb:c917:92a9::/64
otbr-agent[314]: 00:00:00.345 [N] Mle-----------: Role disabled -> detached
otbr-agent[314]: 00:00:00.450 [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.
[12:29:55] 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[314]: 00:00:26.021 [N] Mle-----------: RLOC16 5800 -> fffe
otbr-agent[314]: 00:00:26.025 [W] Platform------: [netif] Failed to process request#5: Unknown error -95
otbr-agent[314]: 00:00:26.365 [N] Mle-----------: Attach attempt 1, AnyPartition reattaching with Active Dataset
otbr-agent[314]: 00:00:32.867 [N] RouterTable---: Allocate router id 22
otbr-agent[314]: 00:00:32.868 [N] Mle-----------: RLOC16 fffe -> 5800
otbr-agent[314]: 00:00:32.872 [N] Mle-----------: Role detached -> leader
otbr-agent[314]: 00:00:32.873 [N] Mle-----------: Partition ID 0x678ac244
otbr-agent[314]: 00:00:39.924 [W] Platform------: [netif] Failed to process request#6: Unknown error -17
otbr-agent[314]: [NOTE]-BBA-----: BackboneAgent: Backbone Router becomes Primary!
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::702f:3fff:fed5:deb4/veth7b6fec1/20
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::702f:3fff:fed5:deb4/veth7b6fec1/20
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::702f:3fff:fed5:deb4/veth7b6fec1/20
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::702f:3fff:fed5:deb4/veth7b6fec1/20
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::702f:3fff:fed5:deb4/veth7b6fec1/20
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::702f:3fff:fed5:deb4/veth7b6fec1/20
1 Like