LeeG

What does Help | About show for Firmware and UI levels? I use Google Chrome for every ISY image for the last year or two with no problems. Now running 4.2 30. What level of OS and Java is being used?

The ON/OFF buttons use the same node. Pressing the ON button sends an On command to node 1, pressing the OFF button sends an Off command to node 1.

I do not see your approach not being viable (except maybe for the newest Mini Remote. Just that Auto Discover provides more information and may be required for the latest Mini Remote where the ISY must know the Mini Remote firmware so the correct Insteon commands are used.

oberkc Selecting the specific device type through the Link Management options invokes "New INSTEON Device" with the Device Type pre selected. If Link Management | New INSTEON Device is selected the same New INSTEON Device popup is displayed with the Device Type set to Auto Discover. Most devices no longer need a specific Device Type specified. Auto Discover uses the Device Type and device firmware information provided by the device. Auto Discover normally displays the device firmware in the device definition. The TriggerLinc firmware level v28 is displayed because TriggerLinc added using Auto Discover

First, Backlight does not turn On/Off a Keypad button. Backlight defines all the buttons intensity, not just the button identified in the Program. If Backlight affected a single button it might be impossible to know which button was On and which button was Off because the Off level of one button could be the same as the On level of another button. Is the ISY Scene definition Scene xxxx Parking Stall Light Sw Red Controller Parking Motion 5 -Sensor Red Controller Parking stall light KP B Red Controller If Insteon comm is good a separate Program may not be necessary to manage Keypad button but that depends on whether the motion sensor is/should also turning the Scene Off and should the motion sensor turn the Parking Stall Light Sw Off. Need more info as to what action the motion sensor should take regarding turning Stall Light Off

From the MorningLinc sales page Important Note Regarding Lock Status: The MorningLinc converts INSTEON commands to Morning Industry's RF commands. Since this RF is one-way, an INSTEON system cannot confirm whether the lock has received the RF command or not. Please exercise your best judgment when remotely controlling or automating door locks.

The MorningLinc should have multiple link records. Also note my EDIT in previous post. The MorningLinc does not send messages to the ISY when the Set button is pressed, regardless of missing link records. - <isy.diag> <title>ISY Links Table : MorningLinc 2-On / 18 EC F 1</title> - <insteon.lincs> - <eventInfo> <ix>0</ix> <ad>4088</ad> <fl>162</fl> <gr>0</gr> <id>2261003</id> <data>16711680</data> </eventInfo> - <eventInfo> <ix>1</ix> <ad>4080</ad> <fl>162</fl> <gr>0</gr> <id>2261003</id> <data>16711681</data> </eventInfo> - <eventInfo> <ix>2</ix> <ad>4072</ad> <fl>0</fl> <gr>0</gr> <id>0</id> <data>0</data> </eventInfo> </insteon.lincs> </isy.diag

Right click the MorningLinc On node, select Diagnostics | Show Device Links Table. Post the link records. EDIT: the Set button does not send a signal to the ISY with my MorningLinc.

The MorningLinc has special link requirements because of what it controls. Follow the procedure in the Wiki for linking a MorningLinc http://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Linking_a_MorningLinc

Try running the Admin Console for 4.2.18 so your ISY firmware level matches the Admin Console. Not sure 4.2.30 Admin Console is compatible with 4.2.18 ISY. The Internet Disabled simply means the File | Enable Internet Access has not been used. It does not mean the router has not been set up for ISY remote access which is the preferred method.

Not owned by Smarthome, SmartLabs, nor UDI. Owned by InsteonNut, a third party. See the Mobilinc forum topic under Third Party Products

It depends on the firmware level. My two v.40 Open/Close Sensors have a Heartbeat node. They also have an external Set button. The v.28 firmware does not have a Heartbeat and the Set button is internal.

doctorjerry That is normal. At v.40 there should be three nodes, Opened/Closed/Heartbeat

I suspect there is another variable in play. That is why the event trace is important. The event viewer is not meant to run 24/7. Would be a good idea to end trace and restart the Admin Console each evening.

The link table is not helpful. All the buttons point to the PLM, as they should, with no additional links to other devices. That does not mean the InlineLinc cannot respond. If it has a Responder link for the KPL the InlineLinc will react to the initial Group Broadcast message from the KPL which has no specific device address. The Group Broadcast message is not ACKed by the Responders so there is no means of tracking the InlineLinc address.

If you can post the old KPL link table and the button that is controlling the InLineLinc I may be able to identify the Insteon address. The KPL could have part of a link (the Group Broadcast without the Group Cleanup Direct) so it may not be possible. If the full link is there it should be possible.

The switch must be a Red Controller in a Scene to appear in the In Scene devices. Only devices that have been defined as Red Controllers in a Scene are in the In Scene list.

The Controllers devices are listed before the Scene names

The Smoke Bridge does not need to be paired with a Smoke Alarm to be able to add the Smoke Bridge to the ISY. Also only one Smoke Alarm needs to linked to the Smoke Bridge. With all the Smoke Alarms linked they all alert so only one needs to trigger the Smoke Bridge. Use New INSTEON Device. Enter the Smoke Bridge Insteon address and Name of choice. Device Type remains at default Auto Discover and remove existing links. Explain the details of the symptom and what ISY firmware and UI is being used. The UI should be at the same level as the ISY firmware.

The Scene name should not be the same as the device name Scene xxxx Controller device name yyyy of SwitchLinc In Scene 'yyyy' Set 'yyyy' must be coded this way for In Scene to change Local On Level of yyyy When the first parameter is a Scene name the Responder link record is changed rather than the Local On Level. "My garage door sensor, my mini remotes and my 8 button keypad." None of those devices have a Local On Level expect the Keypad load control button.

The "In Scene" does not turn On/Off the SwitchLinc. It sets the Local On Level for when the paddle is pressed On. The In Scene Program has to be saved and Enabled at the From time, otherwise the Program is not triggered. What is 'Bedroom Lights'?

Something like If Control 'motion1 is switched Off And Control 'motion2' is switched Off does not work. If Control is True only for when the Off message is received. You cannot have two Off messages at the same time. Use If Status If Status 'motion1' is Off And Status 'motion2' is Off I prefer to use ISY Programming to handle the Off processing. If Control 'motion1' is switched On Or Control 'motion2' is switched On Then Wait ?? minutes Set Scene 'motion responders' Off Else The Set Scene Off will execute only when neither motion sensor has switched On for ?? minutes of your choosing. Just personal choice. It can be done multiple ways.

Need to see an Event Trace at LEVEL 3 with the Fan On and the Program is invoked.

As oberkc indicated OnLevelChange1 - [iD 0087][Parent 0001] If From 10:00:00PM To 9:00:00AM (next day) Then In Scene 'SwitchLinc Dimmer' Set 'SwitchLinc Dimmer' 5% (On Level) Else In Scene 'SwitchLinc Dimmer' Set 'SwitchLinc Dimmer' 100% (On Level)

There should be 3 nodes name - Sensor name - Low Bat name - Dusk.Dawn Right click any of the three nodes and select Group Devices to bring all three nodes together. Low Bat will turn On when the Battery is low.