LeeG

gviliunas The message after the Query Insteon Engine is associated with link database management. The SwitchLinc discussion involves using I1 or I2 to do device configuration. The following trace is from my SwitchLinc. The I2 versus I1 message is displayed. However, the SwitchLinc LED brightness is being set with I2. Thu 04/12/2012 12:38:22 PM : [iNST-TX-I1 ] 02 62 16 3F 93 0F 0D 00 Thu 04/12/2012 12:38:22 PM : [iNST-ACK ] 02 62 16.3F.93 0F 0D 00 06 (00) Thu 04/12/2012 12:38:22 PM : [iNST-SRX ] 02 50 16.3F.93 19.70.06 2B 0D 01 (01) Thu 04/12/2012 12:38:22 PM : [standard-Direct Ack][16.3F.93-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 04/12/2012 12:38:22 PM : [16 3F 93 0 ] Calibrating engine version Thu 04/12/2012 12:38:22 PM : [16 3F 93 0 ] May not fully support i2, reverting to i1 Thu 04/12/2012 12:38:39 PM : [All ] Writing 1 bytes to devices Thu 04/12/2012 12:38:39 PM : [16 3F 93 1 ] Memory : Write dbAddr=0x0264 [D2] cmd1=0x2E cmd2=0x00 Thu 04/12/2012 12:38:39 PM : [iNST-TX-I2 ] 02 62 16 3F 93 1F 2E 00 00 03 D2 00 00 00 00 00 00 00 00 00 00 FD Thu 04/12/2012 12:38:39 PM : [iNST-ACK ] 02 62 16.3F.93 1F 2E 00 00 03 D2 00 00 00 00 00 00 00 00 00 00 FD 06 (00) Thu 04/12/2012 12:38:40 PM : [iNST-SRX ] 02 50 16.3F.93 19.70.06 2B 2E 00 (00) Thu 04/12/2012 12:38:40 PM : [standard-Direct Ack][16.3F.93-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Are you having problems configuring the KeypadLincs? Issuing a Query Insteon Engine may restore the use of I2 for device configuration. It does not break anything.

Click on the Primary KeypadLinc node in the My Lighting tree. The second line of information displayed in the right pane shows the firmware level v.??. If it displays v.00 the KeypadLinc was not added using Auto Discover.

The move to I2CS support has resulted in the device Engine information being wrong for some devices. The SwitchLinc LED update should use I2 which looks like this … Thu 04/12/2012 10:10:29 AM : [16 3F 93 1 ] Memory : Write dbAddr=0x0264 [D2] cmd1=0x2E cmd2=0x00 Thu 04/12/2012 10:10:29 AM : [INST-TX-I2 ] 02 62 16 3F 93 1F 2E 00 00 03 D2 00 00 00 00 00 00 00 00 00 00 FD Thu 04/12/2012 10:10:29 AM : [iNST-ACK ] 02 62 16.3F.93 1F 2E 00 00 03 D2 00 00 00 00 00 00 00 00 00 00 FD 06 (00) Thu 04/12/2012 10:10:30 AM : [iNST-SRX ] 02 50 16.3F.93 19.70.06 2B 2E 00 (00) If the SwitchLinc update is using Peek/Poke commands instead of I2 there are two solutions. First try right click on SwitchLinc node, select Diagnostics | Query Insteon Engine. If that does not result in the I2 method being used for updating the LED information the SwitchLinc has to be Deleted and added back under 3.2.4.

Take a look at this section of the forum on Variables. viewforum.php?f=68 Values are normally set for Init and Value when the variable is initially defined. Variables are signed integers. State and Integer variable content is identical. The difference is a change to a State variable value causes a Program to be triggered (like If Status for a device), a change to an Integer variable value does not cause a Program to be triggered. This and much more is covered in topics under the Variables category link provided above. Feel free to post back if these topics do not cover your questions.

Never having lost a device link database by accident I don't know the answer. Set button linking can result in problems as the ISY is not aware of them, eventually deleting or overlaying them. If this is occurring on a regular basis perhaps the next time do a Show Device Links Table on the devices involved to see which one has the problem and exactly what the problem is. By knowing what is wrong, the entire link database gone, something wrong with a specific link record, etc we can figure out what is actually happening. Glad to here the restores resolved the current problem.

Under no circumstances do a Query every 5 minutes of anything. Is the I/O Linc Sensor, which should be connected to the magnetic switch, turning the Green LED on the I/O Linc On and Off as the door opens and closes. If no then the I/O Linc is not connected correctly. If the Green LED is turning On and Off the I/O Linc may have lost its link records if manual Set button links were tried. Could be too far from the house or the 120v phases are not coupled correctly. The easy test is to disconnect the wires from the I/O Linc in the garage, move it to the house at the PLM plug point. Attach two short wires to the Sensor and GND connections. Touch the wires together. The Green LED will turn On. Does the Sensor node in the Admin Console change state. If so there is a communications problem with the garage. If not there is a link record problem. Suggest deleting the I/O Linc and adding it back to the ISY to see if that results in the Sensor node showing state changes.

Unless it is an InLineLinc w/sense it is a Responder only. It can be controlled by the other switch but itself cannot control another Insteon device. One ISY Scene, switch as Controller, InLineLinc as Responder.

Use one ISY Scene. Add both switches as Controllers of the one ISY Scene. The ISY assumes a Controller is also a Responder and will cross-liink the devices.

The old I1 method is still being used. Right click on SwitchLinc node, select Diagnostics | Query Insteon Engine. Set a new On Level (applied locally) value and see if it take effect. If this does not resolve the issue the SwitchLinc will have to be Deleted and added back under 3.2.4.

Run Tools | Diagnostics | Event Viewer with Level 3-Device communications events selected (most important). From the SwitchLinc node display move the On Level (applied locally) slider and Ramp Rate (applied locally) slider to some new position. The On Level and Ramp Rate values have to be changed before the ISY will write the new values to the SwitchLinc. Also be sure a Progress Bar is displayed when the slider is dropped on the new location and wait for the update to complete before moving the next slider. Post the event trace. It will not be very long. Do not go back to an earlier image. This can be resolved quickly. I verified the fix works. Run Help | About and be sure the Firmware and UI lines both show 3.2.4.

The phase test varies by device. The User Guide for the specific device will detail the process. Wired Dual Band devices seem to have less range than the pluggable Access Points. Perhaps because the wired units are in the wall with lots of 120V wiring around them.

Have the tstat dongles been updated with 2.2R or later? The 120v phases may not be well coupled if moving closer the PLM itself worked better.

That size wire is fine. It is switching a low voltage digital circuit so current capacity is not a factor.

Sorry to hear it did not work for you. That is an odd result. I ordered a Dakota Alert Motion Sensor but just got around to testing it with all the I2CS activity. I added the Dakota Alert Motion Sensor as a Sensor to the EZSnsRF. After verifying the motion sensor was signaling On and Off to the EZSnsRF and being reported to the ISY I unplugged the EZSnsRF and restored power. The Motion Sensor continues to report On/Off as motion is sensed. It takes a little less than 30 seconds for the EZSnsRF to boot up. After that motion is reported. The Dakota Alert receiver is easy to set up as it has dip switches for the first 8 bits of the code like the device itself except the channel is not identified. The receiver supports all four channels so there is no need for the last two dip switches. I suggest using the four opto-isolated Inputs on the EZIO6I as these Inputs are the easiest to interface with. Connect the last two Analog possible Inputs to GND to keep stray signals from cycling the last two Inputs.

Jdsmooth The latest KeypadLinc with v.40 firmware supports a separate Controller turning Off Secondary KeypadLinc buttons with an On command. That is, a RemoteLinc can issue a Scene On command to turn one KeypadLinc button On and have that same Scene issue On commands to other Secondary KeypadLinc buttons set to 0% On Level and have those Secondary buttons turn Off. The same behavior achieved when pressing the buttons on the KeypadLinc itself. The v.40 firmware is the only KeypadLinc firmware with that capability. All earlier KeypadLinc firmware will not turn Off a Secondary button with an On command.

wswartz The problem of setting local on level and ramp rate is resolved in 3.2.4. The Program which changes to On Level to 30% at 1Am and back to 100% at Sunrise should work after upgrading to 3.2.4.

bcall It sounds like the PLM was reset. Try a File | Restore Modem (PLM) to rebuild the link database in the PLM. The problem with the local ramp rate and on level not changing is resolved with 3.2.4.

Jdsmooth You will need some new Scenes and new Programs. The operation of the KeypadLinc buttons when pressed locally is different from when driven from another Controller (RemoteLinc). For most KeypadLincs in the field an On command from another Controller cannot be used to turn Off a Secondary KeypadLinc button. This means additional Scenes are required with the various KeypadLinc button patterns so that a Program triggered by a RemoteLinc button press can issue a Set Scene xxxx Off that turns Off the unwanted Secondary KeypadLinc buttons.

The SwitchLinc local on level and local ramp rate can be set programmatically. A Program would be triggered at 1 AM which would set the local On Level to 30%. When the SwitchLinc is operated manually it will go to 30% without additional Program intervention. At Sunrise the same Program would be triggered and set the local On Level to 100% for day time operation. To do this define an ISY Scene with the SwitchLinc as a Controller or use an existing Scene if the SwitchLinc is already a Controller of a Scene. Use the Adjust Scene Action statement specifying the SwitchLinc node name in both Adjust Scene parameters. This combination sets the local value. In the Then clause the Adjust Scene would set the On Level to 30%. The Else clause would set the On Level to 100%. The only issue is that until the problem with setting Local values is fixed in a future beta this may not work without a power cycle of the SwitchLinc which is not practical for this scenario. I would wait for 3.2.4 beta to come out in the next few days to see if it fixes the local values problem. If so move to the above approach. It not fixed then set the On Level (applied locally) slider to 30%, power cycle the SwitchLinc and use a Program to set the SwitchLinc to 100% during the appropriate time range. If From 1:00:00AM To Sunrise (same day) Then In Scene 'SwitchLinc Dimmer' Set 'SwitchLinc Dimmer' 30% (On Level) Else In Scene 'SwitchLinc Dimmer' Set 'SwitchLinc Dimmer' 100% (On Level)

Does the Error Log show anything around the time My Devices is selected? The device list is being pulled with a REST call I believe. What happens if this is entered into a browser session? Change the IP address to match the ISY. http://192.168.2.2/rest/nodes

I believe there have been notify problems reported on 3.1.17. Beta 3.2.4 will be out in the next few days. Suggest moving to that beta when available.

What level was migrated from when the ISY was updated to 3.1.17? Do you have a backup from the that level? Does the Last Run Time information on the Summary screen change when the Run Then is selected? EDIT: take a look at the Error Log, is there anything logged at the time the front end is trying to access the device information. I suspect it is related to the configuration as well.

Yes I am sure it will be. May not be the next beta drop as that is due Monday/Tuesday time frame. The Local values can be set from the ISY at which point the air gap switch has to be pulled out for 30 seconds or so to power cycle the SwitchLinc. When it powers up the SwitchLinc will use the values previously stored by the ISY. I have tested on one of my SwitchLincs and another user has had success doing it this way.

The On command is telling the device to turn On to 0% On Level which effectively turns if Off or leaves it Off? How was the On command initiated? What ISY firmware is being used? Check the On Level (applied locally) slider. If set to 0% the On command will not work/

" do I need to upgrade to the IR in order to use IRLinc Receiver? " No. The ISY IR receive capability is independent of any other Insteon device including the two IRLinc devices.