Z-wave network issues

Hey everyone, C8 pro user, hardline to internet, v2.5.1.142

I recently added two new devices to my z-wave network. an Aeotec multisensor 7, and a Zooz ZSE70 indoor/outdoor motion sensor.

For the sake of this post, they’re both working fine (I have some frustrations with the multisensor 7s driver but that might be another post) and show up in my device list and poll and report everything I would expect them to. However, when I go to z-wave settings and view the graph, neither one of these are showing up. I’ve tried rebuilding the network. It just doesn’t do it. I haven’t been getting any error message or failure message. It just never really gets past the node mapping. I tried updating the firmware on my multisensor 7, using the firmware from Aeotec, in the Z wave settings firmware updater, that one too just never really went past one percent but never failed either.

Honestly, I don’t know what’s wrong or what I’ve done here. I’m assuming the next thing to do would be to exclude them both from the network and start over after a factory reset but I just don’t understand what went wrong in the first place. Anyway, if anybody has any helpful information or thoughts or advice, I would love it. Thanks.

Is there a reason you care about them being in the graph? If they are working, show as devices, are in the table in zwave settings not sure why the graph is important.

If you included them as Long Range they won’t show on the graph because they are not part of the mesh… If they aren’t LR and it was really recent (minutes) it might have not cached the info yet..

No, I don’t particularly need them to be on the graph. I just assumed that their lack of presence there meant that something was missing or incorrect because I didn’t know there was any reason for them not to be shown there.

No, I did not include them as long range at least not to my knowledge, but I actually don’t know how to do that so unless it’s an automatic thing, I don’t think that’s the case. They’ve been on the network for multiple days and they have been sending and receiving lots of information and messages so I don’t think it was a lack of cache.

On the Z-Wave Details page, does the node number for these two devices have a little "LR" beside it?

On the screenshot below, node 44 is a mesh device, node 100 is an LR device. Notice that node 100 doesn't have the "Rebuild route" option and has no neighbors - because it is an LR device that communicates directly with the hub.

Node 100 will not appear in either the device graph or the device topology, both of which are indicative of mesh health.

It is if you used SmartStart and the device supports it

ah ok, thank you. No none of mine have the LR there, but I had already removed the one that might be long range and did not have neighbors which was the zoo outdoor motion detector so that may explain it.

I did not use smart start on the zooz. Which is the one that may have been long range, but I already removed it so I’m not sure. I’ll check when I add it back.

So I set it up again after excluding it and factory resetting it. I use Smart start scan the QR code and then add it and I enabled the s2 security.

What does this mean? It works perfectly but this doesn’t look like its set up properly.

Is your hub using ZWaveJS or Z/IP?

Based on the below, I would assume the Z/IP.

Click "Refresh" and wake the sensor at the same time.

That’s the first thing I tried. No change.

Although after just leaving it alone for a while, it now appears this way. I can refresh it almost instantly, but it doesn’t offer rebuilding a route and it doesn’t say LR anywhere, although it is long range capable

I thought I recognized the photo. I'm actually attempting a firmware update using your driver tool. I have one of those "sleepy" devices you mention may need to be woken up throughout the firmware update, but this one... doesn't wanna. It's the Zooz ZSE70 Outdoor Motion Detector. It just keeps getting stuck on "Wake your sleepy device". Any tips for extra sleepy devices?

Use the built-in z-wave firmware update tool. And I'd recommend using ZWaveJS over Z/IP.

I tried, several times. It can't fetch the metadata/firmware info cuz the device won't communuicate/wake up long enough

Thanks for reminding me.. I need to add logic to the built-in to handle sleepy devices better… I keep forgetting about it

This does make a difference… It’s completely different code as it uses the ZWave-JS native firmware tools when you are on ZWave-JS.