[ST EDGE] Zooz Edge Driver Channel

How many custom Edge drivers do you have installed? Smart things will only let you have a maximum of custom 50 Edge drivers. It appears that you’ve hit your limit. This is why I am waiting until SmartThings migrates my devices to see which devices need a custom Edge driver so I don’t use up my custom spaces unnecessarily.

2 Likes

Hi all,
Sorry if this have been addressed before.

Is there an Edge driver for “Zooz S2 Multisiren” ?

If not, will there be a driver for “Zooz S2 Multisiren” published in this channel in the near future?

Ps,
I have tried to change the type from “Zooz S2 Multi Siren” to the “Zooz Multi Siren” but that made the siren not working any more.

Best regards,

arcspin

Zooz Multisensor Driver - Update (9/20/2022)

I just published a new version that supports the ZSE44 Temperature | Humidity Sensor

Supported Devices:

  • Zooz ZSE11 Q Sensor
  • Zooz ZSE18 Motion Sensor
  • Zooz ZSE29 Outdoor Motion Sensor
  • Zooz ZSE40 4-in-1 Sensor
  • Zooz ZSE43 Tilt | Shock Sensor
  • Zooz ZSE44 Temperature | Humidity Sensor
2 Likes

My ZSE44 and Q Sensors work great with this. Just waiting on the Zen51 for my Smoke Alarm Relay. Thanks for the good work.

1 Like

If reporting 1% while on usb power, it means you paired it incorrectly. I just fixed two of mine this past week and need to do another.
To fix, you have to exclude and readd. This time, when putting it in inclusion, hold the zwave button for 5 seconds instead triple tapping. That pairs it as a powered device with repeat function instead of as battery.
Keep in mind, automations break when you exclude.

1 Like

Zooz Multichannel Switch Driver - Update (9/21/2022)

I just published a new version that includes the ZEN16 MultiRelay.

It supports firmware 1.00 - 1.04 and it should only display the settings that are supported by the device’s firmware, but I only tested versions 1.00 and 1.02 so let me know if you notice anything weird.

It also has the “Dashboard View” setting and if you change it to “Large” then you’ll be able to see all 3 Relays in a large tile on the Dashboard.

Supported Devices:

  • Zooz ZEN14 Outdoor Double Plug
  • Zooz ZEN16 MultiRelay
  • Zooz ZEN20 Power Strip
  • Zooz ZEN25 Double Plug

   

   

Upcoming Drivers in order: ZEN17, ZEN15/ZEN06, ZEN51, and ZEN52.

6 Likes

Kevin,

Thanks, I have just installed it on one of my ZEN 16’s firmware 1.04, so far it appears to be working as expected, I will update you if any issues show up, and will convert my other two units this evening.

I migrated my Zen16 (fw 1.02) to your new driver and it seems to be working as expected.

@krlaframboise, thanks for the drivers.
I purchased a ZSE44 and it paired immediately with your driver. I have a couple fo questions:

  1. You can set a “Heat Alert Temperature” and a Freeze Alert Temperature. What happens if the temperature goes out of that range? Do you get a notification? If so that would save a couple of routines to get same alerts.
  2. My use case is temperature for a Refrigerator and freezer. Can the Heat Alert temperature be lowered from 50 degrees to maybe 32 degrees?

So I allowed the temperature to drift out of the range I set. I did not get an alert. Even the “Temperature Alert” shows normal when it was outside of the range. So how does this work?

It changes the state of the Temperature alert attribute so if you want to receive an alert you’d need to use that attribute as a condition in an Automation.

I used the range supported by the device…

Did you manually wake the device up after changing those settings? The procedure for manually waking it up is to push the action button 4x quickly and if it’s successful the LED should flash once.

I uninstalled the custom DTH for the ZEN16 and deleted/re-added the device after installing the new drivers. The device shows up and when I pick the large tile layout from settings, I can see 3 relays (Relay 1 to Relay 3).

But I don’t see any separate child devices? Can this still be done, or do child devices behave differently now?

I have the Zen16 in the garage - 2 relays control lights in the front yard and 1 relay controls light in the back yard. I’m used to being able to see 2 child devices in the front yard and 1 in the back yard.

At a minimum, is there a way to rename the relays based on what they control even if I can’t associate separate relays with different locations?

Update: Furthermore, I tried turning different relays on and off. While that does control the corresponding set of lights, logging doesn’t show any information about which relay was activated. I have yet to try routines or voice control.

Short answer to all your questions is No.

Edge drivers for Hub Connected devices currently don’t support creating standalone child devices which is huge problem because it prevents you from using the individual devices with 3rd party integrations like Google Home/Alexa.

That being said, a community developer figured out a way around that limitation, but SmartThings doesn’t recommend it so I won’t be using that workaround in any of the Zooz drivers.

I might reconsider once I’ve finished all the drivers on my To Do list…

1 Like

This can also be solved by creating virtual devices that are only intended for voice announcement and linking them to your desired component. In this case, you can connect your relay component to virtual switches and Alexa will allow you to address them by name.

2 Likes

Zigbee and zwave devices no longer fit the parent/child paradigm in the new architecture. Instead, the device is considered a “multicomponent“ device, but the problem with that, as @krlaframboise already mentioned, is that only the primary device is exposed to third-party integrations like voice assistants, so you no longer have a way to voice control the individual components. And you can’t put them in different rooms or easily rename them.

One common workaround right now is to create virtual devices and use routines so that they match the activity of the subcomponents, and that way you have something that you can control by voice, you can put in a different room, and you can name whatever you want.

But it’s a lot of extra work and it uses up devices and routines from your overall quota. :disappointed_relieved:

Hopefully smartthings will come up with a better solution soon, but at least this is an option now for those who haven’t already hit their device limits.

You can find community-created edge drivers for these by going to the quick browse lists in the community – created wiki and looking for the list for virtual devices.

https://thingsthataresmart.wiki/index.php?title=Quick_Browse_Lists_for_Edge_Drivers

I’m definitely not saying this is a good solution, I’m just saying it is a functional workaround for now. :thinking:

1 Like

It doesn’t seem like multi-component devices are a new thing that should be a surprise to SmartThings and their developers. Given they’ve been pushing/planning this transition for awhile now, I would have thought they’d have a built-in solution by now. It seems like they shouldn’t be saying, “the requirement of supporting the “parent/child” model for Zigbee/Z-Wave will be analyzed later on.”

Certainly, I’m going to have to find a workaround because now Google Home/Assistant sees my Zen16 Multi-relay as a single device. If I turn it on, all relays are activated and vice versa. I can’t control individual relays nor see their separate states elsewhere. Even in the app, I now have to remember what Relay 1, 2 or 3 controls and don’t have a nice way to label them.

I hope @nayelyz and the Developer Support Team are paying attention to this.

2 Likes

This is what the virtual switches allow you to do. I did the same thing with a pair of devices tied to a zooz multi relay.

2 Likes

I think the multi component model is better than parent child devices personally. The issue is the interfaces to systems like Alexa or Google Home don’t support them, but that shouldn’t really prevent ST from trying to move to a better (IMO) model. Alexa still doesn’t support multiple locations internally (all devices on an account are shared, no way to divide them up besides groups which isn’t really dividing anything).

Definitely a lot of work and more routines, but the device count is the same. A device with 3 relays in the old model would be 1 parent 3 children (total of 4). A device in multi component with virtuals for each of the 3 relays is a total of 4 also.

And I would argue that virtuals allow for a better “plug in” than a child device. The child device handlers were “tied” to the parent directly and could only do what they could do. Virtuals can be swapped out for all sorts of behaviours, ala @blueyetisoftware’s fancy new virtual building blocks.

1 Like

I like it too when viewing in the app, but two things need fixing to be perfect IMO:

  1. ability to rename child switches
  2. Voice assistant compatibility

I don’t know why SmartThings can’t fix #2. Companies like TP-Link kasa have had multi component devices for years that expose all the switches individually to voice assistants. SO clearly the problem is on SmartThings’ side to fix.

2 Likes

I’ve never tested one of the cloud multi devices linked to Alexa. All my Meross and TP link devices are singles. How does it appear? As 2 device “line items” on the Alexa side? Or 1 device with multiple controls?