bmercier

It is not down. Please login to my.isy.io, and see if your ISY is online. Benoit

Sean, I'm glad to see it is working. Unfortunately, nothing has changed, so I guess this will remain a mystery for now... Benoit

This is not a bug. Scenes do not have a status. So when you have only scenes in a group, the app does not show you the on/off buttons which also acts as a status. But whenever there is a device in the scene, the button will pick up the status of that device. Benoit

Can you turn it on/off using UDAjax or the admin console?

Hi Sean, I'm currently investigating the logs. I see requests for other devices working, including for kitchen table. Do they actually work, or do you still have an issue? If they still don't work, the issue is not with ISY Portal. If so, please try turning it on/off from UDAjax or the admin console. If they don't work, this needs to be fixed. Michel could help. Benoit

Scenes exposed as devices have the capability to be turned on/off (PowerController) and to be brightened/dimmed (BrightnessController). When a device is added to a routine, somehow, Alexa will use the BrightnessController/SetBrightness to the value specified in the mobile app, and use the PowerController/TurnOff if the value is 0. The issue was that BrightnessController/SetBrightness was not implemented for scenes (or scenes exposed as devices). As you know, ISY scenes can be brightened/dimmed, but they can't be set to an absolute level. So the fix was to enable that functionnality. Now if BrightnessController/SetBrightness is called for a scene with an on level > 0%, then the scene is turned on. You can try it by asking, Alexa, turn on <your scene> to 50%. That will turn on the scene if the requested level > 0%. Now, during my testing, I noticed that sometimes, Alexa simply did not make the API call when triggering the routine. No matter what I tried, it would not work. After searching online, the solution was to completely delete the Alexa App, reinstall, and create a new routine. I also had an issue when I created a routine named "bed time". When I triggered manually the routine using the app, it would work, but when asking "Alexa, Bed time", Alexa did not trigger the routine and only responded with "Have a good night, sleep well". Looks like some names can't be used. Hope that helps. Benoit

Hello everyone, The maintenance is completed! Benoit

Hello Sean, I'm currently investigating the logs. It looks like your Alexa requests are coming in today successfully. Are you still experiencing problems? If so, would you have a specific device that you are trying that is not working? Please let me know which one. Also, I notice that you are still using the Alexa V2 skill. I would recommend switching to V3. Thanks, Benoit

Hello everyone, We will have a maintenance this Sunday 02-25-2018 at 5:00 AM PDT which will last 2 hours, with downtime. We recently encountered stability issues with our AWS servers. We have worked with Amazon to identify the issue, and it was due to the instance type that we are using (m5.large) that are running on new hardware. As per Amazon's recommendation, we will be switching all of our servers to another instance type with runs on different hardware. In addition, we will have a fix for Alexa routines using ISY scenes exposed as devices. With kind regards, Benoit

ISY Portal can only run node servers developed specifically to run on ISY Portal. Benoit

The node needs to look like an insteon or ZWave thermostat. Below is an example: Important things are: Type = 4.8.x.x (Or 5.x.x.x for insteon, but I would stay away from that) The properties ST, CLIMD, CLISPC and CLISPH are mandatory. UOMs for C or F are supported Precision is supported. ZWave example: <node flag="128" nodeDefId="UZW0053"> <address>ZW011_1</address> <name>Thermostat RC</name> <family>4</family> <type>4.8.6.0</type> <enabled>true</enabled> <deviceClass>1</deviceClass> <wattage>1000</wattage> <dcPeriod>60</dcPeriod> <startDelay>0</startDelay> <endDelay>0</endDelay> <pnode>ZW011_1</pnode> <sgid>1</sgid> <devtype> <gen>4.8.6</gen> <mfg>139.21586.21561</mfg> <cat>140</cat> </devtype> <property id="ST" value="234" formatted="23.4°C" uom="4" prec="1"/> <property id="CLIMD" value="1" formatted="Heat" uom="67"/> <property id="CLISPC" value="370" formatted="37.0°C" uom="4" prec="1"/> <property id="CLISPH" value="230" formatted="23.0°C" uom="4" prec="1"/> </node> Benoit

What happened is that in V2, scenes and programs were exposed as a regular Alexa Device. In V3, scenes and programs are exposed as Alexa scenes, by default. However, you can change that in ISY Portal. You have to edit the relevant spokens, and choose to expose them as devices (like it was in V2). Benoit

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