Strange Module Response

[Brian H]

When looking at some logs of Queries I noticed two modules gave back odd replies.

One has been showing a "Beep" response for awhile.

I thought maybe it was a location thing and in a different location it was OK.

Then back in original location it was also OK.

My thoughts. Moving did a power reset.

Any thoughts?

 

2456S3 ApplianceLincs. Old Hardware Revision 1.3 Firmware as reported by My Lighting v.28

Query individual modules.

Event Viewer: 3. Device Communication Events.

Modules are off.

 

Bedroom Wall:

Mon 01/23/2012 07:54:52 AM : [iNST-ACK ] 02 62 00.FC.2B 0F 19 00 06 LTSREQ (LIGHT)

 

Mon 01/23/2012 07:54:52 AM : [iNST-SRX ] 02 50 00.FC.2B 19.70.1A 2B 50 00 (00)

 

Mon 01/23/2012 07:54:52 AM : [standard-Direct Ack][00.FC.2B-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

 

Mon 01/23/2012 07:54:52 AM : [ 0 FC 2B 1] ST 0

 

Mon 01/23/2012 07:54:52 AM : [ 0 FC 2B 1] OL 255

 

Mon 01/23/2012 07:54:52 AM : [ 0 FC 2B 1] RR 31

 

Computer Room:

Mon 01/23/2012 07:54:55 AM : [iNST-ACK ] 02 62 00.FB.B3 0F 19 00 06 LTSREQ (LIGHT)

 

Mon 01/23/2012 07:54:55 AM : [iNST-SRX ] 02 50 00.FB.B3 19.70.1A 2B 30 00 BEEP (00)

 

Mon 01/23/2012 07:54:55 AM : [standard-Direct Ack][00.FB.B3-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

 

Mon 01/23/2012 07:54:55 AM : [ 0 FB B3 1] ST 0

 

Mon 01/23/2012 07:54:55 AM : [ 0 FB B3 1] OL 255

 

Mon 01/23/2012 07:54:55 AM : [ 0 FB B3 1] RR 31

 

Power Cycle Modules.

 

Bedroom Wall:

Mon 01/23/2012 08:27:28 AM : [iNST-ACK ] 02 62 00.FC.2B 0F 19 00 06 LTSREQ (LIGHT)

 

Mon 01/23/2012 08:27:28 AM : [iNST-SRX ] 02 50 00.FC.2B 19.70.1A 2B 00 00 (00)

 

Mon 01/23/2012 08:27:28 AM : [standard-Direct Ack][00.FC.2B-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

 

Mon 01/23/2012 08:27:29 AM : [ 0 FC 2B 1] ST 0

 

Mon 01/23/2012 08:27:29 AM : [ 0 FC 2B 1] OL 255

 

Mon 01/23/2012 08:27:29 AM : [ 0 FC 2B 1] RR 31

 

Computer Room:

Mon 01/23/2012 08:27:31 AM : [iNST-ACK ] 02 62 00.FB.B3 0F 19 00 06 LTSREQ (LIGHT)

 

Mon 01/23/2012 08:27:31 AM : [iNST-SRX ] 02 50 00.FB.B3 19.70.1A 2B 00 00 (00)

 

Mon 01/23/2012 08:27:31 AM : [standard-Direct Ack][00.FB.B3-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

 

Mon 01/23/2012 08:27:31 AM : [ 0 FB B3 1] ST 0

 

Mon 01/23/2012 08:27:31 AM : [ 0 FB B3 1] OL 255

 

Mon 01/23/2012 08:27:31 AM : [ 0 FB B3 1] RR 31

[LeeG]

The Beep annotation results from the ISY looking at the cmd1 field for the command code. Query (0x19) returns the device link database delta number in the cmd1 field rather than the original 19 command code. We see the same thing on Powerhome all the time. The command annotation depends on whether the link database delta number happens to match an Insteon command code. The only way to prevent that would be to remember the last command issued to that device and bypass the cmd1 analysis and annotation if a Query command.

[Brian H]

Can you think of any reason why it went away after I power reset the two ApplianceLincs?

The returned data to the query was different after the power reset.

[LeeG]

A Factory reset would clear the link database and link database Delta number. If just an unplug/plug I don't know why the Delta number would have been reset. Did it go from 30 to 00?

 

The Delta number is meant as a tool for an application to know if the link database has changed. The assumption is the application has remembered the 30. If it finds something other than 30 it knows the link database has been changed. It avoids the need for an application to read an entire link database to see if any changes have been made.

[Brian H]

Thanks for the input.

Only two of them seemed to have changed. Maybe they are getting tired. As they are the replacement for the recalled ones from I believe late 2005 or early 2006.