bmercier

You don't have to if you use the same set of configured devices in ISY Portal. You would link you echo skill to the same ISY portal account. On the other hand, if you want your echo to respond to different devices, then you would need to create a a sub-account, a user profile in that account, and obviously, configure devices in that account. Benoit

Look under Scenes. In V2, scenes and programs were exposed as devices. In V3, the default is scene (But this is now configurable). It was like that in V2 as well. Benoit

It looks like you have more than one skill active. Benoit

I would try to remove the kitchen from the routine and re-add it. I'm guessing that the routine may be referencing the older kitchen device from V2 that no longer exists. Benoit

Technically, I think it can. But Alexa notifications are not meant to work this way. Alexa notifications that are sent by a skill are sent to a queue, then a visual notification and/or an audio indication is sent to the device. At this point, a user can ask “Alexa, what did I miss?” or “Alexa, what are my notifications? So, notifications are meant to be retrieved by a vocal request from the end user. Now, I see a possible trick we could use to speak without a request from the user, and it would involve the use of the audio indicator. But that can be tricky, as this means we would need to create on-the-fly an audio file and use it as the audio indicator. I'm not sure if Amazon would approve a skill which does that. Benoit

Please open a ticket and specify your UUID, and reference this thread. I'll investigate the portal logs. Thanks, Benoit

You can't include a value in the payload. BUT, for things like volume or channel, you can set a state variable to the spoken value. Then, it's a matter of having a program react to that state var and trigger a network resources. You can embed a state variable in the network resource payload. This post could help you get started with variable substitution in network resources: https://forum.universal-devices.com/topic/23212-setting-up-directtv-control-with-alexa-using-network-resources/?hl=%2Bvariable+%2Bsubstitution+%2Bnetwork+%2Bresources Benoit

Hello everyone, Just a quick note to let you know that the maintenance is complete. Benoit

No, this has already been taken care of. To be more specific, we need to increase network throughput at the VM level. It's a matter of drivers that needs to be changed on all servers, including database servers. Benoit

Hello everyone, We will have a maintenance on Sunday 01-28-2018 at 5:00 AM PDT which will last 1 hour, with downtime. Due to the increased workload, we are giving additional resources to our servers. With kind regards, Benoit

Good suggestion. Thanks, Benoit

In the echo app, in the web version, here: https://alexa.amazon.com/spa/index.html#smart-home Go to Smart Home / devices, scroll to the bottom. Forget all is there, unless you have no devices. Benoit

My guess is that you are using the V2 skill. Please upgrade to the V3 skill: - Disable V2 - Forget all devices - Enable V3 Benoit

If the device can be turned on/off using regular vocal commands, then this must be an Alexa problem. There is nothing specific to routines in the Alexa API. It simply uses the same APIs. I have not played much with routines yet.

For this to work, you also need to run the program then/else whenever the status of the scene changes; you could monitor the kpl button or any other device in the scene.

Let me share some technical details. Device statuses are sent to Amazon either: - Proactively (proactivelyReported=true) - Retrieved by Amazon on request. (retrievable=true) These are properties of a device returned during discovery. When looking at a device in the echo app, there is a status request sent to ISY Portal and to your ISY about every 2 seconds. That's if retrievable=true. The error message in the Alexa app is a bug. Whenever the retrievable=false, the error message appears, even if proactivelyReported=true. It should not, this is a known problem at Amazon. Now, in the case of a scene, there are no status available. Both proactivelyReported and retrievable must be set to false. That will not help you. You could use a work-around though. It's tedious, but what you could do is use a program to turn on/off your scenes, and expose your program to Alexa, instead of the actual scenes. Programs do have a status. If you need dimming for your scenes, there's no easy way. You could use a state variable to hold the dimming level, but then, you can't really set the dim level of a scene. Benoit

I see 2 possible reasons: - A discovery has not run yet (A discovery is required, and Amazon runs that automatically every 1-2 hours) - The device is a scene (Scenes exposed as a device will still have that error message). Benoit

Thanks for the suggestion. I'll see with Michel if/how we can do this.

The maintenance is complete. Benoit

If you look at your devices under Smart Home/Devices, if there is nothing, this is good. Step 3 is completed. The "Forget all" button will not appear if there are no devices. Just proceed to find and enable the V3 skill. You are almost done. Benoit

Hello everyone, We will have a small maintenance on Sunday 01-21-2018 at 5:00 AM PDT which will last a few minutes. No downtime is planned. Enhancements: - Amazon Echo V3 usage through the mobile app will work better; The device status will be shown, and there will no longer be "There was a problem". This will work for all device types, except for scenes due to the status which can't be retrieved. With kind regards, Benoit

@Ebrune, forget it, I found and fixed the problem. The issue was specific to the Auto mode, when using F. Benoit

@EBrune, I investigated further, and the query works as expected. Contrary to what I said above, it's normal that temperatures are passes in celsius at the API level. I contacted Google Home support. Please try this; Open your GH app, click on the upper left icon, and go to More settings/My Day/Weather Set it to Fahrenheit. Please let me know if that helps. Benoit

Ok thanks for the feedback. I took another look at the logs, and the setpoints are still passed in celsius. I noticed something strange though - When GH queries the thermostat, the temperatures returned are in the celsius range. There's no reasons for this, unless the thermostat is working in celsius. I'm lacking the time for further investigation as I'm leaving on vacation early tomorrow morning. I will look into this in about a week. Benoit

It is not, it's like this on purpose. Alexa does not have a concept of device nicknames. Therefore, if we want multiple spokens, then extra alexa devices needs to be created. Benoit