I just re-tested the pre-production ZEN12 with the updated firmware 0.5. The improvement across all the z-wave hubs I’ve tested was significant. Here’s my updated video of the testing results.
Scene control, direct associations, and sensor improvements almost across the board.
Here’s the summary of what’s improved:
Nice update! I also immediately tested reversing the action of the dimmer button on my Z-Box Hub as I prefer the device orientation with the large button on the bottom: nice feature.
One thing not corrected yet is the use of sliders for all parameter settings on the Z-Box Hub. Still hoping not everything will show up as sliders, but many as radio button choices as we’re accustomed to seeing. That’s something that definitely will be a more user-friendly approach in the UI and I hope it gets corrected before the initial public release.
Yes.. Good catch! I didn’t even notice that. I was annoyed by the wide sliders and didn’t consciously realize why… LOL
I’m also still working on the bouncing lux when its in my garage (daytime only)… But it didn’t do that on the bench, so I’m thinking it is something in my garage itself. (why I didn’t highlight in the video)… but still testing.. I’ve set Parameter 19 to 200 (highest lux reporting threshold) and that seems to be working, since the garage light is either on, off or sunshine. I don’t need fine measurements. So far much better.
Excellent feedback! You’re correct; parameters with value options should display with values, not a slider. We’re contacting the engineers on this today. Keep up the awesome work, it’s much appreciated!
Hi Everyone.
Just to finish out my ZEN12 review as promised, I’ve released the “Part 2” video (which actually is video #4!). This video contains my final thoughts after having this device installed in my home (via the z-box) for more than a month and used dozens of times each day, since it was in a high traffic area.
I think we are all anxiously awaiting the release of the final product! But for now, here’s some video goodness!
There’s even a surprise walk-on role of the ZSE11 in here
[And no comments on my garage. It definitely needs some spackle, paint and love! lol.]
Your comments on the ZEN12 in your garage closely parallels my Beta unit installed next to the door entering our home office. It quickly recognizes one of us has entered the office and, if the lux level is below threshold, immediately turns on the ceiling lights. As you noted when sitting still at your workbench, our lights also time out if we’re sitting still at the desk. This is to be expected with PIR sensors and I’m looking forward to the day when I can combine a PIR sensor with an Occupancy Sensor (probably mmWave): quickly turn on with PIR and turn off only after room occupancy goes away for some period of time.
The “bouncing lux sensor” comments are also interesting and reinforce many of my thoughts on the matter. I’m sure you saw the discussion on Adaptive lux Level Reporting, which explores the topic in more detail. Wouldn’t it be nice if lux sensor devices could be “tamed” with, say, a low pass filter to cause fewer reports? IMHO, it would still be a useful relative illumination number, albeit with a “settling time” before drastic changes occur. For some applications, that would be ideal–others, perhaps, might need the instantaneous report frequency. Choice is good.
Overall, I heartily agree: the ZEN12 Motion Dimmer is a very impressive device.
The default lux reporting threshold on the ZEN12 is set relatively low at 10, with a maximum configurable value of 200. This gives us some room to adjust the threshold and reduce the number of lux reports if needed.
By comparison, the ZSE11 has its lux reporting threshold set to 50 by default. This difference is most likely why you are seeing different reporting behavior between the two devices, and also why the ZEN12 appears to generate more fluctuating or “bouncing” lux reports when installed in a garage environment where lighting conditions can change frequently.
At this point, I would prefer not to change the default value of the lux reporting parameter. We have already completed integrations with the various Z-Wave hubs, and changing the default behavior now could introduce unnecessary complications. I think it would be best to wait for additional feedback once the ZEN12 becomes available for sale in July and then evaluate whether any adjustments are needed based on real-world usage.
Hi @BartekZooz ,
Unfortunately I had the setting on the zen12 as high as 80, and the bouncing continued (since the bounces in some cases were greater than a difference of 80.). In my testing, both the ZEN12 and ZSE11 were set at the same threshold of 20. (…if we are talking about the same threshold parameter)
But I certainly am interested to check out the production model once it arrives.
Also, as I mentioned in the video, I’m not 100% convinced that there isn’t something in my garage itself causing the bouncing. (I’m thinking a reflection of some sort, perhaps maybe ‘flashing’ because of a tree branch shadow or something…) When I had it on my test bench I did NOT experience the bouncing, and that was pointed up towards a skylight.
