SmartThings Edge Drivers: LZW30-SN, LZW30, LZW31-SN, LZW31, LZW36, LZW41, LZW42, LZW45, LZW60, VZM31-SN, VZM35-SN, VZW31-SN, VZM36, NZW30, NZW31

Thanks for posting the pictures showing that, I was going to try to post a video but got side tracked. Are you using an iphone as well?

Yes, I’m also using an iPhone. Must me a ST software issue just not sure how best to address it!

Seems to be iPhone App only, as Android is still working OK.

Not sure if either or you guys are running SharpTools, but you can set notifications with the Rule Engine there as an interim fix.

1 Like

Thanks @Bry. I am running SharpTools. I actually don’t have an immediate need but was more validating @PJones bit SharpTools is a good idea for a workaround if needed in the meantime!

1 Like

Was a driver for nzw37 ever released?

1 Like

Yeah, it looks like the recent iOS update is causing an issue with the ability to use custom capabilities without turning the switch on or off. I am reaching out to their support. Not sure if @jody can help in this regard.

There should be a zwave-switch driver from ST that supports the nzw37.

1 Like

Thanks! Found it!

1 Like

Does this mean there is still no way to change over to the edge driver without excluding and re-adding the red dimmer switches? Is there any type of ETA on when the switch to the native driver would happen automatically by Smartthings?

AFAIK, excluding and re-adding is the only way.

Samsung has stated that these would be accomplished Q1 2023, but this date has been slipped. So my opinion is it will happen sooner or later, maybe . . .

To me, it’s not that big of a deal to remove and re-add. You can preserve routines but inserting another device as a placeholder. Other than that, it’s about a minute or two to remove and re-add, and then a bit of time tweaking some code.

I got a response last night and they are aware of the issue and are looking into it. I will post back when I receive an update.

4 Likes

I am pressing Samsung because I deleted, reset, and added the on/off switch device but the Inovelli Red series Edge driver did not come with the add even though it is on the hub list of Edge drivers. The add device pulls the Smartthing generic Z-wave switch driver by default. I go back and delete the generic from my hub list and no matter how many times I go through this delete/reset/add process, the generic comes back on the hub list. When you choose Select other drivers, there are none listed. I even deleted the old Inovelli driver from the IDE so all was clean. Waiting on Samsung.

It may well be on the Samsung side, but out of curiousity, let’s check this:

Log into the channel, click on the available drivers button and screenshot the Red Switch and Red Dimmer entries.

It should look like this:

image

Bryan, here is what I took from your channel, and is on my hub list of drivers.

Yep, that looks correct. Are you sure it’s a Red and not a Black?

@rcjny0829 If it came in a black box then it is a Black series not a Red. I would load the black switch edge driver. Exclude and factory reset the switch and add it again.

2 Likes

Bry,
That’s why you get the big bucks. I loaded the black series driver and it went as it should. Your assessment based on the box it came in was correct–thank you for helping.

2 Likes

I messaged ST support again and they have no ETA on when it will be fixed, but that they are aware of it. I have been working on a workaround, but it is not ideal. If they don’t have any more info by next week I might just implement it. It essentially will delay any on / off commands by a second or two to wait to see if any other capability commands come in. If they do, then it will cancel the on / off. Not ideal if you actually do want to do an on / off command with a notification, but I am not seeing any other workaround. SharpTools may be the best solution as I have no idea how long ST will take.

You could probably work around it in smarthings but it would take extra automations to do it.

The particular one I discovered it on (my dining room light) I use the notification to tell me both doors are locked and the garage door is closed. I guess I could add “if dining room light is on” as a pre condition, and both locks are locked and garage door is closed, change the notification to green and turn the light on. Which would not change the state of the light because it was on, then you could copy the routine with a precondition of “if dining room light is off” and all the above conditions are met, make the notification green and turn the light off, again not changing the state of the light because it was already off.

But honestly my workaround right now is, create the automations and then call my son and have him log into my account and deselect that option on his android phone.

1 Like

That is actually a really good idea as a workaround. Hope that SmartThings gets it sorted out soon.

2 Likes