Andremain
August 7, 2020, 12:39pm
1
i have quite a few alexa virtual switches inside yhe new app and they keep failing. I keep fixing them by going inside the ide and changing the published to self published but they keep failing after a few days. What is going on?
1 Like
Andremain
August 7, 2020, 4:42pm
2
Update. By changing the pushing setting inside the ide no longer fixes the issue
@Brad_ST please help me!!!
I added a new device of this type today. It shows up in the app fine, but the sensor and the switch no longer stay in sync.
Here you can see that the switch is off, but the sensor remains open.
Andremain
August 7, 2020, 5:33pm
4
The virtual switch does change state within alexa when changed inside smartthings, but it does not work with alexa routines anymore.
@Andremain That issue is due to the new alexa skill. See this thread:
I tweeted a bit about this , but thought it might be a good heads up for the ST nerds not on Twitter
1 Like
Andremain
August 7, 2020, 8:44pm
6
Well that sucks. I have lots of devices operated through virtual switches. Now my automations dont work.
BTW, here is the staff response on this issue:
Hi all, I wanted to address some of your questions and comments:
*We are aware of the issues with events not triggering for motion sensors etc and are currently testing a fix. I’ll let you know when fix is out so we can confirm that everything is working as expected.
*If you decide to switch to the new skill, you should not have to forget all devices in Alexa app before relinking.
*“Hopefully, the new Alexa skill will live sync devices better than the old skill does”
New skill reports any changes in SmartThings app to Alexa immediately. However, sometimes the Alexa app lags a bit in updating the state visually.
*Blinds are supported and can be set using 0-100%, there is currently no support in Alexa APIs to use more natural language like “open the shades”. If device only support open…
