Yeah I moved a SWATH of devices over to ST and it seems to be working MUCH faster and hitting much higher rates of change (15 switches now takes ~2-3 seconds instead of 10+).
I’m pleasantly surprised with their development in the past 2 years or so.
Still no MyQ, still no Alexa speaker utilization, still no “level 2” automation builder in the app (choose, if/then, etc.). Biggest miss for me is the circadian lighting. Wish that was available in new app.
Installed the Smartthing Edge driver for LZW36. Everything is working great both local and remotely by Smartthings app through the one switch but find it cumbersome to drill down into the settings to turn on the light and fan independently. Want to confirm there is only single switch in Smartthings app and not missing child switches to control the light and fan independently.
in other subject… is there a “fix” in the way for this “issue” where google thinks inovelli switches are color bulbs?
this might not sound as a big deal but it’s a little annoying that you can change the LED color if some speaker heard you and changed one or more switches LEDs by mistake. plus, google insists in grouping all lights and you cannot change the device type in google home, as opposed to other switches.
Admittedly, I haven’t had a chance to really dig into the Edge Drivers at my house yet because they had beta testing off for the WiFi router ST hub and I just realized they turned it back on so I’m now testing them.
I have Google Home at home and will do some testing this week.
Can you let me know a bit more about this issue? I can try to replicate at my house.
this issue is been inherited from the device handlers. is not something new. Eric once told me to remove a string from the DH and that solved it (color control, if I recall correctly). but can’t do that with the edge drivers. that’s why I haven’t installed the driver for the black series. since they don’t have scenes, I don’t need to install a dedicated driver. should I do that, I’d have 2 more switches seen as color bulbs, thus adding up to my issues.
google thinks it’s a bulb, not a switch. and as long as it does, you can change the switch LED’s color either by voice command or in the google home app. and it’s very common for smart speakers to misunderstand your commands. plus, if the speaker that “heard” you is not in the same room as the switch is (or that room doesn’t have a bulb added in google home), ALL your bulbs are gonna change to that color.
I remember once I summoned one of the speakers but funnily enough, a speaker in the other room was the one to pick up my command… and did it wrong! so it changed ALL my bulbs in the house to orange (included the 4 inovelli switches.
Is anyone running the new Edge Drivers with an LZW30-SN experiencing an issue where scene commands for 2 up presses don’t work even with scene commands for 1, 3, and 4 presses working?
last night I factory reset the switch and installed it again and now notifications work perfectly. it seems there was some bug with the switch that was crushed when I did the reset.
For some reason my old device handler stop working. Neverless I installed the new Edge driver but how can you do an automation only to control the notification color of switch without requiring to turn on the load? My old device handler I had virtual switch that controlled the notification color. The new edge driver requires the switched load to be turned on to control the notification color.
Can the edge driver have a option to leave the switch load state in current state and allow the other aspect of the notification to be modifiied?
That is how I do it but the edge driver for the Red Dimmer does not allow for the switch load other than “Turn On”. If you use off it will grey out all other options. See image below.