I do see the options cleaned up on the red dimmers but my problem is with the red on/off switches and unfortunately, double pressed and held on the up, down, and config button also didn’t work for me on the device in question. These were suggested as working shortcuts to hold me over by @Bry so we know they currently work for some.
That said, i have a bit of good news: moments ago i removed and reinstalled both red series on/off switches i was troubleshooting with and after reinstalling, both, do now at least support double pressed.
Not sure if i didn’t get a recent update, edge drivers didn’t install right, etc but, after a reinstall, we can manage with the available shortcuts while you guys work on the rest.
If there is anything I can do to help, let me know. Logs, screen recordings, etc I’m up for it.
Just a guess here, but what happens occasionally is that when you add a device, it adds, but does not add fully. When that occurs, the switch only has partial functionality, such as what you experienced. Removing and re-adding the device, as you did, is the solution.
While it’s around, you can look at the raw description in the IDE. For devices that didn’t add properly, the details will not have been populated properly, displaying zeroes instead of the proper data.
I’m guessing this is what happened to your device the first time around.
@Triplethreat117 I have made the button press changes to the Red On / Off. I’ve also added the ability to set a different color for when the switch is on vs off. This is done via SmartThings for the Gen 2 Z-Wave stuff and not in the firmware like the Blue series. So there is a little bit of a delay when the switch turns on or off if the colors are set different. At least it mostly works and lets me re-use the capabilities in the Red and Blue.
@EricM_Inovelli good thinking - i do see the delay but it’s nothing crazy especially when talking notifications maybe 3s max?
I also woke up this morning to “double press” no longer working but a quick look at the routine settings revealed your update in place and now everything is cleaned up and seems to work - 3x at least works as expected so thank you for that.
I’ve updated the black series now to also support the LED color capabilities instead of the regular color capability. Now all of these devices should be prevented from showing up in Alexa as color bulbs.
Hi, since the update, in a scene we can’t update the LED bar color/level if we turn off the switch. LED options only appear if we turn On the switch. Can we enable LED options independently of the switch command ?
I may not be understanding you correctly, but are you talking about when you create a Routine and by default, the ON is selected? If that’s the case. Just press the ON and it will deselect. You do not have to turn ON or OFF to change the other parameters.
In a routine/scene, if I want to change the switch to OFF and change the LED color, I can’t anymore. I was able before the update. All LED options are unselectable.
I have been using the edge driver for the red series dimmer. It has been working great for 2 months. But with the latest driver (2022-12-08), my automation stopped working (Double UP and down). I just deleted and recreated them. It is now working.
My problem is with the notification LED. I do not want the LED to react when the light is off or on. I want to use it only in automation (Contact sensor open or closed) It used to work fine, but now with the latest driver, the LED keeps getting overwritten when I turn the light on or off)
Are you referring natively with SmartThings? I don’t recall ever setting the LED color from within SmartThings using anything but the color picks from the menu.
If you can address the switches externally, with SharpTools for example, you’ll have a choice of 256 colors.
I created scenes for each of my notification types (plus "clear notifications). My automations call the scene rather than referencing the device directly. That might achieve what you’re looking for. An additional advantage is that you can call up the same notification from multiple automations, and on multiple switches, without having to set all the parameters every time you call it.
I do the same thing on virtual switches. Set routines on the virtual switches to set notificatons as needed. The actual devices change the virtual switch state to start/stop notifications. I like virtual switches as they have an on and off state vs scenes which can only be “run”.
Sorry for the inconvenience, let me see if we can get this worked out. I think currently the solution would be to change both the On and Off color when something like a contact sensor is tripped. I can see that might not be ideal, so let me see what the best solution would be there. Example of workaround would be:
When contact sensor is open →
Change LED Switch on color to red
Change LED Switch off color to red
I will add some more colors to the list. I just need to verify that doing so won’t cause any problems.
Can you please try to create two separate routines? I believe this is a limitation of the SmartThings app where turning the device off disables all other options for the device. I don’t see how the changes I made could have caused this to happen.
I agree. Never realized that before. Tested with a non-Inovelli device and I am seeing the same behavior. As at @Ericm_inovelli suggested, two routines are the answer
Just realized there might be a different way to read your question. If the issue is that operating the switch is cancelling your notification -
Which switch, and is it on current firmware? I think with the Red Dimmers, the older firmware let switch operation override notifications, but newer firmware makes the notifications persist. Maybe other models do the same. I have one older dimmer and one newer - I was unsuccessful updating the firmware on the old one but haven’t tried very hard (aka removing from ST to update) - and they do behave differently in this regard.
The old edge driver (and the old custom Ide child device) allowed for the led indicator color to be adjusted using the color spectrum wheel. Now, the driver was updated with a drop down list of colors.
Got it. I never used the color wheel with the Edge driver, which explains my asking. With the Groovy driver you could have created a child object for the LED and used the color wheel there.
FWIW, the switch still has the capability to accept custom RGB values (0 - 255) even though the color wheel isn’t presented via the driver menu. So as an alternative, you can send that parameter to the switch externally, via SharpTools Rule Engine, for example. You might consider that as a workaround until either more colors are added and/or the color wheel comes back.
You can use the Inovelli Switch Toolbox to determine the RGB value to send.
@MarkTr322. Good clarification/question. I am using a red switch lzw30-sn, probably with an old firmware (not sure how to see the firmware version when using edge driver).
When I turn on or off the light connected to the switch I do not want the led notification light to change. It was working fine in the previous edge driver prior to Dec 8. I think the setting notification effect Off is not working.
