# Manually editing Z-Wave routes **URL:** \ **Category:** Questions & Help\ **Tags:** z-wave\ **Created:** [August 31, 2024, 11:09pm UTC](https://community.homey.app/t/manually-editing-z-wave-routes/115304 "2024-08-31T23:09:53Z")\ **Posts on this page:** 1\ **Showing post:** 11
**Author:** ![DirkG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dirkg/32/118897_2.png) [@DirkG](https://community.homey.app/u/DirkG)\ **Post date:** [September 2, 2024, 1:00pm UTC](https://community.homey.app/t/manually-editing-z-wave-routes/115304/11 "2024-09-02T13:00:01Z")
First of all, It wasn’t very smart to start with adding the battery-powered sensors first. They don’t act as router and therefore cannot forward the Z-Wave signal for other devices. And if they are from the beginning too far away to Homey or a router, the chance is small that they will integrate into the Z-Wave network on their own. 12 out of 14 devices which are not reachable or lose the connection from time to time are battery-operated devices. And 10 of these 12 devices were added first. All devices with an **Unknown** in the **Route** column (ID 4, 7, 9, 45, 46) have most likely lost the connection to the Z-Wave network completely. If you are unable to integrate them using the “Heal” function, these devices have to be deleted and added again. Btw, to “heal” battery-operated devices, they must be woken up manually!!! It’s noticeable that all devices, 33 pcs., are included with the S2 security standard. This is the first time I’ve seen a Z-Wave network where all devices have been included with the security standard. This should not really be a problem with an HP23, I assume that you have an HP23, but with the HP19 (and earlier) this could lead to problems such as delays. The reason for this is that devices with the S2 standard send more data than devices without the security standard and it also requires more processing power. If there were problems such as delays with HP19 (and earlier), these could often be eliminated by deleting the devices and adding them again without the security standard. At the moment, however, it’s only possible to add devices “unsecure” that ask for a PIN during inclusion, which means the devices that are labeled “Secure (Authenticated)” in Developer Tools. > **[Connecting Z-Wave devices in unsecure mode](https://support.homey.app/hc/en-us/articles/4410500384274-Connecting-Z-Wave-devices-in-unsecure-mode)** > > It's possible to connect Homey with some Z-Wave devices in unsecure mode. When adding such device, simply type 00000 as the PIN code. What is also noticeable is that many devices have a relatively high “Tx Error” value. Ideally, this should at least be 0 % for mains-powered devices and low for battery-powered devices. My suggestion is to try to repair all devices using the “Heal” function (battery-operated devices must be woken up!!!) and then observe the functionality of the devices. If there are still problems, please contact Athom support. > [@Giovanni\_Dienstmann](#): > > In my list attached, the “(Relay)” ones are the 2PM. They add a third item for the whole bunch, separately from the two lights it controls. Ok, what’s the problem with this? > [@Giovanni\_Dienstmann](#): > > I’ve also been experiencing another issue which may be related: the batteries of 4 of 6 of my Aeotec motion sensors died within a week Maybe because of this: > [@Giovanni\_Dienstmann](#): > > I had four Aeotec Trisensors clearing motion every 5 seconds. The default setting is 240 seconds. Even then, I don’t think the battery should be flat after a week. I assume that this problem has also to do with the unstable connections and the sensor keeps trying to connect to the Z-Wave network again and again. --- _[View the full topic](https://community.homey.app/t/manually-editing-z-wave-routes/115304)._