[update: solved - seems that my zen12’s didn’t get a full interview so I was missing options. Thanks darren.stp!]
There are a few other Zen12 threads, but none really discuss my problem so I decided to start new and not hijack.
I got my first Zen12 and installed just fine. There’s some oddity in Home Assistant as the device name hasn’t detected properly yet, but that I’m sure will come in a future update.
My problem is that the two places that I wanted to install the Zen 12 have similar issues.
The first location wide room but the back walk-in closet the light is tied to the main lights. I walk into the closet for 30 seconds and the lights turn off on me!!! Grrrrr…
The second location the light switch is right next to the door, turns on the moment I open the door. Great. But it’s long hallway and I guess the sensor can’t see the other end. So I’m at the end of the hallway doing my thing and 30 seconds later the lights turn off on me!! Grrrr…
OK. Let’s read the manual…
Motion Clear Delay
Parameter 17: Set the amount of time the device waits to send a motion clear notification after the last motion event is detected.
Values: 0-3600 seconds. Default: 30.
Size: 2 byte dec
Hey. That looks promising! Booo… doesn’t look like that is exposed in Home Assistant yet. OK. Head over to Z-Wave JS and I’ll add it manually. I’ll set it to wait 1200s (20 minutes) after it stops detecting motion… Nothing. As soon as it stops detecting motion, it turns the lights off.
I figured out I can disable the motion detection. That works… REALLY defeats the purpose of having motion detection… and if I’m working in space #1 I don’t want to have to remember to turn off motion detection every time I need to get something out of the closet storage… and it’s not like I’m back there for long. But generally longer then the timeout apparently…
Looks like I have 1.0.0 firmware. I know there’s a plan for 1.0.1 but I don’t see it as an available update in Home Assistant yet.
Any thoughts or ideas on how to give me some time after last motion detection before it turns the lights off on me?
Thanks!
If so, I did create an issue on GitHub about this. A device configuration file needs to be created, and the team there asked if someone wanted to volunteer to write it as they are overwhelmed with requests. Not sure I’m ready to bite that off at this point, but that is where it stands.
Are you in JS UI? That parameter (17) is working for me, although I didn’t have the patience to test 1200 seconds (LOL). But if I set 5, 30, 60, 90, 120 - all of those tests work to the second.
I do see that as available to be activated on the HA Side…
I’m wondering if perhaps you have Z-Wave JS (not JS UI) and if perhaps there is a difference there. I dont have a HA test instance with JS only to test. What versions of HA and JS are you running? Just curious where the differences might be.
(FYI - not a Zooz employee - just trying to be helpful.)
I see you tried to manually add P17 at the bottom of Z-Wave JS. But instead it should be expressed there as a settable parameter. By contrast here’s a screenshot of mine in JS UI. I see a lot more parameters than you do…? I also have 51 configuration entities on the HA side.
I wonder if you need to reinterview the device, or if perhaps you need to update Z-Wave JS on your HA instance? I’m on a slightly older version(s) myself as I usually wait for updates. All my versions are below. What are yours?
I think that was it! I don’t think mine got a full interview… but since they were showing the same options I just went with it. I’m a little ahead of you on the versions but a reinterview now shows loads more options. I also realized it didn’t quite work the way I expected. I was hoping for a “stop detecting motion” event, but I don’t see that. But I can confirm that the 1200s timeout gives me plenty of time to disappear before the light turns off. Huzzah! Thank you very much.
I’m a little ahead of you on the versions but a reinterview now shows loads more options. I also realized it didn’t quite work the way I expected. I was hoping for a “stop detecting motion” event, but I don’t see that. But I can confirm that the 1200s timeout gives me plenty of time to disappear before the light turns off. Huzzah! Thank you very much.
