Alexa Skill does not support SmartThings button

[bertabcd1234]

Except Alexa only lets you use motion or contact sensors to trigger routines, so a switch won't work. The rest is exactly what I'd do (and have recommended several times to apparently unwilling eyes).

@nfatoys

Or is this simply a guess?

We don't need to guess. Echo buttons are specifically called out in the UI as a special type of device, and you can go into the regular "Devices" section yourself and see that only motion and contact sensors are exposed. It would make so much sense if even just switches were exposed asís often assumed; alas, not even they are.

[mike.maxwell]

@bertabcd1234

Except Alexa only lets you use motion or contact sensors to trigger routines, so a switch won't work

I see, I don't use alexa routines, so no idea on that, thanks.

[corerootedxb]

@mike.maxwell

personally I would create a virtual switch device, then build a rule using the button controller to toggle that switch, add that virtual switch into our Alexa integration, then do what you need on the alexa side to control the alexa wifi devices...

Unless you have made a change to the Alexa skill (or that capability is a server side rollout on the Amazon side), virtual switches are not available for actions. I have about 15 of them shared to Alexa and cannot trigger a routine based upon them.

[Ryan780]

@mike.maxwell

personally I would create a virtual switch device, then build a rule using the button controller to toggle that switch, add that virtual switch into our Alexa integration, then do what you need on the alexa side to control the alexa wifi devices...

@Ryan780

Now, what you can do is create virtual switch devices in HE and then link those to Alexa. Alexa does support switch devices. So, you create a virtual switch in Hubitat and when it's on, turn on the other switch in Alexa and when it's off turn the switch off in Alexa. If you ABSOLUTELY have to control this switch with your ST button, set up a button controller in HE to toggle the Virtual Button when it is pressed. There.....problem solved.

Is there an Echo in here. Get it....Echo. As Alf would say, "I KILL ME!"

And mike, that was not a criticism...just a perfect opportunity to use a pun I've had in my back pocket far too long. hehe

[nfatoys]

@corerootedxb

An easier route would be to just write your own apps in Groovy. The language itself is dead simple and doesn't carry the limitations or overhead of RM.

GROOVY? That's a new one to me. Over the years I've written programs in every sort of assembly language, Basic, Forth, FORTRAN, Pearl, C, C++, C#, and a couple mini compilers I wrote myself. Is Groovy the native code for HE? Is there an IDE or Compiler available to play with?

[mike.maxwell]

@corerootedxb

or that capability is a server side rollout on the Amazon side

yeah, this^, we have no control over what they allow in the way of routines.

[mike.maxwell]

Groovy sits on top of Java...

[Cobra]

https://groovy-lang.org

[corerootedxb]

Groovy is "basically" a subset of Java and seeing as you already have ECMA based language experience, it should come naturally to you. Think of it like VB for apps (I dreaded that language).

There isn't an IDE or compiler, but if you explore the Apps Code/Drivers Code sections on your hub, you'll come across the built-in editor.

Groovy Language Documentation and Groovy Basics — SmartThings Classic Developer Documentation will get you stated quickly. I hate sharing SmartThings links, but they do have some great documentation on writing apps and drivers and Hubitat and SmartThings, from a developer's perspective, is nearly identical.

[nfatoys]

@nfatoys

If I want to add two or three or more buttons into the mix, then I'll have to create two or three or more identical Virtual Devices and Rules to support them. And though I really appreciate what Rule 4.0 programming brings to the table, the interface has much to be desired. I only wish there was a way to export rules to text files, that could be edited and imported back into Rule Machine.

@mike.maxwell

personally I would create a virtual switch device, then build a rule using the button controller to toggle that switch, add that virtual switch into our Alexa integration, then do what you need on the alexa side to control the alexa wifi devices...

As I originally stated, I've implemented Virtual devices and Rules to trigger Alexa Routines. But, as I also stated this requires creating a new duplicate Device and Rule for each new ST button added. Not as simple as just pairing a new device.

[ogiewon]

@nfatoys

Not as simple as just pairing a new device.

We are all in agreement with you on this! The community has provided you with workarounds based on the current hardware you own, and the current capabilities of the Amazon Alexa platform (i.e. only motion and contact sensors can trigger Routines via a skill) and the existing capabilities of the Hubitat platform.

As you have acknowledged previously, the long term solution is to replace the WiFi devices that you'd like to control via Hubitat with devices that are natively supported by Hubitat. While not the 'easiest' on your wallet, it is "as simple as just pairing a new device."