Z-Wave device map shows loop - some devices not being turned off per schedule

My C-8 has been working great for the past year. Recently, I've seen some of my outdoor lights (Z-Wave devices) still on after sunrise.
I tried Z-Wave repair but the device map looks like this:

The topology map looks like this:

Z-Wave repair made no difference - neither did rebooting. Cycling power did fix it - at least once before: It then showed typical hub and spoke configuration and all the devices worked as expected.

I Recently experienced the same issue several weeks later and saw the same device map loop with the hub on it's own.
This time, rebooting and cycling power made no difference.

I've read other posts which said the loop causes no harm but it seems to me that it's a symptom of a problem somewhere in the Z-Wave network because I still have lights on after sunrise.

  • Anyone have any ideas what is going on?

Can you control all devices from the dashboard?

Yes, but it's a bit odd. For example, the front light post is supposed to turn off at sunrise. It was (once again) still on this morning. The dashboard indicated that it was off. I had to press it once on the dashboard to make it appear "on" and then, again to turn it "off". The light actually did turn off then.

You can control all the other devices normally from the dashboard?

Yes, but the are largely Zigbee.

Can you post a screenshot of your ZW Details page (Settings -> Z-Wave details)... In particular, a full capture of the table on that page.

It appears you just have a few devices, so they should all fit in one screenshot.

ETA - maybe post a screenshot of the corresponding sunrise lighting rule too... Might as well try to cover all bases here.

1 Like

Here you go - appreciate the assistance....


Hopefully one of the smarter ZW folks will be able to weight in here with their overall thoughts, but how old is that Jasco switch?

Some older GE/Jasco models are prone to issues where they can wreak havoc on the mesh when they start failing prematurely. I think their newer models are better, but @danabw - would you be able to add some more color on all that?

I am not sure of the age of the switch. I bought it used on eBay when I moved in about a year ago.

Given the distance from the hub, I would expect that switch to be the first one it talks to, so what you say makes sense.

I have no other switches to replace it with at the moment, but it sounds like I should get one to see if it improves things.
Even if it doesn't, home automation people like us can always use another switch!

The Jasco switch is S2. Wouldn't that indicate it's a newer switch? I can't remember exactly when S2 security was introduced.

S2 came out around 2016/2017, introduced w/500 series devices, but not all 500 series got S2. AFAIK all 700 series and later do.

This reddit post refers to the GE 12727 / Jasco ZW4003 as one of the affected switches. I believe Model ZW4005 was also subject to this problem. I had several of the GE/Jasco switches that were affected). Common symptom was clicking sound coming from the switch and failure root cause was a defective capacitor that was in the switches. GE/Jasco extended warranty and replaced them free. If it was failing due to the capacitor issue it's usually pretty obvious.

Your Front Light is directly connected to your hub (see Route column). Not top speed connection (40 rather than 100) but should work fine.

Sounds like you can consistently control it from its Device page or Dashboard w/out issues, and it's only failing when called from your Rule. If the switch was failing I'd expect problems controlling it from Rules, Device page, & Dashboards.

Have you tried shutting down your hub, pull power, wait 30s, restore power? That will restart the Z-Wave and Zigbee radios, a reboot does not do that. Just to cover all the bases, you could first do a reboot (Settings>Reboot) and choose advanced options on the Reboot dialog and select the option to rebuild your database. Then after your hub reboots w/rebuilt database, do the shut down/pull power process. See if things settle down after that. If not then would want to look at your hub logs around that time in the morning to see if there is anything interesting going on...

2 Likes

Just thought I'd chime in again.
Three devices! Should be cake! :slight_smile:

1 Like

Yup - def not a Z-Wave congestion issue. Maybe the opposite, the switch is lonely. :slight_smile:

2 Likes

How about excluding, factory resetting and re-including at least the two switches? The usual placeholder, swap devices in apps, etc. Or whatever.

I've got no idea about the garage door, and what effect S2 Access Control might have on mesh if things go sideways.

I just tried rebooting with the rebuild database option, followed by a power recycle after a couple of mins. but I still have the lonely loop - even after a network repair.

I think my next step is to order a replacement switch - Zooz Zen71 seems reasonably priced.

I'll report back.

So switch is still not responding properly to the automation, or you just are still seeing the loop?

You could also try as suggested, remove and re-include the switch.

The loop is still there and the automation ran successfully this morning. I'll let it run a few days to prove that it is really fixed.
If not, I'll try the remove and re-include process.

1 Like

I don't think you need to worry too much about the loop being there or not. I don't spend any time looking at my Z-Wave graph as mine is just too hard to read.

Post your current Z-Wave topology. Here's a post w/a good explanation w/examples of how to read the Hub Z-Wave Topology:

And the usual "if it ain't broke" rule applies. If things are working, leave 'em be. :slight_smile:

1 Like

Amen on the "if it ain't broke" rule!
Your graph looks like a Manhattan NY street map.

Here's my map - seems fine:

The way I would read your map is that the Hub (01) can NOT see any of the other three devices.

No BLUE in either row or column for (01).

1 Like