bmercier

Good to know. It works because when setting to low, it sets it to 24 (which is below 33), medium sets it to 49 (below 67) and High sets it to 74, which is (above 67).

Thanks for the info. The ZWave support was made for a Homeseer fans. The presets for a ZWave fans are those: { value:0, name: 'Off', maxSpeed: 0}, { value:1, name: 'Low', maxSpeed: 24}, // 1% - 24% / Low { value:2, name: 'Medium', maxSpeed: 49}, // 25% - 49% / Medium { value:3, name: 'High', maxSpeed: 74}, // 50% - 74% / Medium-High { value:4, name: 'Maximum', maxSpeed: 100}, // 75-100% / High If this swith operates with different presets, then it is likely to not work for some speeds. When you set to medium, as an example, it would set the ST property to 49 (The max speed for medium) Benoit

Great question. Not sure how a fan would work with a ZWave fan switch. If the switch is only On/Off, then the Fan support would not work. A ZWave fan would be expected to have a Value from 0 to 100%, with 5 speeds (including Off).

Thanks for the quick response. I'm from eastern canada, and it works 100% here. In an attempt to get to the bottom of it, I've setup this poll:

Hello, We are having issues with Alexa fans, for some users it works, for some others, not so much. Please help us diagnose this issue. To properly test this, make sure that: You set the Alexa category to "Fan" You see the device in the Alexa app, and it has a Fan icon Then answer the survey.

I'm starting to think this might be a regional issue, all this works well here. I tried it in production with exactly this spoken "Fan". Works all the time. Where are you located? (Country, region)

Please redo a device discover and try again. Due to the multiple reports of "Medium" not being recognized, I made a change that might help. Here, when testing, it always works.

Another good way to test is to change settings through the Alexa app. If it works there, then the skill is responding as expected.

There are no plans to have variables exposed as fan devices. There is a work-around however - just use a variable and set the Alexa category to Lower/Raise syntax. With this, you can ask to set to low / medium / high and it will set the variable to, if I recall correctly, 25 - 50 and 80. You can then have programs that branches on these values. The only lack of functionnality you will experience is that the device icon will not be a fan. Benoit

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!