How to Fix Inovelli Device Not Responding After Hub Restart
- Device hasn't re-established with the restarted hub
- Integration slow to reconnect
- Mesh needs to re-form after the restart
Problem Description
Your Inovelli switch shows 'Unavailable' in Home Assistant after a hub restart and does not come back online. After a restart, the Z-Wave JS or ZHA integration re-establishes communication with every device — this takes 3-10 minutes with large networks. If the switch remains unavailable after that, the Z-Wave controller may have lost its serial connection, or the switch's radio needs a physical reboot via the air gap.
Why This Happens in Real Homes
An Inovelli switch not responding after a hub restart usually just hasn't re-established communication with the freshly-restarted hub yet — after a Zigbee2MQTT or Z-Wave JS restart, the network and integration take a little time to re-form and re-sync device states, so devices can briefly show unavailable.
Give the network a few minutes to settle after the restart, then re-ping or re-interview the switch to re-establish it, and confirm the integration fully reconnected (not stuck initializing). Physically toggling the switch prompts it to report its state. If it stays unresponsive, reload the integration or entity, verify the coordinator/controller re-initialized, and update firmware. Most post-restart unavailability clears once the network re-forms.
Symptoms
- Not responding after hub restart
- Unavailable after restarting the hub
- Switch dead after HA/hub reboot
- Doesn't reconnect post-restart
- Needs re-pair after hub restart
- Unresponsive following a restart
- Lost after hub reboot
- Won't reconnect to the hub
Recognize these? Here's what usually causes it.
Common Causes
- Device hasn't re-established with the restarted hub
- Integration slow to reconnect
- Mesh needs to re-form after the restart
- Device unreachable momentarily
- Coordinator/controller re-init
- Stale entity state
- Firmware issue
- Network needs to settle
Most fixes happen in the first 3 steps.
Do not mass-rejoin devices if only post-boot interview state is stale.
Tools & Requirements
Step-by-Step Solution
Wait 5-10 minutes after the hub restart
When Home Assistant restarts, the Z-Wave JS or ZHA integration reinitializes and re-establishes communication with every device. For Z-Wave: the controller sends NOP (No Operation) commands to each node to verify it is alive. With 30+ Z-Wave devices, this process takes 3-5 minutes. For Zigbee: the coordinator sends check-in requests to all routers and end devices. During this period, devices may show 'Unavailable' in Home Assistant. Wait at least 5 minutes before concluding that a device is not responding. Check the Z-Wave JS or ZHA log for progress.
Check the Z-Wave controller status
For Z-Wave Red Series: in Home Assistant, go to Settings > Devices & Services > Z-Wave JS. Check the controller status. If it shows 'Disconnected' or 'Error': the Z-Wave USB stick (Aeotec Z-Stick, Zooz ZST10, etc.) may have lost its serial connection. Unplug the Z-Wave stick, wait 10 seconds, replug it. In Home Assistant, reload the Z-Wave JS integration. A known problem: USB power management on the host OS puts the Z-Wave stick to sleep. Disable USB autosuspend on the stick's USB port.
Ping the unresponsive switch
In Z-Wave JS: go to the device page for the Inovelli switch > click 'Ping' or 'Test Node.' If the ping succeeds: the switch is communicating but Home Assistant may not have re-subscribed to its events. Reload the Z-Wave JS integration or restart Home Assistant. If the ping fails: the switch is not responding at the Z-Wave level. Check if the switch has power (the LED bar should be visible). Try pressing the paddle physically — if the light responds to the physical press, the switch has power but its Z-Wave radio may be hung.
Air-gap the switch to force a radio reboot
Inovelli switches have an 'air gap' feature: pull the bottom of the paddle outward (toward you) until it clicks. This physically disconnects the switch from power. Wait 10 seconds, push the paddle back in. The switch reboots completely, including its Z-Wave or Zigbee radio. After the reboot, it re-joins the network and responds to hub commands. This is more effective than a breaker cycle because it fully power-drains the switch's capacitors — a breaker cycle sometimes does not fully cut power on no-neutral installations.
Heal the network route for persistent issues
If the same switch consistently goes unresponsive after hub restarts: its Z-Wave route may be through a device that takes longer to initialize. In Z-Wave JS: go to the switch device > click 'Re-interview Node' to force the controller to rebuild communication with that specific node. Then click 'Heal Node' to optimize its route. Do not run a full network heal unless you have time to wait (it can take 30+ minutes with large networks and causes temporary disruption). For Zigbee Blue Series: removing and re-adding the device to ZHA can fix persistent routing issues.
Quick Solutions
Still having issues? This is usually the deeper cause below.
If the hub reconnects then drops every few minutes, check for an IP conflict — two devices sharing the same DHCP address fight each other continuously.
Post-restart validation prevents hidden automation failures.
Hub disconnections that cycle repeatedly are almost always IP conflicts — two devices fighting over the same DHCP lease after a router restart.
- Device hasn't re-established with the restarted hub
- Integration slow to reconnect
- Mesh needs to re-form after the restart
- Device unreachable momentarily
- Coordinator/controller re-init
Before you go — try one of these (they fix most cases).
Official Manufacturer Manual
Inovelli provides official product documentation through their online manual rather than downloadable PDF. Access setup guides, troubleshooting steps, and product specifications for your Inovelli Post-Restart Recovery.
Source: help.inovelli.com
Need More Help? Inovelli Support
Note: The contact information below connects you directly to Inovelli's official customer support team, not Trunetto. They can help with warranty claims, device replacements, and advanced technical issues.