LeeG

Assuming this is a new Leak Sensor once Wet node turns On it will stay On until the Leak Sensor is Dry and the Set button on the Leak Sensor is tapped to reset the Leak Sensor back to Dry. The older Leak Sensors would cycle back to Dry when they were no longer physically Wet. The newest Leak Sensors require a tap on the Set button to come back to Dry. I do not use MobiLinc so cannot say what alerts it sends.

The second Program monitors the Heartbeat node. The HeartBeat node sends a message every 24 hours which resets the Wait to a new 25 hour Wait. As long as the Heartbeat sends the expected message the Program just monitors the Heartbeat node. If the Wait times out the Program will perform the statement(s) after the Wait which should be something that alerts you to the missing HeartBeat.

The latest Leak Sensor with v.43 firmware (the version that once Wet continues Wet until Set button tapped) requires nothing more than a simple Wet - [iD 008D][Parent 0001] If Control 'Leak Sensor 2-Dry / Leak Sensor 2-Wet' is switched On Then Send Notification to 'Name.3' content 'Custom with date' Else - No Actions - (To add one, press 'Action') The earlier firmware that would cycle back to Dry could be more challenging because Dry/Wet status could cycle. Does not happen with the newest Leak Sensor firmware. Also note that with the latest firmware the Heartbeat node does not get a message when tapping Set button. The older firmware sends a Heartbeat approx 14 seconds after the Dry/Wet test message when Set button tapped. Sorry, this part did not make the post. The Heartbeat can also be simple. I turn lights On but a Notify works just as well. The Leak Sensor battery lasts 10 years so it is not something that needs changing like a Motion Sensor battery. HeartBeat - [iD 0044][Parent 0001] If Control 'Leak Sensor-Dry / Leak Sensor-Heartbeat' is switched On Or Control 'Leak Sensor-Dry / Leak Sensor-Heartbeat' is switched Off Then Wait 25 hours Send X10 'A10/All Lights On (5)' Else - No Actions - (To add one, press 'Action')

Take a look at this topic for how to handle userid/password with Network module. http://forum.universal-devices.com/topic/13901-userid-and-password

The Energy Display 2448A2 creates a Responder link in the iMeter Solo. The ISY does not support the 2448A2 so the link between iMeter Solo and Energy Display has to be established manually.

I used New INSTEON Device. Entered Insteon Address, Name of choice, and Auto Discover.

The ZIP is not empty. It is not a standard ZIP file and cannot be viewed using your approach. Do a Restore ISY using the original ZIP file created by the Backup ISY if you want to test it. Under no circumstances use the file you have been playing with.

The ISY .ZIP is not a normal ZIP file. What are you trying to determine? The contents of that ZIP file cannot be modified and most info will not be understood.

The information in the ISY is in the Backup file. ISY configuration, Variables, Programs, device nodes, perhaps other things in the ISY related to optional modules, etc. Information physically in Insteon devices, PLM is not part of the Backup file. Information to Restore devices, PLM is in the Backup file. Upgrading from Official release 4.2.18 to Official release 4.2.30 should not introduce issues that would not allow going back to 4.2.18. However, life is not an absolute. There have been cases where a pre v2.0 PLM failed when an upgrade was done even though the upgrade did not modify the PLM. There could be issues with device communication that exist at 4.2.18 but were not noticed. Electronics fail at unexpected times. I upgrade my ISY with every new image and have never found it necessary to return to a previous image. Others that require a turn key environment from Insteon in general may find something to have an issue with. I would recommend taking a current ISY Backup and upgrading to 4.2.30.

The normal sequence is to add new thermostat under a dummy name. Right click on existing old thermostat primary node and select Replace 'old thermostat' With ...... which will display a list of devices that can Replace old thermostat. The new thermostat replaces the old thermostat using the old thermostat name but with the new thermostat Insteon address. No Program or Scene changes are necessary as the old thermostat name remains and the new thermostat dummy name is automatically deleted I've never tried to replace a thermostat so cannot say the Replace 'xxxxx' With .... works on a thermostat.

There is a relatively new Program statement (it is in Official release 4.2.30, it is not in Official release 4.2.18) that allows a Motion Sensor to be updated without manually putting the Motion Sensor into linking mode. It is time dependent so it may not function depending on where the Motion Sensor is located relative to the Insteon network. Enable a Program similar to the following and have the Motion Sensor detect motion. The Time range is not required. UpdateMS - [iD 0075][Parent 0001] If Control 'MS I2CS-Sensor' is switched On And From 5:20:00AM For 1 hour Then Set 'MS I2CS-Sensor' Write Device Updates Else - No Actions - (To add one, press 'Action')

Exactly right.

The two "cherries" indicate motion sensor nodes. The three Gray Icons with 1011 inside on the next motion sensor nodes indicate updates are pending for a battery powered device that has the updates suspended by last Option Icon on right.

Great question. No, changing a node name automatically changes Program and Scene references.

They are related to opening a file on the SD card. Number Error Message -110012 SD DRIVE CONFIG FILE OPEN READ FAILED -110022 OPEN FILE FAILED What is being done when messages occur?

paulbates Having network wide issues from adding a single Dual Band device is very odd. I've not seen anything related to how coupling is being performed (is it RF or passive) which would even be more odd if RF coupling is used but a single new Dual Band device creates such issues. Need more information about the electrical environment which might add clarity. When such an odd situation exists there is often some additional information not yet known that allows the pieces to fit together.

REST API does not use the Network Module.

Being a previous commercial building does it now have residential power (split single phase - 2 120 volt legs) or something from the commercial days? What does Tools | Diagnostics | PLM Info/Status show for PLM firmware (xx.xx.xx ???/Connected)? With likely little Dual Band devices running a PLM beacon test may be limited. Tap the PLM Set button 4 times. How are the Dual Band devices reacting as far as Status LED (color and blinking)?

Manually linking a single node at a time versus trying to Restore Device is like comparing Apples and Oranges. The commands that Set button link a single node are very simple and different than what is needed to programmatically create a single link let alone update a complete KPL data base. The V.43 Keypad is an I2CS Dual Band device where the v.36 KPL is I2 and powerline only. It suggests there is some issue with the existing Insteon network now having a Dual Band device where it did not exist before. If the plan is to move away from Insteon there is no sense analyzing the existing Insteon. If the desire is to maintain the Insteon investment paulbates ideas are a great place to start. Folks on the forum are happy to help in this effort if that is your choice.

The Programs should trigger with their respective Control/Insteon command combination. Run Tools | Diagnostics | Event Viewer at LEVEL 3 to see what Insteon command is being generated. The problem is how to generate the command and in what order. Not possible to generate a Fast On followed by an On followed by an Off or Fast Off from the same KPL button.

The latest Official release 4.2.30 is stable. No reason not to upgrade ISY and download 4.2.30 Admin Console. With Trigger Reverse not being used it sounds like comm to I/O Linc may be marginal. Possibly something else is running/powered at the time making comm appear to be an issue. Suggest issuing Query 4-5 times against the I/O Linc with the Event Viewer running at LEVEL 3. Post the event trace to allow evaluation of the comm to that device.

dimB physically turned On/Off turns On/Off dimA which powers the load. This happens because dimA and dimB are in a Scene which cross-links the two devices. This Scene (actually multiple Insteon Scenes) applies to manual operation of either switch. The Scene DOES NOT apply to a switch that is turned On/Off by another device that is not part of the specific Scene, the PLM in this case. When the Admin Console turns on dimB the Scene is not in effect so dimA is not affected. Standard Insteon operation. Has nothing to do with the ISY. As was noted earlier to have both switches operate together a Scene has to be operated by the PLM that has both switches defined as Controllers. Again normal Insteon operation. There is an insteondetails.pdf document on insteon.com that describes Scene operation. Much more Insteon detail than a newbie is interested in but this document can be useful as you learn more about how Insteon works.

Normal if ELK not installed Wed 04/22/2015 10:48:37 PM : [FileOpen ] Open failed for [/CONF/ELK.CNF] ® Wed 04/22/2015 10:48:37 PM : [FileOpen ] Open failed for [/CONF/ELK.CNF] ® Wed 04/22/2015 10:48:38 PM : [FileOpen ] Open failed for [/CONF/ZIGBEECO.CFG] ®

If Status does work here RLAllOnKPLD - [iD 008B][Parent 0001] If Status 'KeypadLinc 8 Button-2 / KeypadLinc 8 Button-2 - D' is 100% Then Send X10 'D1/On (3)' Else Send X10 'D1/Off (11)' Tue 04/21/2015 10:17:49 AM : [iNST-SRX ] 02 50 11.AD.CF 00.00.FF CB 12 00 LTON-F (00) - RemoteLinc ALL ON Tue 04/21/2015 10:17:49 AM : [std-Group ] 11.AD.CF-->Group=255, Max Hops=3, Hops Left=2 Tue 04/21/2015 10:17:49 AM : [D2D EVENT ] Event [11 AD CF 1] [DFON] [0] uom=0 prec=-1 Tue 04/21/2015 10:17:49 AM : [ 11 AD CF 1] DFON 0 Tue 04/21/2015 10:17:49 AM : [D2D EVENT ] Event [8 49 E7 4] [sT] [255] uom=0 prec=-1 - KPL D Status On Trigger Tue 04/21/2015 10:17:49 AM : [ 8 49 E7 4] ST 255 Tue 04/21/2015 10:17:49 AM : [D2D-CMP 008B] STS [8 49 E7 4] ST op=1 Event(val=255 uom=0 prec=-1) is Condition(val=255 uom=0 prec=-1) --> true Tue 04/21/2015 10:17:49 AM : [ X10] D1 Tue 04/21/2015 10:17:49 AM : [X10-RSP ] 02 63 A6 00 06 Tue 04/21/2015 10:17:49 AM : [ X10] D1/On (3) Tue 04/21/2015 10:17:50 AM : [iNST-SRX ] 02 50 11.AD.CF 00.00.FF CB 12 00 LTON-F (00) Tue 04/21/2015 10:17:50 AM : [std-Group ] 11.AD.CF-->Group=255, Max Hops=3, Hops Left=2 Tue 04/21/2015 10:17:50 AM : [iNST-DUP ] Previous message ignored. Tue 04/21/2015 10:17:50 AM : [X10-RSP ] 02 63 A2 80 06 Tue 04/21/2015 10:17:51 AM : [X10-RX ] 02 52 A6 00 Tue 04/21/2015 10:17:51 AM : [ X10] D1 Tue 04/21/2015 10:17:57 AM : [iNST-SRX ] 02 50 11.AD.CF 00.00.FF CB 14 00 LTOFF-F(00) - RemoteLinc ALL OFF Tue 04/21/2015 10:17:57 AM : [std-Group ] 11.AD.CF-->Group=255, Max Hops=3, Hops Left=2 Tue 04/21/2015 10:17:57 AM : [D2D EVENT ] Event [11 AD CF 1] [DFOF] [0] uom=0 prec=-1 Tue 04/21/2015 10:17:57 AM : [ 11 AD CF 1] DFOF 0 Tue 04/21/2015 10:17:57 AM : [D2D EVENT ] Event [8 49 E7 4] [sT] [0] uom=0 prec=-1 - KPL D Status Off Trigger Tue 04/21/2015 10:17:57 AM : [ 8 49 E7 4] ST 0 Tue 04/21/2015 10:17:57 AM : [D2D-CMP 008B] STS [8 49 E7 4] ST op=1 Event(val=0 uom=0 prec=-1) is Condition(val=255 uom=0 prec=-1) --> false Tue 04/21/2015 10:17:57 AM : [ X10] D1 Tue 04/21/2015 10:17:57 AM : [X10-RSP ] 02 63 A6 00 06 Tue 04/21/2015 10:17:57 AM : [ X10] D1/Off (11) Tue 04/21/2015 10:17:57 AM : [iNST-SRX ] 02 50 11.AD.CF 00.00.FF C7 14 00 LTOFF-F(00) Tue 04/21/2015 10:17:57 AM : [std-Group ] 11.AD.CF-->Group=255, Max Hops=3, Hops Left=1 Tue 04/21/2015 10:17:57 AM : [iNST-DUP ] Previous message ignored. Tue 04/21/2015 10:17:58 AM : [X10-RSP ] 02 63 A3 80 06 Tue 04/21/2015 10:17:58 AM : [X10-RX ] 02 52 A6 00 Tue 04/21/2015 10:17:58 AM : [ X10] D1

Is the Program using "If Control" or "If Status" to monitor button D? Are the RemoteLinc buttons manually linked or using ISY Scenes? Does button D show On in Admin Console when RemoteLinc All On used?