Unable to connect Matter Light Switch to Home Assistant

RE: Unable to connect Matter Light Switch to Home Assistant

Charlie — Mon, 08 Jan 2024 13:03:41 GMT

No problem.

Just follow this ticket again if you need any help or want to share how the issue is solved.

Best regards,

Charlie

RE: Unable to connect Matter Light Switch to Home Assistant

Vincent124 — Mon, 08 Jan 2024 12:58:10 GMT

Hi Charlie,

[quote userid="93921" url="~/f/nordic-q-a/107100/unable-to-connect-matter-light-switch-to-home-assistant/463139"]Do the two logs from the same try?[/quote]

No, it was another try. Sadly I didn't capture the log from the first one.

[quote userid="93921" url="~/f/nordic-q-a/107100/unable-to-connect-matter-light-switch-to-home-assistant/463139"]but the logs from the device show that there was connection to the ecosystem app established successfully[/quote]

I guess this is because somehow the device connects to the Thread Border Router but not to the HA.

Okay I will contact some kind of Home Assistant suppport for help.

I wasn't sure if the problem might lie with the sample and my build of it or with my Home Assistant configuration. But since you can't find anything wrong in my device log either, I guess my problem might be somewhere else.

Thanks for your help!

RE: Unable to connect Matter Light Switch to Home Assistant

Charlie — Mon, 08 Jan 2024 12:48:06 GMT

Do the two logs from the same try?

From the Matter server log I can see that the device has not been discovered by the Home Assistant ecosystem, but the logs from the device show that there was connection to the ecosystem app established successfully:

I: 71470 [SWU]Device commissioned, schedule a default provider query
I: 71477 [SVR]Commissioning completed successfully

Then there are some strange logs in the device log, that there were some tries to "open commissioning window" so the device prepared itself for the commissioning to the next ecosystem:

I: 73249 [ZCL]Received command to open commissioning window

I guess that this command comes from the ecosystem app.

Honestly we don't test any devices with HomeAssistant.io, so we don't know how it works. Could you also generate an issue here to check with Home Assistant team about this issue? Issues · home-assistant/core · GitHub

The light switch sample uses Dimmable Light Switch Matter device type. It is not clear if this device type is supported by the Home Assistant ecosystem. Please be realized the Matter integration of Home Assistant is still in beta stage. Matter (BETA) - Home Assistant (home-assistant.io)

Best regards,

Charlie

RE: Unable to connect Matter Light Switch to Home Assistant

Vincent124 — Mon, 08 Jan 2024 11:45:06 GMT

Sure this is it: devzone.nordicsemi.com/.../device_5F00_log.txt

RE: Unable to connect Matter Light Switch to Home Assistant

Charlie — Mon, 08 Jan 2024 10:28:41 GMT

so the current state is light_bulb is ok but light_swith has commissioning issue?

If yes, could you also share the log from the light_switch device?

RE: Unable to connect Matter Light Switch to Home Assistant

Vincent124 — Mon, 08 Jan 2024 09:50:08 GMT

Hi Charlie,

I'm not working in a office environment and as I understand it, mDNS should be enabled in my network configuration, since I don't receive these many "ERROR Timeout waiting for mDNS resolution." Errors anymore.

So the important logs form Matter Server Log state this:

2024-01-08 08:34:09 core-matter-server matter_server.server.device_controller[126] INFO Starting Matter commissioning on network using Node ID 5.
2024-01-08 08:34:39 core-matter-server chip.CTL[126] ERROR Mdns discovery timed out
2024-01-08 08:34:39 core-matter-server matter_server.server.client_handler[126] ERROR [548351953232] Error handling message: CommandMessage(message_id='afe520bcea0e4fdc8fcc09c8a1dd984d', command='commission_on_network', args={'setup_pin_code': 6859429, 'ip_addr': None})
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 261, in commission_on_network
    raise NodeCommissionFailed(
matter_server.common.errors.NodeCommissionFailed: Commission on network failed for node 5

What I don't understand is why this only occurs when I use the light_switch. Adding another light_bulb is no problem

RE: Unable to connect Matter Light Switch to Home Assistant

Charlie — Fri, 05 Jan 2024 10:42:16 GMT

Hi Vincent,

mDNS is used for bidirectional service discovery. Matter device commission would not work if the mDNS feature is disabled by your network.

I used to test in the office environment which blocks mDNS discovery, and the commission did not work. Switching to a home network or mobile phone WiFi host will solve the issue. Could you have a try?

Best regards,

Charlie

RE: Unable to connect Matter Light Switch to Home Assistant

Vincent124 — Thu, 04 Jan 2024 14:11:17 GMT

Hi Charlie,

The mDNS Error was also there for the time the commissioning worked. I wasn't able to resolve this yet but it also wasn't a problem till now. I'll look into this too.

I'm using SDK verion 2.4.2.

For some reason I'm now getting the same Error for the light bulb too even though it worked just fine before. Here are some of the last few lines of the light bulb device log before the error occurs:

I: 90714 [ZCL]Commissioning window is now open
I: 90719 [EM]<<< [E:10474r S:23150 M:251748559 (Ack:124261149)] (S) Msg TX to 1:D07881E73455012C [23E9] --- Type 0001:09 (IM:InvokeCommandResponse)
I: 90732 [IN](S) Sending msg 251748559 on secure session with LSID: 23150
I: 90765 [EM]>>> [E:10474r S:23150 M:124261150 (Ack:251748559)] (S) Msg RX from 1:D07881E73455012C [23E9] --- Type 0000:10 (SecureChannel:StandaloneAck)
I: 90832 [EM]>>> [E:10475r S:23150 M:124261151] (S) Msg RX from 1:D07881E73455012C [23E9] --- Type 0001:02 (IM:ReadRequest)
D: 90843 [IM]Received Read request
I: 90848 [EM]<<< [E:10475r S:23150 M:251748560 (Ack:124261151)] (S) Msg TX to 1:D07881E73455012C [23E9] --- Type 0001:05 (IM:ReportData)
I: 90860 [IN](S) Sending msg 251748560 on secure session with LSID: 23150
I: 90897 [EM]>>> [E:10475r S:23150 M:124261152 (Ack:251748560)] (S) Msg RX from 1:D07881E73455012C [23E9] --- Type 0000:10 (SecureChannel:StandaloneAck)
I: 90914 [EM]>>> [E:10476r S:23150 M:124261153] (S) Msg RX from 1:D07881E73455012C [23E9] --- Type 0001:0a (IM:TimedRequest)
I: 90926 [EM]<<< [E:10476r S:23150 M:251748561 (Ack:124261153)] (S) Msg TX to 1:D07881E73455012C [23E9] --- Type 0001:01 (IM:StatusResponse)
I: 90938 [IN](S) Sending msg 251748561 on secure session with LSID: 23150
I: 90968 [EM]>>> [E:10476r S:23150 M:124261154 (Ack:251748561)] (S) Msg RX from 1:D07881E73455012C [23E9] --- Type 0001:08 (IM:InvokeCommandRequest)
I: 90981 [ZCL]Received command to close commissioning window
I: 90987 [SVR]Closing pairing window
D: 90990 [IN]SecureSession[0x20003320]: Released - Type:1 LSID:23152
I: 90996 [DIS]Updating services using commissioning mode 0
D: 91001 [DL]Using Thread extended MAC for hostname.
I: 91006 [DIS]Advertise operational node 310A9064FE4923E9-FCAA50B3BD23B59E
D: 91013 [DL]Using Thread extended MAC for hostname.
I: 91019 [DIS]Advertise commission parameter vendorID=65521 productID=32773 discriminator=3840/15 cm=0
I: 91029 [DL]advertising srp service: 592473A0AEB11410._matterc._udp
D: 91035 [DIS]Scheduling extended discovery timeout in 900s
I: 91040 [DL]removing srp service: FC0492C5D7C89E9C._matterc._udp
I: 91046 [ZCL]Commissioning window is now closed
I: 91051 [EM]<<< [E:10476r S:23150 M:251748562 (Ack:124261154)] (S) Msg TX to 1:D07881E73455012C [23E9] --- Type 0001:09 (IM:InvokeCommandResponse)
I: 91064 [IN](S) Sending msg 251748562 on secure session with LSID: 23150
I: 91412 [EM]>>> [E:10476r S:23150 M:124261155 (Ack:251748562)] (S) Msg RX from 1:D07881E73455012C [23E9] --- Type 0000:10 (SecureChannel:StandaloneAck)
I: 91429 [EM]>>> [E:10477r S:23150 M:124261156] (S) Msg RX from 1:D07881E73455012C [23E9] --- Type 0001:02 (IM:ReadRequest)
D: 91440 [IM]Received Read request
I: 91445 [EM]<<< [E:10477r S:23150 M:251748563 (Ack:124261156)] (S) Msg TX to 1:D07881E73455012C [23E9] --- Type 0001:05 (IM:ReportData)
I: 91457 [IN](S) Sending msg 251748563 on secure session with LSID: 23150
I: 91497 [EM]>>> [E:10477r S:23150 M:124261157 (Ack:251748563)] (S) Msg RX from 1:D07881E73455012C [23E9] --- Type 0000:10 (SecureChannel:StandaloneAck)
I: 91513 [EM]>>> [E:10478r S:23150 M:124261158] (S) Msg RX from 1:D07881E73455012C [23E9] --- Type 0001:02 (IM:ReadRequest)
D: 91524 [IM]Received Read request
I: 91529 [EM]<<< [E:10478r S:23150 M:251748564 (Ack:124261158)] (S) Msg TX to 1:D07881E73455012C [23E9] --- Type 0001:05 (IM:ReportData)
I: 91541 [IN](S) Sending msg 251748564 on secure session with LSID: 23150
I: 91582 [EM]>>> [E:10478r S:23150 M:124261159 (Ack:251748564)] (S) Msg RX from 1:D07881E73455012C [23E9] --- Type 0000:10 (SecureChannel:StandaloneAck)
I: 91598 [EM]>>> [E:10479r S:23150 M:124261160] (S) Msg RX from 1:D07881E73455012C [23E9] --- Type 0001:0a (IM:TimedRequest)
I: 91610 [EM]<<< [E:10479r S:23150 M:251748565 (Ack:124261160)] (S) Msg TX to 1:D07881E73455012C [23E9] --- Type 0001:01 (IM:StatusResponse)
I: 91622 [IN](S) Sending msg 251748565 on secure session with LSID: 23150
I: 91680 [EM]>>> [E:10479r S:23150 M:124261161 (Ack:251748565)] (S) Msg RX from 1:D07881E73455012C [23E9] --- Type 0001:08 (IM:InvokeCommandRequest)
I: 91694 [ZCL]Received command to open commissioning window
D: 91700 [IN]SecureSession[0x20003320]: Allocated Type:1 LSID:23153
I: 91706 [DIS]Updating services using commissioning mode 2
D: 91711 [DL]Using Thread extended MAC for hostname.
I: 91716 [DIS]Advertise operational node 310A9064FE4923E9-FCAA50B3BD23B59E
D: 91723 [DL]Using Thread extended MAC for hostname.
I: 91728 [DIS]Advertise commission parameter vendorID=65521 productID=32773 discriminator=3106/12 cm=2
I: 91738 [DL]advertising srp service: 77AD62A682F4EF64._matterc._udp
I: 91744 [DL]removing srp service: FC0492C5D7C89E9C._matterc._udp
I: 91750 [DL]removing srp service: 592473A0AEB11410._matterc._udp
I: 91756 [ZCL]Commissioning window is now open
I: 91761 [EM]<<< [E:10479r S:23150 M:251748566 (Ack:124261161)] (S) Msg TX to 1:D07881E73455012C [23E9] --- Type 0001:09 (IM:InvokeCommandResponse)
I: 91774 [IN](S) Sending msg 251748566 on secure session with LSID: 23150
I: 91849 [EM]>>> [E:10479r S:23150 M:124261162 (Ack:251748566)] (S) Msg RX from 1:D07881E73455012C [23E9] --- Type 0000:10 (SecureChannel:StandaloneAck)
D: 92618 [DL]SRP update succeeded
E: 120209 [SWU]No suitable OTA Provider candidate found
I: 120214 [SWU]No provider available

I hope this is enough of the log, I'm not sure how much of it is important sorry!

Thanks in advance!

RE: Unable to connect Matter Light Switch to Home Assistant

Charlie — Thu, 04 Jan 2024 11:57:01 GMT

Hi Vincent,

I doubt it is related to the sample itself since we normally test the samples on Apple and Google smart home ecosystems.

(+) Matter: Testing the nRF Connect platform with Apple, Google and Samsung ecosystems - Blogs - Nordic Blog - Nordic DevZone (nordicsemi.com)

The Home Assistant log shows some errors are related to mDNS resolution timeout. Do you test in an office network environment? you need to pay attention to the router's mDNS setting.

Can you share the nRF Connect SDK version you are testing? Maybe you can enable more log information from the device and share it here. It would be helpful to understand the device's behaviour even if an error does not happen.

Best regards,

Charlie