What Edge driver for Inovelli dual channel outlet

What Edge driver for Inovelli dual channel outlet? I haven’t found one that works.

In the Inovelli forums their staff said a stock dual channel driver should work. A couple of people asked about it but nobody followed up to confirm whether that did it for them.

1 Like

@Mariano_Colmenarejo “Z-Wave switch and Child Mc” Edge Driver might work. I use it on my old Inovelli double plug after Mariano so nicely modified it so it would work.

1 Like

I installed them from the site, but they do not show in the list of drivers.

Is that the one that says (OLD) if not please provide link.

The drivers currently in their channel don’t include one for this plug - I meant the ST stock drivers, but I don’t know which specifically would/should work here.

Old would work for now, but you want the version without old. He released a new version in the past day or two. As SmartThings breaks thing Mariano quickly fixes his drivers.

Thanks, I hate having to stop using this dual channel plug.

What model? I have an Edge driver that supports the NZW-97, the outdoor dual outlet adapter. Its in final testing and @philh30 and I should be releasing it soon.

It is the indoor Z-Wave dual channel. I will love to try it once you launch it.

Follow… got two of these

Specifically, for the record, I have the NZW37 Inovelli Smart Plug 2 Channel Zwave Plus indoor switch.

Okay, just got it working for me. Removed from ST hub via go to app, remove device to enter exclusion mode, then on Innoveli device, cycle power button 5x quickly. This removed it with its old drivers. Next, add a device in the app, search by brand Inovelli, then the only option is light switch/dimmer… select it. It says to cycle power on device 3x but I did 5x. And it was properly recognized as an outlet, and I have control of both sides of the switch, and it shows as local. Hope this helps someone.

1 Like

Isn’t the end result of switching to Edge not being able to rename each side of the switch, anymore (and not being able to revert)? Is there an advantage to Edge in this case? Is there a way to rename the sides?

It appears you are correct in that I see no way to change the names of the sides.

Routines can still control one side or another though. So maybe just create virtual switches to either side with the names you desire? This is an indirect approach of course, and frustrating that one must resort to roundabout ways to get what one wants, but this may work for you…

Virtual switch is much better than nothing!

1 Like

I have several Inovelli NZW37 Dual Outlet’s that were converted and have stopped working correctly.

The Edge driver ST selected was Z-Wave Switch and Childs Mc @Mariano_Colmenarejo but when activating the main switch both turn on/off, the slave switch has no effect. I tried switching to the ST Z-Wave Switch (default) but it does the same. Can anyone suggest a solution?

zw:L type:1001 mfr:0312 prod:B221 model:251C ver:20.17 zwv:4.54 lib:06 cc:5E,85,59,5A,72,60,8E,73,27,25,86 role:05 ff:8700 ui:8700

Hi @gst

This device has a profile with the “main” component that simultaneously controls switch1 and switch2.

The switch1 and switch2 components control them independently.

If it doesn’t work like this then this is a stock driver endpoint assignment problem.

The base of my driver was the stock driver to which I added other functions, components and subdrivers.

I already corrected several misassignments of endopoints in other devices when users were testing them, but not all of them have been tested during these 2 years of transition to edge.

I can’t correct it until August, that I have access to the CLI and pc.

You can open an incident in smartthings to fix it, since those devices are in the stock driver, I hope they fix it before August!

Maybe @nayelyz can help you in the process

1 Like

My Inovelli (Show Home) Dual Outlet works as expected. You debugged it months ago when you initially released the driver.


Thank you for the responses, you helped me solve it.

The issue was the conversion left the old child device which is tied to routines but now obsolete, your driver is working as expected now I understand how it works and have removed the old device.