bmercier

What fans are you using? Could you send the output of http://<isy ip>/rest/nodes/<your_fan> ? Benoit

FYI, without changing a thing, you can say: Alexa, turn on kitchen lights to 50%

For lighting, you are better with Set/Lower/Raise as the verbiage is in the range of 0-100 percent, instead of fan speeds of 0-3 or 0-4 for Fans,

This is now fixed.

Thanks for the video. I could not believe it. Now I can reproduce it. It happens only if you edit and save without changing the Alexa category. Will fix that. Benoit

Good catch! It's fixed

Chrome on iOS, Mac or Windows? Can you try on Windows? Benoit

Which browser are you using? Could you try the same with Chrome as a test? Benoit

When you change your device to set/lower/raise and save, Does the spoken still appear as set/lower/raise in ISY Portal? When you say "after discovery", does it show as a contact sensor in Alexa, or in ISY Portal? The discovery does not change what you have on ISY Portal, so not sure what is happening here.

Fan support has been added. We added a new echo category in order to have a better user experience. Both Insteon Fanlinc are supported (4 settings: off, low, medium, high) and ZWave (5 settings: off, low, medium, high, max). It will also display a Fan icon, instead of a generic icon. That was also required so that raise/lower would bump the speed to the correct values.

Fan support has been added to the Echo skill. To enable this feature: On ISY Portal, go to Select Tools | Connectivity | Amazon Echo Edit your Fan "spoken" In the Alexa Category, choose the "Fan" option Save your "spoken" After changing the Alexa Category, ask "Alexa, discover my devices" Both insteon and ZWave fans are supported. To change your Fan settings: Alexa, Set <spoken> to {Off | Low | Medium | High | Max} Alexa, Turn {on | off} <spoken> Alexa, Raise <spoken> Alexa, Lower <spoken> Enjoy!

Thanks for the suggestion. We now use the first controller, if available, otherwise the first node (controller or not). It's in production.

No

The logic is quite simple: If the device is non-zero, the scene is considered on (Regardless of the On level configured in the scene) If the device is 0, the scene is considered off. Not perfect, but better than systematically returning off as the initial state. Benoit

When you control a scene, GH remembers that the scene was turned on, or turned off. If you then change the state of the scene members, GH has no way to know you did this. The change I implemented is only for the initial query of the device. Note that in the Assistant, if you quit the device and get back in, it should query the device state.

Please pm me your uuid Another test you could do: http://<your isy>/rest/nodes/<your scene>?members=true Check if the members sections has link tags. For further analysis, I would need your uuid and/or the output of the above rest command. Benoit

You may want to check your scene, just make sure it has members. I made a fix to adress the case where a scene has no members, please try again. Benoit

Please PM me you uuid, I will check the logs

The query of ISY scenes has been enhanced, please see the edit at the bottom:

I think this may be due to the spoken used. It might be similar to another one you have, and Alexa is asking you if this is the correct device. Can you try changing the spoken?

There has been no changes to the skill. Must be an Amazon change.

If discovery is not recognized, then it's not specific to the skill. I would guess it's a transient error at Amazon and is likely to come back soon. Or perhaps it could be a local networking issue?

Thanks for the quick feedback. The "Device with Open/Close syntax" is something totally different. I understand that intuitively one would expect to get an Open/Close status. The thing is that to achieve this open/close syntax, we need to use one of the "controllers" that supports it, one of them being the "ToggleController". Then, to also support turning it on/off, we need to combine it with the Power Controller. All this results in the UI that you can see. I think it would be possible to show open/close instead, if we got rid of the PowerController, but that would mean those devices would not longer be able to be controlled with turn on/off. Only with Open/Close. Benoit

Hello, I made a fix to address this case. Would you mind testing again? Please test by looking at the Alexa app, but also using a routine. Thanks, Benoit

To answer your first question, I don't think passing the isyKey in a header would help, you would still have a POST reuse in the response. I checked your payload, and I noticed a few differences with the one the admin console uses. Use this soapaction header (Notice the ", I believe this is the cause of the problem): Soapaction "urn:udi-com:service:X_Insteon_Lighting_Service:1#Subscribe" And here's a body you should use (I noticed you have a malformed /reportURL tag : <s:Envelope><s:Body><u:Subscribe xmlns:u="urn:udi-com:service:X_Insteon_Lighting_Service:1"><reportURL>REUSE_SOCKET</reportURL><duration>infinite</duration><send>F</send></u:Subscribe></s:Body></s:Envelope> Benoit