Zooz Zen25 Double Plug

[rakeshg]

I recently installed 2 Zooz Double Plugs and for some reason, the two show up slightly differently in on the "Devices" page.

The first one does not show any "child" devices

The second one shows the two child devices (left and right plugs)

I've checked the configuration and both are the same and both devices have the same firmware version (2.0). I don't really need to control the 2 outlets separately or even monitor energy usage and was wondering how to suppress the 2 outlets (or why the two would be different).

Also, does anyone know if these devices are "dimmable"? The lamps connected to the plug have dimmable bulbs but I can't control them from the dashboard (only on/off).

Thanks for your help.

[krlaframboise]

@rakeshg

The first one does not show any "child" device

The configuration didn't finish on the 1st one so as soon as you save the settings it will create the child devices.

@rakeshg

I don't really need to control the 2 outlets separately or even monitor energy usage and was wondering how to suppress the 2 outlets

Most people purchase this device because they want to be able to control the outlets individually so you can't remove the child devices.

You can, and should, disable the energy reports in the settings if you don't plan on using that data.

@rakeshg

does anyone know if these devices are "dimmable"?

No, they're just switches.

[rakeshg]

@krlaframboise

The configuration didn't finish on the 1st one so as soon as you save the settings it will create the child devices.

Hmm - I went back in to the device and clicked on the "Configure" button. Scrolled down (I changed the "Power Reporting Threshold" parameter to disabled just to make sure that the change took), hit save and the device still shows without the child devices. Is there anything else that I need to do?

[steve.maddigan]

Exclude the switch, Dona factory reset on the switch and re-pair it with HE.

[nibyak]

I had the same problem for a while. Like steve.maddigan said, exclude the Zen 25 and re-pair it with HE. When its re-pairing don’t press the save button as soon as it pops up. Wait a minute for everything to load. Also, since it’s a plug-in, move it in the same room as the hub to exclude and repair.

[rakeshg]

@nibyak

I had the same problem for a while.

Thanks @nibyak and @steve.maddigan. I have a few automations connected to this device and it's also being shared with Alexa and Homekit (via Homebridge), so a little reluctant to remove it. Any harm in leaving the config the way it is?

[krlaframboise]

@rakeshg

Any harm in leaving the config the way it is?

Someone else reported that issue with a different device this morning and it took 2 configure attempts for it to create the children.

Open logging, enable the debug logging save, wait for log messages to stop, click configure, wait again, and post logging results.

That might display something that will explain why it's not creating them.

[nibyak]

I have three of them. I used one of them like that for months. I didn't notice any issues. The two child devices were available to use. When I updated the firmware to version 2.0 I had to exclude and re-pair them. That’s when it got fixed. I never noticed any issues with it. I recently updated the firmware on six Zooz products and had to exclude/re-pair all of them. There is a little work involved in reestablishing all of the links and automations. I’m looking at a list of associations for two devices on the note pad next to my computer right now. I’m finally getting rid of my last non Z-wave plus switch and planning for everything that I will need to fix.

[rakeshg]

Turned on logging, waited to logs to clear. Did not create the child instances...

dev:12020-05-15 08:46:40.068 am infoBookcase Lamps power is 0W

dev:12020-05-15 08:46:18.665 am warndescription logging is: true

dev:12020-05-15 08:46:18.664 am warndebug logging is: true

dev:12020-05-15 08:46:18.663 am infoupdated...

dev:12020-05-15 08:46:10.079 am infoBookcase Lamps power is 0W

dev:12020-05-15 08:46:07.322 am warndescription logging is: true

dev:12020-05-15 08:46:07.321 am warndebug logging is: true

dev:12020-05-15 08:46:07.320 am infoupdated...

dev:12020-05-15 08:45:40.066 am infoBookcase Lamps power is 0W

dev:12020-05-15 08:45:10.759 am infoBookcase Lamps energyDuration is 6.76 Days

dev:12020-05-15 08:45:10.751 am infoBookcase Lamps energy is 3.87kWh

dev:12020-05-15 08:45:10.664 am infoBookcase Lamps power is 0W

dev:12020-05-15 08:45:10.356 am infoBookcase Lamps current is 0A

dev:12020-05-15 08:45:09.901 am infoBookcase Lamps voltage is 0V

dev:12020-05-15 08:44:40.052 am infoBookcase Lamps power is 0W

dev:12020-05-15 08:44:30.553 am infoBookcase Lamps power is 0W

dev:12020-05-15 08:44:30.251 am infoBookcase Lamps current is 0A

dev:12020-05-15 08:44:29.747 am infoBookcase Lamps voltage is 0V

dev:12020-05-15 08:44:29.640 am debugSwitchBinaryReport(value:0, targetValue:0, duration:0) (right)

dev:12020-05-15 08:44:29.617 am debugSwitchBinaryReport(value:0, targetValue:0, duration:0) (left)

dev:12020-05-15 08:44:29.537 am debugSwitchBinaryReport(value:0, targetValue:0, duration:0) (left)

dev:12020-05-15 08:44:29.435 am debugSwitchBinaryReport(value:0) ()

dev:12020-05-15 08:44:29.341 am debugoff()...

dev:12020-05-15 08:44:10.054 am infoBookcase Lamps power is 0W

dev:12020-05-15 08:43:52.455 am warndescription logging is: true

dev:12020-05-15 08:43:52.454 am warndebug logging is: true

dev:12020-05-15 08:43:52.453 am infoupdated...

dev:12020-05-15 08:43:51.000 am debugEnergy Reporting(#18) = 4

dev:12020-05-15 08:43:50.478 am debugRight Outlet Auto Turn-On After(#15) = 60

dev:12020-05-15 08:43:49.980 am debugRight Outlet Auto Turn-On Timer Enabled(#14) = 0

dev:12020-05-15 08:43:49.445 am debugLeft Outlet Auto Turn-On After(#11) = 60

dev:12020-05-15 08:43:48.929 am debugLeft Outlet Auto Turn-On Timer Enabled(#10) = 0

dev:12020-05-15 08:43:48.420 am debugRight Outlet Auto Turn-Off After(#13) = 60

dev:12020-05-15 08:43:47.904 am debugRight Outlet Auto Turn-Off Timer Enabled(#12) = 0

dev:12020-05-15 08:43:47.389 am debugLeft Outlet Auto Turn-Off After(#9) = 60

dev:12020-05-15 08:43:46.881 am debugLeft Outlet Auto Turn-Off Timer Enabled(#8) = 0

dev:12020-05-15 08:43:46.368 am debugElectrical Current Reporting Frequency(#6) = 300

dev:12020-05-15 08:43:45.860 am debugVoltage Reporting Frequency(#5) = 300

dev:12020-05-15 08:43:45.324 am debugEnergy Reporting Frequency(#4) = 300

dev:12020-05-15 08:43:44.831 am debugPower Reporting Frequency(#3) = 30

dev:12020-05-15 08:43:44.323 am debugPower Reporting Threshold(#2) = 0

dev:12020-05-15 08:43:43.822 am debugLED Indicator Mode(#17) = 1

dev:12020-05-15 08:43:43.275 am debugManual Control(#16) = 1

dev:12020-05-15 08:43:42.758 am debugOverload Protection(#7) = 10

dev:12020-05-15 08:43:42.341 am debugOn/Off Status Recovery After Power Failure(#1) = 0

dev:12020-05-15 08:43:41.568 am debugCHANGING Energy Reporting(#18) from 4 to 4

dev:12020-05-15 08:43:41.564 am debugCHANGING Right Outlet Auto Turn-On After(#15) from 60 to 60

dev:12020-05-15 08:43:41.552 am debugCHANGING Right Outlet Auto Turn-On Timer Enabled(#14) from 0 to 0

dev:12020-05-15 08:43:41.546 am debugCHANGING Left Outlet Auto Turn-On After(#11) from 60 to 60

dev:12020-05-15 08:43:41.542 am debugCHANGING Left Outlet Auto Turn-On Timer Enabled(#10) from 0 to 0

dev:12020-05-15 08:43:41.537 am debugCHANGING Right Outlet Auto Turn-Off After(#13) from 60 to 60

dev:12020-05-15 08:43:41.532 am debugCHANGING Right Outlet Auto Turn-Off Timer Enabled(#12) from 0 to 0

dev:12020-05-15 08:43:41.528 am debugCHANGING Left Outlet Auto Turn-Off After(#9) from 60 to 60

dev:12020-05-15 08:43:41.523 am debugCHANGING Left Outlet Auto Turn-Off Timer Enabled(#8) from 0 to 0

dev:12020-05-15 08:43:41.518 am debugCHANGING Electrical Current Reporting Frequency(#6) from 300 to 300

dev:12020-05-15 08:43:41.514 am debugCHANGING Voltage Reporting Frequency(#5) from 300 to 300

dev:12020-05-15 08:43:41.508 am debugCHANGING Energy Reporting Frequency(#4) from 300 to 300

dev:12020-05-15 08:43:41.504 am debugCHANGING Power Reporting Frequency(#3) from 30 to 30

dev:12020-05-15 08:43:41.500 am debugCHANGING Power Reporting Threshold(#2) from 0 to 0

dev:12020-05-15 08:43:41.496 am debugCHANGING LED Indicator Mode(#17) from 1 to 1

dev:12020-05-15 08:43:41.491 am debugCHANGING Manual Control(#16) from 1 to 1

dev:12020-05-15 08:43:41.487 am debugCHANGING Overload Protection(#7) from 10 to 10

dev:12020-05-15 08:43:41.450 am debugCHANGING On/Off Status Recovery After Power Failure(#1) from 0 to 0

dev:12020-05-15 08:43:40.031 am infoBookcase Lamps power is 0W

dev:12020-05-15 08:43:30.519 am infoBookcase Lamps power is 0W

dev:12020-05-15 08:43:30.219 am infoBookcase Lamps current is 0A

dev:12020-05-15 08:43:29.720 am infoBookcase Lamps voltage is 0V
dev:12020-05-15 08:43:29.605 am debugSwitchBinaryReport(value:0, targetValue:0, duration:0) (right)
dev:12020-05-15 08:43:29.506 am debugSwitchBinaryReport(value:0, targetValue:0, duration:0) (left)dev:12020-05-15 08:43:29.409 am debugSwitchBinaryReport(value:0) ()
dev:12020-05-15 08:43:29.288 am debugoff()...
dev:12020-05-15 08:43:10.024 am infoBookcase Lamps power is 0W
dev:12020-05-15 08:42:40.019 am infoBookcase Lamps power is 0W
dev:12020-05-15 08:42:30.517 am infoBookcase Lamps power is 0W
dev:12020-05-15 08:42:30.218 am infoBookcase Lamps current is 0A
dev:12020-05-15 08:42:29.714 am infoBookcase Lamps voltage is 0V
dev:12020-05-15 08:42:29.606 am debugSwitchBinaryReport(value:0, targetValue:0, duration:0) (right)dev:12020-05-15 08:42:29.517 am debugSwitchBinaryReport(value:0, targetValue:0, duration:0) (left)
dev:12020-05-15 08:42:29.407 am debugSwitchBinaryReport(value:0) ()
dev:12020-05-15 08:42:29.292 am debugoff()...
dev:12020-05-15 08:42:15.525 am warndescription logging is: truedev:12020-05-15 08:42:15.524 am warndebug logging is: true
dev:12020-05-15 08:42:15.523 am infoupdated...

[krlaframboise]

@rakeshg

Turned on logging, waited to logs to clear. Did not create the child instances...

I've played around with this device a lot in the past and based on what I saw in the logs and with a z-wave sniffer, the actions performed by the driver during inclusion are the same as when you click save.

If the children are missing and you click save it logs a message saying it's creating them and then creates them, but that's not happening based on your logs and I have no clue what could cause that.

If your device has newer firmware then enable the create child device for usb setting and see if that child device gets created when you click save.

If that doesn't work or you don't see that setting then you might have to remove the device and join it again. The issue has nothing to do with the device so re-joining shouldn't be necessary, but I can't think of another way to reset the driver.

I just remembered that I wrote a Hubitat driver for this device before it was fully supported by Hubitat. The driver is no longer needed, but it works fine and it might be a way for you to get the child devices without having to remove the device.

If the child devices get created with the custom driver then you won't be able to switch it back to the built-in driver without removing the device.

[OBSOLETE] Zooz Double Plug

This topic was created for a custom driver that was needed for this device at one point, but users should be using the built-in driver now because it's fully functional...

[rakeshg]

@krlaframboise - Tried to create a child device for the USB hub but that did not work either. For now, the plug seems to be working and since I don't need individual control (both the attached lamps turn on/off together), I'm going to leave this as it is. Thanks again for your help.

[rakeshg]

I'm still trying to figure out what is going on with my Zooz Zen25 Double Plug.. a few other issues that I noticed recently (apart from the missing "child" switches") - I can't seem to turn of power reporting (power, current, voltage). I have set the frequency to 24 hours for all and Power Reporting Threshold is "disabled". I am still getting entries in my logs every minute or so. I've switched to the original community driver (didn't fix the issue) and then switched back to the built-in driver (didn't fix the issue).

Is resetting this plug the only way to go? Since I am new to Hubitat, are there any "best practices" in removing and adding the same device back? I'm assuming that I will lose all the simple lighting rules etc that I have created - any way to preserve those?

EDIT: I have another Zooz Zen25 plug that is behaving just fine. Does not spam the logs and has the child devices (even though I don't need them).

Thanks

[neonturbo]

Did you use "configure" after changing the driver and the settings for power reporting?

I don't think you always need to do configure, but my understanding of that function is that it can force read and write these settings. Maybe someone else can tell me I am right or wrong.

[rakeshg]

@neonturbo

Did you use "configure" after changing the driver and the settings for power reporting?

I did do that (a couple of times). On the "Devices" page, I could see the driver change. The child devices show up on the configuration page, but don't show under the parent on the "Devices" page.

Here is a picture from the devices page.

And this is what I see on the configuration page.

[krlaframboise]

@rakeshg

And this is what I see on the configuration page.

Can you post a screenshot of the "Device Information" section above that?

[rakeshg]

@krlaframboise

Can you post a screenshot of the "Device Information" section above that?

See below.. let me know if this is not the correct screenshot?

[krlaframboise]

@rakeshg

let me know if this is not the correct screenshot?

I just wanted to make sure that the 02 in the device list matched the device you were looking at.

At this point I think your only option is to:

1. Remove the custom handler
2. Create a virtual device using the Zooz Double Plug driver,
3. Use the virtual device as a placeholder in your automations. That won't work for Alexa and Homekit
4. Exclude the device
5. Factory Reset it
6. Open live logging
7. Join the device
8. If you see a warning that says something about pending changes in live logging then save the preferences again. This device has tons of preferences and I think the save button sends the pending changes, but configure sends everything so repeatedly clicking configure might actually prevent the settings from syncing completely.
9. Swap the virtual device out with the new device in your automations.
10. Add the new device to Alexa and Homekit.

[rakeshg]

@krlaframboise

Use the virtual device as a placeholder in your automations. That won't work for Alexa and Homekit

Thanks! I was wondering if I could use a virtual device to hang on to the automations (I've done something similar with Wink). Quick question though - should I REMOVE the faulty device from the automations before excluding it or can I just add the virtual switch to existing automations?

[nibyak]

It depends on the automations. If they are simple automations rules you will just have to open it up and reselect the device in the device list and all will be well. Same goes for groups and the Alexa app. If you have dashboards with the device its also easy to correct, just select the 3 dot menu on the tile and reselect the device in the list. If you are talking about RM, you might want to do more pre planning

[rakeshg]

@nibyak

If you are talking about RM, you might want to do more pre planning

Thanks - most of the rules that I have a simple automation rules and the device is also included in one RM rule. However, when I go to the look at the device, it shows as being in 3 RM rules - 2 of which don't use this device. I think I had originally included this device to test the rule but then changed it to the final device. For some reason, Hubitat thinks that this device is still associated with these rules

Hopefully, removing this device will fix all of this craziness