Quick perusal of the Zen25 threads and could not locate what I have recently experienced.
Couple year smarting user, no issues the past year. But I pulled a bone head move during the migration to the new app and ended up starting from scratch. Deleting the classic app and starting from ground zero with the new app.
Actually got more than a dozen devices added back to my version 3 hub and when attempting to pair the zen25s, I can successfully pair the main device, but over multiple attempts with exclusions, resets I am unable to get the 2 child controls for each outlet.
I will continue on but will need to revisit these zen25s later.
The handlers for the devices were recently updated to accommodate changes in the new platform, do you have the latest handlers installed for the Double Plug?
Thanks again, currently blocked by "access denied " when I attempt to modify any device handler in my IDE. I have a help ticket out on that issue (4 different browsers, incognito etc same result ).
My intuition is it’s the device handler I am using. Probably at least a yr old.
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 device for the USB Port, 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 device and change its “Type” field because the new version doesn’t create the USB Port the same way as the old version.
The last version was supposed to create the USB Port using that new custom DTH, but it ended up just using the VIrtual Switch because I forgot to remove a test name before publishing the code.
I just released a new version that fixes it, but you’ll need to delete the USB Port child device again if you want to use it…
@krlaframboise Is this anytime the device handler is updated? I have 11 of these things and the recent changes in the ST platform have broken all of my child devices in anything outside of the Classic app. I updated to the v1.3.2 device handler and really don’t want to deal with going through all that work for 11 devices.
My DTH originally specified the componentLabel and componentName attributes while creating a non-component child and the new mobile app doesn’t like that.
I’ve fixed the DTH so everything should be good going forward, but I can’t remove those attributes from the children that were already created which is why you have to delete them and let the fixed version of the DTH re-create them.
Is your device handler the one linked to on the Zooz website or is yours different?
Edit -> I answered my own question.
It looks like I’m going to have to delete and re-add 11 devices. Then configure 22 child devices with their old names, change all the energy reporting settings since having 22 outlets with the default reporting causes my network to crash, then fix whatever breaks in Webcore and ActionTiles.
You don’t have to exclude those devices and doing so will probably mess up your mesh since you have so many of them.
All you have to do is delete the children through the IDE.
If deleting a device used in a webcore piston or action tiles prevents you from editing it afterwards then do the children one at a time and replace it with a virtual switch before deleting it so you can swap it with the new one afterwards.
Excluding and re-join the device isn’t necessary, but it’s easier to explain which is probably why they said that.
It turns out that you can also delete the child by opening it in the new mobile app, going to edit and tapping delete device so deleting it through the ide isn’t necessary.
Once the child is deleted, open the parent’s settings in the mobile app, change any setting and exit the settings screen. Changing a setting causes the updated method to execute which will re-create any missing children so it doesn’t matter which setting you change.
Thanks for your help Kevin. I deleted all the child devices, changed a setting on the parent and they all appeared again. I had to go through and figure out which was which and rename them all, but at least that’s out of the way.
Since you are the resident expert on these, can you help me with the energy / power reporting settings? I have 10 double plugs each with 2 devices attached. They are pinball machines so their energy / power usage fluctuates drastically based on if someone is playing, what is happening with the game as far as flashing lights, pop bumpers, etc.
I’d like to get some sort of energy usage, but when I had them all at default previously and there were people over to play, the hub was flooded with data. So much data that the entire Smartthings platform was completely unusable. I had to manually walk around and turn off the Zen25s before things would respond again.
Anyway, is there a way to enable some reporting so I have a little data without flooding the network?
There is Voltage reporting frequency, power reporting threshold, power reporting frequency, energy reporting frequency, electrical current reporting frequency.
I’m not sure what does what and what supersedes what.
The IDE makes that a lot easier because when you open the parent it has a link for each of its children at the bottom so you can rename them from there.
Energy is a cumulative value so if it’s reported once at the end of the day the value will be the same as if it was reported every 5 minutes.
If you’re not doing anything with the power, voltage, and/or amperage data then disable those settings or set them to their least reporting option.
I’ll be releasing a new version soon that displays a tile for Energy Duration and a reset button, but at the moment custom buttons are broken in ST so tapping it will just display a network error.
One of my last updates to the handler increased all the default values to prevent that problem, but it should only affect newly joined devices.
in 2019 I had ClassicApp & all worked fine, but now (2021) my ModernApp and my ZEN-25-Left (& Right) show “Checking…”. It seems stuck on “Checking”, and I cant yet figure out how to make the “Checking” status go away (e.g. show “ready” instead). DTH v1.4 & Child-DTH v1.0 & ST hub ver.3. Maybe the plug’s firmware needs updating? Any suggestions appreciated. TYIA.
My original code included the componentLabel and componentName attributes when creating the non-component child devices which didn’t cause any problems with the Classic Mobile app, but it causes the issue you’re seeing in the new mobile app.
I fixed that issue back in August, but unfortunately because the issue has to do with the way the child devices for the left and right outlets were created the only way to fix the problem is to delete those child devices and then go into the settings of the parent device and change any setting which will cause them to get re-created.
Does it have an effect on the devices while charging them? I am thinking of buying some smart plugs from https://www.amazon.com/smart-plug-wifi-plugs-alexa/dp/B09KTYH3MJ. I am planning to have a smart home ecosystem at my house. It helps to save energy and money on energy bills. For example, I noticed that after I changed all the bulbs in my house to smart light bulbs, I started to pay significantly less for energy bills. Also, they last longer, so I don’t need to change them as often as the regular ones.
