Devices sometimes stop working with Alexa....

[davlarso]

[sonypoolplr]

I have noticed things like that as well. I have devices that work one day, then not the next, or they work with only part of the device name, Kitchen lights will sometimes work and then other times I only need kitchen.

[scg]

The same thing happens to me. I tried two different commands. Then I opened the Alexa app on my phone to see if it was online, and it was. Then repeated the commands and they worked. Not sure why.
Art

[davlarso]

Happened again yesterday....

I had this happen again yesterday. This time trying to turn on or off a few different devices via the connected home API didn't kick it out of its funk like it has in the past. My triggering an IFTTT recipe through Alexa got it working again this time.

Can someone from HS please comment on what we can look at to figure out what's happening? Alexa integration had been rock solid for me until this started happening occasionally a few weeks ago. I'm a bit concerned that I'll soon be expanding from a single echo to 7 echos throughout the house and I was expecting this to be rock solid like it had been in the past.

[TeleFragger]

well I originally unplugged HS in July due to wife complaining never consistent.. so now I am going back in and setting stuff up...

Amazon Echo was on my list... but since I see this I cannot place it in my setup! thus I am subscribing to this...

[rjh]

Check the HS log and see what is there when it did not work, maybe there is an error message. You can turn on JSON debugging from the control panel with:

hs.debugmode=2048

This will allow us to see what Amazon sent to HS, if anything. That error sometimes means it could not reach the system at all for some reason.

[davlarso]

I've been able to get some log data from a few times where Alexa says a command doesn't work on a device. Here's what I've figured out so far.

- There is nothing recorded in the HS log when Alexa says a command doesn't work on a device. This is with JSON debug turned on.
- In all the cases I've seen so far, there is usually a MyHS device change notification logged shortly before this happens.

This log snippet shows 2 device change notifications being sent to MyHS, followed by the successful control of a device with Alexa. It was between the device change notification and the successful Alexa control where Alexa responded that the command does not work on the device.


Nov-02 10:38:40 AM Event Event Trigger "Alexa Events Shower - On"
Nov-02 10:38:40 AM Device Control Device: Upper Level Master Bath Shower to On (100) by/from: CAPI Control Handler
Nov-02 10:38:40 AM Info Controling device Shower from JSON ECHO
Nov-02 10:38:40 AM DEBUG JSON Query: request=echocontrol&command=ON&ref=621&token=122451538781381 43148
Nov-02 10:38:34 AM Event Event Trigger "Motion Events Mechanical Lighting - Off Timer"
Nov-02 10:38:34 AM Z-Wave Device: Lower Level Mechanical Motion Set to Off/Closed/No Motion
Nov-02 10:37:34 AM DEBUG JSON Sending device change notification to MyHS for device: 389,0,255
Nov-02 10:37:34 AM Z-Wave Device: Lower Level Mechanical Lights Set to OFF
Nov-02 10:37:22 AM DEBUG JSON Sending device change notification to MyHS for device: 389,255,0
Nov-02 10:37:22 AM Z-Wave Device: Lower Level Mechanical Lights Set to 255
Nov-02 10:37:21 AM Device Control Device: Lower Level Mechanical Lights to On (255)

I've tried to confirm that it's the device change notifications that are causing this by trying to get rid of them, but I can't figure out how to make them stop happening. The device change notification is for a device that I used to have setup to trigger an IFTTT recipe. I've deleted that recipe in IFTTT and restarted homeseer, but something appears to still have some record of it causing HS3 to send the notification when that device changes.

Does this give HS anything to go on to try to figure this out?

How can I get HS3 to stop sending device change notifications for this device to MyHS?

[rjh]

When Alexa says that the command does not work, that is all internal to Amazon. It is using the information it received from the discovery process. Note that it periodically sends a discovery request to your system to pick up new devices. Its possible that maybe it got some new info that might be causing this. If the devices don't change, I don't see how this would be it though.

Is the device in question a device that is created/changed by a plugin.

The device changes only go to IFTTT, they do not go to Amazon, so I don't see how that would be it.

I've been able to get some log data from a few times where Alexa says a command doesn't work on a device. Here's what I've figured out so far.

- There is nothing recorded in the HS log when Alexa says a command doesn't work on a device. This is with JSON debug turned on.
- In all the cases I've seen so far, there is usually a MyHS device change notification logged shortly before this happens.

This log snippet shows 2 device change notifications being sent to MyHS, followed by the successful control of a device with Alexa. It was between the device change notification and the successful Alexa control where Alexa responded that the command does not work on the device.


Nov-02 10:38:40 AM Event Event Trigger "Alexa Events Shower - On"
Nov-02 10:38:40 AM Device Control Device: Upper Level Master Bath Shower to On (100) by/from: CAPI Control Handler
Nov-02 10:38:40 AM Info Controling device Shower from JSON ECHO
Nov-02 10:38:40 AM DEBUG JSON Query: request=echocontrol&command=ON&ref=621&token=122451538781381 43148
Nov-02 10:38:34 AM Event Event Trigger "Motion Events Mechanical Lighting - Off Timer"
Nov-02 10:38:34 AM Z-Wave Device: Lower Level Mechanical Motion Set to Off/Closed/No Motion
Nov-02 10:37:34 AM DEBUG JSON Sending device change notification to MyHS for device: 389,0,255
Nov-02 10:37:34 AM Z-Wave Device: Lower Level Mechanical Lights Set to OFF
Nov-02 10:37:22 AM DEBUG JSON Sending device change notification to MyHS for device: 389,255,0
Nov-02 10:37:22 AM Z-Wave Device: Lower Level Mechanical Lights Set to 255
Nov-02 10:37:21 AM Device Control Device: Lower Level Mechanical Lights to On (255)

I've tried to confirm that it's the device change notifications that are causing this by trying to get rid of them, but I can't figure out how to make them stop happening. The device change notification is for a device that I used to have setup to trigger an IFTTT recipe. I've deleted that recipe in IFTTT and restarted homeseer, but something appears to still have some record of it causing HS3 to send the notification when that device changes.

Does this give HS anything to go on to try to figure this out?

How can I get HS3 to stop sending device change notifications for this device to MyHS?

[rotunnoe]

This happens to me periodically. My thought is that Alexa is using the HomeSeer skill to log into the HomeSeer "cloud" with your credentials. Might there be some latency between Amazon and the HomeSeer cloud?


Sent from my iPhone using Tapatalk