Alexa Device Status


(Gene Clark) #1

I’m not sure where to post this and also know this is possible using Ask Alexa, but here I go anyway. When I ask Alexa if my devices are on she responds saying “blank device doesn’t support that”. Just curious if there’s some devices that do support that feature out of the box or if perhaps it’s a feature that may be coming soon.


#2

Not yet available as part of the official integration. A lot of people suspect it may be coming eventually, but nothing has been announced. As you mentioned, it could be done with askAlexa, EchoSistant, or other advanced skills.

For those interested in researching more about the currently available third-party skills, use the quick browse list in the community – created wiki, look under project reports, and check The Voice list. :sunglasses:

http://thingsthataresmart.wiki/index.php?title=How_to_Quick_Browse_the_Community-Created_SmartApps_Forum_Section#Quick_Browse_Links_for_Project_Reports.2FQuestions


(Bobby) #3

I don’t remember how @MichaelS is checking to determine if the device is on or not. He could probably tell you why you get the error you get. EchoSistant is set up to look at the device’s main capability, which is different than checking the “heartbeat” (just because not all devices support that capability).


(Micheal ) #4

It is my understanding from the post above this is with the native integration…Not with a custom SmartApp…Either way, this appears to be a null label…While the ‘name’ may appear correct, the label may be empty or null. This is the only thing I can think of if this is the native integration. Again, you hit the nail on the head…Ask Alexa does this better than the native integration.


(Jason "The Enabler" as deemed so by @Smart) #5

Pretty much ask Alexa and EchoSistant does everything better than the native integration.


(Joel Smith) #6

Now I am getting basically the same response when I ask Alexa to “Turn off Cooking.” She is responding with “Cooking doesn’t support that.” Started today (near as I can tell). Notice, I’m not asking for a device status, as OP was, just asking her to turn off a light (actually a group of HUE lights) she has had no trouble turning off and on for several months. I have both Ask Alexa and EchoSistant installed and (I’m pretty sure) up to date. But tbh, she’s been acting up in a number of ways since ES went in (maybe @bamarayne can help me figure out what’s tripping her up).

Thank you, nonetheless, to the very talented dev community we have here.


(Jason "The Enabler" as deemed so by @Smart) #7

What kind of ways has it been messing up?


(Joel Smith) #8

I don’t think IT’s messing up, more likely I did - someplace in the install. I got all the way through, and got the proper response from the “test” phrase at the end. But I get a lot of “Sorry, I didn’t get that. Would you like to try again?” Or sometimes just a flash of the blue ring followed by darkness and silence.

Here’s an example: I installed the Virtual Presence DTH and built a Virtual Presence profile for my nephew (we’ll call him “Nephew”). When I say, Alexa tell Our House (the invocation I used in the main intent - if this is causing the problem, I’m not married to it) “Nephew” is checking in." She came back with, “Sorry, I didn’t get that. Would you like to try again?”

I get that a lot from her, so much that I admit I kind of gave up on trying to fix it. I think I need to better learn what to ask her for as well, something that occurred to me as I was re-reading the wiki. So now, a couple months later, I figured I’d try to get at these previous problems while I’m trying to fix the whole “[device] doesn’t support that” problem, which came up several times as I was testing ES to find you a good example. I appreciate any assistance you can offer - the WAF is headed for the cellar… :no_mouth:

BTW, should I move this to the ES thread?


(Jason "The Enabler" as deemed so by @Smart) #9

How joel, I’m sorry you’re having so many problems.

I’m thinking it might huge an issue if Alexa not understanding properly. Will you try this please,

Change your invocation word to Home.

Thanks


(Joel Smith) #10

Okay, changed invocation word to “Home” (btw, how do you do that thing with the second invocation word, “my home”?). Asked’ “Alexa, ask Home if the Bedroom door is open.” There is such a device and it’s on the list of devices in the Amazon intent page, but she responds with either, “Sorry, I didn’t find Bedroom door,” or simply the little tone she makes to let you know shes ignoring you (don’t know what else to call it).


(Jason "The Enabler" as deemed so by @Smart) #11

Alexa does not like the “if”… Try it like this…

But first, did you select that particular device in the main app devices section?

Alexa, all home, is the bedroom door open?


(Joel Smith) #12

Same response. Confirmed, Bedroom door is listed in the main app configuration page under “Allow These Contact Sensor(s) that are used on a Door(s)…” Is that maybe the wrong place for it?

Here are a couple more, and keep in mind that it’s not like I have a thick accent of any kind:
"Alexa, ask Home who is home"
Alexa: “I’m not sure about that.”
(FWIW, she got this one right earlier today…)

"Alexa, Ask home what’s the current mode"
Alexa: “I’m not sure how to help you with that”

"Alexa, Ask home what windows are open"
Alexa: “I’m not sure how to help you with that”

At this point, I’m pretty sure I must have missed something in the install, no?


(Jason "The Enabler" as deemed so by @Smart) #13

Yeah, I’m thinking something was missed in the install. Those responses are from the native Alexa, not EchoSistant.

Let’s take this to a pm.