Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
fanlinc_and_keypadlinc [2016/07/07 17:01]
jay [Setting buttons into non-toggle mode]
fanlinc_and_keypadlinc [2018/05/14 00:21] (current)
Line 65: Line 65:
 Well, we're almost done. If you never intend to control the fan from Indigo, then yes, you're done. However, if you also want to control the fan from Indigo as well as from the KeypadLinc, you need to do just a bit more work. As you might have read in the [[scenes_multiway_groups_overview|multi-way groups]] and [[inst_keypadlinc_buttons|KeypadLinc Buttons]] articles, keeping KeypadLinc buttons in sync when controlling the lights they'​re linked to requires a little more work. This is because when you control a device from Indigo, we have to use direct commands. This will not cause the links you've created between devices to be activated (there isn't a way to simulate a button press on a KPL to cause that behavior). Because of that, the KeypadLinc buttons that are linked to other devices can get out of sync if the device is controlled from Indigo. Well, we're almost done. If you never intend to control the fan from Indigo, then yes, you're done. However, if you also want to control the fan from Indigo as well as from the KeypadLinc, you need to do just a bit more work. As you might have read in the [[scenes_multiway_groups_overview|multi-way groups]] and [[inst_keypadlinc_buttons|KeypadLinc Buttons]] articles, keeping KeypadLinc buttons in sync when controlling the lights they'​re linked to requires a little more work. This is because when you control a device from Indigo, we have to use direct commands. This will not cause the links you've created between devices to be activated (there isn't a way to simulate a button press on a KPL to cause that behavior). Because of that, the KeypadLinc buttons that are linked to other devices can get out of sync if the device is controlled from Indigo.
  
-One other thing that complicates this particular scenario is the fact that Indigo can't create multiple links to the same device in a single group. For instance, you can't create a PowerLinc scene that includes multiple buttons on the same KeypadLinc. This is a limitation in Indigo that's not likely to be overcome soon because of the nature of how those links are maintained and how Indigo treats devices and links. Because of these things, you'll need to control the FanLinc Fan through Action Groups (rather than directly) so that the KeypadLinc'​s buttons will stay in sync. Fear not, we've also added another ​action in the [[plugins:insteon_commands|INSTEON Commands]] plugin ​that will help with that as well. +One other thing that complicates this particular scenario is the fact that Indigo can't create multiple links to the same device in a single group. For instance, you can't create a PowerLinc scene that includes multiple buttons on the same KeypadLinc. This is a limitation in Indigo that's not likely to be overcome soon because of the nature of how those links are maintained and how Indigo treats devices and links. Because of these things, you'll need to control the FanLinc Fan through Action Groups (rather than directly) so that the KeypadLinc'​s buttons will stay in sync. Fear not, there's an action in the [[https://​wiki.indigodomo.com/​doku.php?​id=indigo_6_documentation:​overview#​insteon_actions|Insteon Actions]] section ​that will help with that as well. 
  
-The simplest approach is to create 4 triggers - one each for when the Fan speed becomes ''​**High**'',​ ''​**Medium**'',​ ''​**Low**'',​ and ''​**Off**''​. The action for those actions will be to set the KPL's button LEDs appropriately. Rather than setting each LED separately using the built-in mechanism for setting LEDs (which would require a lot of INSTEON communication),​ you can use the ''​**Turn On/Off KeypadLinc Buttons**''​ action in the [[plugins:insteon_commands|INSTEON Commands]] plugin. That will only send 1 command to the KPL to set the state of all buttons. So, for the trigger that fires when the Fan speed becomes ''​**High**'',​ in the action'​s config dialog you would select the KeypadLinc, then select ''​**Turn Off**''​ for buttons 1, 2, 4, 5, 6, 7, 8 and ''​**Turn On**''​ for button 3. Now, you might be asking yourself why we'd want to turn off 1, 2, 7, and 8. Actually, because this is a 6 button KeypadLinc, those actions will be ignored since 1 and 2 are the load ON button and 7 and 8 are the load OFF button. The only important ones to turn off are 4 (''​**Medium**''​),​ 5 (''​**Low**''​),​ and 6 (''​**Off**''​) since the fan is on ''​**High**''​ and turn button 3 (''​**High**''​) on. Now, if you're operating the switch buttons manually, this will already be the case - but that's OK. If you're operating the fan from somewhere else - like a control page - this will keep the KeypadLinc'​s LEDs in sync. +The simplest approach is to create 4 triggers - one each for when the Fan speed becomes ''​**High**'',​ ''​**Medium**'',​ ''​**Low**'',​ and ''​**Off**''​. The action for those actions will be to set the KPL's button LEDs appropriately. Rather than setting each LED separately using the built-in mechanism for setting LEDs (which would require a lot of INSTEON communication),​ you can use the ''​**Turn On/Off KeypadLinc Buttons**''​ action ​in the  ​in the [[https://​wiki.indigodomo.com/​doku.php?​id=indigo_6_documentation:​overview#​insteon_actions|Insteon Actions]] section of the Action type popup. That will only send 1 command to the KPL to set the state of all buttons. So, for the trigger that fires when the Fan speed becomes ''​**High**'',​ in the action'​s config dialog you would select the KeypadLinc, then select ''​**Turn Off**''​ for buttons 1, 2, 4, 5, 6, 7, 8 and ''​**Turn On**''​ for button 3. Now, you might be asking yourself why we'd want to turn off 1, 2, 7, and 8. Actually, because this is a 6 button KeypadLinc, those actions will be ignored since 1 and 2 are the load ON button and 7 and 8 are the load OFF button. The only important ones to turn off are 4 (''​**Medium**''​),​ 5 (''​**Low**''​),​ and 6 (''​**Off**''​) since the fan is on ''​**High**''​ and turn button 3 (''​**High**''​) on. Now, if you're operating the switch buttons manually, this will already be the case - but that's OK. If you're operating the fan from somewhere else - like a control page - this will keep the KeypadLinc'​s LEDs in sync. 
fanlinc_and_keypadlinc.txt ยท Last modified: 2018/05/14 00:21 (external edit)
 

© Perceptive Automation, LLC. · Privacy