# Report unreachable Z-wave devices **URL:** \ **Category:** Ideas & Suggestions\ **Created:** [December 14, 2019, 11:09am UTC](https://community.homey.app/t/report-unreachable-z-wave-devices/22493 "2019-12-14T11:09:19Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![jwstroes](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jwstroes/32/12687_2.png) [@jwstroes](https://community.homey.app/u/jwstroes)\ **Post date:** [December 14, 2019, 11:09am UTC](https://community.homey.app/t/report-unreachable-z-wave-devices/22493/1 "2019-12-14T11:09:19Z")
I believe I am not the only one having occasional problems with unreachable Z-wave devices. You can easily spot them on [developer.athom.com/tools/zwave](http://developer.athom.com/tools/zwave). But wouldn’t it be nice to be notified by Homey about such malfunctions in stead of experiencing suddenly not working flows? It would be even better to have a repair option in Homey. ---
**Author:** ![PetervdK](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/petervdk/32/20669_2.png) [@PetervdK](https://community.homey.app/u/PetervdK)\ **Post date:** [December 14, 2019, 11:19am UTC](https://community.homey.app/t/report-unreachable-z-wave-devices/22493/2 "2019-12-14T11:19:34Z")
Unreachable doesn’t mean it is unusable. It just states that it has missed a request at some time for whatever reason. Mostly the device is working fine. You can try that by using the “Test” function behind the 3 dots on the end. Or, in case of a plug, send a “basic on (or off)” command. In 99.9% of the time it will switch immediately. If the device is marked “unknown” in the “Route” column it is really unusable. This is what Athom replied when i asked: > [@](#): > > Hi Peter, > > Unreachable nodes are simply not reachable. This could be because they’re battery devices. They may start working again over time. > > A node is marked unreachable when Homey tried to communicate with it and it didn’t get a response. That’s all there’s to it. ---
**Author:** ![jwstroes](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jwstroes/32/12687_2.png) [@jwstroes](https://community.homey.app/u/jwstroes)\ **Post date:** [December 14, 2019, 2:54pm UTC](https://community.homey.app/t/report-unreachable-z-wave-devices/22493/3 "2019-12-14T14:54:22Z")
A useful correction. Thanks. Still, I have unusable devices at least every month. A notification would be very useful. ---
**Author:** ![PetervdK](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/petervdk/32/20669_2.png) [@PetervdK](https://community.homey.app/u/PetervdK)\ **Post date:** [December 14, 2019, 4:15pm UTC](https://community.homey.app/t/report-unreachable-z-wave-devices/22493/4 "2019-12-14T16:15:50Z")
Then define unusable. Empty battery? Do you have to re-pair? Or are they working again after pressing a button? You might try the “A device hasn’t reported” trigger card, but that only works if the device stops responding to Homey completely. ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/4/e/4ed603a8be8e11aa60f2e5cd4357d6319700ee93.jpeg) ---
**Author:** ![rzarajczyk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rzarajczyk/32/8447_2.png) [@rzarajczyk](https://community.homey.app/u/rzarajczyk)\ **Post date:** [December 23, 2019, 7:17pm UTC](https://community.homey.app/t/report-unreachable-z-wave-devices/22493/5 "2019-12-23T19:17:23Z")
I agree it would be useful to have flow cards: - Z-wave device hasn’t acknowledge command - Send z-wave “Test” command - Heal device And generally everything which is available in developer tools panel should be available via flow cards. ---
**Author:** ![jwstroes](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jwstroes/32/12687_2.png) [@jwstroes](https://community.homey.app/u/jwstroes)\ **Post date:** [December 23, 2019, 8:09pm UTC](https://community.homey.app/t/report-unreachable-z-wave-devices/22493/6 "2019-12-23T20:09:10Z")
What I meant with unusable is not responding to commands from Homey (either directly or in a flow). The most common solution, for wall plugs, is to remove the plug from the socket and re-insert it. Your “hasn’t reported” card might be a very good idea to get notified. I will try that. ---
**Author:** ![PetervdK](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/petervdk/32/20669_2.png) [@PetervdK](https://community.homey.app/u/PetervdK)\ **Post date:** [December 23, 2019, 10:43pm UTC](https://community.homey.app/t/report-unreachable-z-wave-devices/22493/7 "2019-12-23T22:43:37Z")
What brand are the plugs? ---
**Author:** ![jwstroes](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jwstroes/32/12687_2.png) [@jwstroes](https://community.homey.app/u/jwstroes)\ **Post date:** [December 24, 2019, 9:30am UTC](https://community.homey.app/t/report-unreachable-z-wave-devices/22493/8 "2019-12-24T09:30:59Z")
I have Neo Coolcam and Fibaro. It is not only a price difference. With Fibaro I have experienced this problem once. A Neo Coolcam plug typically fails 2 to 3 times per year. In 95% of the cases pull-the-plug works. Knowing when to pull-the-plug would be nice. ---
**Author:** ![PetervdK](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/petervdk/32/20669_2.png) [@PetervdK](https://community.homey.app/u/PetervdK)\ **Post date:** [December 24, 2019, 5:34pm UTC](https://community.homey.app/t/report-unreachable-z-wave-devices/22493/9 "2019-12-24T17:34:10Z")
Do you have the latest version of the Coolcam app? Do you have unknown nodes or strange node numbers in the Z-Wave mesh? ---
**Author:** ![jwstroes](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jwstroes/32/12687_2.png) [@jwstroes](https://community.homey.app/u/jwstroes)\ **Post date:** [February 10, 2020, 4:01pm UTC](https://community.homey.app/t/report-unreachable-z-wave-devices/22493/10 "2020-02-10T16:01:13Z")
All apps are updated automatically. And indeed I do have numbers in the routing table that are non-existing nodes like 128 and 132. It feels like my Z-wave mesh is becoming more and more unstable. At this very moment 8 out of 15 devices have an unknown route and do not respond. Heal or restart Homey does not have any effect. Pull-the-plug or deleting and re-including seem to be the only options. Usually. For some devices this will be the second time in a few days pull-the-plug is needed. ---
**Author:** ![PetervdK](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/petervdk/32/20669_2.png) [@PetervdK](https://community.homey.app/u/PetervdK)\ **Post date:** [February 10, 2020, 4:44pm UTC](https://community.homey.app/t/report-unreachable-z-wave-devices/22493/11 "2020-02-10T16:44:54Z")
Ghost nodes generally only appear with unknown devices because the path of unknown devices can’t be determined. Unknown as in removed physically and not unpaired or empty battery so not responding. They are most of the times only marked as unknown after a reboot. ---
**Author:** ![Manu\_F](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/manu_f/32/32192_2.png) [@Manu\_F](https://community.homey.app/u/Manu_F)\ **Post date:** [December 26, 2020, 12:03pm UTC](https://community.homey.app/t/report-unreachable-z-wave-devices/22493/12 "2020-12-26T12:03:46Z")
Hi, I did not want to start a new thread so I am adding my problem here. Everything was working flawlessly before but I have unplugged my homey by accident and after plugging it back in, my z-wave devices are reported as unreachable. Zigbee works. I can find and trigger them on the developer page - so they are working and are connected. But in the app and web app they report the red “!”-sing and won’t work. I have tried un- and replugging the devices but still no response. The devices are everspring / technisat sockets and a fibaro roller shutter… Thanks for any kind of help! ---
**Author:** ![Manu\_F](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/manu_f/32/32192_2.png) [@Manu\_F](https://community.homey.app/u/Manu_F)\ **Post date:** [December 26, 2020, 4:35pm UTC](https://community.homey.app/t/report-unreachable-z-wave-devices/22493/13 "2020-12-26T16:35:03Z")
I tried to add another everspring socket but homey already gives me the red “!” for the two sockets that I own in the menu to choose the device from. How can that be? ---
**Author:** ![PetervdK](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/petervdk/32/20669_2.png) [@PetervdK](https://community.homey.app/u/PetervdK)\ **Post date:** [December 26, 2020, 8:55pm UTC](https://community.homey.app/t/report-unreachable-z-wave-devices/22493/14 "2020-12-26T20:55:37Z")
Did you already try a PTP? ---
**Author:** ![Manu\_F](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/manu_f/32/32192_2.png) [@Manu\_F](https://community.homey.app/u/Manu_F)\ **Post date:** [December 27, 2020, 6:43am UTC](https://community.homey.app/t/report-unreachable-z-wave-devices/22493/15 "2020-12-27T06:43:58Z")
Thanks, yeah, I did. But the ptp was the problem in the first place as the zwave did not work afterwards. I reset the zwave network and restarted homey. Afterwards I was able to add the devices again. Then I unplugged homey again by accident (the socket is a bit flimsy due to child protection) and encountered the same problem. The zwave devices were not working and I could not add more of the same. So I reset again and its working now. Is this a known problem? ---
**Author:** ![PetervdK](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/petervdk/32/20669_2.png) [@PetervdK](https://community.homey.app/u/PetervdK)\ **Post date:** [December 27, 2020, 10:27am UTC](https://community.homey.app/t/report-unreachable-z-wave-devices/22493/16 "2020-12-27T10:27:41Z")
How long did you wait after the PtP? It can take a while before all devices are up & running again and the mesh has settled. Or maybe an app has problems starting, preventing other apps, devices or even the z-wave network to work. ---
**Author:** ![Manu\_F](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/manu_f/32/32192_2.png) [@Manu\_F](https://community.homey.app/u/Manu_F)\ **Post date:** [December 27, 2020, 10:08pm UTC](https://community.homey.app/t/report-unreachable-z-wave-devices/22493/17 "2020-12-27T22:08:19Z")
I’d say long enough 😊 Half an hour maybe or even more. ---
**Author:** ![Manu\_F](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/manu_f/32/32192_2.png) [@Manu\_F](https://community.homey.app/u/Manu_F)\ **Post date:** [December 28, 2020, 1:32pm UTC](https://community.homey.app/t/report-unreachable-z-wave-devices/22493/18 "2020-12-28T13:32:26Z")
@PetervdK Thank you very much for the hint regarding the app. It turns out that the everspring app needs a restart to work again after having unplugged homey… ---
**Author:** ![Roman.Chizhevskiy](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/roman.chizhevskiy/32/44745_2.png) [@Roman.Chizhevskiy](https://community.homey.app/u/Roman.Chizhevskiy)\ **Post date:** [November 16, 2021, 10:36pm UTC](https://community.homey.app/t/report-unreachable-z-wave-devices/22493/19 "2021-11-16T22:36:26Z")
Hi. My situation is exactly like yours. Routes to some devices include unexisting nodes and these devices become completely unusable. Heal does not work. Happens every week. Remove and pair again helps but a lot of work required to restore numerous workflows driving me crazy. Did you find any solution? Should we complain to Homey? Can we activate some logs to find what causes this issue? ---
**Author:** ![Edwin\_D](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/edwin_d/32/136417_2.png) [@Edwin\_D](https://community.homey.app/u/Edwin_D)\ **Post date:** [November 17, 2021, 3:35am UTC](https://community.homey.app/t/report-unreachable-z-wave-devices/22493/20 "2021-11-17T03:35:40Z")
Sounds like there’s an active z-wave router in your home that Homey is no longer aware of but that wasn’t properly unpaired? [Next page](https://community.homey.app/t/report-unreachable-z-wave-devices/22493.md?page=2)