I have six of the ZEN54's being delivered today. Plan is to use them to control 0-10V dimmable LED flood lights. What driver will they use, and will it the driver be found during registration?
There is no driver I am aware of, So not sure how its going to work.
I could possibly whip something together based on the docs but it may take a few rounds of testing to get it working 100%
Order came in, so I unboxed one and hooked it up for bench testing. I was able to include it, but the device page doesn't show much. None of the stuff one would expect for a dimmer.
Well the manual does not even list the command classes... I am pretty sure that is supposed to be required for z-wave certification.
First I would try changing the type (driver) to "Generic Z-Wave Plus Dimmer", that might get you something.
You can also use this basic Z-Wave tool: HubitatPublic/basicZWaveTool.groovy at master ยท hubitat/HubitatPublic ยท GitHub and run the command class report, then get a screenshot of that info from the logs and post it. To use that tool you just change the driver/type to that temporarily.
I saw in another thread where the Qubino 0-10V driver worked for the ZEN54, so I tried that. It now shows some basic commands (on/off, set level, start/stop level change, and refresh) and a few preferences.
I may try the generic dimmer tomorrow.
Thanks.
The "Generic Z-Wave Plus Dimmer" driver worked about the same as the Qubino,
Neither seem to work correctly with the ZAC99 momentary switch connected to the ZEN54. For example, if the ZEN54 is on at 100%, pressing the ZAC99 does nothing. Holding it down causes the light to dim and ultimately turn off, but as soon as the ZAC99 is released, the light turns on again and increases to 100%. I may have it wired incorrectly, or maybe neither driver supports the ZEN54/ZAC99 combo, or maybe there's a ZEN54 firmware problem.
I've gotten far enough to know that the ZEN54/ZAC99 combo will meet my needs.
The driver does not control the interaction between the device and momentary switch. There is a parameter setting (number 12) you have to set for a momentary switch in order for it to work correctly. https://www.support.getzooz.com/kb/article/1243-zen54-0-10-v-dimmer-advanced-settings/
That says the default is option 2 which is a toggle, you need to set it to option 1. You could set it using the Basic Z-Wave Tool driver until there is a proper driver with all the settings exposed.
Hi Jeff!
I, too have bought 3 of these devices to control a VFD, and of course no driver, YET.
I did get the command class report:
Hope this helps!
You have been VERY helpful with your great drivers in the past.... thank you!
I would use the generic dimmer for now. It should support all the functions of the device. The Qubino driver could possibly set some parameters to incorrect values since it is not designed for the ZEN54.
And actually... if you want to work on the settings try out my Z-Wave Scanner.
-- [RELEASE] Z-Wave Universal Device Scanner
This should be able to scan the device for the parameter options and then present you with the settings in a somewhat sane format. Once you have it configured switch back to the Generic Z-Wave Plus Dimmer to control the device.
I have a dream of making some universal drivers that would read the info saved by the scanner so you could scan, save the info, then switch to a universal driver that would control the device and have all the settings. I have lots of ideas though, not enough time to make them all.
Wow, I see a few of you have jumped in, wasting no time If one of you are able, can you look to see how the 0-100 settings on the Zen54 dimmer in the driver correspond to 0-10V at the output side of things? I'm interested to see how they map out.
Disclaimer: I'm using a 20 year old, very cheap multimeter, so maybe not real accurate.
I ran the tests four times. Two sets had a 15 watt flood light wired in. Two sets had no load wired in.
The results were very repeatable, within +/-.01v each time. I ran the test using the "Generic Z-Wave Plus Dimmer" driver for the ZEN54. It looks like it the driver has a built-in max level of 99%. With the switch off (and even with power to the switch disconnected), the multimeter still shows .01v until I pull the multimeter leads. Here's the results...
1% .21v
5% .61
10% 1.11
20% 2.11
30% 3.10
40% 4.10
50% 5.09
60% 6.06
70% 7.06
80% 8.07
90% 9.08
99% 9.91
According to Zooz support, if you put the ZAC99 dumb momentary rocker switch in the same box with the ZEN54, the ZAC99 can provide on/off (tap the top of the rocker for either) and dimming (hold down the top of the rocker). I'm waiting on the ZEN54 driver to fully test the dimming capability of the ZAC99.
You dont need a special driver, the driver has nothing to do with that function, its all hardware based. All you need to do is change the one parameter. See my post above about using the Zwave scanner.
Awesome..and that confirms it's a full 10V range. I was only seeing 9V with the Leviton ZS057-D0Z.
I'd like to try this out with the AC infinity fans, but I can't seem to get one shipped to Canada yet How are you guys sourcing these? Smartesthouse? ? They don't offer CAD shipping, so I suspect I'll have to wait for the CAD supplier to list them via amazon.ca
I got mine from thesmartesthouse.com.
I installed your driver, changed the ZEN54 to use the "Z-Wave Universal Scanner" driver shown in the "User" section of the driver list pull-down, set the preferences, saved the preferences, did a refresh, did a sync from device, and then clicked Scan Parameters. It went thru the first seven parameters, but is hung on "Scanning (8)".
You might just have to try it again, its a lot of traffic so if your zwave mesh is busy it can get jammed up. Try it first with the name/info options turned off, see if it finds all the parameter numbers. If that works then you can try with the other settings. I have gotten it to work on a Zooz dimmer which has like 30 something parameters so I know it can work.
Looking at the log...
dev:332023-03-02 08:24:03.148 AMerrorjava.lang.NumberFormatException: For input string: "FFFFFFFF" on line 239 (method parse)
dev:332023-03-02 08:24:01.089 AMdebugZEN54 0-10V Dimmer: Found Param 7 and saved, next scanning #8
dev:332023-03-02 08:23:59.033 AMdebugZEN54 0-10V Dimmer: Found Param 6 and saved, next scanning #7
dev:332023-03-02 08:23:56.976 AMdebugZEN54 0-10V Dimmer: Found Param 5 and saved, next scanning #6
dev:332023-03-02 08:23:54.921 AMdebugZEN54 0-10V Dimmer: Found Param 4 and saved, next scanning #5
dev:332023-03-02 08:23:52.865 AMdebugZEN54 0-10V Dimmer: Found Param 3 and saved, next scanning #4
dev:332023-03-02 08:23:50.811 AMdebugZEN54 0-10V Dimmer: Found Param 2 and saved, next scanning #3
dev:332023-03-02 08:23:48.757 AMdebugZEN54 0-10V Dimmer: Found Param 1 and saved, next scanning #2
dev:332023-03-02 08:23:48.697 AMdebugZEN54 0-10V Dimmer: scanParameters: Starting with #1
There's literally nothing on my z-wave mesh other than the device(s) I'm testing at the moment. All of what I am doing is bench testing for a new home we are building. None of the devices are installed/active unless I am testing it. In this case, the only device with power to it is the ZEN54.
Ok param #8 is a huge 4 byte parameter, maybe I am not handling it correctly in that driver. I will have to dig into it later today.
Ok if you are OK with editing the code, right above line 239 add a log.trace, so it looks like this:
void parse(String description) {
log.trace "parse: ${description}"
hubitat.zwave.Command cmd = zwave.parse(description, commandClassVersions)
Then try again. This wont fix it, but should log the message it is having a problem with. It seems the actual parse command is having a problem, not sure why, have never seen this before.