Jump to content

Fan support


Recommended Posts

Posted
On 5/25/2020 at 10:35 PM, dinostop said:

Not sure if you can help or not, however when I setup my fan through ISY and then Alexa as described above what I am finding is that when I tell the fan to turn off it works as supposed to however if I tell the fan to set to Low, Medium, or High, the fan goes to high.  When I trouble shoot and look at the real time status below is what I get then reverts back to 100%

Low = 127%

Medium = 253%

High = 255%

What fan are you using. Fanlinc?

Posted

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:

  1. Delete the device from the echo App. (This is a critical step I found lately with respect to fans especially)
  2. 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:

  1. 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
  2. Then try vocally to set the speed to 0-1-2-3. "Alexa, set fan to 2" should set the fan to medium
  3. Then try vocally to set the speed to off-low-medium-high

Please let me know how it goes.

Benoit

Posted
17 hours ago, PurdueGuy said:

Any progress on this?  I just tried with a different fan, and nothing has changed.

I also can't change my vote in the poll (I should have chosen "I have issues even in the Alexa app. The device icon is indeed a Fan.")

 

 

Posted
11 minutes ago, bmercier said:

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:

  1. Delete the device from the echo App. (This is a critical step I found lately with respect to fans especially)
  2. 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:

  1. 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
  2. Then try vocally to set the speed to 0-1-2-3. "Alexa, set fan to 2" should set the fan to medium
  3. Then try vocally to set the speed to off-low-medium-high

Please let me know how it goes.

Benoit

Thanks for helping.

Deleted Fan in Alexa app. Re-discovered.

  1. Alexa app - fine
  2. Saying "Alexa, set fan to 0/1/2/3" - fine
  3. Saying "Alexa, set fan to off/low/medium/high/on" - mixed results
    • Off = Works
    • Low = Works
    • Medium = Does not work ("I don't know how to set Fan to that setting.")
    • High = Does not work ("I don't know how to set fan Fan that setting.")
    • On = Work (fan goes to High)

For now, I am ok using 0/1/2/3.  Raise and Lower are still hit-or-miss.

Posted
47 minutes ago, bmercier said:
  • 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

Benoit, I followed these steps and it all works perfectly.  The only comment is that in the App (fan icon indeed) there are 4 levels, while my fan only has 3.  High and maximum give the same 100% result.

Posted
32 minutes ago, asbril said:

Benoit, I followed these steps and it all works perfectly.  The only comment is that in the App (fan icon indeed) there are 4 levels, while my fan only has 3.  High and maximum give the same 100% result.

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

  • Like 1
Posted
1 hour ago, PurdueGuy said:

Thanks for helping.

Deleted Fan in Alexa app. Re-discovered.

  1. Alexa app - fine
  2. Saying "Alexa, set fan to 0/1/2/3" - fine
  3. Saying "Alexa, set fan to off/low/medium/high/on" - mixed results
    • Off = Works
    • Low = Works
    • Medium = Does not work ("I don't know how to set Fan to that setting.")
    • High = Does not work ("I don't know how to set fan Fan that setting.")
    • On = Work (fan goes to High)

For now, I am ok using 0/1/2/3.  Raise and Lower are still hit-or-miss.

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

Benoit.

Posted
9 hours ago, bmercier said:

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:

  1. Delete the device from the echo App. (This is a critical step I found lately with respect to fans especially)
  2. 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:

  1. 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
  2. Then try vocally to set the speed to 0-1-2-3. "Alexa, set fan to 2" should set the fan to medium
  3. Then try vocally to set the speed to off-low-medium-high

Please let me know how it goes.

Benoit

I have deleted the fan from the alexa app, and rediscovered it.  I see a fan icon only when I am looking at "all devices".  The fanlinc shows up in a under the category of "switches" when viewing as part of a group.

1) From a starting condition of power off, when I set the slider to 1, it reverts back to 0 after about five seconds but the fan is on low speed.  When I set the slider to 2, it reverts to 1 after about five seconds, but the fan is on medium speed.  When I set the slider to 3, it stays on 3 and the fan is on high speed.

2) vocal commands 0-1-2-3 appear to work, but the alexa app slider does not accurately track state of fan.

3) vocal command off-low-medium-high appear to work, but the alexa app slider does not accurately track state of fan

The fan does NOT appear on the screens of either the echo spot or echo5.

Posted
12 hours ago, bmercier said:

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

Benoit.

Definitely nothing defined in the ISY Portal with those values.  I don't see anything in my list on the Alexa app either.

High:

Alexa_High.thumb.jpg.fd4d289a971485c7a412cc1e7cf11697.jpg

Medium:

Alexa_Med.thumb.jpg.0b091bbedc5877139d8a6adf54a057a3.jpg

Posted
On 5/30/2020 at 10:27 PM, oberkc said:

I have deleted the fan from the alexa app, and rediscovered it.  I see a fan icon only when I am looking at "all devices".  The fanlinc shows up in a under the category of "switches" when viewing as part of a group.

1) From a starting condition of power off, when I set the slider to 1, it reverts back to 0 after about five seconds but the fan is on low speed.  When I set the slider to 2, it reverts to 1 after about five seconds, but the fan is on medium speed.  When I set the slider to 3, it stays on 3 and the fan is on high speed.

2) vocal commands 0-1-2-3 appear to work, but the alexa app slider does not accurately track state of fan.

3) vocal command off-low-medium-high appear to work, but the alexa app slider does not accurately track state of fan

The fan does NOT appear on the screens of either the echo spot or echo5.

I though about this. I'm thinking you may have an insteon issue.

Could you try to control your fan using a browser using these commands:

To get the fan status:

https://<your isy>/rest/nodes/<your fan address>

 

To control your fan:

Set speed:

https://<your isy>/rest/nodes/<your fan address>/DON/<level>

To stop the fan:

https://<your isy>/rest/nodes/<your fan address>/DOF

 

For a fanlinc, levels should be (use the maxSpeed)

{ value:1, name: 'Low', maxSpeed: 127}, // 1% - 49%
{ value:2, name: 'Medium', maxSpeed: 253}, // 50% - 99%
{ value:3, name: 'High', maxSpeed: 255}, // 100%

Example:

https://<your isy>/rest/nodes/<your fan address>/DON/253 to set it to medium.

After changing the speed, get the status of your fan, see what the ST property. It should be set to the value you just set. I think it doesn't. If it goes back to fan speed 1, the value would be between 1 and 127.

Benoit

Posted
On 5/31/2020 at 2:05 AM, PurdueGuy said:

Definitely nothing defined in the ISY Portal with those values.  I don't see anything in my list on the Alexa app either.

High:

Alexa_High.thumb.jpg.fd4d289a971485c7a412cc1e7cf11697.jpg

Medium:

Alexa_Med.thumb.jpg.0b091bbedc5877139d8a6adf54a057a3.jpg

Then I have no clue what is happening. The voice recognition and Amazon AI sometimes does funny things. I still think it gets confused somehow.

Posted

Amazon vocals  went crazy tonight. Suddenly it is acting like GH and grouping everything.

Vocals I have used for years suddenly cannot be differentiated. TV and TV lights now mean the same thing. This was a GH shortcoming and why I dumped it. Now Alexa is doing it.

Posted (edited)
3 hours ago, bmercier said:

Could you try to control your fan using a browser using these commands:

I might be willing to try, but I am not sure how much trial-and-error in which I am willing to engage.  Since this is something I do not routinely (maybe never) try, I might need a little more guidance.  For example, I tried:

https://192.168.0.33:1026/rest/nodes/14.A0.A.2

and got a stalled browser window and, ultimately, an error that safari cannot open a secure connection to the server.  What did I miss?

Edited by oberkc
Posted
1 hour ago, oberkc said:

I might be willing to try, but I am not sure how much trial-and-error in which I am willing to engage.  Since this is something I do not routinely (maybe never) try, I might need a little more guidance.  For example, I tried:

https://192.168.0.33:1026/rest/nodes/14.A0.A.2

and got a stalled browser window and, ultimately, an error that safari cannot open a secure connection to the server.  What did I miss?

In your node address, use spaces instead of dots (I know, not intuitive for a url)

Posted
1 hour ago, oberkc said:

Alright.  Tried the following:

https://192.168.0.33:1026/rest/nodes/14 A0 A 2

Same results. Also tried in Chrome Browser.  In both cases, the browser auto-corrected to:

https://192.168.0.33:1026/rest/nodes/14%20A0%20A%202

The spaces are replaced by %20, this is normal.

It could be that your ISY is not configured for https. Try http instead:

http://192.168.0.33:1026/rest/nodes/14%20A0%20A%202

Posted

This raises lots of questions for me

I have set up my FanLincs to be controlled by Insteon Keypads so a button for each level and would illuminate the button to reflect the fan status via a scene for each fan speed.  I linked each of the speed control Scenes to Alexa for voice control. It recently stopped working.

Is there a new way link the Keypads to the fan control so the buttons stay synced to the motor speed?

When I press the KP button for each speed and look and then query the FanLinc using https://<your isy>/rest/nodes/<your fan address> I get very different speed numbers then you listed above. Mine are:

  • Low:  64
  • Medium: 191
  • High: 255

Why the difference? How are these number set up. (BTW, I'm running 5.0.16C) The query response I get back doesn't contain any values like :

{ value:1, name: 'Low', maxSpeed: 127}, // 1% - 49%
{ value:2, name: 'Medium', maxSpeed: 253}, // 50% - 99%
{ value:3, name: 'High', maxSpeed: 255}, // 100%

This is what I get when I type https://<your isy>/rest/nodes/3F%208B%20AF%202

<nodeInfo>
<script/>
<node flag="0" nodeDefId="FanLincMotor">
<address>3F 8B AF 2</address>
<name>Bedroom3.FanLinc-Motor</name>
<parent type="3">3266</parent>
<type>1.46.69.0</type>
<enabled>true</enabled>
<deviceClass>0</deviceClass>
<wattage>0</wattage>
<dcPeriod>0</dcPeriod>
<startDelay>0</startDelay>
<endDelay>0</endDelay>
<pnode>3F 8B AF 1</pnode>
<ELK_ID>K06</ELK_ID>
<property id="ST" value="64" formatted="Low" uom="100"/>
</node>
<properties>
<property id="ST" value="64" formatted="Low" uom="100"/>
</properties>
</nodeInfo>

Also, the commands speed commands from my browser do nothing.Why?

  • https://<your isy>/rest/nodes/<your fan address>/DON/<level>
  • https://<your isy>/rest/nodes/<your fan address>/DOF

What is the best way to set up an insteon controlled fan so that the Keypad buttons stay synced up correctly with the fan speed even when the fan speed is controlled by voice?

Posted
7 minutes ago, david-4 said:

This raises lots of questions for me

<snipped>

What is the best way to set up an insteon controlled fan so that the Keypad buttons stay synced up correctly with the fan speed even when the fan speed is controlled by voice?

I use a program for each fan level.  Note: Downstairs / Downstairs Fan is the Fan itself (not a scene).  The Downstairs / Fan Off is a scene, which has all KPLs and the Fan itself as members.

Off - [ID 007D][Parent 007C]

If
        'Downstairs / Downstairs Fan' Status is Off
 
Then
        Wait  5 seconds
        Set 'Downstairs / Fan Off' Off
 
Else
   - No Actions - (To add one, press 'Action')
 

This way, no matter how I change it, in 5 seconds, the KPLs get set correctly.  It causes a small amount of extra traffic, but I am ok with that.

  • Thanks 1
Posted
19 minutes ago, PurdueGuy said:

I use a program for each fan level.  Note: Downstairs / Downstairs Fan is the Fan itself (not a scene).  The Downstairs / Fan Off is a scene, which has all KPLs and the Fan itself as members.


Off - [ID 007D][Parent 007C]

If
        'Downstairs / Downstairs Fan' Status is Off
 
Then
        Wait  5 seconds
        Set 'Downstairs / Fan Off' Off
 
Else
   - No Actions - (To add one, press 'Action')
 

This way, no matter how I change it, in 5 seconds, the KPLs get set correctly.  It causes a small amount of extra traffic, but I am ok with that.

What I like about using scenes is that if the ISY goes down, the wall controls still work. I think that's the best part of  the Insteon system is that the basic functions will work independent of the controller and I don't lose all functionality if the controller goes down.

Posted
1 hour ago, david-4 said:

What I like about using scenes is that if the ISY goes down, the wall controls still work. I think that's the best part of  the Insteon system is that the basic functions will work independent of the controller and I don't lose all functionality if the controller goes down.

That's exactly how my solution operates.  If the ISY goes down, the only thing I lose is the Alexa voice integration.  All the KPLs still work as intended.

Posted (edited)
On 5/30/2020 at 11:01 AM, bmercier said:

What fan are you using. Fanlinc?

@bmercierI am actually using a wifi fan controller called Bond.  Is there a way to make an adjustment so Low is 25%, Medium is 50% or 75%, and High is 100%?

Edited by dinostop
Posted
13 hours ago, bmercier said:

The spaces are replaced by %20, this is normal.

It could be that your ISY is not configured for https. Try http instead:

http://192.168.0.33:1026/rest/nodes/14%20A0%20A%202

OK.  Was successful checking status, but could not change speeds via HTTP command.  I performed a modified experiment...commanded fan speeds via voice/alexa.  Once commanded, checked the status via HTTP command, looking at "value" 

Commanding fan LOW resulted in value=64.  Commanding fan MEDIUM resulted in value=191.  Commanded fan HIGH resulted in value=255.  Fan OFF resulted in value=0.

I hope this helps.

Posted
11 hours ago, oberkc said:

OK.  Was successful checking status, but could not change speeds via HTTP command.  I performed a modified experiment...commanded fan speeds via voice/alexa.  Once commanded, checked the status via HTTP command, looking at "value" 

Commanding fan LOW resulted in value=64.  Commanding fan MEDIUM resulted in value=191.  Commanded fan HIGH resulted in value=255.  Fan OFF resulted in value=0.

I hope this helps.

The values don't make sense to me.

I had a typo in the command to set values. Could you try:

http://192.168.0.33:1026/rest/nodes/14%20A0%20A%202/cmd/DON/127

Then:

http://192.168.0.33:1026/rest/nodes/14%20A0%20A%202

You should be seeing 127 in the ST property.

Benoit

Posted
16 hours ago, dinostop said:

@bmercierI am actually using a wifi fan controller called Bond.  Is there a way to make an adjustment so Low is 25%, Medium is 50% or 75%, and High is 100%?

@bmercier

When using the command line as you show I am able to set my fan to 25% (low), 50% (medium), and 100% (high), however when you use the spoken works they set to: Low (127%), Medium (253%), and Hight (255%).  As I noted above I am using a Smart by Bond fan controller which runs through Polyglot for control.  I would need to put in Low (25%), Medium (50% or 75%), and High (100%)  Is this possible?

 

Posted (edited)
5 hours ago, dinostop said:

@bmercier

When using the command line as you show I am able to set my fan to 25% (low), 50% (medium), and 100% (high), however when you use the spoken works they set to: Low (127%), Medium (253%), and Hight (255%).  As I noted above I am using a Smart by Bond fan controller which runs through Polyglot for control.  I would need to put in Low (25%), Medium (50% or 75%), and High (100%)  Is this possible?

 

Insteon using 1 byte for the brightness range, which is 0 to 255.

127 is 50% (of 255).

Since a FanLinc is seen as a dimmer:

  • 255 x 0.00 =  0 (Off)
  • 255 x 0.25 = 63.75 => 64 (Low)
  • 255 x 0.75 = 191.25 => 191 (Medium)
  • 255 x 1.00 = 255 (High)

Sounds like the node server needs to be updated to handle the values differently.

Edited by PurdueGuy
  • Like 1
Guest
This topic is now closed to further replies.

×
×
  • Create New...