In the IE, what does the “Type” field show for the child devices?
That should have said IDE, but you sent me what I was looking for…
Check to make sure that the child handler is version 2.1.0 and the parent handler is version 2.2.3.
If you’re not using one of the outlets in any automations then delete that child device through the IDE and save the settings screen to re-create it. Once that outlet is re-created, toggle it using the new mobile app to see if it still displays that network error.
my version matches
I did the steps and still get the error I can not do anything with the power strip the app
I just joined the device and tested the child device in the new Android app and new iOS app and everything works as expected so the issue is specific to your setup which explains why I haven’t heard any other complaints about this for any of my DTHs that use child devices.
Which hub are you using and what’s the firmware version of your device? The mobile app doesn’t display the custom firmware version attribute so you’ll need to open the device in the IDE and check the “Current States” list.
Providing some logging results will also help:
Remove // from the beginning of the log.trace line at the bottom of the power strip DTH and then save/publish the code. Open live logging, go into the device’s setting in the new mobile app and verify that Debug Logging is enabled, then attempt to toggle one of the child devices, wait for it to display the error, and post the logging results.
The hub is Smartthings V 2
Firmware Version 000.031.00004
devoce firmwareVersion: 2.0
here logging
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:39:48 AM: debug Zooz Power Strip VER 2.0-CH5 - secondaryStatus is 2.2 W / 0 kWh - 1.99 Hours
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:39:42 AM: debug Zooz Power Strip VER 2.0-CH5 - power is 2.2 W
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:39:41 AM: debug Zooz Power Strip VER 2.0-CH4 - power is 0 W
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:39:40 AM: debug Zooz Power Strip VER 2.0-CH3 - power is 0 W
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:39:40 AM: debug Zooz Power Strip VER 2.0-CH2 - power is 0 W
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:39:39 AM: debug Zooz Power Strip VER 2.0-CH1 - power is 0 W
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:39:16 AM: debug Zooz Power Strip VER 2.0-CH5 - secondaryStatus is 2 W / 0 kWh - 1.99 Hours
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:39:11 AM: debug Zooz Power Strip VER 2.0-CH5 - power is 2 W
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:39:11 AM: debug Zooz Power Strip VER 2.0-CH4 - power is 0 W
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:39:10 AM: debug Zooz Power Strip VER 2.0-CH3 - power is 0 W
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:39:10 AM: debug Zooz Power Strip VER 2.0-CH2 - power is 0 W
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:39:09 AM: debug Zooz Power Strip VER 2.0-CH1 - power is 0 W
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:38:45 AM: debug Zooz Power Strip VER 2.0-CH5 - secondaryStatus is 2.1 W / 0 kWh - 1.99 Hours
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:38:41 AM: debug Zooz Power Strip VER 2.0-CH5 - power is 2.1 W
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:38:41 AM: debug Zooz Power Strip VER 2.0-CH4 - power is 0 W
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:38:40 AM: debug Zooz Power Strip VER 2.0-CH3 - power is 0 W
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:38:39 AM: debug Zooz Power Strip VER 2.0-CH2 - power is 0 W
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:38:39 AM: debug Zooz Power Strip VER 2.0-CH1 - power is 0 W
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:38:12 AM: debug Zooz Power Strip VER 2.0-CH5 - power is 2.2 W
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:38:11 AM: debug Zooz Power Strip VER 2.0-CH3 - power is 0 W
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:38:11 AM: debug Zooz Power Strip VER 2.0-CH4 - power is 0 W
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:38:10 AM: debug Zooz Power Strip VER 2.0-CH2 - power is 0 W
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:38:09 AM: debug Zooz Power Strip VER 2.0-CH1 - power is 0 W
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:37:50 AM: debug Zooz Power Strip VER 2.0-CH5 - secondaryStatus is 2.1 W / 0 kWh - 1.99 Hours
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:37:50 AM: debug Zooz Power Strip VER 2.0-CH4 - secondaryStatus is 0 W / 0 kWh - 1.99 Hours
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:37:50 AM: debug Zooz Power Strip VER 2.0-CH3 - secondaryStatus is 0 W / 0 kWh - 1.99 Hours
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:37:50 AM: debug Zooz Power Strip VER 2.0-CH2 - secondaryStatus is 0 W / 0 kWh - 1.99 Hours
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:37:50 AM: debug Zooz Power Strip VER 2.0-CH1 - secondaryStatus is 0 W / 0 kWh - 1.99 Hours
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:37:45 AM: debug Zooz Power Strip VER 2.0-CH5 - energyDuration is 1.99 Hours
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:37:45 AM: debug Zooz Power Strip VER 2.0-CH5 - energy is 0 kWh
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:37:44 AM: debug Zooz Power Strip VER 2.0-CH4 - energyDuration is 1.99 Hours
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:37:44 AM: debug Zooz Power Strip VER 2.0-CH4 - energy is 0 kWh
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:37:44 AM: debug Zooz Power Strip VER 2.0-CH3 - energyDuration is 1.99 Hours
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:37:44 AM: debug Zooz Power Strip VER 2.0-CH3 - energy is 0 kWh
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:37:43 AM: debug Zooz Power Strip VER 2.0-CH2 - energyDuration is 1.99 Hours
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:37:43 AM: debug Zooz Power Strip VER 2.0-CH2 - energy is 0 kWh
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:37:42 AM: debug Zooz Power Strip VER 2.0-CH1 - energyDuration is 1.99 Hours
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:37:42 AM: debug Zooz Power Strip VER 2.0-CH1 - energy is 0 kWh
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:37:42 AM: debug Zooz Power Strip VER 2.0-CH5 - power is 2.1 W
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:37:41 AM: debug Zooz Power Strip VER 2.0-CH4 - power is 0 W
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:37:40 AM: debug Zooz Power Strip VER 2.0-CH3 - power is 0 W
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:37:40 AM: debug Zooz Power Strip VER 2.0-CH2 - power is 0 W
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:37:39 AM: debug Zooz Power Strip VER 2.0-CH1 - power is 0 W
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:37:23 AM: trace SwitchBinaryReport: SwitchBinaryReport(value: 255) (CH0)
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:37:22 AM: debug childOff(16-CH4)…
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:37:12 AM: debug Zooz Power Strip VER 2.0-CH5 - power is 2.1 W
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:37:12 AM: debug Zooz Power Strip VER 2.0-CH4 - power is 2.9 W
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:37:11 AM: debug Zooz Power Strip VER 2.0-CH3 - power is 0 W
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:37:10 AM: debug Zooz Power Strip VER 2.0-CH2 - power is 0 W
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:37:09 AM: debug Zooz Power Strip VER 2.0-CH1 - power is 0 W
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:36:46 AM: debug Zooz Power Strip VER 2.0-CH4 - secondaryStatus is 2.9 W / 0 kWh - 1.83 Hours
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:36:42 AM: debug Zooz Power Strip VER 2.0-CH5 - power is 2.1 W
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:36:42 AM: debug Zooz Power Strip VER 2.0-CH4 - power is 2.9 W
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:36:41 AM: debug Zooz Power Strip VER 2.0-CH3 - power is 0 W
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:36:40 AM: debug Zooz Power Strip VER 2.0-CH2 - power is 0 W
396d115d-5ac3-44b1-aea2-e3485bad09dc 11:36:39 AM: debug Zooz Power Strip VER 2.0-CH1 - power is 0 W
I have removed the device put it back if i turn it on by had it shows in the app if i turn it off in app i get the error an can not turn it back on
It looks like the device isn’t sending back a report stating that the endpoint changed, but I’m unable to reproduce that problem. I checked the code and the handler is requesting that report so the problem isn’t an association issue so I’m thinking it’s either a device or mesh issue.
Try removing the device and factory resetting it. If that doesn’t work then try disabling all the reporting settings.
I have been using this DTH for over a year now and have the latest versions, for both parent and child handlers, without any issue. However, this morning I realized that the status of the child devices were not reporting status, although the parent device did so. This problem is only in the new app. The old app continues to work well, and the logs on IDE report accurately.
It’s not a big issue for me at this point, as my pistons in WebCore don’t seem to be impacted yet.
So, it’s clearly related to the new App. Now, that ST has come out with more documentation on custom capability development, I was wondering if there is a plan to update this DTH. I was also interested to see if others have experienced similar issues with the use of this DTH and the new app.
There was an issue with the way the DTH originally created the child devices, which I fixed in version 2.2.3, but unfortunately the only way to solve that problem is to delete the child devices and save the settings screen which make it re-create them.
I’m not sure if that’s your issue, but if you have a spare outlet that’s not being used by any SmartApps then you can easily test it on that one.
Custom capabilities are only necessary to provide attributes and/or commands that aren’t already part of a capability. They can also be used to change the appearance of it on the device list and device details screens.
This device is almost fully functional with the built-in capabilities so creating a custom capability isn’t necessary. It could use a custom capability to add support for the usb ports and/or electrical current, but that’s unrelated to your issue.
@beau76 is also having issues with the child devices, but based on the logs he posted, the device isn’t sending the switch reports so I don’t believe that’s the same issue.
I did some testing the other day and the child devices work as expected in the new mobile app. I mentioned the issue to Zooz today so they did some testing and they also couldn’t find any problems with the child devices and the new mobile app.
Thank you @krlaframboise for your reply on this issue. Based on what you wrote, I believe that the issue may reside with my settings. So, I’ll do more testing.
I don’t have any spare child device to test your suggestion on, but that’s an option I’ll have to consider doing with the four outlets.
I’ll report back on my testing. Thanks again.
Nope…
I believe the issue is that you joined the device prior to 8/16/2020 and the only way you’re going to solve the problem with the child devices not working in the new mobile app is to delete them and save the settings so that when they’re re-created they won’t have a componentName or componentLabel.
Update: That’s based on the assumption that you’re getting a network error when you attempt to control the child devices in the new mobile app…
I don’t see any network error, but only “Checking status” on the icon not changing. I actually turns the device on and logs so on the IDE. However, once turned on and I attempt to turn it off, the wheel on the Icon spins for a while and continues to report “Checking status.” The log on IDE reports a “switch on” status on that attempt to turn it off.
Since I definitely joined the device prior to 8/ 16/2020, it’s worth trying to delete the child devices and re-create them. I’ll report back. Thanks again.
You might want to just delete one of them to test it instead of deleting them all.
After deleting it you’ll need to open the settings and change one of them which will force it to re-create that child.
It doesn’t matter which setting you change, it’s just the only way I know of to execute the updated method because the settings screen in the new mobile app doesn’t have a save button.
That worked! Thanks for your much appreciated help.
1 Like
Zooz Power Strip 2.0 (v2.2.4)
I just released a new version that creates a child device for the USB port so it can be used in Automations.
To use this functionality you’ll need to install the Child USB Port DTH, delete the existing USB port devices through the IDE, and change one of the device’s settings which will force it to re-create the usb port device using the new handler.
You can’t just open the existing child USB Port devices and change their “Type” field because the new version doesn’t create the USB Port the same way as the old version.
1 Like
Awesome! Updating mine now.
See you have done this to a few items now. Is the ZEN06 Smart Plug on the upcoming list as well?
The ZEN06 hardware doesn’t support on/off reporting for the USB ports so making that change isn’t possible.
The ZEN20 and ZEN25 already had that fuctionality built into the DTH, it just wasn’t exposed by the new mobile app so that’s the only change I made…
1 Like
Awesome, I need to give this a try when I get some time! Thanks!
Hi Kevin -
I recently migrated to the new app and while the zooz power strip worked it did not report information back to the app correctly. So after reviewing this thread in its entirety I decided to try to update and resolve this issue.
- I removed (excluded) the power strip completely from ST,
- updated the DHT code for the strip, the outlet, and the USB child ports
- hard reset the power strip (3click and hold 10 seconds)
- added the power strip back to ST
Everything appears to work correctly now - outlets and USB ports added automatically and the power use is reporting back - HOWEVER - I have lost the ability to control on/off from the app completely. I get the dreaded " A network or server error occurred. Try again later".
The new ST app is reporting power correctly but the power state does not update when I change it physically on the device and I can not control the power state from the app.
DHT
Power strip ver 2.2.5
Outlet ver 2.1.0
USB ver 1.0.1
The hub is Smartthings V 2
Firmware Version 000.032.00012
device firmwareVersion: 2.0
I have repeated the process twice now (removed - reset - added back), however, I can still not control the power state from the ST app. Any assistance is appreciated.
John
Are you able to control the parent device from the new mobile app?
If you physically turn off all the outlets does the parent’s switch attribute change to “off” and then change back to “on” when any of the outlets are physically turned on?
If not, remove “//” from the log.trace line at the bottom of the handler, save/publish, open live logging, attempt to physical control the device, and then post the live logging results.