Hi @Lars, I have noticed you PM’d a few people with the same issue as myself, i.e. child devices are not showing in the new Alexa Skill. Is there a solution or work around for this? Thanks in advance.
I had very similar issues with devices no longer turning on and off via Alexa since changing to the new skill. I decided to delete all devices, disable the skill and start again with discovery.
Everything working fine now… obviously.
After talking to people about this I have identified the issue. However, I cannot yet give a date to when this will be fixed.
Be nice if it just picked up among the devices that worked before
In case you are using Google too, the corresponding changes are now live for Google as well.
I’ve read the subsequent posts/replies and I don’t see that anyone else has addressed the question of excluding individual devices from the ST-Alexa link? Is this not possible in the new skill?
It’s been mentioned. You can no longer do it in the smartthings app. Instead, you have to allow the devices to be added to Alexa, then go into the Alexa app and individually disable each one you don’t want to use with Alexa.
It’s tedious, and there is the window when they are added before you get them disabled, and they will continue to be visible in the Alexa app. But you can remove the voice functionality if you want.
Got it. Every time I discover new devices on Alexa, though, will it add those back, or can I permanently block them using the Alexa web portal?
If you delete them from the Alexa app, they will get added back next time.
If you disable them in the Alexa app, then voice control won’t work but they will remain visible on the Alexa list of devices.
So it depends what you are trying to accomplish.
and most importantly, they will remain disabled when discovering devices again.
What hasn’t been answered thus far is if there are any plans to re-introduce the ability to select what you add to the skill to avoid the above (hugely time-consuming) process, that messes up your Alexa app with duplicates everywhere, some active, some disabled with no way of knowing unless you re-name everyone of them or click on the device. Surely this would make for a much better user-experience if implemented and save everyone a ton of hassle?
All true, but no official response yet although multiple customers have made the same point.
Among other things, as I mentioned, not everyone wants all of their devices to be exposed through the Alexa app device list, not just because they don’t want them voice activated, but perhaps for security reasons. Just sayin’…
I can’t even imagine how difficult this must be for many. I am a 300 device user (max) and only need Alexa control for 1/8 of my devices. The naming is already a mess. To have to contend with 300 devices screwing up my voice control would be disastrous.
Now imagine you have to make the changes by listening to the list of devices.
This. Exactly this.
Me no like.
Me no like either, and I’m glad I didn’t move to the new skill. I’m at 271 devices, with maybe half in Alexa.
Between this skill being rolled out without much in terms of release notes, and the issues and concerns people have, and the multichannel zwave issues (with Fibro devices for now) plaguing the latest hub firmware release, I can’t imagine what virtual meetings must be like for the ST guys right now.
I’ll be honest, it doesn’t seem to be any different than most of the previous rollouts. Going all the way back to the V2 hub. Things change, things break. Nothing new there.
I’ve been screaming for years that SmartThings desperately needs closed beta testing. With such a strong community, they would have plenty of volunteers and could easily catch problems like this. Other large IoT companies (Ring, ecobee, wyze, etc.) have functional beta programs that catch stuff. Anyway, off my soapboax…