My Smart Lighting app had been working great for years. I’d been using it primarily to turn lights on at sunset/off at sunrise, as well as some other routines. Just last week all routines quit working completely. I’ve deleted/recreated all routines to no avail. Is this a repeat of what happened a year ago? Is anyone else having issues? Granted, I’ve got a V2 SmartThings hub (STH-ETH-200) so it’s a bit dated but has been working fine and other than the Smart Lighting it’s good.
I’m also on a V2 Hub.
I rebuilt most of my Smart Lighting routines as regular Routines a few years ago when the supported number of Routines was raised.
I do have a few things in Smart Lighting that use the Sync With Switch operation. They ask seem to still be working without issues.
Hi, @philcook
We suggest you create those automations in the Routine section to recover your automations.
Most of the features in SmartLighting are already available in the normal Routines.
Have you reported the issue to Customer Support?
In this forum, we haven’t seen a recent report. The last one was about not being able to edit/see the Routines, but they still ran correctly.
Also, let me know if the change doesn’t work since we saw this report as well:
We already shared it with the team. But as far as I know, the SmartLighting works differently; the issues shouldn’t be deleted.
Another report of smart lighting routines not triggering here, at least not for motion. I have several switch sync routines that are still performing normally, but I don’t think I’ve seen any motion routines work correctly in at least a few days. I didn’t recognize it at first because I called it up to batteries needing replacement.
I could replace them with routines, but the smart lighting interface is cleaner. Built-in routines for motion sensors allow you to turn a light on and turn it off after no motion, but won’t allow other conditions. Standard routines allow more elaborate conditions but require a separate turn-off routine. Smart lighting combines both in a relatively understandable UI.
At the suggestion of @nayelyz I replaced the Smart Lighting with Routines a few days ago but they were not working as well, until yesterday. All of a sudden yesterday they started working and I’d not changed anything. Plus I’d been having issues with the hub not recognizing the current state of lights and locks but those too started working yesterday. Must have been some sort of update by SmartThings?
2 Likes
Hi, @philcook
I don’t know exactly what made it work again. But feel free to ping us again if you find another issue.
Hi, @MarkTr
Did your issue get solved as well?
Not that I’ve noticed. I’ll double check this evening.
It looks like Smart Lighting is still offline for me.
Does normal routines have a mirror switch option yet (sync physical switch status to virtual and visa-versa)? Smart lighting has been messing up for me as well with random ghost commands. Something would be on for while then suddenly shut off with no rules telling it to. If I turn off SmartLighting off then the ghost commands stop. If I turn a couple of devices on then randomly, another devices turn on.
This is all associated with power strips where the individual plugs do not show up as individual switches in ST. Therefore you have to use SmartLighting to syncs the nodes to VS.
You thoughts?
Hi, @MarkTr
So, in your case, only Motion routines are not working, correct?
Have you checked that the Motion event is being reflected correctly in the app? It has happened in the past that routines are not triggered due to communication issues with the device (and it can be identified thanks to the lack of events reflected).
If the events are shown for the Motion sensors, please help me with the following to be able to report it:
- Replicate the issue. This means you need to trigger a motion event from one of your devices.
- Provide the name of the device so we can get its info
- Take note of the date and time at which the event was triggered and share it with us as well, including your timezone. For example: April 10th, at 14:10 CST
- Open support access to your account:
Hi, @rontalley
You would need to create a routine per device to mirror its behavior in others.
The other option is creating a Rule through the Advanced Users app
Here’s an example of how it can be done considering two main switches to mirror. In the command section, you can put all the devices you want them to react the same way.
This is the text you need to put inside the symbols [] when creating the Rule through this tool:
{
"if":{
"changes":{
"equals":{
"left":{
"device":{
"devices":[
"deviceID"
],
"component":"main",
"capability":"switch",
"attribute":"switch"
}
},
"right":{
"string":"on"
}
}
},
"then":[
{
"command":{
"devices":[
"deviceID", "deviceID2",...
],
"commands":[
{
"component":"light",
"capability":"switch",
"command":"on"
}
]
}
}
],
"else":[
{
"if":{
"changes":{
"equals":{
"left":{
"device":{
"devices":[
"deviceID"
],
"component":"main",
"capability":"switch",
"attribute":"switch"
}
},
"right":{
"string":"off"
}
}
},
"then":[
{
"command":{
"devices":[
"deviceID", "deviceID2",...
],
"commands":[
{
"component":"light",
"capability":"switch",
"command":"off"
}
]
}
}
]
}
}
]
}
},
{
"if":{
"changes":{
"equals":{
"left":{
"device":{
"devices":[
"deviceID"
],
"component":"light",
"capability":"switch",
"attribute":"switch"
}
},
"right":{
"string":"on"
}
}
},
"then":[
{
"command":{
"devices":[
"deviceID", "deviceID2",...
],
"commands":[
{
"component":"main",
"capability":"switch",
"command":"on"
}
]
}
}
],
"else":[
{
"if":{
"changes":{
"equals":{
"left":{
"device":{
"devices":[
"deviceID"
],
"component":"light",
"capability":"switch",
"attribute":"switch"
}
},
"right":{
"string":"off"
}
}
},
"then":[
{
"command":{
"devices":[
"deviceID", "deviceID2",...
],
"commands":[
{
"component":"main",
"capability":"switch",
"command":"off"
}
]
}
}
]
}
}
]
}
}
The ghost commands are strange in this case, since the common causes are:
- A misconfiguration. This means routines colliding with each other.
- A third-party service sending them (like Alexa).
- Since it’s a multi-endpoint device, there can be something in the driver causing the propagation of the received on/off events to the incorrect endpoints.