#SwitchBot Hub 2 repeatedly going offline

1 messages · Page 1 of 1 (latest)

fallow jay
#

I have a SwitchBot Hub 2 that goes offline every 48 hours or so, according to Home Assistant. However, the SwitchBot app shows the Hub 2 as connected to wifi and online. The device itself also shows tat it is connected to wifi.

The Matter Server logs do seem to mention it, but as far as I can gather from the errors, they think the device is offline too:

2025-07-12 10:29:35.335 (MainThread) INFO [matter_server.server.device_controller] <Node:3> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 11
2025-07-12 10:36:20.538 (Dummy-2) CHIP_ERROR [chip.native.DIS] Timeout waiting for mDNS resolution.
2025-07-12 10:36:34.527 (Dummy-2) CHIP_ERROR [chip.native.DIS] OperationalSessionSetup[1:0000000000000003]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:123: CHIP Error 0x00000032: Timeout
2025-07-12 10:36:34.528 (Dummy-2) CHIP_ERROR [chip.native.DMG] Failed to establish CASE for re-subscription with error 'src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:123: CHIP Error 0x00000032: Timeout'
2025-07-12 10:36:34.529 (MainThread) INFO [matter_server.server.device_controller] <Node:3> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 12
2025-07-12 10:48:19.412 (Dummy-2) CHIP_ERROR [chip.native.DIS] Timeout waiting for mDNS resolution.
2025-07-12 10:48:33.402 (Dummy-2) CHIP_ERROR [chip.native.DIS] OperationalSessionSetup[1:0000000000000003]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:123: CHIP Error 0x00000032: Timeout
2025-07-12 10:48:33.403 (Dummy-2) CHIP_ERROR [chip.native.DMG] Failed to establish CASE for re-subscription with error 'src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:123: CHIP Error 0x00000032: Timeout'
2025-07-12 10:48:33.404 (MainThread) INFO [matter_server.server.device_controller] <Node:3> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 13
2025-07-12 10:48:33.405 (MainThread) INFO [matter_server.server.device_controller] <Node:3> Node considered offline, shutdown subscription

It's possible it's something network related on my end, since I use Ubiquiti equipment, but I do not have firewall rules that block Home Assistant and the Hub 2 from talking to one another, and they are both on the same VLAN. Could this be because the Hub 2 is on a dual 2.4/5GHz network? It just stays connected to 2.4 so that seems unlikely but brainstorming here.

I have IGMP Snooping and Broadcast Control off, etc. The usual problems.

Restarting Home Assistant does nothing, I always have to restart the Hub 2 to fix it.

daring laurel
#

As you can see from your log the Matter server cannot resolve the "current" IP address of the switchbot, due to an mDNS resolution timeout. Now it is said that Unifi APs have trouble passing on mDNS messages correctly.
There are a number of reasons why the Matter server cannot resolve the address for the switchbot, and they are probably somewhere hidden in the interplay between the Matter server, your APs and the switchbot. From my observation I can say: WiFi Matter devices that don't at least implement version Matter 1.2 are extremely suffering from this in Unifi environments. Unfortunately, as it seems, your switchbot seems to be on 1.0?

And: Have you tried restarting your AP instead of the switchbot just to see if that also works?

fallow jay
#

I can definitely give that a try, but it's a shame it's at 1.0 when Switchbot literally just started adding Matter to all their products. This one got Matter support within the last year, even.