Sorry, but the ZSE19 Multisiren won’t be getting a driver because it’s certified as Works with SmartThings and it’s been discontinued for a while…
That’s not Zooz’s manufacturer ID so is there a Zooz label on the back of the device?
Is there something else I can include from the IDE? I’ve probably had this plug for 5 or 6 years now, is it possible Zooz had a different manufacturer ID at that time?
I have a few of these so I’ll take a look at them and see if they show the same Raw Description.
Some of their older products were sold with that manufacturer id for a short period of time, but I wasn’t aware that was one of them.
I’ll add that fingerprint to the driver, but I’m still working on adding the ZEN51 so it probably won’t be published until late tonight or tomorrow.
1 Like
I think it’s a Hank SO03 metering switch - Z-Wave Product Id: 0x0208.0x0101.0x000A. I got one (no manufacturer label) from Monoprice, I think… It can report voltage, current, and load state change. Power-up state can be set. This and this look to be good documentation
I installed the zen25 double outlet edge driver and everything works fine at the device level. However, when I try to create a routine that turns an outlet off based on what happens with another device, the only “then” options provided are “on or off” for each outlet. I would expect to see the option to explicitly select the “on” or the “off” option.
Likewise, when I try to set up a scene with the double switch, I only get the “turn on”, “turn off” options for the left outlet. The right outlet section only shows the “energy consumption” option.
Is this at all related to the driver or a problem on the service/smartthings app side? Everything worked as expected using the original custom DTH, but not with the edge driver. If on the smartthings side, I would appreciate a pointer to the appropriate place to post the issue. Thanks for any guidance!
@jds13 is correct, it’s a known iOS mobile app bug with all multi component drivers.
When it was initially reported I thought it was only impacting Routines if you try to set them up from the device so if you create a new routine from the mobile app’s main automations screen everything worked as expected, but it wouldn’t surprise me if they broke that too…
I have a ZEN30 device I installed 2-3 weeks ago. I noticed that there is a “no cloud” icon and several “untitled” labels displaying on several of the status page items (see screenshots below). It was purchased early last month so I presume the firmware is relatively current. Is this a driver update issue, a firmware issue, an installation issue, an ID10T issue? I think I’ve seen this in other devices but it seemed to clear up after an automatic update of the driver. I know Kevin has been posting new and corrected drivers like a madman so I have been patienty waitinng for the dust to settle after September 30. What do I need to do? I have a ZST10 if I need to update the firmware.
Thank you.
@SkippyJohn
Yes, I reported this issue to ST last week. Others may have also. It also affects scenes where it only provides the turn on/off options for the main, not any other components.
Hi all, last month I moved my Zen30 double switch (dimmer for fan light & relay for fan motor) from groovy to Edge driver & I use the McVirtual workaround for flawless voice control of the fan motor)…
My issue is that with the old Zooz groovy code I was able to disable the LED on the dimmer paddle…. But I don’t see an option in driver settings… drives us crazy at night… so since the relay is on (fan motor), no led light on… good, but since the dimmer light is off, led light is on… not good.
The LED Control is now on the device page, but you’ve got the infamous “no cloud” icon. Try clearing the application cache. Not sure if you can do that on iOS, but that usually addresses the issue on Android. There are some ST bugs they are working through, but here you can see an example of the LED option on a ZEN32 switch…
1 Like
Wow figures I have the worse luck.
Anyone with iOS figure this out yet? I’ve deleted the old groovy DTH from IDE & re-installed the ST app… still have the dreaded clouds:
Create a routine to change the led options. Once you’ve executed it once the tiles on the device details screen should start working as expected.
2 Likes
I created a routine for “power on at 10:30a”, it powered on at 10:30a, but the clouds are still showing.
Any other ideas to try?
Oh I think I see what I did wrong… creating new routine of this then “set led mode”…
Assuming the routine ran and it’s not still a cache issue, that should have fixed the led mode tile on the device details screen.
Did the led mode change to what you set it to?
1 Like
The same way…
If the firmware tile isn’t populated then dragging down on the device details screen might populate it.
SmartThings broke the labels of custom capabilities which is why they show “untitled” and there’s a workaround, but I haven’t had a chance to apply it to all the drivers yet.
Fyi, the led tiles are supposed to get populated when the device is joined and I’m not sure why they’re not, but looking into it is on my to do list.
1 Like
Got it!
I’ll run some routines on those functions now, Thx!
I see a small anomaly in the ZSE42 water sensor. I have five of these, all 027A-7000-E002, all with driver 2b2a0ff7-033d-49a1-8142-b79f358f5624. But weirdly, in the yaml device report one of them has a “name:” of “zooz-xs-water-sensor” while the other four have “base-water”.
Also, for all five the device panel has four panes:
- Water sensor: Dry
- Untitled: 1.3
- Untitled: Synced
- Battery: nn%+ color bar
Is the first “Untitled:” firmware version and the second sync status?
The driver version is 2022-08-21T17:55:10.274818386. It all works fine but this seemed odd…
That driver only has 1 profile so I’m not sure how that’s possible…
I think this device is supported by the built-in drivers and “base-water” sounds like one of their profiles so I’m guessing that has something to do with the issue.
Try changing it to a different driver and then changing it to this one. If that doesn’t work or it’s unable to find another driver then remove one of them and see if everything looks OK once it’s added again.
Yes.
The “untitled” labels is a platform bug with custom capabilities which has a workaround, but I haven’t applied it to that driver yet. I was hoping they were going to actually fix the problem so I wouldn’t have to apply the workaround, but at this point I doubt they’re going to.
1 Like