LeeG

Button D is the Controller of ten Responders plus the PLM. The ISY is aware of all of these as the Compare results show "Identical". Are there more devices in the bathroom being controlled by button D than the ten listed Responders?

When Jumper 5 is in place the Motion Sensor options are set by software. Jumper 3 has no affect. Put the Motion Sensor into linking mode to keep it awake. Click the Motion Sensor - Sensor node and click the Options button. Insure the Night Mode: option is unchecked. Also the Dark Sensitivity: number controls how dark it has to get to be in Night Mode. The smaller the number the darker it has to be to enter Night Mode.

An ApplianceLinc cannot be used as it has no Controller function. That is, it does not send a message to the ISY/PLM when sense turns the ApplianceLinc On. The newer Insteon On/Off Module 2635-222 is a 2-prong replacement for the ApplianceLinc and it does have Controller capability. I'm not certain but I thought Smarthome no longer sells a SwitchLinc that has sense capability.

The newest ApplianceLinc equivalent (Insteon On/Off Module 2635-222) is a Dual Band device. The devices that carry the actual ApplianceLinc name are not Dual Band. The event trace shows poor powerline comm. Hops Left=1 is okay but the next command issued has a Hops Left=0 (as bad as it gets and still work). The fact that Hops Left=x count is changing from command to command indicates a unreliable comm problem is likely.

It should not have to be enabled. The ISY does not have a UI (Admin Console) option to Enable/Disable the Beep function on a LampLinc. My Dual Band LampLinc that beeps has firmware v.3B. What level firmware is in the LampLinc?

A working example of a Program the uses the Beep capability of a Dual Band LampLinc If Control 'MotionSensor2-Sensor' is switched On Then Repeat 5 times Set 'LampLinc DB' 100 (Beep Duration) Else - No Actions - (To add one, press 'Action') Note that none of the existing devices support the duration aspects of the Beep command. Some day SmartLabs may release a device that honors "duration" but for now the duration of the Beep is fixed by the device itself.

Run Tools | Diagnostics | Event Viewer at LEVEL 3. Trace adding the RemoteLinc2 to the ISY. The only way the RL2 should have timed out would be comm issues where some of the commands fail to reach the device or the ACK does not make it back to the PLM. If there is a gap in time where the ISY is waiting 9 seconds (the 9 seconds is from memory) between commands because the RL2 did not ACK a command, the RL2 could time out after the 4 minute default timeout has expired.

When the alarm condition was reset the Program was triggered again because of the change in I/O Linc Sensor Status in combination with the Wait. Whenever a Wait or Repeat is executed the Program can be retriggered when Status changes. The If is now False driving the Else so the statement(s) after the Wait are not executed. One solution is to split the Program into two Programs. The first Program with the If section invokes Program Two which has the Wait. That way when Program one is triggered with a False evaluation because the Sensor Status changes it cannot interrupt the Wait in Program two.

When the roof is leaking a bucket can be used to catch the water or the leak can be fixed. The Program to correct the status is a bucket. There is clearly a communications problem when that many direct commands fail. Direct commands are automatically retried multiple times so a failure indicates multiple attempts have failed.

ApplianceLincs do not report local status changes. Do not know what the comm issue is but it is unrelated to an ApplianceLinc not reporting local status changes. The newest Insteon On/Off Module 2635-222 (ApplianceLinc replacement) does report local state changes.

Run Show Device Links Table on the KeypadLinc followed by a Compare when the link record display completes. Post the popup with the Compare results. To restate the circumstances from a different perspective, an ISY Scene definition exists with various bathroom devices as Responders. The KeypadLinc button D was a Controller of the Scene at some point in the past but is no longer shown as a Controller of the ISY Scene. Is this correct? Is the Scene definition correct except for button D no longer listed as Controller?

Are other devices being updated at the same time? In theory a device should not timeout as long as the reads or writes to the device continue. It sounds like other devices are being updated at the same time allowing a gap between reads/writes to the RemoteLinc2 allowing it to timeout.

I believe the v.35 firmware has a problem that interferred with powerline comm. Michel will have to validate that as I have not have any with the v.35 firmware.

If I remember right this is a new SwitchLinc. v.35 is an older firmware that has been replaced/updated several times. Michel's question was related to if there are v.35 SwitchLincs installed which might explain the intermittent comm issues. A new SwitchLinc firmware will be in the v.4x range or higher. The rev 5.4 on the paper sticker is the device hardware revision.

The three KPLs are Controllers of the same ISY Scene with the I/O Linc Relay as Responder? If that is the case click on the KPL node name below the ISY Scene name (the one that works) and look at the I/O Linc Relay On Level. Do not change it for the KPL button that is working. Click on one of the other KPL node names below the ISY Scene name (one that is not working) and check the I/O Linc Relay On Level. It may be different than the KPL button that is working. If different change it to the same On Level as the KPL button that is working.

v.35 is the device firmware level. It is listed on line 2 after the device type, on the right side of the node display.

"Run File | Restore Modem (PLM) to rebuild the PLM link database. Then repeat the manual switch test." From my earlier post. When multiple devices stop reporting particularly after dealing with the Start Linking it looks like the PLM has lost some of its link records. These link records are required for the PLM to recognize the paddle/button press on the device.

Run Tools | Diagnostics | Event Viewer at LEVEL 3. Use the paddle to turn a switch On and Off. Post the event trace and the Program that should trigger.

Bring up the Admin Console and watch the Current State column for the switch as the switch is manually operated (not thru Admin Console). If the Admin Console is not showing the On/Off state changes in real time the PLM was likely reset during the efforts to clear the Start Linking. Run File | Restore Modem (PLM) to rebuild the PLM link database. Then repeat the manual switch test.

Start Linking puts the PLM into linking mode for 4 minutes unless Finish button is clicked. It sounds like the Finish button was not clicked and the PLM was not left powered Off long enough. Also the ISY would require a reboot to get out of Start Linking mode. Is it the Programs that are triggered by device activity or based on Time that are not being triggered?

It sounds like the RF coverage is not the same at the new house Run Tools | Diagnostics | Event Viewer at LEVEL 3. Add the RemoteLinc2 to the ISY (attempt to). Post the event trace. It will show if any of the commands sent to the RL2 are being answered.

Where was the ISY and PLM obtained? Try another cable between the PLM and the ISY. The ISY will have to be rebooted after the installing the new PLM cable. The RX LED On steady indicates the ISY cannot communicate with the PLM. The ISY enters Safe Mode when this occurs. The various symptoms noted before are the result of not being able to communicate with the PLM. Once PLM communication is established those symptoms should no longer exist.

Safe Mode usually indicates the PLM cannot be accessed. What ISY front panel LEDs are On? The ISY is not functional without a working PLM.

As for the KPLs I suggest opening a ticket with UDI. It sounds like the combination of 3.3.10/4.0.11 will not help. However, UDI should comment on the combination and support for the Dual Band KeypadLinc. The RemoteLinc2 (Mini Remote) is supported under 3.3.10 so I would expect that to work. What is the symptom? "Additionally, now I tried to add a remotelinc2 and its not recognized at all..." The Insteon address is not recognized? The device type is not recognized? The Set button is not recognized? (cannot use Set button to add RL2)

Turning an ISY Scene On and/or Off is a single Insteon message. No ACKs, no retries. There is no load on the Insteon Mesh Network associated with 2 devices versus 20 devices. That many loads turning Off all at the same time may be an issue from an electrical load perspective. Might pay to turn each floor off separately.