# ZWave Device unreachable

**URL:** <https://community.homey.app/t/zwave-device-unreachable/111934>\
**Category:** Questions & Help\
**Tags:** z-wave\
**Created:** [June 24, 2024, 3:20pm UTC](https://community.homey.app/t/zwave-device-unreachable/111934 "2024-06-24T15:20:32Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![feRon](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/feron/32/34515_2.png) [@feRon](https://community.homey.app/u/feRon)\
**Post date:** [June 24, 2024, 3:20pm UTC](https://community.homey.app/t/zwave-device-unreachable/111934/1 "2024-06-24T15:20:32Z")

</div>

Hello

I have a Z-Wave Device (Neo Coolcam Door Sensor).It changed the state all the time from on to off. When I have a look on Z-Wave on Homey Developer Tools and will Test the Device I get Node Unreachable.

It should connect over the Aeotec Range Extender. The Aoetec Range Extender I can Test without problems. Is it possible to set, that the Neo Coolcam Sensor 5 has to try to connect only to the Aeotec Range Extender?

 ![Screenshot 2024-06-24 171754](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/e/1/e1033f6962dfa2bbb8bd56fcdb85ceb1eebeb3e1.png)

On the Z-Wave Log I have this entry. Can you see what’s the problem?

[2024-06-24T15:12:57.552Z] Transmit failed with TRANSMIT\_COMPLETE\_NO\_ACK - txStatusReport: {“wTransmitTicks”:“0x1f5”,“bRepeaters”:“0x0”,“rssi\_values\_incoming\_0”:“0x7f”,“rssi\_values\_incoming\_1”:“0x7f”,“rssi\_values\_incoming\_2”:“0x7f”,“rssi\_values\_incoming\_3”:“0x7f”,“rssi\_values\_incoming\_4”:“0x7f”,“bACKChannelNo”:“0x1”,“bLastTxChannelNo”:“0x1”,“bRouteSchemeState”:“0x7”,“pLastUsedRoute\_0”:“0x0”,“pLastUsedRoute\_1”:“0x0”,“pLastUsedRoute\_2”:“0x0”,“pLastUsedRoute\_3”:“0x0”,“pLastUsedRoute\_4”:“0x2”,“bRouteTries”:“0xb”,“bLastFailedLinkFrom”:“0x7”,“bLastFailedLinkTo”:“0x5”,“bUsedTxPower”:“0x0”,“bMeasuredNoiseFloor”:“0x0”,“bDestinationAckUsedTxPower”:“0x0”,“bDestinationAckMeasuredRssi”:“0x0”,“bDestinationAckMeasuredNoiseFloor”:“0x0”}

Best  
feron

---

<div class="post-metadata">

**Author:** ![Caseda](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/caseda/32/138695_2.png) [@Caseda](https://community.homey.app/u/Caseda)\
**Post date:** [June 24, 2024, 4:59pm UTC](https://community.homey.app/t/zwave-device-unreachable/111934/2 "2024-06-24T16:59:45Z")

</div>

it is a battery device, they are only awake to receive signals for like 2-6 times (depending on the wakeup interval) a day for a few minutes (at max) to save on battery life (or the battery would be drained within a week).  
if you have issues with the device suddenly not responding, then probably the battery is dead.

---

<div class="post-metadata">

**Author:** ![feRon](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/feron/32/34515_2.png) [@feRon](https://community.homey.app/u/feRon)\
**Post date:** [June 24, 2024, 5:21pm UTC](https://community.homey.app/t/zwave-device-unreachable/111934/3 "2024-06-24T17:21:36Z")

</div>

Hi Caseda

Thank you for your answer. Yesterday I took the battery out and put it again and then it worked for a few hours. That could be with the battery. But when I test the battery on a battery tester, it shows me OK. But the batterie has a older date from 2019. Could it be that the batterie is too old? I will buy a new one and will test it.

Thanks  
feron

---

<div class="post-metadata">

**Author:** ![feRon](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/feron/32/34515_2.png) [@feRon](https://community.homey.app/u/feRon)\
**Post date:** [June 25, 2024, 4:38pm UTC](https://community.homey.app/t/zwave-device-unreachable/111934/4 "2024-06-25T16:38:17Z")

</div>

Hi Caseda

Today I changed the battery. I still have the same problem. The first time I changed the battery it was Online and now its Offline again (unreachable). Do you have another idea?

Best  
feron

---

<div class="post-metadata">

**Author:** ![Caseda](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/caseda/32/138695_2.png) [@Caseda](https://community.homey.app/u/Caseda)\
**Post date:** [June 25, 2024, 10:34pm UTC](https://community.homey.app/t/zwave-device-unreachable/111934/5 "2024-06-25T22:34:40Z")

</div>

Even with a new battery it is asleep 99.8% of the time, so unless you wake it up manually just before you test, or can time it right when it auto awakens (which I can guarantee you is very, very difficult to do).  
It will be unreachable.

---

<div class="post-metadata">

**Author:** ![ricercar](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ricercar/32/101928_2.png) [@ricercar](https://community.homey.app/u/ricercar)\
**Post date:** [June 26, 2024, 1:48pm UTC](https://community.homey.app/t/zwave-device-unreachable/111934/6 "2024-06-26T13:48:34Z")

</div>

Hello,  
I’ve had the same problem with a few of my NeoCoolcam door sensors (I have more than 20 of those) and had to throw them away
