Z-Wave unreachable issues

[Goshawk29]

First off I am new to homey pro experience and learning the different nomenclature like App Store etc so apoligize in advance if I confuse things.

My main purpose of purchasing homey pro was I wanted to migrate away from my Vivint security system and homey offered z wave radio, zigbee, and IR all in one in their hub.

I have slowly and methodically migrated things over to homey, all these devices worked in Vivint and they were not Vivint specific equipment. Have GE light switches, Jasco/GE outlet plug modules, Remotec outlets, and kwikset door locks.

SO far it has been a nightmare experience in z wave area. I love homey pro app, home automation and possibilities of just having one device for all my needs but z wave setup has caused issues and looking for help/advice. I have been emailing support for months now and can’t seem to find any issues in my setup.

My setup is as follows, 1400 sq ft single story home. Homey pro is located in center of home, kitchen which is open floor layout to dinning room, living room, hallway. Bedrooms, there is only one wall to go through which is the room causing me major issues. The wall is traditional wall, no metal, just plaster.

I have outlet modules in that room that lose connection, and a door lock that becomes unreachable too.

Is there is limit on radio signal homey pro uses? I ask this because I can just simply add the devices where they are are located to my Vivint hub. Where with homey I have to move the hub basically within a few feet for it to see the device. When I move homey back to where I want in located in kitchen, it loses connections with those devices. It appears Vivint panel has much stronger z wave radio than homey but can’t prove that.

I added a lock to homey but it losses connection. I add it back to Vivint and works great sigh. I have trouble email into kwikset app developer so what they say but so far at a lose for range of z wave capabilities. The lock is node 74 and it jumps off of node 2. Those 2 nodes are literally 2 feet apart so should be working.

As a last resort, if I was to nuke my entire z.wave network and start from scratch, do I have to go and “exclude” every device from homey before starting over? Security etc?

Any ideas? I am at a complete loss. Developer app shows reachable, but homey app says unreachable.

[Peter_Kawa]

As you don’t share the ideas of Support:
No ack = no acknowledgement from the device. Homey somehow can reach it, but the device hasn’t always the same reach to Homey and can’t deliver it’s ack.

Distance issue, or too much walls, glass.

Also note Homey’s zwave reach is rather small, I’d put several router devices near Homey (1, 2 or 3 mtrs), to increase reach.

Also look for “chatty” devices, some update values every sec, which can ruin your mesh.
On top of my head, Aeotec sensors could cause massive traffic with default sensor update settings.

[Sharkys]

On the first view, you have problem with Node71. I would suggest to remove it (remove unknown nodes) and pair it again - you also would need to manually repair your flows, eg. using script (ensure you note down the device ID prior removal) : [HOW-TO][Pro][Cloud] - Tool to FIX (advanced) flows after removing and re-adding devices

Also it’s not clear from your list,which of those devices are NON-battery, so they can act as routers. If you have lack of routers and higher distances from Homey, then issues may arise as Peter mentioned.

Als you can try to build ZWAVE map to see or to troubleshoot further.

[HOW-TO][Pro][Cloud] - Z-Wave Route map

Hi, I saw this thread and was inspired to create a script which can do this for you. I made 2 variants: Zigbee Variant Zwave Variant Instructions: Run this script in the WebAPI playground: (make sure to empty the text area first) const main = async function () { console.log('Starting main function...'); let state = await Homey.zwave.getState(); let data = await Homey.zwave.runCommand({ command: 'getNetworkTopology' }); let failed = Homey.zwave.runCo…

[Goshawk29]

Node 71, the one with just simple name of z wave device is actually working now. I am able to control it. Turn it on and off from the homey app (either web or iPhone). On the developer page, when select test, it says node 71 is reachable. On developer page when I send a test frame, get transmit_complete_ok. When I try to heal, get request_timeout. But once again I am able to control it via app so I am at a lose as to what is going on. I will try remove and add it again and see what happens. And this is the outlet that is located within 2 ft of the door lock to help as a repeater.

All my devices are powered except the single door lock. My devices are either a plug in wall outlet, or a hard wired z wave wall light switch. GE Smart Fan switch model 12730, or GE 12729 Z-Wave Wireless Lighting Control Smart Dimmer Toggle Switch. Outlets are GE Z-Wave Wireless Smart Lighting Control Lamp Module 12718 or Remotec ZDS-110NA and ZDS-220NA

Strange part is some days when I reference the developer page, some nodes that were working, say unreachable and have to test and heal them. I am just totally confused.

This is an interesting routing and not what I would expect based on location of devices

[Goshawk29]

Support recommendations were extremely vanilla. They looked at my network and said they don’t see any issues with z wave hardware/network. Had me power cycle the homey pro, check for metal surfaces etc, and still have issues.

When you say homey’s zwave reach is small…what kind of range are we talking? My house is only 1400 sq ft and single story.

Newbie question, how do I look for “chatty” devices?

[Peter_Kawa]

Hmm OK.
Didn’t Support point to the KB pages? This one is quite useful, answers your questions:

Common Z-Wave error messages

_

@Goshawk29

When you say homey’s zwave reach is small…what kind of range are we talking

The usable/reliable range can be as low as a few meters. Just (temporarily) add a router device near it, to increase the range, and to see if that makes a difference.