bmercier

Both Alexa and GH have been fixed. Please try again! Thanks, Benoit

Maybe one last thing to try before trying V2 again. Try the routine one more time, and take note of the precise time and device address. I will see if I can find something in the logs. I will need to know, the time with timezone, your uuid and device address. Benoit

Hello reisender, Are you able to turn on/off the device that you are using in the Routine, either vocally, or through the alexa mobile app? If so, the routine should be able to turn it on or off too. From the skill perspective, whether this is initiated by a vocal command, the mobile app, or a routine, the process is identical. The skill is not ware if it is called by a routine. If the routine does not trigger the device on/off, then there is an echo problem, or it does not have the correct device. Before calling Amazon for support, I would recommend to double-check that you have the correct device in the routine. I would look in the alexa app, the web version, and I would look under devices AND scenes. One possibility I see is that you may have an ISY device from V2 AND V3, which would mean 2 echo devices related to the same ISY device. Perhaps the routine has the V2 version it it? Benoit

Hi Jimbo, Can you PM me the output of your node? I need to see what in the node may prevent it. Use http://<your_isy_ip>/rest/nodes/<node_address> Thanks, Benoit

What does not work with the routine exactly? Is it creating the routine? Adding a device to the routine? Running the routine? If so, what does Alexa says? Benoit

You are correct. I'll talk with Michel. We may add support for multiple ISYs. Benoit

Technically, yes, the ISY skill which allows to get the status can coexist with V3. It is not problematic... other than it is planned to be removed. Benoit

> And why can't the portal support an echo to be aware of devices on 2 different ISYs and just send the right command to the right ISY? This is a feature we could add. Today it is simply not implemented. > The restriction is that an echo can only see one ISY. > --Why is this restriction there? And what is "an echo"? Do you mean "an amazon account which is assigned to specific echos"? An echo is an echo. The amazon account used is irrelevant. During account linking, you link with an ISY Portal user profile. That user profile has a preferred ISY, and that's the one used to discover devices. Benoit

A spoken command to Alexa will send the request to an ISY Portal API, which then sends the request to an ISY. A command is related to a device which belongs to a specific ISY of the linked account. The request can't go to another ISY, it goes to the ISY where the device exists. No. It is sent to ISY Portal. But it's for a specific device which belongs to a specific ISY. That's how ISY Portal knows where to send the request. Does any of your echo need to be aware of devices on 2 different ISYs? If yes, that's not supported. If no, you can link your echos to a different ISY Portal user profile. You could have a user profile for ISY A, and a user profile for ISY B. You could, if you wish, have 15 different sub-accounts with each their ISY Portal user profile and their own set of spokens. The restriction is that an echo can only see one ISY. Benoit

Today, a Smart Home skill does not allow to do that. This is something Amazon has not implemented yet. At the API level, there is a query function that has been implemented, but it's not yet used by Amazon when using the voice interface. On the other hand, if you use the mobile app, you can see the status of a device, or even a state variable. Our ISY Custom skill (Names "ISY") offered a way to query devices, but this skill is being sunset. We could do it because in a custom skill, we have control over the vernacular, unlike a smart home skill (Live V2 and V3).

Is it that you would like to use a single echo with multiple ISYs? If so, this is not a supported configuration. An echo skill can only use one ISY. If you switch your preferred ISY, the devices for the new echo will be discovered, but the other ones will be marked offline. Offline devices used to work anyway. If this does not work anymore, it must be that Amazon no longer sends requests for offline devices. For ISY Portal, offline or not, it does not matter. If a request comes in, the device has a unique ID, and will be found if the record in ISY portal has not been deleted. There's no such thing as an offline device in ISY Portal. The preferred ISY setting is used only to know for which ISY to do a discovery. Benoit

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.