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.
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.
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.
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.
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.
Just been informed that a new batch of these Power Strips are available with the updated firmware. Anyone know how we can get our current ones updated?
Just reach out to our support or Zooz here and request an update. There is an option to update the firmware over the air but SmartThings doesn’t support it so if you don’t have another tool to perform the update, we’ll be able to do it for you in-house.
Yesterday I upgraded the firmware to 2.0 and re-included it on my network. As I did before, I slowed down the reporting by picking less frequent updates (slower that default settings). I will keep an eye on the logs to see if it still gets the timeout notice.
I knew that a high rate of reporting would bog down the zwave mesh network, but I was unaware it would also result in hitting the 20 second execution limit timeout. Could an overloaded zwave network cause the DTH to take so long to report all the values?
I have been trying to lighten my traffic as it seems to be causing me several issues (mostly difficult inclusions and general slowness).
@brianr - I updated mine yesterday using HomeSeer’s Z-Flash tool. Worked like a charm after excluding it from my network. I believe the error I got when I tried updating it while included was due to some timeout caused by other zwave issues I am experiencing (likely high traffic or a bad node). Adding the power strip back to ST was now a normal procedure unlike the first time that required some hacking in the IDE. Thank you @krlaframboise and @TheSmartestHouse !
I just ordered this device. I am still a novice with smartthings at this point but just now diving in to see the true power of what can be done.
With the Zooz power strip I understand you can control each outlet individually. What I am trying to figure out how to do is say when turning outlet 2 on then outlet #1 turns off automatically. I don’t want a scenario where 1 and 2 can be on at the same time. I am not sure if I can get this through a routine logic or if I need more advanced handling? I am new to this community but impressed by how everyone bands together to solve problems. Any pointers or recommendations would be appreciated
You need to use a SmartApp to accomplish it. You might be able to do it with Smart Lighting, but if not you’ll need to use a community app like CoRE or WebCoRE.
ST’s device ID is HEX while Z-Flash uses a decimal reference. I converted the HEX ID of the Zooz 2.0 power strip and found it listed in the devices Z-Flash could reach.
