Can you share a screenshot of the driver page in the ST app? The page that shows the driver date, etc.?
Actually meant the default driver that creates the child devices. I would like to see it in action.
Sometimes it doesn’t do it right away, I just readded one, and i had to switch it back to the inovelli driver, and used it for a second, then when i switched it back to the zwave switch, the devices were created.
Typically when you make a change in a device driver / settings, if you go back to the Devices page, then select the device again, you should see the change take effect.
Known issue with the iOS app. You only see the main component in THEN actions.
1 Like
Well that’s frustrating. Wish there was a place that tracked outstanding issues.
thanks for the heads up though!
@EricM_Inovelli @Eric_Inovelli I am having the same issue with the fan module, I’ve created the virtual dimmers and set the smart lighting to mirror. When I turn the Main Switch on it turns both the fan and light on and updates the virtual switches but selecting the virtual switched on doesnt control the devices. I am unable to use a routine to test this as the isn’t an option for the channels I see only the main. I am also seeing a rather long delay in the light turning off after pressing the physical button (about 10-15 seconds).
I am guessing still no way to update the Blue’s firmware on Smartthings? I haven’t heard anything new on their forums
I don’t think it’s available yet (or if/when).
1 Like
Lately my Black dimmer on the edge driver has been somewhat unstable. It will go offline in Smartthings, but somehow even when it shows offline it will take commands with a long delay. Alexa control will stop working in this state.
I’m pushing an update to the LZW36 driver that has 3 options in the device settings:
- Create Light Child Device
This will create a child device for the light endpoint. - Create Fan Child Device
This will create a child device for the fan endpoint. - Disable Root Endpoint Control
Make it so that the main switch does not control both the fan and light at the same time. Useful if you want to only use the child devices for control. Helpful if you use voice control and don’t want the main device to be controlled along with the child devices.
I’ve been testing for a lot of the day and everything seems to be working for me, but let me know if there are any issues. It might take a few hours to show up for you.
3 Likes
So excited to see this. I tried the method @Jamesonrw suggested and it did create the child devices for me as well. The Z Wave Switch from Smartthings now has the Version “2023-05-09T18:33:45.26072198”. Inovelli Driver shows 2022-10-04. I wonder how long updates take to hit the hub and if there are any ways to speed up hub to check.
Update.
I was curious so I updated my Fan+Light devices to SmartThings Driver, it created the child devices. I then uninstalled/reinstalled the Inovelli driver from the invitation page. That pushed the newest version of the driver down to my hub.
I changed my devices from the SmartThings driver to Inovelli, this worked but my fan had a dimmer slider unlike @EricM_Inovelli screenshot. I removed the child devices and enabled the “Seperate Control” in the settings of the device and it created two new child items with the proper slider and logos.
1 Like
Ok, so sounds like positive results. I guess if you have used the SmartThings driver that created child devices you have to delete them to make the Inovelli driver work.
@pmjoen @Jamesonrw @danny.pena
Just a notification that our LZW36 driver has child device support now. If you have a working setup already there is no need to change it, but in case you are still having problems.
2 Likes
Thank you so much for updating this Edge Driver. I’ve updated my 4 Fan+Light switches and they seem to be working properly.
1 Like
I converted one of my NWZ37 outlet switches to Edge and can tell you how. It might not be a good idea, though. All that happened in my case was I lost the ability to rename the individual outlets. This is a major downgrade for me. Hopefully, I just haven’t learned enough about what’s possible.
Is it within the realm of possibility that I could figure out how to make my own Edge driver for this, one that would allow naming (and, better yet, ending up with individual devices)?
It would be great (and used to be possible) to directly tap on “bedside lamp” or whatever I have plugged into one of the sides. It would be great to be able to say “OK Google, turn on the bedside lamp.”
The multi component (main with sub components) style of device can’t change the names of the sub components. There is a documented label field for the subcomponents but it doesn’t appear to ever have been supported. And the names would be hard coded within the driver itself.
The easiest way is for Inovelli to update the NZW37 driver to support child devices. It would create top level devices for both outlets that you could do whatever you can with a single device, including renaming it.
I have a multi-component driver that supports the NZW37 and NZW97 but I never distributed it and it would have to be reworked to support parent/child type devices.
Thanks. My bad for migrating to the Edge driver. I’m using a virtual switch, but it isn’t a great solution because the on/ off state isn’t coupled with whether the thing is on or off. Oh, well.
@coreystup @sophware I just pushed an update to the “First gen” driver package that supports child devices for the NZW37 and NZW97. I think I got all of the fingerprints, but there were so many I may have missed one. Let me know.
2 Likes