As I improve my environment - I'm relying more on the Amazon Echo Skill.
I think it was about a year ago, that, being delicate, voiced issues - about certain skill responses were failing - ie; alexa would say 'blah blah isn't responding' a new modification appeared:
The 'Respond immediately without waiting for device'. This did solve many items but in general it was harmful to my environment. Why do I feel I can say that? Because not ALL the devices had problems, more than most were already working correctly. IMHO it was a work around, not a fix. Regardless.
I submit that this should be 'per device'. It is NOT all or nothing. In fact, it breaks as much as it fixes. Today, working on more of my migration I kept getting 'Garage Door Failed to Respond', when, in fact it operated correctly (using a Tuya GDO with community created Simple GDO app- not that it should matter).
As you can see above, I enabled it. And the Vacuum broke. At least, the vacuum can no longer report it has returned to dock, as Alexa - not waiting around for things to occur, doesn't see the Vacuum hasn't yet returned to dock. This has worked since 2024 but is now forcing me to choose, do I want the Vacuum to work right or the GDO?
I'm certain my post on this is just for documentation purpose - but at least the wayback machine will see it when some future user stumbles on to it.
FWIW, that has been there since platform version 2.2.2, over 5 years ago,
Can you share more information about this device, including what the driver is, what capabilities the driver has if it's custom, and how it appears in Alexa (switch, contact sensor, combination of these or others, etc.)? Enabling this option shouldn't break anything -- just makes the hub say the device responded as soon as the command from Alexa is received rather than waiting on the device state to actually report a change and for that information to make it back to Alexa. But it's possible something is wrong with the behavior for devices with specific combinations of features. That would help figure it out. Thanks!
That being said, a per-device option is an interesting request, and I think it would be technically possible. Anyone have other thoughts on this?
While probably not relevant to this request, I don't really understand what this means. All Community posts since the beginning are still available -- no digging through others' archives needed.
You’ve said this many times over the past six years, so I’ll say it again.
Feature requests from users are incorporated all the time. Perhaps you mean that the feature requests you make don’t get acted on.
Did you notice that Robert appears to be considering how to implement this feature request that you’ve made?
And if you don’t believe Robert (or you haven’t been paying attention as you just acknowledged you haven’t), take a look at the hub platform v. 2.2.2 release notes from July 2020 for yourself.
This feature request has been added to the newest hub beta platform release. Since not all users can see the beta category of the forum, here’s the relevant section of the release notes (emphasis added):
Revamped Amazon Echo Skill app to support changing primary device type exposed to Alexa; added ability to remove undesired attributes; changed "respond immediately" option to per-device instead of global option; added ability to override "open" voice command percentage per-device for blind/shade devices.
