bmercier

I would suggest to change you "Master Bedroom Fan" to just "fan" during testing. I suspect most of your issues are related to Alexa not understanding the spoken correctly all the times, and perhaps sometimes directing the request to another of your devices. You can also double-check what she understood in the Alexa history: alexa.amazon.com -> settings -> History

Start by testing basic turn on/off on the fan. If this works, Alexa at least is talking to the right device. This sort of error is often a case where there are several devices with similar names, and Alexa is directing requests to another device which does not have the capability or is offline. You can also check the device in the Alexa app. If it has the fan icon, this means it is setup correctly. Benoit

Could you look at the history, make sure Alexa understands "Medium". Testing here shows that Medium works with the 2 types of Fan (Insteon Fanlinc / ZWave)

It's up to Amazon to update the skill to allow touch interface for fans. Scenes are not supported, only devices.

Found out a bug today, it was reported by asbril. When editing a spoken and saving without changing the Alexa cat, the alexa category would be messed up. It's fixed now.

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?