Help with Zigbee Routing - NWK_NO_ROUTE:205

Configuration Zigbee
1

Hi all,

Very new here, been using Hubitat for a couple of years but have recently started tinkering with HA. I have recently paired a zigbee Centralite Pearl thermostat using a Coordinator about 5 metres away. I also paired a Sonoff plug at about the same distance. After a few hours the thermostat becomes unresponsive with the error in the Subject line; when I look at the zigbee map it does not show offline.

image
image1722×1595 105 KB

Can anyone provide some troubleshooting tips? I have seen that if I pop the battery out and back in on the thermostat it will start to react to commands, so I guess it is dropping off the network. Also, this is a 2 wire setup for a gas fireplace, no C wire so running on batteries.

2025.4.2: All ZigBee devices unresponsive
2

You don’t have enough devices to make a viable mesh, most likely. The Home Assistant Cookbook - Index

3

I added a few more devices (including another thermostat device) and my new thermostat (called Temp) is seen on the network:

image
image578×513 19.7 KB

But when I try to issue a command the device does not respond:

**2026-01-28 18:16:29.892 DEBUG (MainThread) [zha.zigbee.device] [0x16B5](Zen-01): Device seen - marking the device available and resetting counter**
**2026-01-28 18:16:29.892 DEBUG (MainThread) [zha.zigbee.device] [0x16B5](Zen-01): Update device availability -  device available: True - new availability: True - changed: False**
2026-01-28 18:16:29.892 DEBUG (MainThread) [zha.application.helpers] Device availability checker interval finished
2026-01-28 18:16:30.969 DEBUG (MainThread) [zha.decorators] [<Task pending name='global-updater_GlobalUpdater' coro=<periodic.<locals>.scheduler.<locals>.wrapper() running at /usr/local/lib/python3.13/site-packages/zha/decorators.py:78> cb=[set.remove()]>] executing periodic task [zha.application.helpers::GlobalUpdater.update_listeners]
2026-01-28 18:16:30.969 DEBUG (MainThread) [zha.application.helpers] Global updater interval starting
2026-01-28 18:16:30.969 DEBUG (MainThread) [zha.application.helpers] Global updater interval finished
2026-01-28 18:16:34.881 DEBUG (MainThread) [zigpy.application] Feeding watchdog
2026-01-28 18:16:34.881 DEBUG (MainThread) [zigpy_znp.api] Sending request: SYS.Ping.Req()
2026-01-28 18:16:34.881 DEBUG (MainThread) [serialx.descriptor_transport] Immediately writing b'\xfe\x00!\x01 '
2026-01-28 18:16:34.881 DEBUG (MainThread) [serialx.descriptor_transport] Sent 5 of 5 bytes
2026-01-28 18:16:34.885 DEBUG (MainThread) [serialx.descriptor_transport] Event loop woke up reader
2026-01-28 18:16:34.886 DEBUG (MainThread) [serialx.descriptor_transport] Received b'\xfe\x02a\x01Y\x06='
2026-01-28 18:16:34.886 DEBUG (MainThread) [zigpy_znp.api] Received command: SYS.Ping.Rsp(Capabilities=<MTCapabilities.SYS|AF|ZDO|UTIL|GP|APP_CNF: 1625>)
26**-01-28 18:16:43.930 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] **[140668896027936] Error during service call to climate.set_temperature: Failed to send request: device did not respond**

Any help on how a device can be seen but not respond?

4

6 devices is a pretty weak mesh… The Home Assistant Cookbook - Index
Check some of the info in that section about zigbee.

5

Hello Locutus-JuratiRob and Amanda:

Same issue here.

Unfortunately for me the given answer here was not good enough because my Zigbee mesh did work with “just” 5 devices before. It does also work using a gateway and app instead HA.

Tried all things that seem to have helped others (flashing the stick, reloading HA, rebooting the host, remove the integration, reconfiguring it, unplugging the stick etc. to no avail.

First I saw this using a Sonoff temp/humidity sensor and thought it might be more of a quality issue device vice.
The other day there was a HA update and sometime later the sensor did integrate properly.
I can’t see why…

Next I started with the Thermostats and added a new Sonoff TRVZB. It gets configured in HA but than HA can’t talk to it (no route) and it’s shown in the same way yours does in the screenshot.

Did you find a solution for that?

Best regards
Holger