Why Is Inovelli Device Showing Unavailable in Home Assistant?
- Device dropped from the Zigbee/Z-Wave network
- Hub/integration offline or restarted
- Weak mesh / device unreachable
Problem Description
Your Inovelli switch shows 'Unavailable' in Home Assistant — the entity is greyed out and you cannot control it from the dashboard or automations. This can happen after a Home Assistant restart, a Z-Wave/Zigbee controller disconnection, a physical power loss at the switch, or a corrupted device entry in the integration.
Why This Happens in Real Homes
An Inovelli switch showing "Unavailable" in Home Assistant means HA can't currently reach it — either the device dropped off the Zigbee/Z-Wave network, the mesh can't reach it, or the hub/integration itself had a problem. The switch may be physically fine while its connection to the hub is broken.
Confirm the hub and integration (Zigbee2MQTT, Z-Wave JS) are online, then check the device's connection: strengthen the mesh so it's reachable, re-ping or re-interview it, and if it truly dropped, reconnect/re-pair it. Restart or reload the Home Assistant integration if it's a hub-side glitch. Update firmware, and stabilize the network (channel separation, coordinator placement). A reachable device on a healthy hub shows available again.
Symptoms
- Device shows 'Unavailable' in HA
- Unavailable entity
- Switch greyed out
- No control from HA
- Unavailable status
- Device dropped in HA
- Shows unavailable then returns
- HA can't reach the switch
Recognize these? Here's what usually causes it.
Common Causes
- Device dropped from the Zigbee/Z-Wave network
- Hub/integration offline or restarted
- Weak mesh / device unreachable
- Needs re-interview/reconnect
- Firmware issue
- Coordinator/controller problem
- Network instability
- HA integration issue
Most fixes happen in the first 3 steps.
Do not rejoin repeatedly before fixing mesh quality.
Tools & Requirements
Step-by-Step Solution
Wait for the integration to reconnect
After a Home Assistant restart or a brief network hiccup, Inovelli devices show 'Unavailable' until the Z-Wave JS or ZHA integration re-establishes communication. Z-Wave JS: the controller pings each node on startup — with 30+ devices, this takes 3-5 minutes. ZHA: Zigbee routers check in quickly (under 1 minute), but if the switch is an end device or has a weak route, reconnection takes longer. Wait 5 minutes before assuming the device has a problem.
Check if the switch has power
Look at the physical switch. The LED bar should show a color (configured by parameter 95/97/98). If the LED bar is completely dark: the switch has no power. Check the breaker. If someone pulled the air gap (bottom of paddle pulled out): push it back in. If the breaker is on and the air gap is in but the LED bar is dark: the switch may have a wiring issue — check the line/load/neutral/ground connections in the switch box.
Ping the device from the integration
For Z-Wave Red Series: in Z-Wave JS, go to the device > click 'Ping Node.' If it responds: the switch is online but Home Assistant lost its event subscription — restart the Z-Wave JS integration (Settings > Devices & Services > Z-Wave JS > 3 dots > Reload). For Zigbee Blue Series: in Zigbee2MQTT, check the device page — if 'Last seen' is recent (within minutes): the switch is online. In ZHA: try sending a command to the switch (toggle it) — if it responds, ZHA just needs to re-subscribe.
Check the Z-Wave controller or Zigbee coordinator
If multiple Inovelli devices show 'Unavailable' simultaneously: the controller/coordinator itself may have disconnected. For Z-Wave: check that the USB stick is still detected by the system ('ls /dev/ttyUSB*' or 'ls /dev/ttyACM*' on Linux). USB sticks can disconnect due to power fluctuations. Replug the stick and restart the integration. For Zigbee: check that the coordinator is detected and Zigbee2MQTT or ZHA is running. Check the integration's logs for error messages about the serial connection.
Re-interview or reconfigure the device
If one specific switch stays 'Unavailable' while others are fine: the device's Home Assistant entity may be stale. For Z-Wave: go to the device in Z-Wave JS > click 'Re-interview Node.' This takes 1-3 minutes and refreshes all the switch's capabilities and entities. For Zigbee: in Zigbee2MQTT, click 'Reconfigure' on the device page. If re-interview does not help: remove the device from the integration and re-pair it (this is destructive — you lose automations tied to the old entity IDs).
Quick Solutions
Still having issues? This is usually the deeper cause below.
If this comes back after following these steps, check whether a recent app or firmware update reset a default setting — the fix works, but the setting gets reverted silently.
Track availability drops by time to correlate with network events.
Home Assistant issues that only appear after restart are a well-known quirk — triggers that require prior state history simply can't fire until that history rebuilds.
- Device dropped from the Zigbee/Z-Wave network
- Hub/integration offline or restarted
- Weak mesh / device unreachable
- Needs re-interview/reconnect
- Firmware issue
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 Availability Issues.
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.