Zooz ZEN24 4.x Problem with inclusion

I cannot seem to add my Zooz ZEN24 v4.0 to my C7, at all. I can add/remove it to/from my HomeAssistant network all day long without any trouble, but it doesn't even show up on the Hubitat. I've done all the removals, resets, re-adds, repairs, reboots... nothing is happening. Zwave "logs" show nothing. I currently have ZSE40 and a ZEN15 on network and working fine.

Any thoughts on what I can do as next-steps here?

Did you suddenly have issues? In other words were you adding the other devices and it stopped working when you went to do this? Or did you do a recent hub update after you added those other Zooz devices and maybe that update caused problems?

Did you try doing a controlled shutdown (Settings tab, shutdown) pull the wall plug for 1 minute, and boot back up and try again? Not just a reboot like you said above.

What do normal logs (Log tab, not Zwave logs) show when you are trying the inclusion?

Could you post a screenshot of your Zwave details page here?

And you didn't specifically mention it, so I was wondering if you did an exclusion of this device in Hubitat before trying to include?

1 Like

Hi neonturbo! Thanks for the quick response!

This is the latest device I've tried to add since getting my hub a week or two ago. I haven't had any issues loading other zwave devices onto it, just this guy. I actually tried 2 or 3 adds today on 2.2.5.126 and subsequent attempts on 2.2.5.127.

I did not try a full shutdown with power removal.

Logs tab shows the following for sys1:

sys:12021-02-02 16:40:52.243 Z-Wave Inclusion timed out, status:7
sys:12021-02-02 16:40:52.232 Z-Wave Discovery Stopped
sys:12021-02-02 16:40:39.868 Z-Wave Exclude Stopped
sys:12021-02-02 16:40:36.131 Z-Wave Discovery Running
sys:12021-02-02 16:40:09.851 Z-Wave Exclude Started for 30 Seconds
sys:12021-02-02 16:40:08.042 Z-Wave Inclusion timed out, status:7
sys:12021-02-02 16:40:08.025 Z-Wave Discovery Stopped
sys:12021-02-02 16:39:57.191 Z-Wave Exclude Stopped
sys:12021-02-02 16:39:41.916 Z-Wave Discovery Running
sys:12021-02-02 16:39:27.049 Z-Wave Exclude Started for 30 Seconds
sys:12021-02-02 16:39:25.456 Z-Wave Inclusion timed out, status:7
sys:12021-02-02 16:39:25.444 Z-Wave Discovery Stopped
sys:12021-02-02 16:39:19.579 Z-Wave Inclusion timed out, status:7
sys:12021-02-02 16:39:00.828 Z-Wave Discovery Running

I'm new; how does one include a screenshot?
Edit:

Yes, I did try the "exclude before include" process, several times.

Oh, newbie, you might not be able to include a screenshot yet. :grin:

But if you have that option, it will be in the editing bar as shown here. Or you can simply drag-n-drop from your computer to this window.

pic

Edit: looks like you got it.

So it looks like it didn't even attempt to do anything. See what happens after a full shutdown.

Is this device further away than the others? Have you tried moving the hub closer before inclusion?

That office sensor looks a tiny bit odd with the clusters, but maybe it is normal. Shouldn't affect anything with pairing I think.

I'll do the shutdown thing now.

It's about 20ft (~6m) away. The HomeAssistant system (using a Zooz USB stick) to which I can easily join/remove is literally right next to the C7, so I assume distance isn't an issue (would hope not at only 20ft/6m).

That office sensor is the Zooz ZSE40. It started looking like that after I initiated a Zwave Repair. It still appears to be reporting everything (and responding to things) appropriately, however... so I haven't poked at it any harder.

I would temporarily move or better yet shut down that Z-stick. You might be drowning out the Hubitat radio.

Try moving the Hubitat closer to the switch if at all possible. I know it should work where it is if the other device pairs there, but just try it to rule anything out.

I think the shutdown trick worked! It joined this time, but sys logs show:

sys:12021-02-02 17:48:00.251 Z-Wave Inclusion timed out, status:7
sys:12021-02-02 17:48:00.238 Z-Wave Discovery Stopped
sys:12021-02-02 17:47:16.140 Z-Wave Network responded with Busy message.
sys:12021-02-02 17:47:15.611 Z-Wave Network responded with Busy message.
sys:12021-02-02 17:47:14.318 Z-Wave Network responded with Busy message.
sys:12021-02-02 17:47:13.509 Z-Wave Network responded with Busy message.
sys:12021-02-02 17:47:13.140 Z-Wave Network responded with Busy message.
sys:12021-02-02 17:47:12.958 Z-Wave Network responded with Busy message.
sys:12021-02-02 17:47:10.140 Z-Wave Network responded with Busy message.
sys:12021-02-02 17:47:07.140 Z-Wave Network responded with Busy message.
sys:12021-02-02 17:47:04.140 Z-Wave Network responded with Busy message.
sys:12021-02-02 17:47:01.158 Z-Wave Network responded with Busy message.
sys:12021-02-02 17:46:58.114 Z-Wave device id: 15 failed S2 bootstrapping - - Bootstrapping was successful - the device needs to be excluded then included again to use securely.
sys:12021-02-02 17:46:21.806 Z-Wave Discovery Running

Which seems worrisome, and it wasn't responding to commands/events properly for a little bit... but after a while it did! Thanks a ton @neonturbo!

Cool! Glad it works.

You might want to include only a couple more things, and let the hub work it's magic overnight to discover new Zwave routing. Doing too much at a time seems to make the Zwave confused sometimes. A break to let it settle out after a few devices seems to work best in most cases.

1 Like