"Applied Locally" Demystified

[LeeG]

"So this means that the dimmer never sends out it's current state?"

 

Within the bounds of the examples discussed here, correct.

 

Outbound Direct messages to the SwitchLinc do provide an On Level in the ACK from the SwitchLinc so "never" does not apply everything.

[Broyd]

Thanks LeeG. Is there any collected documentation on understanding the messages in the event logs or is that scattered helter skelter here and there?

 

And on a different note, the ISY is obviously measuring time on a much finer scale when manually setting the brightness using the dimmer paddle. Has anyone suggested it would be a great addition to have the time in the logs and events show to 1/10 or 1/100 of a second?

Edited February 3, 2016 by Broyd

[LeeG]

Insteon messages start with "02 6x" for messages outbound from ISY/PLM and "02 5x" for inbound messages.

 

The ISY adds messages that interpret what the Insteon message contains.

 

 

 

Tue 02/02/2016 10:21:51 AM : [iNST-SRX ] 02 50 3C.75.CD 00.00.01 CB 11 00 LTONRR (00) -  02 50 from device

Tue 02/02/2016 10:21:51 AM : [std-Group ] 3C.75.CD-->Group=1, Max Hops=3, Hops Left=2 - generated by ISY - has Insteon address, Group (scene) of node, Hops counts, Max Hops permitted, Hops Left available 
 

 

The basic Event viewer data is covered in this Wiki section

 

http://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Using_the_Event_Viewer

 

 

The web site www.insteon.com has links to other Insteon documents that cover many other 02 5x, 02 6x, and 02 7x Insteon messages.  The PLM User Guide has much detail, too much detail for 99% of users but some data is helpful.  Scan the documents and pick the data that seems interesting.  

 

 

Of course any specific question(s) about actual messages in a trace can be posted.  Several of the ISY and Insteon experts are happy to post answers. 

Edited February 3, 2016 by LeeG

[Broyd]

Thanks LeeG! Appreciated.

[Tim McDermott]

Coincidently, I was corresponding with Michel regarding this very issue. I think I ended up believing the settings eventually "took" after some time had elapsed or some action had happened.

 

Sent from my D5803 using Tapatalk