Overview
A Z-Wave device may stop working for different reasons. The issue can be related to power supply, wiring, signal strength, routing, gateway communication, device configuration, firmware, or the connected load.
This guide explains the recommended checks to perform when a Z-Wave device does not respond anymore or does not work as expected.
The steps are written for general Z-Wave troubleshooting and can be used for relay devices, dimmers, shutters, sensors, input modules, and battery-powered devices.
Common symptoms
The issue may appear in one or more of the following ways:
The device does not respond to commands.
The device is shown as unavailable, dead, or offline.
The device does not report status changes.
The device does not react to the wall switch or input.
The relay does not click.
The light, shutter, or load does not move or turn on.
Sensor values are not updated.
Battery device does not wake up.
Parameters are missing or not shown.
The device works only sometimes.
The device worked before but stopped after some time.
When a Z-Wave device stops working, troubleshoot in this order:
1. Check if the device has power
First, confirm that the device is powered.
For mains-powered devices, check:
The breaker is ON.
The device has live and neutral connected correctly.
There is voltage between L and N.
The device LED turns on or shows normal indication.
The terminals are tightened correctly.
There are no burned marks, smell, or visible damage.
For battery-powered devices, check:
The battery is installed correctly.
The battery is not empty.
The battery contacts are clean.
The device LED reacts when the button is pressed.
The battery protector has been removed, if applicable.
If the device has no power, it will not communicate with the Z-Wave gateway.
2. Power-cycle the device
A power cycle can clear a temporary state.
For mains-powered devices:
Turn off the breaker.
Wait at least 30 seconds.
Turn the breaker back on.
Wait for the device to boot.
Test the device again.
For battery-powered devices:
Remove the battery.
Wait at least 30 seconds.
Insert the battery again.
Wake up the device according to the manual.
Test the device again.
If the device starts working after a power cycle, the issue may have been temporary.
3. Check the device status in the gateway
Open your Z-Wave gateway and check the device status.
In Home Assistant with Z-Wave JS or Z-Wave JS UI, check if the device is shown as:
| Status | Icon | Meaning |
|---|---|---|
| Alive |  | The device is reachable |
| Asleep |  | Normal state for many battery-powered devices |
| Awake |  | Battery device is awake |
| Dead |  | The gateway cannot communicate with the device |
| Unknown |  | The gateway does not have enough current information |
In Homey the status of the device can be checked in the Homey Developer Tools, where the status is visible under the Flags column.
| Flag | Meaning |
| S2 Authenticated | Included with S2 Authenticated. The device is reachable. Verify if the number under the RX is greater than 0. |
| Unreachable | Indicates a mains-powered node that isn't returning commands, or a battery sensor that missed its expected wake-up intervals |
| Offline, Battery | Battery device which is sleeping. |
| Online, Battery | Battery device reporting. |
If a mains-powered device is shown as dead, check power supply, signal strength, routes, and possible device failure.
If a battery-powered device is shown as asleep, this can be normal. Wake it up before changing settings or testing communication.
4. Test local control
If the device has a local switch input or button, test it locally.
Examples:
Press the wall switch connected to the SW input.
Press the device button, if accessible.
For shutter devices, test open and close from the local switch.
For dimmers, test local ON/OFF or dimming.
For sensors, trigger the sensor manually.
This helps separate a local device problem from a gateway or Z-Wave communication problem.
Result interpretation
| Result | Possible meaning |
|---|---|
| Local control works, gateway control does not | Z-Wave communication, routing, gateway, or association issue |
| Gateway control works, local control does not | Input wiring or input configuration issue |
| Neither local nor gateway control works | Power, wiring, protection, firmware, or hardware issue |
| Device reports status but output does not work | Output wiring, load, parameter, protection, or relay issue |
5. Check signal strength and route quality
Z-Wave is a mesh network. A device can communicate directly with the controller or through other mains-powered Z-Wave devices. --> Troubleshooting Weak Z-Wave Signal: Causes, Impact, and Solutions
Poor signal or bad routing can cause:
Slow response
Missed commands
Missing reports
Device shown as dead
Failed interview
Failed parameter changes
Network Graph
Device statistics
Sent and received packets
Dropped packets
Last Working Route
RSSI, if available
Health Check result, if available
If the signal is weak:
Move the controller away from the computer or hub using a USB extension cable.
Avoid metal cabinets or electrical panels.
Add mains-powered Z-Wave devices to improve the mesh.
Rebuild routes after moving devices.
Test the device closer to the gateway.
Shelly Wave battery-powered devices do not repeat Z-Wave traffic.
6. Ping or test communication
Use the gateway communication test.
In Z-Wave JS UI:
Open the device.
Use Ping, if available.
Check if the device responds.
If the device does not respond:
Check power.
Check signal strength.
Check if the device is asleep.
Move the device closer to the controller for testing.
Rebuild routes if it is mains-powered.
Wake up the device if it is battery-powered.
For battery-powered devices, ping may fail while the device is sleeping. This is normal unless the device does not respond after wake-up.
7. Check for alarms and protection states
Some devices can disable output control if a protection alarm is active.
Check the gateway or device notifications for:
Overcurrent
Overload
Overheat
Overvoltage
Low battery
If a protection alarm is active:
Turn off the power.
Disconnect the load, if safe and applicable.
Check the wiring.
Check the connected load type and power.
Power the device again.
Test with no load or with a small known load, if suitable.
Do not continue using the device if a protection alarm appears repeatedly.
8. Check the connected load
For relay, dimmer, shutter, or output devices, the connected load can cause problems.
Check:
Load type
Load power
Inrush current
Motor type
LED driver type
Transformer type
Pump or fan starting current
Whether an RC snubber is needed
Whether the load is within the device rating
A load can make the device appear faulty if it causes overcurrent, high inrush, or unstable operation.
Common difficult loads include:
LED drivers
Transformers
Motors
Fans
Pumps
Valve actuators
Refrigerators
Air conditioners
Capacitive or inductive loads
If possible, test the device with the load disconnected or with a simple resistive load.
9. Check wiring and terminals
Incorrect or loose wiring can cause the device to stop working or work only sometimes.
With power OFF, check:
L and N are connected correctly.
Output wires are connected to the correct terminals.
SW input wires are connected correctly.
Neutral is present where required.
The load is connected according to the correct wiring diagram.
No wire is loose.
No copper is exposed outside the terminal.
No terminal is damaged.
The device is not installed in a way that causes overheating.
For dry contact relay devices, remember that the output does not provide voltage by itself. The relay only connects the input terminal to the output terminal when active.
10. Check device parameters
Wrong parameters can change how the device behaves. Check the important parameters for the device type.
Relay devices
Check:
Switch input type
Detached mode
Auto OFF timer
Auto ON timer
Contact type NO/NC
Restore state after power failure
Input/output swap, if the device has more outputs
Dimmer devices
Check:
Minimum dimming value
Maximum dimming value
Dimming speed
Switch type
Calibration, if available
Detached mode
Shutter devices
Check:
Shutter operating mode
Calibration status
Input/output swap
Up and down movement times
Manual time settings, if used
Sensor devices
Check:
Battery status
Report thresholds if available
Sensitivity settings
Temperature or humidity offsets, if applicable
If the device behavior changed after parameter changes, restore the parameters to the default values and test again.
11. Refresh values or re-interview the device
If the device is added to the gateway but values or functions are missing, try a refresh or re-interview.
In Z-Wave JS UI:
Open the device.
Run Refresh Values, if values look outdated.
Go to Advanced.
Run Re-interview Node, if functions, parameters, or endpoints are missing.
Wait until the process finishes.
A re-interview makes the gateway read the device information again.
Use it when:
The device is not recognized correctly.
Parameters are missing.
Endpoints are missing.
Sensor values are not shown.
The device was only partially included.
The gateway shows wrong device information.
For battery-powered devices, wake up the device before and during the re-interview.
12. Rebuild routes
If the device communicates poorly or was moved after inclusion, rebuild the route.
In Z-Wave JS UI:
Open the device.
Go to Advanced.
Select Rebuild Routes.
Wait until the process finishes.
Test the device again.
Use this when:
The device was moved.
The controller was moved.
New mains-powered devices were added.
The device is slow to respond.
The device sometimes appears dead.
The route quality is poor.
13. Check firmware version
Check if a newer firmware version is available for the device.
Firmware updates can fix:
Communication issues
Parameter issues
Reporting issues
Calibration issues
Gateway compatibility issues
Stability problems
Before updating:
Make sure the device has stable power.
Keep the device close to the controller if possible.
Do not restart the gateway during the update.
Wait until the update finishes fully.
After a firmware update, check the parameters again. Some settings may change or need to be adjusted.
14. Exclude and include the device again
If the previous steps do not help, exclude and include the device again.
Recommended steps:
Start exclusion from the gateway.
Put the device into exclusion mode according to the manual.
Confirm that the device was removed.
Factory reset the device only if needed.
Move the device close to the gateway.
Start inclusion.
Wait until the interview is fully complete.
Check that all parameters, values, and endpoints are shown.
Move the device to the final location.
Rebuild routes if needed.
A good practice is to include Z-Wave devices close to the gateway. This reduces the chance of missed data packets during inclusion.
15. Factory reset only when needed
Factory reset should be used only as a later step.
A factory reset will remove:
Device parameters
Associations
Gateway connection
Node ID
Routing information
Energy counters, if supported
Calibration data, if supported
After factory reset, the device must be included again.
Use factory reset when:
Exclusion is not possible.
The device is stuck.
The device was moved from another gateway.
The device does not respond to normal recovery steps.
16. When the device may be faulty
The device may have a hardware fault if all of the following are true:
The device has correct power.
Wiring is correct.
The gateway sends commands.
Local control does not work.
Power cycle does not help.
Re-interview does not help.
The device does not respond when close to the gateway.
No parameter setting explains the issue.
No protection alarm explains the issue.
The same load works with another known working device.
The device shows no LED reaction or abnormal LED behavior.
For relay devices, a missing relay click when commanded ON can indicate a relay or output stage problem.
For dimmers, no output with a known supported load can indicate a dimmer stage problem.
For shutter devices, no motor movement after wiring and calibration checks can indicate output, motor, or protection issues.
For battery devices, no LED reaction after replacing the battery can indicate a device fault.
If the device still does not work after these checks, and power, wiring, load, parameters, and communication are confirmed correct, the device may require replacement or warranty review.
Information to collect before contacting support
Before contacting support, collect the following information:
Device model
Firmware version
Gateway model
Z-Wave controller model
Z-Wave JS or gateway software version
Power supply type
Wiring diagram or photo, if safe to provide
Connected load type and power
Battery voltage, for battery devices
Device status in the gateway
Signal strength or Health Check result
Error messages or alarms
Relevant Z-Wave logs
Parameter values that were changed
Result of power cycle
Result of local control test
Result of re-interview
Result of testing close to the gateway
Result after excluding and including again, if performed
This information helps support understand if the issue is caused by wiring, load, signal, gateway configuration, firmware, or hardware.