I just traded emails with Zooz… ETA is now just after July 4th - I’m guessing mid-July?
Also I have a follow up video about how the prototype worked in my home over the past 4-5 weeks… note that I did my testing on the Z-box, but interesting device results nonetheless. (Spoiler alert: some oddities with Lux reporting). I’ll drop the link below if interested:
I’m sure it is detailed somewhere and I am missing it - can this switch be programmed as off/on only (no dimmer function)?
Yes. Via parameter 44
Here’s the full parameter list and manual
FYI that it is posted on the alliance website now too.
There are other quirks too (mine is also on 0.5 firmware)… I’m not thrilled with the light off being directly tied to the motion off with no offset capability. If you want a long off timer on the light you have to make a long motion off event delay as well. They should really be decoupled.
I hadn’t considered that, but I can see that may be useful. Is your thought that every new motion detection could, in theory re-start the ‘off timer’ on the light itself, thereby ensuring the light stays on during constant occupancy? I do like that idea.
Also today it is hot and very humid here… and very much so in my garage where I have the ZEN12 installed. Today is the first time it was slow to recognize motion in the months I’ve had it. I wonder if the lens was foggy or something. Just an observation…. (Only about 2 second delay, but very noticeable.)
Yes. This is also how the GE motion switch / dimmers have worked for many years.
It lets you have higher frequency motion events decoupled from the light on off function. This can be really useful if you want to use the motion events for other things in other automations.
I submitted that feedback to zooz months ago.
ICYMI - Zen12 went on sale recently.
Sadly, this would have been a great fit for our old house but less so for our new one.
@Hatallica Beat me to it, but yes, the ZEN12 is now available!
Zooz also is doing special intro pricing this week (starting July 28 2026).
Here’s the link (direct, this is not an affiliate link):
I had heard there may have been physical changes between the beta unit I tested and the production unit, but this looks the same. I reached out to Zooz to ask that question and can report back. I can say it continues to work flawlessly in my garage all this time.
So confirming that the zen12 motion and switch can not be separated? I want to use one of these in a guest room. I want the switch to only be activated by manual touch….but also work at a virtual 3-way switch with another zooz switch.
I want the motion to be able to provide logic for my motorized shades….If there is motion in the guest room I don’t want my auto open rule to run…..I.e. don’t auto open the shades at sunrise if we have guests staying over….but if no motion for 24 hours…there are no guests, open those shades at sunrise.
I suppose I don’t need the device decoupled….but at a minimum the ability to make it so that the motion switch does not auto control my lights.
Can anyone confirm if this situation will work in my case?
Yes that absolutely can be done. Set parameter 13 to a value of 1.
Disable Motion Trigger
Parameter 13: Enable (0) or disable (1) motion trigger to control the connected light.
Values: 0 – enable motion trigger; 1 – disable motion trigger. Default: 0.
Size: 1 byte dec
Thanks. Just ordered 3!!!
What driver is everyone using? I'm using the default HE built in driver. I don't have a parameter for how long the light stays on after motion is detected. As a result, I walk in the room, the light turns on and about 15 seconds later the light turns off with me still moving in the room.
Strange.. I thought that was there… I’ll update the driver
Thanks.....How does that update get pushed? Is that one of those things that will come with the next HE OS update?
Also, my motion just stays on "active" the whole time.
It will be in a hotfix build..
Yea.. That was fixed already in the version that’s in beta.. Should be out tomorrow
So a very interesting thing I noticed.
I have a Zooz ZSE11 Q Sensor in a room. I am replacing it with this Zen12. The two are located about 3ft apart.
With the lights off in the room, My ZSE11 is reporting 40 lumens while the Zen 12 is reporting 22 Lumens.
With the lights on, the ZSE11 is reporting 319 lumens wile the Zen12 is reporting 135 Lumens.
This isn't a huge deal for me as the only thing I use this attribute for is notification of a light left on.
But the mis compare is pretty large. Curious if this is normal or if this is a case of "its a beta device.....inaccuracies are possible".
How do you know the ZSE11 isn't the incorrect one? Just because it was there 1st doesn't mean it is right.
I have a bunch of lux/light detectors (different brands/models) and they are all over the place even when right next to each other. Those sensors are trash (in general) for accuracy.
Very true.
This is what I was assuming. And in my case trash is fine. I am more concerned about a change (or lack there of) in lux.