bmercier

I looked at the logs and found an error that I think is related to your problem. That's the only thermostat query which is failing. You seem to be querying a thermostat that no longer exists in your ISY Portal Echo device list. Could you have 2 thermostats, one you are vocally controlling, but when querying you are using another one (an older insteon device?) If you look the at the web alexa app, the thermostat would be marked as offline. Benoit

Yes. Please unlink the skill and relink. When prompted for your ISY credentials, enter your ISY Portal user and password (the one for the location you want to synchronize with).

This is surprising. Could you retry it? If it still does not work, please PM me your uuid and I will check the logs. Benoit

Please retry. I looked at both of your ISYs, and both need to be re-linked. I see that the discovery worked for one of yours, but still, they need to be relinked. Benoit

Hello everyone, If your echo is no longer responding since this morning, please unlink and relink the skill. Instructions: Go to https://alexa.amazon.com Click Skills Search for "isy v3" Click on "ISY Optimized for Smart Home V3" Click on Disable Click on Enable Enter your Amazon user and password (if asked by Amazon) Enter your ISY Portal user and password (In the ISY Portal Authorization dialog) This is a side effect of this morning's update, which unfortunately affects a portion of our echo users. Thanks, Benoit.

Hello everyone, If your echo is no longer responding since this morning, please unlink and relink the skill. I unfortunately found a bug in a DB conversion program used for the update. Anyone which did NOT have live update enabled will have to unlink and relink. My apologies, Benoit.

Please PM me your uuid

Hello Everyone, Maintenance has completed. Enjoy! Benoit

@nadler & @apnar, the above documentation applies to Alexa Custom Skill. Smart Home skills don't have that capability. We can't retrieve the deviceId in a smart home skill.

This should not have any impact. The preferred ISY is still on the user profile. The only changes are a new field on the user profile, and the GH/Echo integration which now supports multiple ISYs. Benoit.

Multi-ISY Support is coming next sunday:

Hello everyone, We will have a maintenance next Sunday 11-25-2018 at 5:00 AM PDT which will last for up to 1 hour. During this period, ISY portal will be down. New features: Multi-ISY Support for Amazon Echo Multi-ISY Support for Google Home Amazon Echo: The live update button has been removed. It will be enabled automatically if the skill is enabled. Notes: In "My Profile", you will have an option to include your preferred ISY or all ISYs in the account. Duplicate spokens: Make sure your spokens are unique across your ISYs. There is a validation when you save your spokens, but this only checks that it is unique for the current ISY. If using all ISYs in the account, the "Send to Google Home", will send all spokens from all ISYs in account. Not just the spokens in the current ISY dialog. Benoit

Thanks for the suggestion. Unfortunately, there is no echo device ID or anything else that allows to identify from which echo a request has been made. If you see documentation that says otherwise, please let me know. I looked at the actual payload sent by Amazon when making a request such as turn on/off, and there was nothing that would allow to identify from which echo device a request has been made from. Benoit

Sorry I should have been more explicit. You can use programs to control a variable exposed as a motion sensor, which can triggers Alexa Routines which sends announcements. Program1, when the door is open, repeatedly trigger program2 every 5 minutes. Program2, in the then statement, just turn on the state variable to the motion detected value, wait 10 seconds then another value (no motion). In your Alexa routine, send the announcement whenever there is motion. Benoit

No. But you could accomplish this using programs.

Yes, I think that would be a good idea. The "ping" would need to be a valid request. If there are no devices for which we can send a status, then, the only valid request we could send is a sync request. The same as when clicking the "Send spokens to Google Home". Benoit

Alexa does not know state variables. I however knows about motion and contact sensors. Have you configured an Alexa Motion or Contact sensor using the state variable, in ISY Portal? Have you then run a device discovery (Alexa, discover my devices)? Benoit

Excellent, thanks for the feedback! Benoit

Try to disable the skill, and re-enable it. It is likely to fix the problem. Benoit. Sent from my iPhone using Tapatalk

Did you turn on Live Update in ISY Portal?

Are you exposing state variables as an Alexa sensor? Are you perhaps exposing the same state variable as multiple Alexa sensors (using different values)? Benoit

About the delays, I can tell you that the detection is debounced with a delay of 30 seconds, as per Amazon specs. If the sensor changes come too rapidly, some will be skipped. In other words, the Alexa sensor will always stay in the open or closed state for at least 30 seconds. So let's take an example: Sensor is initially Closed (since at least 30 seconds). At t=0s, sensor is Open -> Alexa Sensor will change to open immediately At t=10s, sensor is Close -> Alexa Sensor will stay open (Up to t=30s) At t=12s, sensor is Open -> -> Alexa Sensor will stay open (Up to t=30s) --> This one is skipped At t=22s, sensor is Close -> Alexa Sensor will stay open (Up to t=30s) At t=30s, Alexa Sensor will change to closed At t=40s, sensor is Open -> Alexa Sensor will stay closed (Up to t=70s (40s + 30s)) --> This one is skipped At t=50s, sensor is Close -> Alexa Sensor will stay closed (Up to t=70s) At t=70s, Alexa sensor stays closed (The physical sensor is closed) Benoit

I'm not aware of native Google Home support for multiple homes. Can you share what you have seen? For now, the only method I know you could use is ISY to ISY communication using Rest commands & network resources, but it's rather tedious. This involves Alexa controlling a program, which runs a network resource which talks to the other ISY through ISY Portal.

When you have a device as a controller in a scene, it will only turn on/off the scene when physically activated, not remotely. This is how insteon works. Somehow, it looks like Mobilinc reads the scene, and activates the scene when it sees one of the member being controlled. Here's a way to do the same thing with Echo: Create a program like this: IF Device is not off Then Turn on Scene Else Turn off scene Expose that program as a Light. You will be able to control your scene using Alexa, and it will hold a status (The true/false status of the program). Obviously it can't be dimmed, but at least, you will have a status. One of the drawback to the above is the additional Insteon communication that will occur. Whenever the scene will be turned on, the member device will turn on, which will trigger the program, which will trigger the scene. The propram will be triggered only once, because once the device is on or off, it will stay in that state, and not trigger the program.

The original "ISY" skill has been sunset and no longer works. Please disable the "ISY" skill. Benoit