Hi, I have installed zimi powermesh bluetooth switches. I am located in Australia. I have enabled the ZIMI skill in Alexa and the switches show up fine and can be controlled by Alexa. If I have the smartthings skills also enabled in Alexa, why wont the bluetooth switches show in Smartthings. (Im new to bluetooth integrations, sorry if i missed something stupid.)
The integration between smartthings and Alexa exposes smartthings controlled devices to Alexa but not the other way around. So those Bluetooth devices will not show up as Devices in smartthings unless they have their own separate smartthings Integration.
You can get a partial integration by using an Alexa routine and a smartthings virtual sensor so that when the virtual Sensor opens, you can have the Alexa routine turn on the zimi Switch. But it’s still only one way. If you turn on the zimi switch in any other way, including via voice control to Alexa, SmartThings won’t know it was turned on.
Whether that’s useful to you or not, just depends on the details of what you are trying to accomplish.
There are many devices that fall into this situation. They work with Alexa or Google assistant but not with smartthings.
It’s possible that the new “matter“ standard being introduced will help with this and more devices will become compatible with each other, but that will likely be early next year at the soonest and won’t cover all devices, just those where the manufacturer has decided to add matter compatibility.
Here’s the FAQ on setting up the integration if you do want to try it:
JDRoberts, thanks for the clarity on the one way nature. That was the piece I was missing. I was looking to create smartthings automations and have the devices show up on a actiontiles browser. Thanks for the link!
You can set up virtual switches to be proxy devices and put those on your action tiles dashboard, but again it’s only going to be a one-way Integration. You’ll be able to turn them on and off from action tiles via the Alexa routine method, but the status won’t always be right because of the synchronization issue.