Google Home Thread devices share to Home Assistant

Hello,

I have a Google TV Streamer as a Thread Border Router and Matter wifi. I share my credentials and now the Google Streamer is my main Border Router.

image

I connect my Matter devices with my Google Home App. I can share my Matter over wifi devices with Home Assistant.

But i cant share my Thread devices with Home Assistant. In Google Home, I can link my Thread device with more Apps. I select Home Assistant and the Home Assistant will open. In the Home Assistant App, i push select device and the link process is starting. But it ends with a message, that this device can´t link.

The same with sharing the Code.

I try it with Nanoleaf Essentials Bulbs and a Eve Motion Blind.

I make a couple of restart and resets on the matter devices.

Here are the logs:

2024-09-27 22:15:55.721 (MainThread) INFO [matter_server.server.device_controller] Starting Matter commissioning with code using Node ID 43.
2024-09-27 22:16:25.736 (Dummy-2) CHIP_ERROR [chip.native.CTL] Discovery timed out
2024-09-27 22:16:25.736 (Dummy-2) CHIP_ERROR [chip.native.ZCL] Secure Pairing Failed
2024-09-27 22:16:25.736 (Dummy-2) WARNING [chip.ChipDeviceCtrl] Failed to establish secure session to device: src/controller/python/ChipDeviceController-ScriptDevicePairingDelegate.cpp:89: CHIP Error 0x00000003: Incorrect state
2024-09-27 22:16:25.737 (MainThread) ERROR [matter_server.server.client_handler] [140065491564240] Error while handling: commission_with_code: Commission with code failed for node 43.

And my Matter Settings:

No one have an idea?

How does your Home Assistant looks like (type/board etc.)?

2024-09-27 22:16:25.736 (Dummy-2) CHIP_ERROR [chip.native.CTL] Discovery timed out

From that line it seems like finding the device via mDNS/DNS-SD did not work. Do you have the two devices on the same network (L2)? What networking gear do you have? Some Ubiquiti has Multicast optimization options which are known to be problematic.

  • Core2024.9.3
  • Supervisor2024.09.1
  • Operating System13.1
  • Frontend20240909.1

Home Assistant running in a Proxmoxx VM. I did the same test with Home Assistant on a Raspberry Pi4.

My Thread devices, my Home Assistant and my Phone with the App are all in the same network. My network Gear is a Fritzbox (AVM) system. I have a IPv6 connection from my provider.

I make one more test. I delete the devices from Google Home and try to connect it direct to Home Assistant. Home Assistant found the device, start with the connection and ends with an error.

Proxmox (or rather the Linux bridge implementation) uses Multicast snooping and only forwards multicasts to the ports it deems necessary. Can you try disabling Multicast snooping. Check this Proxmox forum thread: Disable Multicast Snooping | Proxmox Support Forum. You can simply use the echo as root on the Proxmox shell for a one-off test, it will reset that setting when you restart though.

Well, I guess if Raspberry Pi 4 with HAOS showed the same behavior this can’t be it :see_no_evil:

The way device sharing works is that the device makes itself discoverable with the service _matterc._udp (c for commissioning). The Discovery timed out message means that the Matter Server was not able to find the device annoucing with that service (and/or the discriminator did not match).

One thing to note is that the Google TV Streamer who acts as a Thread Border Router forwards the mDNS/DNS-SD entries on behalf of the Thread device (SRP). I’ve previously seen that stale mDNS/DNS-SD entries on the SRP server caused issues. What I would recommend to try is to restart both the Google TV Streamer and the Home Assistant instance, and to be certain it is also not a device invovlement, maybe also your Thread device.

Hello,

now is running.

I change in Home Assistant the IPv6 settings from static to Automatic.

My eve and Nanoleaf devices are now in Homeassistant

1 Like

Dear agners,

Thank you very much for your support