| Author |  | 
      
        | smarty Super User
 
  
  
 Joined: May 21 2006
 Location: United States
 Online Status: Offline
 Posts: 729
 | 
          The "Insteon Device Change" trigger has been very useful for me to keep my touchscreens in-synch with my Insteon light status (no matter how the light change occured).
           | Posted: December 09 2006 at 20:22 | IP Logged |   |  
           | 
 |  
 I have not made much use of DirectIn/Out or GroupIn/Out, because they have limitations depending upon how the light change was initated (locally or remotely).
 
 The additional triggers I could make use of would be "Insteon Level Change" (triggers when the device is brightened or dimmed either locally or remotely) and "Insteon Status Change" (triggers when the device is "full on, 255/255" or "full off, 0/255".  The caveat here is that 0/255 would mean OFF rather than DIMMED (I reported this as a bug a while back, but Dave said this was by design; X10 carry over).
 
 While these items can be figured out via ph_getinsteonstat(), the new triggers would add a new level of trigger granularity that would make a buch of my macros much less complex.
 
 __________________
 Elk - Insteon - BlueIris - DMC1 - PowerHome - XLobby - HA_Bridge w/Dots - Brultech
 | 
       
        | Back to Top |     | 
       
       
        |  | 
        | dhoward Admin Group
 
  
  
 Joined: June 29 2001
 Location: United States
 Online Status: Offline
 Posts: 4447
 | 
          Steve,
           | Posted: December 18 2006 at 12:28 | IP Logged |   |  
           | 
 |  
 I can look into the additional triggers but I need to be careful not to add too many different checks otherwise speed may become an issue.
 
 Not sure if Ive documented it elsewhere, but the new Insteon Device Chg trigger includes addtional supporting info in the TEMP variables that may assist you in your efforts (most triggers include addl info in the TEMP vars).
 
 Below is the data that is contained in the TEMP vars for the Insteon Device Chg trigger:
 
 
 
| Code: 
 
    
    | 
      
       | TEMP1     ID of Trigger
 TEMP2     0
 TEMP3     Insteon CMD 2
 TEMP4     Type of trigger
 1 = Direct Command from PH PLC
 2 = Group Cleanup from PH PLC
 3 = Group Broadcast from PH PLC
 4 = Direct Command from device
 5 = Group Broadcast from device
 6 = Group Cleanup from device
 TEMP5     The address of the sending device
 TEMP6     20 = Direct type command
 21 = Broadcast type command
 TEMP7     The address of the receiving device
 TEMP8     The Group number for group type commands, 1 otherwise
 TEMP9     Insteon CMD 1
 TEMP10     ID of Receiving device
 
 |  |  |  
 You can effectively get your "Level Change" trigger by using the "Insteon Device Chg" trigger with [Any] group and [Any] command and then placing this formula in the "Boolean" field:
 
 case([TEMP9] when 21,22,24 then 1 else 0)
 
 This will only allow the trigger to fire when a dim, bright, or stop manual change command affects the desired device.  You could then create multiple "Insteon Device Chg" triggers with appropriate formulas in the "Boolean" field all executing different macros to pick up some granularity.
 
 Dave.
 
 | 
       
        | Back to Top |       | 
       
       
        |  | 
        | smarty Super User
 
  
  
 Joined: May 21 2006
 Location: United States
 Online Status: Offline
 Posts: 729
 | 
          Dave,
           | Posted: December 18 2006 at 22:20 | IP Logged |   |  
           | 
 |  With this additional TEMP VARIABLE info, I have what I need to write better triggers!!!!
 
 Request for new triggers is WITHDRAWN.
 
 Thanks
 Steve
 
 __________________
 Elk - Insteon - BlueIris - DMC1 - PowerHome - XLobby - HA_Bridge w/Dots - Brultech
 | 
       
        | Back to Top |     | 
       
       
        |  |