[RELEASE] Zooz Power Strip VER 2.0

Anyway we can link to github? Also can we make it so we can change the names and icons of each channel on the strip?

It’s already linked to github. It’s krlaframboise and SmartThings

If you open the individual outlets you can rename them, but at this point I don’t plan on adding a way to rename the component labels shown in the parent device.

I have ran into problems when the canChangeIcon attribute was set to true in the past, but it’s been a while so I’ll re-test and if it doesn’t cause any problems I’ll enable it.

In workaround link: http://www.support.getzooz.com/kb/article/149-how-to-add-your-power-strip-ver-20-to-smartthings/

steps 7-8 calls for ‘zwjoin’ event but after the lights on the power strip stopped flashing all I can see is ‘zw device’ in my hub>list events>

Any screenshot that shows ‘zwjoin’ event? or the powerstrip I received is DOA maybe?
Hub v2.

I’ve run into that before, but those zw device entries near the top usually include the device network Id value that you’re looking for so that specific event isn’t necessary.

There are multiple ‘zw device’ events and all seem to have different ids.
It would be nice if the workaround was updated with screenshot or at least mention which zw device event to pull the id from. I’m seeing 8 zw device events

The zw device gets bigger each time I switch id on the Power Strip Device type. lol
I’ve lost track

Not sure the workaround has been tested…wait am I beta testing now?LOL

Finally, I would like credit for beta testing. lol

The device id is next to zw device: 61 in this photo.

So for step 8. Look for the number next to zw device in the name or value columns.

Then use that number for Step number 12.

After some good old trial and error [62 was my lucky id number, time for powerball?]:

Do not use the id value that’s inside the event.

The documentation is correct, most of the time. I think I’ve run into 1 instance out of probably 25 where that event didn’t get created.

If you removed the device and tried again it probably would have created the event.

I removed 3-6 times, I lost count actually. not once did I see zw join event. Anyway for those users that come across this issue, they’ll know where to look for to get the id.

if the documentation had just only one screenshot it should be the screenshot where the zwjoin event shows the id number for step 12. It would be tremendously helpful.

2 Likes

We’ll add screenshots to the instructions!

2 Likes

So far so good, looks like a comprehensive device - lots of options available.

Couple of bugs though:

Renaming a child outlet works (i.e. ‘TV’) works but the name doesn’t get updated in the parent view. Still shows as ‘CH 1’. … ok, I just saw above that you’re not planning on fixing that.

The USB ports shown in the parent view can be toggled and unfortunately they seem tied to the first two the first two power outlets. That is, clicking on USB1 toggles CH1, when I don’t believe anything should happen at all.

This isn’t a bug, but since multiple users have requested it I’ll add a setting that enables the automatic renaming.

Thanks for pointing this out.

I originally used the built-in simulated switch handler as the child which didn’t cause it to toggle CH1 and CH2, but it displayed switch icons instead of outlet icons so I changed it to the built-in zooz outlet handler.

It appears that handler is causing the USB ports to toggle CH1 and CH2 and it’s also preventing the USB ports from displaying in the new mobile app.

I think I’m going to create a 3rd handler for the USB ports that display an outlet icon and don’t display as buttons so that they can’t be toggled. If users opt not to install the 3rd handler then it will use the built-in simulated switch handler which will show switch icons, but at least tapping them won’t cause them to toggle CH1 and CH2.

I won’t be making these changes until tonight so if anyone can think of a better solution to the USB port issue or has any other suggestions, please let me know before tonight. @TheSmartestHouse

1 Like

Kevin, thanks for the insights.

In my application I’m more interested in monitoring power usage and incorporating current values provided by the powerstrip to control logic in webCore. Since most of the devices are always intended to be left on, I want to avoid clicking on the switch controls and show the power/energy values in the primary tile. To that end I’ve just swapped the “PRIMARY_CONTROL” & 'SECONDARY_CONTROL" values in the child handler and that seems to work for now. Need the same for the parent and colours need to be tweaked though. Providing an option to let the end user do what I did would be great but not seeing how to do that without providing whole separate handler implementations.

Also, what is the ‘acceleration sensor’ alluded to in the code, an unimplemented Zooz feature?

Considering that users can easily see the power of all their devices on the same screen using an app like Simple Device Viewer and that the device has a setting to disable turning the switches off, I don’t see enough benefit to spending time on that. (i know that setting is all or nothing, but still don’t think there’s enough benefit to add a bunch of complexity to the handler.)

With my Zooz Power Strip handler, some users wanted an easy way to determine if the device plugged into it is on. I implemented that by adding a threshold setting and using the Acceleration capability so that if the power is above the threshold the device reports Acceleration active and below the threshold it reports inactive.

I added that feature to this handler, but thought it might confuse people so I commented it out. If it’s something users want I can easily add it back by removing the comments.

I added that feature to this handler, but thought it might confuse people so I commented it out. If it’s something users want I can easily add it back by removing the comments.

Nice, that sounds useful. How about renaming it to ‘Usage/On sensor’ or something that won’t be mistaken for something that monitors a physical/motion aspect? That and some explanation/how-to comments in the code would be great.

Screenshots and an extra tip for the key step has been added here: http://www.support.getzooz.com/kb/article/149-how-to-add-your-power-strip-ver-20-to-smartthings/

2 Likes

Zooz Power Strip VER 2.0.6 Update

  • Allows you to change the Outlet Icons.

  • Added a new DTH for the USB Ports which displays the ON/OFF status as text instead of a button and display properly in the new mobile app. (not required)

If you already have the device installed and you want to use the new DTH for the USB ports you need to install the DTH and then open the USB ports in the IDE and change their Type. The USB ports are not listed on the My Devices page, but the power strip device in the IDE will have links to them.

2 Likes

It turns out the component label is read only so I can’t add a setting that allows the user to choose whether or not the actual device labels are displayed in the power strip.

That being said, if you manually delete the outlets, comment out the line below which is currently line 224, and then save the settings it will create the outlets without the component label and you’ll see the device labels in the power strip. After the outlets are created you can remove the comment.

componentLabel: "CH ${endPoint}",

When trying to add this I accidentally created two phantom nods that come up as failures everytime I try a Zwave repair. Anyway I can fix this and get them off my network? I did successfully add the power strip and the phantom nods seem to be unreleated to the powerstrip other than they were created when I was trying to add the power strip.

try this loop:

I just released a new version that displays the actual outlet names and their power level in the primary device. I also removed the USB child handler because it’s no longer needed.

After upgrading to the latest version you need to tap the refresh button to force all the device names and their power levels to populate.

4 Likes