2.3.0.120 Broke several Z-Wave links?

Just curious if anyone else has broken links to zwave devices after the update? For my system, several of my connections to Minostan devices are broken and will not be repaired.

I haven't noticed anything, but a Z-Wave Repair won't necessarily fix a missing "link"--just make devices (that respond, generally powered devices) update their neighbors. This would really only help if there was a mesh issue and it hadn't yet resolved itself because, say, you just moved a repeater or you're dealing with pre-Plus Z-Wave.

What are the exact problems you're seeing? Does the device respond to commands? Does it report states back from phyiscal changes? Anything in logs if you enable debug logging? If so, it might be a driver issue; I don't see Minostan on the official compatibility list, so I assume you've either found a Generic driver that worked or are using custom code.

Worst case, you could do a Z-Wave Replace (reset the device but leave it on the hub; you should see Repair in Z-Wave Details if the device can't be reached, though it may take a refresh or two), or if you're not using it in any/many apps, try an exclude or reset, removal, and re-pair.

EDIT: Oh, also try the general Z-Wave advice. Any "ghosts" under Settings > Z-Wave Details? Any potentially problematic devices like chatty S0 devices, a ZEN25 with power reporting enabled, or similar?

2 Likes

Devices have stopped responding. I’ve added a few more devices that I have been trying to pair and having a tough time. I guess I will have to try exclusion/inclusion again.

Devices are Minoston not Minostan. They are on the compatible list. Just checked again.

Think a Fortrezz relay device added as S0 for some reason so maybe that is being chatty and killing my other connections?

One thing you can do in case there was some unrecoverable Z-Wave crash (I think the UI warns you about this now, so you'd probably have seen it, and after a long-ago update I don't think this happens much anymore...) is power the hub down from Settings > Shut Down, then unplug it from power at the wall for about 30 seconds or more before plugging it back in. This will shut down/restart the Z-Wave radio, which a normal hub reboot won't do.

Also, I was just doing a literal search, so "Minoston" would do it. Looks like stock drivers, then!

A single S0 device is not necessarily a problem, but there are a couple that are known to be particuarly problematic (Inovelli LZW42 bulb or the 500-series Zooz ZSE40 4-in-1). I haven't heard of the particular one you mentioned being problematic, and if you're using for a secure application like a garage door, I'd probably keep it that way unless you can make it use S2 (which I'd always prefer over S2 if it's available)--though it's certainly possible that it is and just no one has noticed anything, though less likely if it's just an on/off relay and not sending power reports or anything on a regular basis.

2 Likes

Good to know that reboot doesn’t reset zwave network. I tried that several times but never tried a full disconnect from power. I appreciate the help.

There have been no changes to existing drivers that Minoston devices use, and we have not received other incident reports. Do you mind sharing the model of your devices and the driver type they use (Settings >> Devices >> Device Details >> Device Type)

I applied this update last night and lost all radio functions on my C5 with external stick. A full power off corrected the issue after several reboots failed to.