LeeG

The manual Query of Motion Sensor Low Bat node does reset the node to Off. That is the expected process to reset Low Bat node after battery replaced. If the manual Query is done without replacing battery the Low Bat=On is lost. The 3AM Query Program has no affect on Motion Sensor Low Bat node.

MrWorf The iMeter is not responding to three attempts to process the command to access Insteon Engine information. Here is what should happen .... Fri 01/08/2016 02:59:26 AM : [All ] Writing 1 bytes to devices Fri 01/08/2016 02:59:26 AM : [iNST-TX-I1 ] 02 62 18 F5 40 0F 0D 00 Fri 01/08/2016 02:59:26 AM : [iNST-ACK ] 02 62 18.F5.40 0F 0D 00 06 (00) Fri 01/08/2016 02:59:26 AM : [iNST-SRX ] 02 50 18.F5.40 22.80.0B 2B 0D 01 (01) Fri 01/08/2016 02:59:26 AM : [std-Direct Ack] 18.F5.40-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 01/08/2016 02:59:26 AM : [18 F5 40 0 ] Calibrating engine version Fri 01/08/2016 02:59:26 AM : [18 F5 40 0 ] May not fully support i2, reverting to i1 Fri 01/08/2016 02:59:27 AM : [iNST-ERX ] 02 51 18 F5 40 22 80 0B 1B 82 00 00 04 01 FF 00 91 00 01 00 00 00 00 F0 79 Fri 01/08/2016 02:59:27 AM : [Ext-Direct ] 18.F5.40-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 The event trace shows no iMeter response to the three attempts. Note that I have no link records in my iMeter Solo. There is much activity going on while trying to add iMeter Solo. Not sure if that is having a negative impact or simply a comm issue with current location. jerlands suggestion to move to the PLM plug point is good. Also if you can suspend some of the current activity that might help. I am running 4.4.2. 4.3.26 is the latest Official release.

The 3AM Query does not query Motion Sensors.

I'll run the Event Viewer for the 3AM Query. I don't think any battery powered device is queried at 3AM because they are asleep.

Just read the last several posts made while I was writing mine. Unlike larryllix I do see Low Bat On. It is a single attempt so if something on the Insteon network blocks the message from the battery powered device (battery powered devices do not monitor Insteon network) I can see where a busy Insteon network could miss a Low Bat On. I keep my Insteon network relatively quiet so I may be seeing messages for Low Bat On that larry does not see.

The Motion Sensor Low Bat node does not go back to Off state on its own. Once the battery has been replaced right click on Low Bat node and select Query. This will cause the ISY to reset the Low Bat node to Off. Below are two examples where I right clicked and selected Query on two Motion Sensors. Note that no actual Query command was sent to the Motion Sensor. The Query request simply directs the ISY to reset the Low Bat node to Off. Thu 01/07/2016 09:05:46 AM : [D2D EVENT ] Event [13 F2 57 3] [sT] [0] uom=0 prec=-1 Thu 01/07/2016 09:05:46 AM : [ 13 F2 57 3] ST 0 - ISY marks Low Bat Off for 13.F2.57 Thu 01/07/2016 09:08:05 AM : [D2D EVENT ] Event [14 C1 C7 3] [sT] [0] uom=0 prec=-1 Thu 01/07/2016 09:08:05 AM : [ 14 C1 C7 3] ST 0 - ISY marks Low Bat Off for 14.C1.C7 The Motion Sensor has no Off message associated with the Low Bat node. The Motion Sensor monitors battery voltage and sends an On Message for Low Bat (node/group 3) node when voltage drops to a point where the battery should be replaced.

Sounds like a comm issue but need more detail. Suggest running Tools | Diagnostics | Event Viewer at LEVEL 3. Attempt to add device using New INSTEON Device. Enter Insteon address, Name of choice, and Auto Discover. Post the event trace. Also check Help | About to be sure UI and Firmware both indicate 4.3.26.

The I/O Linc User Guide would be discussing manually linking the I/O Linc Sensor to a Responder.

"The light on the iolinc does track the actual sensor correctly and I am seeing reports correctly, but seeing ON when I should see OFF and vice-versa." Can you expand on what a report is, and is it the Admin Console Sensor node that is opposite to the LED state LED (LED On, sensor node Off).

Also how was the lack of Trigger Reverse being set confirmed? Clicking on Options does not pull information from the I/O Linc. The Options display may be misleading. Suggest doing a Factory Reset on I/O Linc followed by a Restore Device. This rebuilds the I/O Linc Options without any lose of Scene definitions.

I've added an IO Linc first in sensor Off state, then in sensor On state. Both produced an IO Linc definition that showed sensor state that tracked to the Green Sensor LED next to wire connections. How does the Sensor LED On/Off relate to Sensor node On/Off?

Once Low Bat turns On due to low battery that Program repeats the Send notification every 12 hours. The Run Program repeats the Then which has no check of Low Bat. Would need (If Path) to check Low Bat state. Run Program 'Front Door LBC' (Then Path) [which is this program] Else Wait 12 hours Also note that the Wait 12 hours in Else has no affect because there are no statements after the Wait.

Run Tools | Diagnostics | Event Viewer at LEVEL 3 before Sunrise. Post the event trace after the Scenes run. Also post the Programs that are issuing the Scene commands.

Cormacs 4.4.2 Beta or 5.x Beta? I'm not seeing that problem on 4.4.2. Is that a State variable (as it should be) or Integer" Did the search suggested by jerlands show any other Program changing $Light?

Suggest posting actual Program. Information presented is conflicting. Sounds like a Program issue but that is speculation at this point.

Did you put each Motion Sensor into linking mode (only one at a time) so update to battery powered device will be done? Be sure to take Motion Sensor out of linking mode before updating next one.

Change If Status 'Motion (Deck)-Sensor' is On . . . to If Control 'Motion (Deck)-Sensor' is switched On . . . Also add to Else Else Set 'Living Rm Keypad-Fireplace LT' Off The Else change insures Fireplace LT is not left On at Sunrise.

When the Restore Modem (PLM) and Restore Devices does not fix the missing link the next step is to Restore ISY and repeat Restore Modem (PLM) and Restore Devices. If a current ISY backup is not available (or the ISY Backup does not fix problem because the issue existed when backup taken) the next step would be to delete device, factory reset, and add device to ISY. Not sure what you are referring to "re-pair" device.

klebel The E2 in device and A2 in PLM is an Insteon Scene. It is created when the device was initially added to the ISY and must be there at all times for the device to work correctly.

klebel There must be an E2 in the device and an A2 in the PLM for local switch activity to be reported to the ISY. Standard Insteon requirement forever. For the E2 links not to be in the devices something happened during the process of replacing the PLM. ISY and PLM not powered in the correct sequence, I cannot say without knowing exactly what was done during the PLM replacement. Since now the ISY does not have the correct information with multiple Restore Devices not fixing, the next step would be to Restore ISY with backup taken before PLM was replaced. Then do a Restore Modem (PLM) followed by another Restore Devices.

Without the E2 Controller records in each device local activation is not sent to the PLM. Normally the Controller information is in the ISY but since the Restore Devices did not bring the information back first thing is to look at ISY Firmware and UI levels. Help | About displays both ISY Firmware and UI (Admin Console) levels.

For the SwitchLinc that does not report local change to ISY (PLM) do a Show Device Links Table. Looking for a link record that is E2 01 xx.yy.zz .. .. .. where xx.yy.zz is new PLM Insteon address and a Show PLM Links Table that is A2 01 aa.bb.cc .. .. .. where aa.bb.cc is Insteon address of SwitchLinc

jwf Best to put that request to SmartLabs. There are always questions that come up about what a Scene Status would look like. In this Scene On DeviceA is 100% On DeviceB is 50% On DeviceC is turned Off If Scene Status is On as a result of issuing the Scene On, what happens to Scene Status if DeviceB is changed to 80% On. Just one of many questions about Scene Status that has not generated a consensuses opinion.

Scenes have never had Status. An individual device in a Scene can be checked but not the Scene itself.

greensha When the KPL button and OutletLinc were manually linked the ISY has been out of the picture. The Responder link in the OutletLinc that has the OutletLinc Responder On Level and Responder Ramp Rate is not known to the ISY, cannot be changed by the ISY. NEVER manually link devices when using an ISY. The KPL and OutletLinc need to be Factory Reset and a Restore Device issued for both devices. When the Scene between the KPL button and OutletLinc is created by the ISY, set the Responder On Level and Responder Ramp Rate. The Local On Level and Local Ramp Rate do not control the manual link and do not control an ISY Scene. Again, these values cannot be set for the manual link as the ISY has no knowledge of the manual link. That is why the devices must be cleared and restored first.