Yep. Meross also.
On top of that, other zwave hubs are able to expose multi endpoint Zwave devices like the Zooz zen 30 for individual voice control of each endpoint.
So definitely, a smartthings issue. 
1 Like
In Alexa they show as individual devices
1 Like
Individual devices assuming youāre using the Manufacturers skill and not SmartThingsā
2 Likes
Kevin,
I have come across a potential problem with the Zen16 v1.04 when trying to add to a Zen34, when I select add action and select the Zen16 I only get the option on or off (first picture), and if i select relay 2 I get this (2nd picture), the third picture is what shows when adding to the if section of a routine.
It seems that any routine that I try to add to the then section of routines results in picture one
The driver isnāt determining what shows on that screen and I just tested that with a ZEN34 and it displayed the same screen as it does when creating a Routine.
Is that the iOS app or Android? If itās iOS then itās most likely a new bug in the recent updateā¦
1 Like
iOS
i just edited my previous post it is all routines in the Then section.
That makes sense, as I did not have this issue this morning on the first Zen16
1 Like
@nayelyz is this a known bug with the new version of the iOS app?
I just fired up an old Pixel and was able to edit the routines, so it is confirmed to be an iOS issue.
2 Likes
I havenāt switches my zen72ās over yet so havenāt tested. Can anyone tell me if there is dimming association before I manuallyove them?
I have 2 zen72 switches on a 3 way set up (1 only has power) so they are associated but it only has on/off association, not dimming.
The ZEN72 driver supports association group 2 (on/off) and group 3 (dimming)
2 Likes
Iām hoping to have the ZEN17 driver completed by tomorrow morning, but I figured it would probably be a good idea to post my implementation plan ahead of time in case anyone has suggestions or throws a wrench into my planā¦
When the S1 and S2 Input Type Settings are set to Momentary, Toggle (any), Toggle (up/down), or Garage Door:
-
The driver will display the main switch on the dashboard and just the 3 switches (main/R1/R2) on the device details screen.
-
It will have the āDashboard Viewā setting that allows you to see the Large tile on the dashboard with all 3 switches.
-
Iāve already finished this part of the driver.
-
Itās basically the same implementation as the ZEN16.
When the S1 or S2 Input Type setting is set to any of the other options (motion, contact, water, etc.):
-
The look/behavior will be the same as above, except there will also be a tile for each input (S1/S2)
-
The S1 and S2 tiles will be a custom capability that displays the Input Type and its value (Contact Closed, Motion Active, Water Wet, etc.). If only one of the input types is set to a sensor value then the other S# tile will show something like āN/Aā.
-
The driver will support all of the capabilities that are available as input types (Motion Sensor, Contact Sensor, etc.), but only the selected input typeās corresponding capability will change with the state of the input. The other capabilities will always be set to their inactive state. (inactive, closed, dry, etc.)
-
Since the S1 and S2 tiles on the device details screen show the type of sensor and its value the actual capabilities wonāt be shown there.
-
When selecting the device in a Routine youāll see all of those capabilities.
-
I donāt plan on including the āHeatā, āCOā, or āCO2ā input types, but I can easily add them later if requested.
-
The manual says you need to remove the device and join it again after changing the input type settings, which might still be required, but I wonāt know for sure until I start testing that part of the driverā¦
1 Like
I had to re-add ZSE40 sensor 4 times. 1st Time no Motion and Lux report. 2nd time no Motion, Temp and Lux. 3rd time No battery report. The last time all the attributes reporting.
FYI. This sensor is running 17.09.and after I included the device the iOS app show a security warning.
Thanx for the hard work . Hope this info is useful.
I know some had issues with the on/off option missing in iOS and they should have reported it to Customer Support but I donāt have any more info.
I will ask about this, it seems itās only affecting multicomponent devicesā¦
1 Like
I like the style of the DTH for what itās worth.
Iām running into some really inconsistent behavior with the new driver and my ZEN25 double plugs, which Iāve had installed and running the custom DTH for about 8 months now.
To test, I added the Zooz Multichannel Switch Edge driver to my hub. Next, I uninstalled all ZEN25 devices (via Z-wave exclusion) and removed the custom DTH in Graph. Once the DTH was gone, I reinstalled devices one by one to pick up the new Edge driver. After testing with the Edge driver, I uninstalled the devices again, removed the Edge driver from my hub, and then reinstalled the devices to pick up the standard (pre-Edge) SmartThings driver, which gives me a pair of devices (one Z-Wave Multi Metering Switch and one Child Metering Switch).
The device seems to install fine using the Edge driver, and it initially looks like it is working. However, after a while, it starts to become intermittently unresponsive. The usual symptom is that one outlet or the other stops responding for a bit and then eventually works again. Sometimes, if Iām executing a scene that is supposed to turn on or turn off both sides, only one or the other will actually change state.
Iāve also gotten into a situation several times where if I turn off both sides, neither will come back on via a scene until I go into the device panel and manually turn on the main on first. (Iāve tried to fix that in scenes by always turning on the main whenever I turn on either side, but that doesnāt seem to help in general.) The intermittent behavior plus the fact that Iāve reproduced this thing with the state of the main makes me wonder whether the problem is somehow related to order of operations.
These outlets have historically been reliable on the old custom DTH, and were also reliable after I fell back to the standard SmartThings driver, so it seems like the new Edge driver is somehow implicated in the instability. What can I do to help debug this?
Short answer, disable the metering reports to see if that solves the problem as a temporary solution and the next version I release will have a couple of minor changes which should solve the problemā¦
The hub kept dropping reports every time the main switch was used to control the ZEN20 and ZEN16 because too many messages were sent too close together which left some of outlets/relays showing the wrong state.
I had to include a workaround in the driver that checks the state of all the outlets/relays a few seconds after the main switch is used to control them and request a report for any that might be out of sync.
I just noticed that my ZEN25 driver used the hardware default value for the Power Reporting Frequency setting, which is 30 seconds, but my DTH used 5 minutes and the built-in driver uses 10 so Iām pretty sure thatās causing the problem.
Iāve never used scenes, but if they check the state of the switch and only send the on/off command if needed then a switch being in the wrong state would appear unresponsive until you performed an action that causes the state to get refreshed.
I know that Routines always send the on/off command so Iād be interested to see if you experience the same unresponsiveness if you used routines instead of scenes.
Iāll include that workaround for the ZEN25 and increase that settingās default value in the next version, but I suspect your problem will go away if you disable all the metering reports youāre not using or at least change their frequency to reduce the number of messages.
FYI, the hardware automatically turns on both relays when you control it with the main switch so using the main switch and an outlet in the same scene or automation could make the syncing problems worseā¦
I also just noticed that the built-in driver doesnāt support the main endpoint which is another reason why the on/off reports arenāt getting droppedā¦
2 Likes
Was going to post a reply to kpronovici but you literally confirmed my theory. I have two Zen25ās which one of them was basically oversaturating my Z-Wave network and causing timeouts on all Z-Wave devices. My Z-Wave network came back to life when I unplugged the sucker. For now Iāve just upped the frequency which seems to have resolved the issue. .
Also just wanted to mention that it looks like one of my Zen25ās is missing the option to turn off reporting which is the last option in settings. (I have the one that has this setting uninstalled right now which I forget the exact name) plus thereās some āUntitledā labels on random numbers which Iām guessing one of them is to notate the firmware version. Unsure if Iām the only one seeing this.
Edit - Just installed the plug I mentioned above. The setting thatās missing is in fact the āDisable Reportsā option.
That setting was added in the 2.0 firmware so if your device has a lower firmware version then you wonāt see it.
I added the translation workaround for those custom capabilities and I thought I reloaded all the presentations so you shouldnāt be seeing any āuntitledā labels.
If youāre using the iOS app then maybe they broke the workaround, but itās possible I forgot to load the presentation so I just did that again.
I was thinking the same thing too. I registered my plugs the other day to obtain the firmware and the ZST10 usb stick will be in tomorrow.
You make a good point which I didnāt think about checking out my other phone which I have access to both an iPhone (work phone) and an Android phone. For me, it looks like the labels are not set on my Android while the iPhone is showing the proper labels. Reinstalled the SmartThings app on the Android with no luck. (dunno if that would effect anything but did it just in case)
Android:
iPhone
Edit: Last post from me: Looks like the labels have reverted to the proper titles magically on my android and now I have more routines I can run against. Not sure if you did anything but I thank you for doing what you do.
Short answer, disable the metering reports to see if that solves the problem as a temporary solution and the next version I release will have a couple of minor changes which should solve the problemā¦
I disabled reports entirely (Iām not using them right now anyway) and that made a large difference in stability. Itās much more reliable now and there was only one time when a lamp did not go on when I expected it to. When I have a few minutes, Iāll upgrade the other outlets and confirm a similar improvement there.
I do have a few routines (triggered through an Aoetec Wallmote switch), but not for this particular outlet that I tested this morning. Iāll try that out once I convert the other outlets.