bmercier

I'm thinking that Alexa might be confusing things. Would you have any spokens with medium or high in it by any chance? Benoit.

Fanlinc has 4 levels when you include off (0 = off). With Fanlinc, high and maximum are the same speed. When it's a zwave device with 4 levels (5 with off), high and maximum are different speeds. Benoit

Following the Fan poll we had, I could see no correlation with the type of device or the region. I however made a change that might help for Fanlinc. If possible, I would need feedback from Fanlinc users: @asbril, @PurdueGuy, @oberkc First of all, make sure to: Delete the device from the echo App. (This is a critical step I found lately with respect to fans especially) Discover devices asbril, yours was already working, please make sure it still does. I reverted the change I made to recognize "medium", so this could have created an issue for this. Here, Medium works. When testing: First try the Alexa app. The icon should be a fan. You should be able to set the slider from 0 to 3, and the fan should change off-low-medium-high Then try vocally to set the speed to 0-1-2-3. "Alexa, set fan to 2" should set the fan to medium Then try vocally to set the speed to off-low-medium-high Please let me know how it goes. Benoit

What fan are you using. Fanlinc?

This is as expected. No issue here.

After flushing the devices in the Alexa app, after the discovery, did the devices reappear? If so, this means skill linking is ok. If not, please disable the skill and reenable it. Are you able to control devices from portal, ISY Web access? If so, that proves the connectivity between the ISY and portal is good. If you still have a problem, please open a ticket with your uuid referencing this thread, I will check the logs. Benoit

Can you pm me your uuid? I'll see if I can find something. Are you using echo or GH? And if so, do they still work?

Login to my.isy.io has not changed, it should be working. Can you reset yout password? Other UDI sites have changed so that it uses my.isy.io credentials (using oAuth).

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%