Start it in different modes, set temperature, set time, query remaining time.
3 Likes
Don’t remember seeing this issue, but anything I’ve named in SmartThings with an apostrophe in the name will not work properly in Alexa…or Google’s new skill version. The apostrophe gets deleted.
Example: Bob’s Lamp would come through as Bob s Lamp.
Old skill still works correctly.
2 Likes
Hi everyone. First of all, I would like to thank Lars, that PM me, and Abhijeet_Ghosh, that answered me here.
I did something that seemed to solved the issue for now. I do not know if it will last.
I think most of us based on this code to create the virtual sensor/contact to trigger alexa:
https://raw.githubusercontent.com/bjpierron/SmartThings-Alexa/master/devicetypes/bjpierron/simulated-alexa-switch.src/simulated-alexa-switch.groovy
What I did was to create a new device handler with the code above, but REMOVING the following lines:
capability "Sensor"
capability "Actuator"
I tried some routines triggered by this new virtual device and it worked.
Edit: I also used another “location” of the device. I don’t know the difference between these locations. Did some testings and maybe what solved the issue was to change the location, not to change the code.
Yes this happened to me too
It didn’t work. Do I have to create a new virtual device? I just deleted those two lines by going into the ide, deleting the lines, saving, and publishing.
@Lars
Any idea why apostrophes are no longer readable by the new skill? Those worked initially and now they’re disappearing when picked up by Alexa and Google.
@Abhijeet_Ghosh try creating the device in another “location”.
Do I have to do that for every device? It will be tedious. By the way, I can’t do routines between locations in smartthings connect. I’d rather wait in that case.
Anyone else having trouble getting Echo Speaks and Webcore work with Alexa lately? It is ever since the new skill came out.
This is insane - native alexa integrations work better than Alexa->ST->Kasa for instance and this use-case worked perfectly until the change. It makes 100% no sense to be why I can’t choose which devices I expose to Alexa and Google via ST - that should be user configurable and not an all or nothing approach.
Sadly, this breaking change (or regression) renders ST basically unusable in my configuration 
6 Likes
Rename all the masa devices to disabled, then disable them. The original integration will then work well.
Amazon and Googles asked us to remove special characters from names.
1 Like
This is weird, did the routines not work for you before you did that change? Voice service cares nothing for those two capabilities so that would mean that the event issue would be somewhere else in the platform. For now I would say coincidence unless it turns out to solve the problem for other users too 
And if it stays working, that is part of why it is hard to find the issue, since it comes and goes…
Now for changing location, that might be part of the issue. Ill check to see if your locations are in the same “place” server wise…
1 Like
So maybe that should have been announced to the customers? 
8 Likes
I have deleted them but it did not fix anything if I don’t change the location. Should I revert it back? Now they won’t show up as sensors or actuators in WebCoRE and I have to click find devices by capability.
Duh … I would think that would be something you would want to communicate with the users. WHAT other changes, did they forget to tell us about , or figured we did not need to know???
2 Likes
Agree, if they can’t comprehensively sort out this duplicate device issue, then this desperately needs to be reinstated.
As it stands an otherwise rock-solid Alexa skill has seemingly been butchered. It’s very frustrating.
4 Likes
I have to agree. I have 80-odd devices on my system, and only a few are connected to Alexa. There are some security based devices I would not want exposed outside of ST in any way, shape or form. I have an Amazon household account, so several others have access to my Smart Home stuff from there, and I wouldn’t want anyone to have any kind of access to my security devices, disabled or not. For me this is potentially a deal breaker…
2 Likes
Yesterday at night, Alexa started announcing each event multiple times with a 5 minute delay. Today, it is working as normal.
Same here. 