[RELEASE] Zooz Power Strip VER 2.0

Devices & Integrations Community Created Device Types
, ,
128

The app did reflect OFF when I turned off all the individual outlets manually - I then turned on 1 outlet manually and the app reported the main strip as ON. But the strip as a whole did not respond from the app - I get the same “A network or server error occurred. Try again later” message.

HOWEVER - the buttons on the power strip did not respond at all at first :thinking: . I unplugged the strip completely - waited 10 seconds and plugged it back in and the buttons started working again.

Maybe the whole power strip has gone bad?

heres the trace log after a manual activation of each button on the strip x2


5b1d059a-2495-4050-aa2e-fad9e35d2297 4:09:48 PM: debug Zooz Power Strip-CH5 - secondaryStatus is 133.6 W / 2.25 kWh - 1.8 Days

5b1d059a-2495-4050-aa2e-fad9e35d2297 4:09:48 PM: debug Z-Wave Device-CH2 - secondaryStatus is 133.1 W / 2.39 kWh - 1.87 Days

5b1d059a-2495-4050-aa2e-fad9e35d2297 4:09:48 PM: debug Z-Wave Device-CH1 - secondaryStatus is 66.2 W / 2.8 kWh - 1.87 Days

5b1d059a-2495-4050-aa2e-fad9e35d2297 4:09:47 PM: debug Zooz Power Strip-CH5 - power is 133.6 W

5b1d059a-2495-4050-aa2e-fad9e35d2297 4:09:45 PM: trace SwitchBinaryReport: SwitchBinaryReport(value: 255) (CH0)

5b1d059a-2495-4050-aa2e-fad9e35d2297 4:09:45 PM: trace SwitchBinaryReport: SwitchBinaryReport(value: 255) (CH0)

5b1d059a-2495-4050-aa2e-fad9e35d2297 4:09:45 PM: debug Z-Wave Device-CH4 - switch is on

5b1d059a-2495-4050-aa2e-fad9e35d2297 4:09:45 PM: trace SwitchBinaryReport: SwitchBinaryReport(value: 255) (CH4)

5b1d059a-2495-4050-aa2e-fad9e35d2297 4:09:44 PM: trace SwitchBinaryReport: SwitchBinaryReport(value: 255) (CH0)

5b1d059a-2495-4050-aa2e-fad9e35d2297 4:09:44 PM: trace SwitchBinaryReport: SwitchBinaryReport(value: 255) (CH0)

5b1d059a-2495-4050-aa2e-fad9e35d2297 4:09:44 PM: debug Z-Wave Device-CH1 - switch is on

5b1d059a-2495-4050-aa2e-fad9e35d2297 4:09:44 PM: trace SwitchBinaryReport: SwitchBinaryReport(value: 255) (CH1)

5b1d059a-2495-4050-aa2e-fad9e35d2297 4:09:44 PM: debug Z-Wave Device-CH1 - power is 66.2 W

5b1d059a-2495-4050-aa2e-fad9e35d2297 4:09:43 PM: debug Z-Wave Device-CH3 - switch is on

5b1d059a-2495-4050-aa2e-fad9e35d2297 4:09:43 PM: trace SwitchBinaryReport: SwitchBinaryReport(value: 255) (CH3)

5b1d059a-2495-4050-aa2e-fad9e35d2297 4:09:42 PM: debug Z-Wave Device-CH2 - switch is on

5b1d059a-2495-4050-aa2e-fad9e35d2297 4:09:42 PM: trace SwitchBinaryReport: SwitchBinaryReport(value: 255) (CH2)

5b1d059a-2495-4050-aa2e-fad9e35d2297 4:09:40 PM: debug Zooz Power Strip-CH5 - secondaryStatus is 0 W / 2.25 kWh - 1.8 Days

5b1d059a-2495-4050-aa2e-fad9e35d2297 4:09:40 PM: debug Z-Wave Device-CH2 - secondaryStatus is 0 W / 2.39 kWh - 1.87 Days

5b1d059a-2495-4050-aa2e-fad9e35d2297 4:09:40 PM: debug Z-Wave Device-CH1 - secondaryStatus is 0 W / 2.8 kWh - 1.87 Days

5b1d059a-2495-4050-aa2e-fad9e35d2297 4:09:40 PM: trace SwitchBinaryReport: SwitchBinaryReport(value: 255) (CH0)

5b1d059a-2495-4050-aa2e-fad9e35d2297 4:09:39 PM: debug Zooz Power Strip-CH5 - power is 0 W

5b1d059a-2495-4050-aa2e-fad9e35d2297 4:09:39 PM: debug Z-Wave Device-CH4 - power is 0 W

5b1d059a-2495-4050-aa2e-fad9e35d2297 4:09:38 PM: debug Z-Wave Device-CH2 - switch is off

5b1d059a-2495-4050-aa2e-fad9e35d2297 4:09:38 PM: trace SwitchBinaryReport: SwitchBinaryReport(value: 0) (CH2)

5b1d059a-2495-4050-aa2e-fad9e35d2297 4:09:38 PM: debug Z-Wave Device-CH3 - power is 0 W

5b1d059a-2495-4050-aa2e-fad9e35d2297 4:09:38 PM: debug Zooz Power Strip-CH5 - switch is off

5b1d059a-2495-4050-aa2e-fad9e35d2297 4:09:38 PM: trace SwitchBinaryReport: SwitchBinaryReport(value: 0) (CH5)

5b1d059a-2495-4050-aa2e-fad9e35d2297 4:09:37 PM: debug Z-Wave Device-CH2 - power is 0 W

5b1d059a-2495-4050-aa2e-fad9e35d2297 4:09:37 PM: trace SwitchBinaryReport: SwitchBinaryReport(value: 0) (CH0)

5b1d059a-2495-4050-aa2e-fad9e35d2297 4:09:37 PM: debug Z-Wave Device-CH1 - power is 0 W

5b1d059a-2495-4050-aa2e-fad9e35d2297 4:09:35 PM: debug Z-Wave Device-CH4 - switch is off

5b1d059a-2495-4050-aa2e-fad9e35d2297 4:09:35 PM: trace SwitchBinaryReport: SwitchBinaryReport(value: 0) (CH4)

5b1d059a-2495-4050-aa2e-fad9e35d2297 4:09:34 PM: debug Z-Wave Device-CH4 - power is 0 W

5b1d059a-2495-4050-aa2e-fad9e35d2297 4:09:34 PM: trace SwitchBinaryReport: SwitchBinaryReport(value: 255) (CH0)

5b1d059a-2495-4050-aa2e-fad9e35d2297 4:09:33 PM: trace SwitchBinaryReport: SwitchBinaryReport(value: 255) (CH0)

5b1d059a-2495-4050-aa2e-fad9e35d2297 4:09:32 PM: debug Zooz Power Strip-CH5 - power is 128.8 W

5b1d059a-2495-4050-aa2e-fad9e35d2297 4:09:31 PM: trace SwitchBinaryReport: SwitchBinaryReport(value: 255) (CH0)

5b1d059a-2495-4050-aa2e-fad9e35d2297 4:09:31 PM: debug Z-Wave Device-CH1 - power is 61.1 W

5b1d059a-2495-4050-aa2e-fad9e35d2297 4:09:30 PM: trace SwitchBinaryReport: SwitchBinaryReport(value: 255) (CH0)

5b1d059a-2495-4050-aa2e-fad9e35d2297 4:09:30 PM: debug Z-Wave Device-CH2 - power is 133.2 W

5b1d059a-2495-4050-aa2e-fad9e35d2297 4:09:28 PM: debug Z-Wave Device-CH3 - power is 0 W

5b1d059a-2495-4050-aa2e-fad9e35d2297 4:09:01 PM: debug Z-Wave Device-CH4 - power is 0 W

5b1d059a-2495-4050-aa2e-fad9e35d2297 4:09:01 PM: debug Z-Wave Device-CH1 - power is 61.1 W

5b1d059a-2495-4050-aa2e-fad9e35d2297 4:09:01 PM: debug Z-Wave Device-CH3 - power is 0 W

5b1d059a-2495-4050-aa2e-fad9e35d2297 4:09:00 PM: debug Z-Wave Device-CH2 - power is 133.2 W

5b1d059a-2495-4050-aa2e-fad9e35d2297 4:09:00 PM: debug Zooz Power Strip-CH5 - power is 128.8 W

129

Was that from the parent or one of the child devices?

I’ve had one of those goes bad. It was still responding from the hub, but the outlets weren’t actually being powered.

Did you happened to have a router plugged into it?

130

Parent

No, no router - but I did open a ticket with zooz and their reply was that I had too many things plugged in to it (?!?)… My total load was way under what the strip was rated for but I got some lip service about start-up spikes, etc.

I’m just gonna chalk this one up “live and learn” and go with individually controllable smart outlets instead of a power strip.

Thanks for your help.

131

Same issue:

Not able to control child plugs in new oneApp: main power

image
image750×1334 86.2 KB
child device:

.

image
image750×1334 64.1 KB

Controllable in Classic app

image
image750×1334 125 KB

132

Not the same issue, that one appears to have been a faulty device…

There was a bug in the way the handler created the child devices which only caused problems in the new mobile app.

I released version 2.2.3 in August which fixes the problem, but if the device was joined before that you’ll have to manually delete the child devices and let the handler re-create them. After deleting the children you’ll have to make a change to one of the device’s settings, but it doesn’t matter what you change.

133

Thanks this fixed the child outlet devices, now time to re-add the updated devices to the prior rules.

134

I was having trouble controlling child devices from the new app, but my automation were working. I got frustrated and deleted the power strip from my hub, re added it, excluded it, added the 2 custom device handlers, saw the strip in the new app, changed the name, saw the children plugs, but they were just the greyed out “checking status” for each of the 5 outlets.

I renamed them to the names I wanted.

I went to the Smartapp “smart lighting” and tried to create an automation, but none of the child devices were listed, just the main strip.

BTW the main strip can be controlled from the app and shows the current state with no issues.

I tried deleting the child devices again, changed a setting on the power strip, saw the child devices pop up with their default names. I could now see the default names in the smart lighting app. But as soon as I changed the name of one of the children devices, it would disappear from the smart lighting app.

No matter what happened with the naming and smart app, I was never able to control the devices from the app.

135

You have to add and publish the 2 handlers before joining the device…

136

I did. Sorry, I thought I explained that.

137

Any way to resolve this?

138

I just realized that those handlers don’t have an ocfDeviceType defined so that might be the reason why they’re not rendering properly.

In the definition section of both DTHs, which is near the top of the code, replace the vid line with the line below.

ocfDeviceType: "oic.d.smartplug"

The new mobile app caches the UI so it might take a while to know if that change fixed the problem. You can sometimes force it to refresh by changing the device’s label field in the IDE, but that doesn’t always work.

The only reliable way to make a new UI display is to remove the device, delete the DTH, change the “name” field in the handler, create a new handler with the code, and join the device again.

Once you’re sure that the new mobile app is displaying the updated UI, let me know if that change solved the problem and if it did then I’ll publish a new version of the DTH with that change.

139

Thanks for your help, but it didn’t work.

140

Do you have the v2 power strip or the old one?

141

I have the V2.

142

Has anyone had any issue with this device and power monitoring? I have two V2.0 ZEN20 devices at this point and have noticed they randomly stop reporting to SmartThings using the latest and greatest device handler.

I have to remove power from the strip to get it to restore power reporting. It is also still connected to SmartThings as I am able to control the outlet functions remotely so it is only related to power/energy reporting.

I am talking to support but they seem to be useless to be honest and wondered if these are just problems other are seeing.

I bought these switches to utilize in my home office for reporting for power consumption and charge back to my company but if this is going to be unstable I may need another solution. I did like this switch gave each outlet its own power/energy monitoring capabilities but this is getting worse and worse.

143

Does only the power reporting have issues or does it totally drop zwave connection so on/off stops working too?

144

@pyrodex Also, just wanted to mention, when I had this strip on SmartThings, I had issues with it until I disabled the power monitoring functions. I know that doesn’t really help your situation at all. One thing you could try is to pair it without security enabled. Also, since power cycling it seems to clear the issue temporarily for you, you could also try adding another smart plug to reboot the power strip at night.

145

No when this occurs and the strip is in this state all other functions work such as on and off via zwave.

146

Having to buy another device to reboot another device is simply stupid, no offense to you.

I am hoping the creator of the device handlers sees this update and can provide insight and work with engineering on the zooz side.

147

What firmware version is it? I can’t remember If this handler doesn’t show it on the device details screen then you’ll need to check the IDE.

I haven’t seen this problem, but the device can be extremely chatty and I have seen that cause random issues.

You don’t have to completely disable reporting, but you should disable all the reporting that you’re not using. Most people really don’t have a use for A and V reporting.

For most situations you really only need energy to report once a day because the reported value is cumulative.

If power is what you’re most interested in then I recommend using either the % or W thresholds instead of interval, but if you do decide to use interval I recommend setting it to 1 minute or more.

If it stops reporting again, remove // from the log trace line at the bottom of the code and leave live logging open for a while to see if there’s any activity from it.

If not, open the device details screen and swipe down. Since the handler is using a built-in vid I’m not sure if that will do anything, but if it does you should see a “refresh()…” log entry followed by some meter reports.