Anyone else having trouble with these switches? It remains connected to my wi-fi network but goes unavailable in HA consistently within 24 hours of setup.
Nothing seems to fix it besides removing and re-pairing – not restarting HA or the Matter add-on, nor reloading the Matter integration.
I’ve got 4. They work fine with the TP-Link Tapo app. I fix it by resetting to factory defaults and always first pair it to HA’s Matter integration from the iOS Companion app.
I understand Matter support is BETA for now. It’s recently-released hardware, with a fix for it in HA Core that landed in 2023.7.1.
Wi-Fi network details: connected to Unifi access points (AP generations 2, 4, and 5). Currently testing if it works better after turning off IGMP Snooping and Multicast Enhancement (as recommended in the Matter docs regarding networking issues like mDNS and multicast).
Hey there!
Have exactly the same issue with S505 and S505D.
I could connect them to HA Matter Integration, adding new devices. But after a while both devices became unavailable.
I’ve found that the switch is coming back online in HA on its own. Do note the switch works consistently from the Tapo app.
Saw errors and warnings in the logs for the Matter Add-On, then a success message, then quiet.
2023-07-13 22:52:02 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 4
2023-07-13 22:52:02 core-matter-server matter_server.server.device_controller[126] WARNING Unable to subscribe to Node 4 as it is unavailable, will retry later in the background.
2023-07-13 23:03:03 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:85135180 on exchange 29570i sendCount: 4 max retries: 4
2023-07-13 23:03:15 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 4
2023-07-13 23:04:19 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:85135181 on exchange 29571i sendCount: 4 max retries: 4
2023-07-13 23:04:27 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 4
2023-07-13 23:05:34 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:85135182 on exchange 29572i sendCount: 4 max retries: 4
2023-07-13 23:05:40 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 4
2023-07-13 23:05:40 core-matter-server matter_server.server.device_controller[126] WARNING Unable to subscribe to Node 4 as it is unavailable, will retry later in the background.
2023-07-13 23:16:41 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:85135183 on exchange 29573i sendCount: 4 max retries: 4
2023-07-13 23:16:53 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 4
2023-07-13 23:18:00 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:85135184 on exchange 29574i sendCount: 4 max retries: 4
2023-07-13 23:18:05 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 4
2023-07-13 23:19:08 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:85135185 on exchange 29575i sendCount: 4 max retries: 4
2023-07-13 23:19:18 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 4
2023-07-13 23:19:18 core-matter-server matter_server.server.device_controller[126] WARNING Unable to subscribe to Node 4 as it is unavailable, will retry later in the background.
2023-07-13 23:30:22 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:85135186 on exchange 29576i sendCount: 4 max retries: 4
2023-07-13 23:30:31 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 4
2023-07-13 23:31:35 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:85135187 on exchange 29577i sendCount: 4 max retries: 4
2023-07-13 23:31:44 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 4
2023-07-13 23:32:46 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:85135188 on exchange 29578i sendCount: 4 max retries: 4
2023-07-13 23:32:56 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 4
2023-07-13 23:32:56 core-matter-server matter_server.server.device_controller[126] WARNING Unable to subscribe to Node 4 as it is unavailable, will retry later in the background.
2023-07-13 23:44:01 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:85135189 on exchange 29579i sendCount: 4 max retries: 4
2023-07-13 23:44:09 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 4
2023-07-13 23:45:10 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:85135190 on exchange 29580i sendCount: 4 max retries: 4
2023-07-13 23:45:22 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 4
2023-07-13 23:46:27 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:85135191 on exchange 29581i sendCount: 4 max retries: 4
2023-07-13 23:46:34 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 4
2023-07-13 23:46:34 core-matter-server matter_server.server.device_controller[126] WARNING Unable to subscribe to Node 4 as it is unavailable, will retry later in the background.
2023-07-13 23:57:39 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:85135192 on exchange 29582i sendCount: 4 max retries: 4
2023-07-13 23:57:47 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 4
2023-07-13 23:58:52 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:85135193 on exchange 29583i sendCount: 4 max retries: 4
2023-07-13 23:59:00 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 4
2023-07-14 00:00:01 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:85135194 on exchange 29584i sendCount: 4 max retries: 4
2023-07-14 00:00:12 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 4
2023-07-14 00:00:12 core-matter-server matter_server.server.device_controller[126] WARNING Unable to subscribe to Node 4 as it is unavailable, will retry later in the background.
2023-07-14 00:11:17 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:85135195 on exchange 29585i sendCount: 4 max retries: 4
2023-07-14 00:11:25 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 4
2023-07-14 00:12:34 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:85135196 on exchange 29586i sendCount: 4 max retries: 4
2023-07-14 00:12:38 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 4
2023-07-14 00:13:41 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:85135197 on exchange 29587i sendCount: 4 max retries: 4
2023-07-14 00:13:51 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 4
2023-07-14 00:13:51 core-matter-server matter_server.server.device_controller[126] WARNING Unable to subscribe to Node 4 as it is unavailable, will retry later in the background.
2023-07-14 00:24:54 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:85135198 on exchange 29588i sendCount: 4 max retries: 4
2023-07-14 00:25:03 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 4
2023-07-14 00:26:07 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:85135199 on exchange 29589i sendCount: 4 max retries: 4
2023-07-14 00:26:16 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 4
2023-07-14 00:27:17 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:85135200 on exchange 29590i sendCount: 4 max retries: 4
2023-07-14 00:27:29 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 4
2023-07-14 00:27:29 core-matter-server matter_server.server.device_controller[126] WARNING Unable to subscribe to Node 4 as it is unavailable, will retry later in the background.
2023-07-14 00:38:31 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:85135201 on exchange 29591i sendCount: 4 max retries: 4
2023-07-14 00:38:41 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 4
2023-07-14 00:39:45 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:85135202 on exchange 29592i sendCount: 4 max retries: 4
2023-07-14 00:39:54 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 4
2023-07-14 00:40:53 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:85135203 on exchange 29593i sendCount: 4 max retries: 4
2023-07-14 00:41:07 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 4
2023-07-14 00:41:07 core-matter-server matter_server.server.device_controller[126] WARNING Unable to subscribe to Node 4 as it is unavailable, will retry later in the background.
2023-07-14 00:52:10 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:85135204 on exchange 29594i sendCount: 4 max retries: 4
2023-07-14 00:52:19 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 4
2023-07-14 00:53:21 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:85135205 on exchange 29595i sendCount: 4 max retries: 4
2023-07-14 00:53:32 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 4
2023-07-14 00:54:38 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:85135206 on exchange 29596i sendCount: 4 max retries: 4
2023-07-14 00:54:45 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 4
2023-07-14 00:54:45 core-matter-server matter_server.server.device_controller[126] WARNING Unable to subscribe to Node 4 as it is unavailable, will retry later in the background.
2023-07-14 01:05:48 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:85135207 on exchange 29597i sendCount: 4 max retries: 4
2023-07-14 01:05:57 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 4
2023-07-14 01:06:59 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:85135208 on exchange 29598i sendCount: 4 max retries: 4
2023-07-14 01:07:10 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 4
2023-07-14 01:08:11 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:85135209 on exchange 29599i sendCount: 4 max retries: 4
2023-07-14 01:08:23 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 4
2023-07-14 01:08:23 core-matter-server matter_server.server.device_controller[126] WARNING Unable to subscribe to Node 4 as it is unavailable, will retry later in the background.
2023-07-14 01:19:23 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:85135210 on exchange 29600i sendCount: 4 max retries: 4
2023-07-14 01:19:36 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 4
2023-07-14 01:20:42 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:85135211 on exchange 29601i sendCount: 4 max retries: 4
2023-07-14 01:20:48 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 4
2023-07-14 01:21:53 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:85135212 on exchange 29602i sendCount: 4 max retries: 4
2023-07-14 01:22:01 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 4
2023-07-14 01:22:01 core-matter-server matter_server.server.device_controller[126] WARNING Unable to subscribe to Node 4 as it is unavailable, will retry later in the background.
2023-07-14 01:33:09 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:85135213 on exchange 29603i sendCount: 4 max retries: 4
2023-07-14 01:33:14 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 4
2023-07-14 01:34:20 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:85135214 on exchange 29604i sendCount: 4 max retries: 4
2023-07-14 01:34:26 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 4
2023-07-14 01:35:32 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:85135215 on exchange 29605i sendCount: 4 max retries: 4
2023-07-14 01:35:39 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 4
2023-07-14 01:35:39 core-matter-server matter_server.server.device_controller[126] WARNING Unable to subscribe to Node 4 as it is unavailable, will retry later in the background.
2023-07-14 01:46:43 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:85135216 on exchange 29606i sendCount: 4 max retries: 4
2023-07-14 01:46:52 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 4
2023-07-14 01:47:52 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:85135217 on exchange 29607i sendCount: 4 max retries: 4
2023-07-14 01:48:04 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 4
2023-07-14 01:49:10 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:85135218 on exchange 29608i sendCount: 4 max retries: 4
2023-07-14 01:49:17 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 4
2023-07-14 01:49:17 core-matter-server matter_server.server.device_controller[126] WARNING Unable to subscribe to Node 4 as it is unavailable, will retry later in the background.
2023-07-14 01:59:17 core-matter-server PersistentStorage[126] INFO DeleteSdkKey: g/s/q6eTUyjF80t8Zcjvbe8IdA==
2023-07-14 01:59:17 core-matter-server PersistentStorage[126] INFO Committing...
2023-07-14 01:59:17 core-matter-server PersistentStorage[126] INFO SetSdkKey: f/1/s/0000000000000004 = b'\x150\x03\x10\xbc\x9f"\xf4\xc3n.)\x91U\x9bM\x01\xa6\x93\xc10\x04 \x95\xf6\xa5;<\x1a\xec\x9d/k\xec\x11\x8eO4Hl\xbd\xdb^\n\xda\x88\xa2\x1e\x00W\x8c^\xf6\x9f\xf50\x05\x0c\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x18'
2023-07-14 01:59:17 core-matter-server PersistentStorage[126] INFO Committing...
2023-07-14 01:59:17 core-matter-server PersistentStorage[126] INFO SetSdkKey: g/s/vJ8i9MNuLimRVZtNAaaTwQ== = b'\x15$\x01\x01$\x02\x04\x18'
2023-07-14 01:59:17 core-matter-server PersistentStorage[126] INFO Committing...
2023-07-14 01:59:18 core-matter-server matter_server.server.device_controller.[node 4][126] INFO Subscription succeeded
I’ve recently found that using the Restart (bottom-right) button on the switch works to bring it back online in HA.
Nothing else works (not restarting the Matter add-on nor reloading the integration nor using my Unifi gear to trigger the switch to reconnect to wifi).
I have the same issue with 3 Matter over Wifi light bulbs (AiDot/Linkind).
I was able to connect/add them to HA with the Matter Beta integration and the integrated Matter Server but they all became unavailable within a few minutes/hours.
Their own app (AiDot) can connect to them and control them without issues. I also see that their WiFi signal strength is strong, so that’s not an issue either.
Lastly, I get this in the logs:
2023-08-18 07:21:06 core-matter-server matter_server.server.device_controller[126] WARNING Unable to subscribe to Node 2 as it is unavailable, will retry later in the background.
2023-08-18 07:21:43 core-matter-server chip.DIS[126] ERROR Timeout waiting for mDNS resolution.
2023-08-18 07:21:57 core-matter-server chip.DIS[126] ERROR OperationalSessionSetup[1:0000000000000003]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:114: CHIP Error 0x00000032: Timeout
2023-08-18 07:22:12 core-matter-server matter_server.server.device_controller[126] WARNING Unable to subscribe to Node 3 as it is unavailable, will retry later in the background.
2023-08-18 07:22:12 core-matter-server matter_server.server.device_controller[126] WARNING Unable to subscribe to Node 1 as it is unavailable, will retry later in the background.
2023-08-18 07:22:58 core-matter-server matter_server.server.device_controller[126] WARNING Unable to subscribe to Node 2 as it is unavailable, will retry later in the background.
Very weird. I get the Beta status but still…
Oh and any kind of restart does not help, I tried:
full restart of HA server
power cycle the lights
reload of the Matter integration
And there’s no available firmware upgrade for the lights.
Having the same issue with 3 Tapo S505 switches, work fine on tapo app, unavailable on HA. Restarting fixed this but later on they go back to unavailable.
Any help is highly appreciated.
Same issue here. I currently have 52 of them wired in. (the first few worked well so I went all in on them - gulp - I still have more to install…). I’m trying HA as they just are pretty much unusable in homeKit.
I have excellent wifi coverage with 5 eero devices.
They seem to be addressable from the Tapo app even when they have disappeared from HA.
Strange thing is that sometimes they disappear from one platform but are still visible and useable in the other platform.
In HA they eventually get into a state where the device entity states that the device is no longer in use - and I could find no other way of bringing them back online other than deleting them repairing them.
Pushing the restart right button - sometimes works. Killing the power via the breaker seems to be the best way to get them to reset.
Does anyone know how to put them manually into pairing mode? Not a full reset (left button 10 secs) but just to pair with another hub. It must be possible as I can do it from the home app - but if the switch is not responsive to home app it doesn’t work.
Let me know if you have any success here. Like you, I’m all in. 37 switches. Works for a bit, then constant disconnects. Tried everything from new router, using HomeKit, reconnecting, etc. At this point I have to think it’s a Matter/Firmware issue but hard to pinpoint.
I’m not totally convinced that the issue is on the local network - I blocked them from internet access using the firewall and all the switch LED lights went red within a few minutes. So I’m not even sure that them dropping out of service is a local issue. Also when they do become available they cause a state change in HA signaling that the switch was either turned on or off. This plays havoc with some automations. You can code around it but shouldn’t have to.
I am uncomfortable having devices installed that are constantly communicating with something on the internet.
So I’m going to give up on them. Asides from the unreliability there is also the glaring security issue.
I was hoping this was going to be an easy migration away from my old failing Insteon switches…
I think is it a problem possibly with the integration, I reported the issue here.
Also, here is what my syslog has - very similar issues I believe:
Sep 25 15:20:51 kruse-pi addon_core_matter_server[754]: 2023-09-25 15:20:51 core-matter-server matter_server.server.device_controller[126] WARNING Unable to subscribe to Node 1 as it is unavailable, will retry later in the background.
Sep 25 15:24:42 kruse-pi addon_core_matter_server[754]: 2023-09-25 15:24:42 core-matter-server matter_server.server.device_controller[126] WARNING Unable to subscribe to Node 1 as it is unavailable, will retry later in the background.
Sep 25 15:28:43 kruse-pi addon_core_matter_server[754]: 2023-09-25 15:28:43 core-matter-server matter_server.server.device_controller[126] WARNING Unable to subscribe to Node 1 as it is unavailable, will retry later in the background.
Sep 25 15:32:53 kruse-pi addon_core_matter_server[754]: 2023-09-25 15:32:53 core-matter-server matter_server.server.device_controller[126] WARNING Unable to subscribe to Node 1 as it is unavailable, will retry later in the background.
Sep 25 15:37:15 kruse-pi addon_core_matter_server[754]: 2023-09-25 15:37:15 core-matter-server matter_server.server.device_controller[126] WARNING Unable to subscribe to Node 1 as it is unavailable, will retry later in the background.
Sep 25 15:41:46 kruse-pi addon_core_matter_server[754]: 2023-09-25 15:41:46 core-matter-server matter_server.server.device_controller[126] WARNING Unable to subscribe to Node 1 as it is unavailable, will retry later in the background.
Sep 25 15:41:57 kruse-pi homeassistant[754]: #033[32m2023-09-25 15:41:57.672 INFO (MainThread) [matter_server.client.connection] Connected to Matter Fabric 2 (379140135655029197), Schema version 4, CHIP SDK Version 2023.6.0#033[0m
Sep 25 15:41:57 kruse-pi homeassistant[754]: #033[32m2023-09-25 15:41:57.710 INFO (MainThread) [matter_server.client] Matter client initialized.#033[0m
Sep 25 15:41:57 kruse-pi homeassistant[754]: #033[32m2023-09-25 15:41:57.711 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.matter#033[0m
Sep 25 15:41:57 kruse-pi homeassistant[754]: #033[32m2023-09-25 15:41:57.712 INFO (MainThread) [homeassistant.components.climate] Setting up climate.matter#033[0m
Sep 25 15:41:57 kruse-pi homeassistant[754]: #033[32m2023-09-25 15:41:57.712 INFO (MainThread) [homeassistant.components.cover] Setting up cover.matter#033[0m
Sep 25 15:41:57 kruse-pi homeassistant[754]: #033[32m2023-09-25 15:41:57.712 INFO (MainThread) [homeassistant.components.event] Setting up event.matter#033[0m
Sep 25 15:41:57 kruse-pi homeassistant[754]: #033[32m2023-09-25 15:41:57.713 INFO (MainThread) [homeassistant.components.light] Setting up light.matter#033[0m
Sep 25 15:41:57 kruse-pi homeassistant[754]: #033[32m2023-09-25 15:41:57.713 INFO (MainThread) [homeassistant.components.lock] Setting up lock.matter#033[0m
Sep 25 15:41:57 kruse-pi homeassistant[754]: #033[32m2023-09-25 15:41:57.713 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.matter#033[0m
Sep 25 15:41:57 kruse-pi homeassistant[754]: #033[32m2023-09-25 15:41:57.714 INFO (MainThread) [homeassistant.components.switch] Setting up switch.matter#033[0m
Sep 25 15:46:26 kruse-pi addon_core_matter_server[754]: 2023-09-25 15:46:26 core-matter-server matter_server.server.device_controller[126] WARNING Unable to subscribe to Node 1 as it is unavailable, will retry later in the background.
Sep 25 15:51:17 kruse-pi addon_core_matter_server[754]: 2023-09-25 15:51:17 core-matter-server matter_server.server.device_controller[126] WARNING Unable to subscribe to Node 1 as it is unavailable, will retry later in the background.
pi@kruse-pi:~$
That may well be the case, But these lights also failed for me on a completely different platform (homekit) in the same manner. I shall move some of my other Matter devices on to HA. To check that out.
Update - it started working last night. I had to reboot my router (and then HA) as my internet connection was not stable, that isssue is gone, but it appears my same problem came back again. So, it appears that “will retry later in the background” ‘sometimes’ - eventually works. But, it definately is an issue.
For some weird reason the “my Leviton” app on my phone is now telling me that my fingerprint is wrong. WTF! (Time for a cell phone reboot - or - I guess I forgot to put on the correct fingerprints when I woke up this morning.)
Update: For my D26HD dimmer, the only way I got it to make it properly reconnect with the HA Matter integraton was that I actually deleted the integration altogether, re-added it (when I re-added it, it alrteady sawe the dimmer switch!!?!!???) - and then it still wasnt reconnecting (same “Node 1” error message).
Finally, holding the light switch in the “on” position for more than 7 seconds reboots it (but not more than 15 seconds which I think is a factory reset) - I had to do that a couple of times and it finally did reconnect. Once connected, it is rock solid and FAST - but what a PITA
I am encountering this issue on a number of S505 devices. They are still on my network and I can control them in the Tapo app, but it seems both home assistant and google lose them at some point and I have to do a factory reset and repair them to get it all working again. This happens every few days, and seems to be the same few devices, I have 24 of them, but only 5 or 6 seem to have this issue.
Since it also happens in google home I don’t think its a home assistant issue, but figured I should post here just in case and to let others know.
Log from the matter server in case it helps anyone.
2023-11-07 17:05:55 core-matter-server PersistentStorage[126] INFO SetSdkKey: f/1/s/0000000000000009 = b'\x150\x03\x10Y\x91Xc\\\x98*\t\xa9\xf7\xfa\x14GHbn0\x04 \x1d\xe9\x91\xf8^j\xc5\xcc\xa7\x89\xd9K\x9bBD\xe3\xfb\x00\xfc\xbaR\x98\xc6\xdf\xe3\x84iR#~\xed\xa80\x05\x0c\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x18'
2023-11-07 17:05:55 core-matter-server PersistentStorage[126] INFO Committing...
2023-11-07 17:05:55 core-matter-server PersistentStorage[126] INFO SetSdkKey: g/s/WZFYY1yYKgmp9/oUR0hibg== = b'\x15$\x01\x01$\x02\t\x18'
2023-11-07 17:05:55 core-matter-server PersistentStorage[126] INFO Committing...
2023-11-07 17:06:04 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:229861225 on exchange 47376i sendCount: 4 max retries: 4
2023-11-07 17:06:05 core-matter-server root[126] INFO Re-subscription succeeded!
2023-11-07 17:06:05 core-matter-server matter_server.server.device_controller.[node 9][126] INFO Re-Subscription succeeded
2023-11-07 17:07:36 core-matter-server chip.DMG[126] ERROR Subscription Liveness timeout with SubscriptionID = 0xd874d2b7, Peer = 01:0000000000000009
2023-11-07 17:07:36 core-matter-server matter_server.server.device_controller.[node 9][126] INFO Previous subscription failed with Error: 50, re-subscribing in 0 ms...
2023-11-07 17:07:49 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:229861234 on exchange 1125r sendCount: 4 max retries: 4
2023-11-07 17:08:07 core-matter-server chip.DIS[126] ERROR Timeout waiting for mDNS resolution.
2023-11-07 17:08:21 core-matter-server chip.DIS[126] ERROR OperationalSessionSetup[1:0000000000000009]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:119: CHIP Error 0x00000032: Timeout
2023-11-07 17:08:21 core-matter-server chip.DMG[126] ERROR Failed to establish CASE for re-subscription with error 'src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:119: CHIP Error 0x00000032: Timeout'
2023-11-07 17:08:21 core-matter-server matter_server.server.device_controller.[node 9][126] INFO Previous subscription failed with Error: 50, re-subscribing in 3110 ms...
2023-11-07 17:08:27 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 4
2023-11-07 17:08:27 core-matter-server chip.DMG[126] ERROR Failed to establish CASE for re-subscription with error 'src/protocols/secure_channel/CASESession.cpp:553: CHIP Error 0x00000032: Timeout'
2023-11-07 17:08:27 core-matter-server matter_server.server.device_controller.[node 35][126] INFO Previous subscription failed with Error: 50, re-subscribing in 4650689 ms...
2023-11-07 17:09:19 core-matter-server chip.DMG[126] ERROR Subscription Liveness timeout with SubscriptionID = 0x4b29c8b0, Peer = 01:0000000000000027
2023-11-07 17:09:19 core-matter-server matter_server.server.device_controller.[node 39][126] INFO Previous subscription failed with Error: 50, re-subscribing in 0 ms...
2023-11-07 17:09:24 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:252138000 on exchange 53445r sendCount: 4 max retries: 4
2023-11-07 17:09:28 core-matter-server PersistentStorage[126] INFO DeleteSdkKey: g/s/MS0UCHFEkbXEl3PPV6YK4A==
2023-11-07 17:09:28 core-matter-server PersistentStorage[126] INFO Committing...
2023-11-07 17:09:28 core-matter-server PersistentStorage[126] INFO SetSdkKey: f/1/s/0000000000000027 = b'\x150\x03\x10%\xdb{0\xfa\x9a8.g\x147\xc8\xda\xf3&\xb90\x04 \x9d\xc13\x10\xee\xee\x9e\x05\xcaR!*\xee\xd9&\xca\x80\x02\xa5pxu\xec\x10\x02\xef\xffq\xe4\x94\x9eD0\x05\x0c\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x18'
2023-11-07 17:09:28 core-matter-server PersistentStorage[126] INFO Committing...
2023-11-07 17:09:28 core-matter-server PersistentStorage[126] INFO SetSdkKey: g/s/Jdt7MPqaOC5nFDfI2vMmuQ== = b"\x15$\x01\x01$\x02'\x18"
2023-11-07 17:09:28 core-matter-server PersistentStorage[126] INFO Committing...
2023-11-07 17:09:36 core-matter-server root[126] INFO Re-subscription succeeded!
2023-11-07 17:09:36 core-matter-server matter_server.server.device_controller.[node 39][126] INFO Re-Subscription succeeded
2023-11-07 17:09:45 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:50864201 on exchange 47378i sendCount: 4 max retries: 4
2023-11-07 17:09:52 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 4
2023-11-07 17:09:52 core-matter-server chip.DMG[126] ERROR Failed to establish CASE for re-subscription with error 'src/protocols/secure_channel/CASESession.cpp:553: CHIP Error 0x00000032: Timeout'
2023-11-07 17:09:52 core-matter-server matter_server.server.device_controller.[node 9][126] INFO Previous subscription failed with Error: 50, re-subscribing in 7258 ms...
2023-11-07 17:10:26 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:50864208 on exchange 47385i sendCount: 4 max retries: 4
2023-11-07 17:10:28 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 4
2023-11-07 17:10:28 core-matter-server chip.DMG[126] ERROR Failed to establish CASE for re-subscription with error 'src/protocols/secure_channel/CASESession.cpp:553: CHIP Error 0x00000032: Timeout'
2023-11-07 17:10:28 core-matter-server matter_server.server.device_controller.[node 9][126] INFO Previous subscription failed with Error: 50, re-subscribing in 8466 ms...
2023-11-07 17:12:10 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 4
2023-11-07 17:12:10 core-matter-server chip.DMG[126] ERROR Failed to establish CASE for re-subscription with error 'src/protocols/secure_channel/CASESession.cpp:553: CHIP Error 0x00000032: Timeout'
2023-11-07 17:12:10 core-matter-server matter_server.server.device_controller.[node 9][126] INFO Previous subscription failed with Error: 50, re-subscribing in 15767 ms...
2023-11-07 17:12:34 core-matter-server chip.DIS[126] ERROR Timeout waiting for mDNS resolution.
2023-11-07 17:12:48 core-matter-server chip.DIS[126] ERROR OperationalSessionSetup[1:0000000000000024]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:119: CHIP Error 0x00000032: Timeout
2023-11-07 17:13:19 core-matter-server chip.DIS[126] ERROR Timeout waiting for mDNS resolution.
2023-11-07 17:13:33 core-matter-server chip.DIS[126] ERROR OperationalSessionSetup[1:0000000000000024]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:119: CHIP Error 0x00000032: Timeout
2023-11-07 17:13:42 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 4
2023-11-07 17:13:42 core-matter-server chip.DMG[126] ERROR Failed to establish CASE for re-subscription with error 'src/protocols/secure_channel/CASESession.cpp:553: CHIP Error 0x00000032: Timeout'
2023-11-07 17:13:42 core-matter-server matter_server.server.device_controller.[node 9][126] INFO Previous subscription failed with Error: 50, re-subscribing in 36659 ms...
2023-11-07 17:14:04 core-matter-server chip.DIS[126] ERROR Timeout waiting for mDNS resolution.
2023-11-07 17:14:16 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:50864211 on exchange 47388i sendCount: 4 max retries: 4
2023-11-07 17:14:18 core-matter-server chip.DIS[126] ERROR OperationalSessionSetup[1:0000000000000024]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:119: CHIP Error 0x00000032: Timeout
2023-11-07 17:14:18 core-matter-server matter_server.server.device_controller[126] WARNING Unable to subscribe to Node 36 as it is unavailable, will retry later in the background.
2023-11-07 17:14:18 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 4
2023-11-07 17:14:18 core-matter-server chip.DMG[126] ERROR Failed to establish CASE for re-subscription with error 'src/protocols/secure_channel/CASESession.cpp:553: CHIP Error 0x00000032: Timeout'
2023-11-07 17:14:18 core-matter-server matter_server.server.device_controller.[node 9][126] INFO Previous subscription failed with Error: 50, re-subscribing in 32467 ms...
2023-11-07 17:14:44 core-matter-server chip.DIS[126] ERROR Packet to small for mDNS data: 4 bytes
2023-11-07 17:14:44 core-matter-server chip.DIS[126] ERROR Packet to small for mDNS data: 4 bytes
2023-11-07 17:14:44 core-matter-server chip.DIS[126] ERROR Packet to small for mDNS data: 4 bytes
2023-11-07 17:14:44 core-matter-server chip.DIS[126] ERROR Packet to small for mDNS data: 4 bytes
2023-11-07 17:14:44 core-matter-server chip.DIS[126] ERROR Packet to small for mDNS data: 4 bytes
2023-11-07 17:14:44 core-matter-server chip.DIS[126] ERROR Packet to small for mDNS data: 4 bytes
2023-11-07 17:14:45 core-matter-server chip.DIS[126] ERROR Packet to small for mDNS data: 4 bytes
2023-11-07 17:14:45 core-matter-server chip.DIS[126] ERROR Packet to small for mDNS data: 4 bytes
2023-11-07 17:14:45 core-matter-server chip.DIS[126] ERROR Packet to small for mDNS data: 4 bytes
2023-11-07 17:14:45 core-matter-server chip.DIS[126] ERROR Packet to small for mDNS data: 4 bytes
2023-11-07 17:14:45 core-matter-server chip.DIS[126] ERROR Packet to small for mDNS data: 4 bytes
2023-11-07 17:14:45 core-matter-server chip.DIS[126] ERROR Packet to small for mDNS data: 4 bytes
2023-11-07 17:14:45 core-matter-server chip.DIS[126] ERROR Packet to small for mDNS data: 4 bytes
2023-11-07 17:14:45 core-matter-server chip.DIS[126] ERROR Packet to small for mDNS data: 4 bytes
2023-11-07 17:14:45 core-matter-server chip.DIS[126] ERROR Packet to small for mDNS data: 4 bytes
2023-11-07 17:14:45 core-matter-server chip.DIS[126] ERROR Packet to small for mDNS data: 4 bytes
2023-11-07 17:14:45 core-matter-server chip.DIS[126] ERROR Packet to small for mDNS data: 4 bytes
2023-11-07 17:14:45 core-matter-server chip.DIS[126] ERROR Packet to small for mDNS data: 4 bytes
2023-11-07 17:14:46 core-matter-server chip.DIS[126] ERROR Packet to small for mDNS data: 4 bytes
2023-11-07 17:14:46 core-matter-server chip.DIS[126] ERROR Packet to small for mDNS data: 4 bytes
2023-11-07 17:14:46 core-matter-server chip.DIS[126] ERROR Packet to small for mDNS data: 4 bytes
2023-11-07 17:14:46 core-matter-server chip.DIS[126] ERROR Packet to small for mDNS data: 4 bytes
2023-11-07 17:14:46 core-matter-server chip.DIS[126] ERROR Packet to small for mDNS data: 4 bytes
2023-11-07 17:14:46 core-matter-server chip.DIS[126] ERROR Packet to small for mDNS data: 4 bytes
2023-11-07 17:14:46 core-matter-server chip.DIS[126] ERROR Packet to small for mDNS data: 4 bytes
2023-11-07 17:14:46 core-matter-server chip.DIS[126] ERROR Packet to small for mDNS data: 4 bytes
2023-11-07 17:14:46 core-matter-server chip.DIS[126] ERROR Packet to small for mDNS data: 4 bytes
2023-11-07 17:14:46 core-matter-server chip.DIS[126] ERROR Packet to small for mDNS data: 4 bytes
2023-11-07 17:14:46 core-matter-server chip.DIS[126] ERROR Packet to small for mDNS data: 4 bytes
2023-11-07 17:14:46 core-matter-server chip.DIS[126] ERROR Packet to small for mDNS data: 4 bytes
2023-11-07 17:14:47 core-matter-server chip.DIS[126] ERROR Packet to small for mDNS data: 4 bytes
2023-11-07 17:14:47 core-matter-server chip.DIS[126] ERROR Packet to small for mDNS data: 4 bytes
2023-11-07 17:14:47 core-matter-server chip.DIS[126] ERROR Packet to small for mDNS data: 4 bytes
2023-11-07 17:14:47 core-matter-server chip.DIS[126] ERROR Packet to small for mDNS data: 4 bytes
2023-11-07 17:14:47 core-matter-server chip.DIS[126] ERROR Packet to small for mDNS data: 4 bytes
2023-11-07 17:14:47 core-matter-server chip.DIS[126] ERROR Packet to small for mDNS data: 4 bytes
2023-11-07 17:16:54 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 4
2023-11-07 17:16:54 core-matter-server chip.DMG[126] ERROR Failed to establish CASE for re-subscription with error 'src/protocols/secure_channel/CASESession.cpp:553: CHIP Error 0x00000032: Timeout'
2023-11-07 17:16:54 core-matter-server matter_server.server.device_controller.[node 9][126] INFO Previous subscription failed with Error: 50, re-subscribing in 43940 ms...
2023-11-07 17:17:05 core-matter-server chip.DIS[126] ERROR Timeout waiting for mDNS resolution.
2023-11-07 17:17:19 core-matter-server chip.DIS[126] ERROR OperationalSessionSetup[1:0000000000000031]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:119: CHIP Error 0x00000032: Timeout
2023-11-07 17:17:19 core-matter-server chip.DMG[126] ERROR Failed to establish CASE for re-subscription with error 'src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:119: CHIP Error 0x00000032: Timeout'
2023-11-07 17:17:48 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:50864213 on exchange 47394i sendCount: 4 max retries: 4
2023-11-07 17:17:50 core-matter-server chip.SC[126] ERROR CASESession timed out while waiting for a response from the peer. Current state was 4
2023-11-07 17:17:50 core-matter-server chip.DMG[126] ERROR Failed to establish CASE for re-subscription with error 'src/protocols/secure_channel/CASESession.cpp:553: CHIP Error 0x00000032: Timeout'
2023-11-07 17:17:50 core-matter-server matter_server.server.device_controller.[node 9][126] INFO Previous subscription failed with Error: 50, re-subscribing in 144139 ms...
2023-11-07 17:20:43 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:203518392 on exchange 53480r sendCount: 4 max retries: 4
I raise a glass to you all for diving deep in the bleeding edge of Matter while it’s still being developed and integrated, it’s interesting to see the results!
I have almost 50 of these. I have never seen a problem in the Tapo app but they regularly go offline in SmartThings and Google Home. Doing a restart on the device brings them back online. Currently, SmartThings sees 1 offline and Google Home sees 16 offline. So, it’s not just Home Assistant. I opened up a ticket with TP-Link 7 weeks ago. I suggest everyone do the same.
Beginning yesterday afternoon I started having issues commission the Tapo S505 and S505d I’ve been able to commission in the past using Google home as the first addition and then sharing to home assistant via code. But after commission a couple of devices yesterday the last one wouldn’t add to homeassistant and would continue to say “Something went wrong”. While attempting to diagnose the issue I’ve reset a few other devices and those now receive the same error as the others. So once working and commissioned devices will not add to homeassistant anymore. I find this very odd. Attached is the logs for any diagnostics
I completely reset the matter Integration, Matter Python server (Add-on) and removed and reset every light, and rolled back to a previous HomeAssistant Version. After that I was able to add first to google home hub, and then use the Linked Matter services to “share” with HomeAssistant (not using the share with code, but choosing homeassistant. After that I was able to add every light switch, and everything seemed to shape up. So not sure what the underlying problem was, but it is still doable to get these added to HA.
I can definitely confirm that these issues have nothing to do with HA. I have them running through Matter with Homekit and have constant issues of them being unavailable from both HomeKit and the Tapo app. They will be offline on one but online on the other, all while showing as connected with a strong connection on the wifi network. They never actually lose connection, but are unavailable for periods of time, then come back randomly. Resetting via the button works sometimes, but not always. I have rebooted my network multiple times, even installed a new Mikrotik and the issue remains. When they are working, there is almost always a significant delay as well.