Matter device pairable to Apple Home and Tado, but not to Home Assistant

citronjardin · October 22, 2025, 6:20am

Hello,

I’m running a setup with two Matter fabrics: Apple Home as the “frontend” for my family and Home Assistant as the “backend” for advanced automations. Currently, I have 38 Matter devices joined to both fabrics. Most of them use Thread, and my Thread Border Router (TBR) is a HomePod. Home Assistant is running on a Raspberry Pi 5 with Home Assistant OS 16.2, Core 2025.10.3, Supervisor 2025.10.0, Frontend 20251001.4 and the lastest version of the Matter integration (I think, I didn’t find a version number for it).

I recently installed several Tado Smart Radiator Thermostat X devices. They worked well initially — successfully paired with Apple Home, Home Assistant, and also the Tado cloud Matter fabric (used for their proprietary features like smart schedules, room sync, etc.). So, these thermostats were part of three fabrics simultaneously.

However, as of yesterday, all my Tado Smart Radiator Thermostat X units became unavailable in Home Assistant only. They are still online and responsive in both Apple Home and Tado. Since then, they’ve never reconnected to Home Assistant. Interestingly, my Tado Wireless Thermostat X remains available in all three fabrics.

I tried to :

Reset one of the radiator thermostats.
Pair it with Tado fabric then share to Home Assistant → looping indefinitely.
Pair in different orders (Home Assistant first, Apple first, etc.) → still fails.
Change the Apple Home controller from a HomePod to an Apple TV (not sure if it changes to TBR) but it still fails.

The device can still be paired with Apple Home or Tado, but not with Home Assistant.

When attempting to pair in Home Assistant, I see:

[matter_server.server.device_controller] <Node:33> Retrying node setup in 60 seconds...
2025-10-21 21:57:24.762 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:36711i with Node: <0000000000000000, 0> S:0 M:201242931] (U) Msg Retransmission to 0:0000000000000000 failure (max retries:4)
2025-10-21 21:57:35.798 (Dummy-2) CHIP_ERROR [chip.native.SC] PASESession timed out while waiting for a response from the peer. Expected message type was 33

And repeatedly throughout the day:

2025-10-22 07:55:54.001 (MainThread) INFO [matter_server.server.sdk] <Node:34> Attempting to establish CASE session... (attempt 2 of 2)
2025-10-22 07:55:57.141 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from peer <0000000000000021, 1>. Current state was 1

It looks like Home Assistant keeps trying to talk to the Tado devices but never succeeds (not sure of that but these logs didn’t show up before the issue).

Is it safe to share my full Matter log? If so, I can provide it here, maybe I’m missing something important in it.

Some discussions suggest issues like:

mDNS configuration problems
IPv6 being disabled
Multiple subnets in the network
TBR not functioning properly

However, this confuses me : if any of these were the cause, wouldn’t Apple Home and Tado also fail to reach the devices? Here, both are still working fine.

Any ideas ? Could this issue be caused by Tado? Is it possible that a recent firmware update introduced a bug that affects only Home Assistant?

Thanks in advance

afsy_d · October 22, 2025, 9:23pm

Different situation here where a Sonoff minirm4 suddenly stopped talking to HA, however only linked to one matter fabric. The error is the same, and I found the same (confusing) discussions.

Recently heard that there is some fuss with Taro as they are changing some features to only be available if you have a subscription. One example would be that you can Bo longer change the temperature of a single room.

This however does not mean you can’t ‘see’ them anymore in matter.

wmaker · October 23, 2025, 7:03pm

The “PASE” errors means that HA at one time had successfully commissioned the device, but is now trying to setup an “operational” session to control the device and this is failing. This is usually due to a networking problem, and my guess is that HA/Matter does not have a route (or at least one that is not stale) to the Apple Home. Not clear what could cause this, but it has been known to happen. If rebooting HA (the whole thing) does not resolve the problem, then there is some other networking issue likely outside of HA.

citronjardin · October 24, 2025, 6:15am

Thank you for your reply. Unfortunately, rebooting HA didn’t resolve the issue.
Could the routing problem affect only my Smart Radiator Thermostat?
As far as I understand, all 38 of my Matter-over-Thread devices are on the same Thread network. Since all the other devices are working perfectly, am I right to think there’s no network issue? Since a network problem would affect all devices ?

wmaker · October 24, 2025, 6:32pm

I had to re-read this a few times. I first thought all your Thread devices were unavailable in HA, but after re-reading I think what you are saying is that all are available in HA except for your “all my Tado Smart Radiator Thermostat X units” which use to be available in HA but are now no longer.

Assuming I’m now in sync with you, if HA can talk to any of your Thread devices, and all your Thread devices are on the Home Pod TBR, then no it is not a routing issue in HA.

If your Tado SRTX units are controllable in Apple Home, and HA Matter can talk to the other Thread devices, then the Tado SRTX units “should” be commission-able and controllable in HA as well. Because they are not, and from the logs leaves me rather perplexed. I’m kind guessing that there is a timing issue with the commissioning and operational phases that Matter goes through between controller and device. I myself had an issue a couple of years ago where HA would get through the CASE phase of commissioning but would fail the PASE phase. I was using an App to do the commissioning. My solution was to instead use the Matter Server directly to do the commissioning, so maybe you should try using the Matter Server UI to commission an existing device and see if that works.

afsy_d · October 24, 2025, 9:30pm

While your feedback seems useful and it is certainly with a shot, it seems strange that it stopped working all of a sudden.

Can you contact the support of Taxi en Tell them you are no longer able to control the devices? Did you perform am update on the Task devices or HA?

citronjardin · October 26, 2025, 10:15am

I contacted Tado in parallel with this post, but they haven’t responded yet.

This morning, I moved a piece of furniture, which forced me to unplug my HomePod. After plugging it back in, everything started working again. It seems the problem came from my HomePod, perhaps a connection issue where the TBR was blocking traffic only for my Tado devices. I should have tried restarting it sooner.

Thank you all for your replies!

afsy_d · October 26, 2025, 3:25pm

Haha that is very interesting. Thank you for posting your findings!