I don't disagree there's opportunity there for Zooz to clarify that wording, but Zooz forcing you to use a non-zero delay when 2 is set to 1 doesn't make any sense.
In the P16 description, when Zooz says "...for the automatic turn-on [after power outage]...", I read that terminology as a direct reference to having P2 set to 1 .
I might be getting punchy.
I got it working, in coordination with the ZEN16 for the WaterCop shutoff valve.
Works through the Config on the System driver.
Set param 2 to 1, 16 to 120.
Makes sense.
Jeff, sorry for the bloviating verbiage, still had to get a way to get the watts, kwh, etc.
Yes, wording can be improved. The way I read this is that 16 is not used (does not have an effect) UNLESS 2 is set to 1. And it's not forcing a non-zero setting.
It made more sense in the end in my situation as well.
Correct, exactly what I said would happen in the other thread.
All it does is read the settings data from the device and then present it to the user. Any settings that do not work as expected you would need to take up with Zooz.
Hi Jeff,
Firstly, thanks for all the work you've put into the Universal Z-Wave Drivers. I'm testing the Universal Z-Wave Switch driver with an MCO Home MH-S510 (3-gang) and wanted to report what I've found.
Hub
-
Hubitat C-7
-
Latest platform version
Device
-
MCO Home MH-S510 Series
-
3-gang touch switch
-
Firmware 5.0
Results
The driver correctly detects:
However, the child switch devices cannot control the relays.
When I send an On or Off command to a child device, Live Logs reports:
MissingMethodException: No signature of method componentOn(DeviceWrapper)
(and similarly for componentOff()).
The parent and child devices are created successfully, but child commands are not forwarded to the corresponding endpoint.
Switching back to the built-in MCO Home Touch Panel Switch driver immediately restores normal operation, so the hardware and Z-Wave network appear to be functioning correctly.
If it would help, I'm happy to:
I'm happy to help test support for the MH-S510 if you'd like another device to validate against.
This driver does not have all the coded needed for a multi-endpoint switch. It is not designed to work with child devices. So that's why it is getting an error.
Thanks for the clarification. That makes perfect sense.
I have around 30 MCO Home MH-S510 (3-gang) switches throughout my house, so I was hoping to standardise on the Universal drivers if possible.
Do you have any plans to add support for multi-endpoint relay switches with child devices in the future, or is that intentionally outside the scope of the Universal Switch driver?
If it's something you're interested in, I'm happy to help test on real MCO hardware and provide logs, parameter information and feedback.
How did you get the "Rule Machine" to change the colors on the fly? I am unable to get to change the parameter on the fly. I Use "34" as the parameter configuration and "3" as the color and "1" as the bit size. It is stated as "3431" in the "setParameter" field.
Thanks in advance
Good Morning,
For some time now, I have been getting these errors with my Eaton RF9640 Dimmers:
The messages seem random, happen when the dimmers are physically turned on or off, and when they come up, the associated RM automations do not work.
Any thoughts?