Several IOT devices not reachable since router upgrade / HA connectivity issues #138

New issue

Open

opened 2026-08-07 19:19:03 +02:00 by rhandos · 0 comments

rhandos commented

2026-08-07 19:19:03 +02:00

Member

The two Dreame vacuums StaubiV2 (10.89.212.233) and Staubi (10.89.212.232) cannot connect to the new MQTT broker (club-assistant.ccchh.net:1883). Maybe the new broker isn't reachable on the ccchh-iot network? [FIXED]
The main room ESPHome Sensirion SCD41 CO2 sensor is no longer reachable. [FIXED]
The thermostats connected via RaspberryMatic (10.89.213.29) / Homematic are no longer reachable via HA. The web interface is reachable via the above IP adress, the thermostat devices are showing in Raspberrymatic. However, the Homematic integration cannot connect to it. Not sure why
The EH22 WLED sign does no longer seem to have a static IP or a domain name. Its former IP 10.89.212.44 is no longer reachable, there seems to be no corresponding entry in auth-dns/zones/ccchh.net.zone
The WLED integration (specifially the update entity) seems to be unable connect outside the local network to download device updates ("Invalid response from WLED API: Could not download requested WLED version '16.0.1' from https://github.com/wled/WLED/releases/download/v16.0.1/WLED_16.0.1_ESP32.bin"). This happened repeatedly over several days and with the remote files available via other devices, so it seems like a general connectivity issue and not due to GitHub's stellar uptime numbers. The update neither works directly from the WLED web interfaces (http://[IP]/update), though that might be the same issue, depending on if the WLED API simply triggers an on-device update or if the integration tries to push an OTA update itself.

I am really sorry this issue mostly amounts to "these devices don't work plz fix" but networking is by far my weakest field, so my ability to troubleshoot is very limited Q_Q I'd be happy to meet with an infra team member on an upcoming evening to further debug this with somebody with direct access to the router config (and way more network knowledge than me :3)

Since the router upgrade last sunday, several IOT devices associated with Club Assistant are no longer reachable. These are the devices I couldn't fix via the HA interface or where I was missing credentials for further fixes outside HA: - [x] The two Dreame vacuums **StaubiV2 (10.89.212.233)** and **Staubi (10.89.212.232)** cannot connect to the new MQTT broker (club-assistant.ccchh.net:1883). Maybe the new broker isn't reachable on the ccchh-iot network? [FIXED] - [x] The **main room ESPHome Sensirion SCD41 CO2 sensor** is no longer reachable. [FIXED] - [ ] The **thermostats** connected via RaspberryMatic (10.89.213.29) / Homematic are no longer reachable via HA. The web interface is reachable via the above IP adress, the thermostat devices are showing in Raspberrymatic. However, the Homematic integration cannot connect to it. Not sure why - [ ] The **EH22 WLED sign** does no longer seem to have a static IP or a domain name. Its former IP 10.89.212.44 is no longer reachable, there seems to be no corresponding entry in auth-dns/zones/ccchh.net.zone - [ ] The **WLED** integration (specifially the update entity) seems to be unable connect outside the local network to download device updates ("Invalid response from WLED API: Could not download requested WLED version '16.0.1' from https://github.com/wled/WLED/releases/download/v16.0.1/WLED_16.0.1_ESP32.bin"). This happened repeatedly over several days and with the remote files available via other devices, so it seems like a general connectivity issue and not due to GitHub's stellar uptime numbers. The update neither works directly from the WLED web interfaces (http://[IP]/update), though that might be the same issue, depending on if the WLED API simply triggers an on-device update or if the integration tries to push an OTA update itself. I am really sorry this issue mostly amounts to "these devices don't work plz fix" but networking is by far my weakest field, so my ability to troubleshoot is very limited Q_Q I'd be happy to meet with an infra team member on an upcoming evening to further debug this with somebody with direct access to the router config (and way more network knowledge than me :3)