LeeG

Turning devices On/Off with the Admin Console does not use link records. Has the PLM been replaced lately. Short of a defective PLM the only way I know to have an empty PLM link database after a Restore Modem (PLM) is to have Deleted the PLM during the install of a new PLM. Or to have accidently clicked Delete Modem

This is the Controller link in the Micro Dimmer. It is half of what is required for the ISY/PLM to be aware the Sense line has been cycled from Off to On. 3 : 0FE0 : E2 01 1F.21.A9 FF 1F 01 Either the PLM is missing the Responder link or the Micro Dimmer does not have communication with the PLM. The PLM could be full. A Show PLM Links Table followed by Count will provide the count of link records in the PLM. The challenge is any Insteon traffic reaching the PLM during the Show PLM Links Table will produce a false/high low link record count. The Show followed by Count has to be run 3-4 times, each producing the same link record count before the count can be considered accurate. The alternative would be to Restore PLM (Modem) on the assumption the PLM is full.

The Event Trace is running at LEVEL 3. Applying 120v to the Sense line turns the Dimmer On but the event viewer does not trace any traffic? If that is true post the Show Device Links Table output.

The KeypadLinc User Guide is a good source for functional information. Around Page 11 discusses Toggle/non-toggle mode. Around page 15 discusses Button Groups. Page numbers may vary a little depending on whether Dimmer/Relay/Dual Band User Guide

All battery powered RF only devices have the same requirement. Motion Sensor, On/Off Sensor (TriggerLinc), RemoteLinc, RemoteLinc2, 2441ZTH thermostat, all must be put into linking mode so that they stay awake for approx 4 minutes. Otherwise the device is asleep to save battery life and cannot respond to commands.

The default mode of a KeypadLinc button is Toggle mode. Press a KPL button and it sends an On command, press it again and it sends an Off command, press it again it sends an On command, and so on. The KPL button toggles between On and Off commands. There are two non-toggle modes, non-toggle On and non-toggle Off. In non-toggle On mode each KPL button press sends an On command. In non-toggle Off mode each KPL button press sends an Off command.

I'll have to put an OutletLinc Relay on the test bed to verify but I suspect the OutletLinc Relay does not respond to dim/bright. I thought some Relay devices responded to bright by turning On but dim is problematic. Should any dim (not fully off) turn the Relay Off. I'll post back later tonight after testing an OutletLinc Relay.

"Buttons Grouping" button along bottom of Admin Console should not be used. If clicked there is a warning displayed that the function should not be used. Scenes are now used to accomplish what Buttons Grouping did in the past. "Buttons Toggle Mode" button supports setting the toggle/non-toggle mode of individual KeypadLinc buttons.

Please provide detail as to what is not working as expected. KPL button On/Off does or does not turn OutletLinc On/Off, dim/bright does not affect OutletLinc, etc. I would expect KPL button On/Off to correctly control OutletLinc Relay On/Off. Not sure about dim/bright. Will have to test that. Not all devices react to dim/bright.

When the Show Device Links Table completes the Compare button will be enabled (no longer grayed). Click Compare which compares the link information the ISY has stored internally against the information retrieved from the device. The Compare results with indicate link records that match, do not match. The very last record which starts with a 00 may be labeled a mismatch. So long as the last record both from the device and expected link record start with 00 that mismatch is okay.

A link count of 243 is pretty low. How many devices are installed? Xathros makes a good point. Any Insteon traffic reaching the PLM during the Show PLM Links Table will produce a false high/low count. Suggest running a Restore Modem (PLM) and see if that restores the devices that are not sending status changes. If that does not resolve the situation run a Show Device Links Table against a device that is not reporting status change and do a Compare to see if any link records are missing from the device. When multiple devices fail to report it is usually the PLM link table in question because it can affect multiple devices. Not every Insteon device is capable of reporting local status changes. OutletLinc Relay, ApplianceLinc are the first two that come to mind. There are others that are Responder Only devices. Also communication problems can prevent state changes from reaching the PLM.

I have a v.41 8 button. A value of 01 produces the dimmest LED backlight On level. A value of 00 is brighter than 01. From 01 each increment (02,03,04,05,etc) produces a slightly brighter LED backlight On level. I assume the different between the large ON/OFF buttons and the smaller A-D Secondary buttons is the mass of the button rather than the underlying LED itself. Pull the buttons and look at the LEDs directly. I'm running 4.0.2.

KeypadLinc Secondary button LEDs can be controlled but only through a Scene. Define an ISY Scene, assign KPL button D as a Responder. An ISY Program can track the status change of whatever devices you want to control button D. When conditions have been reached, have the Program turn the ISY Scene Off containing KPL button D.

gwarthur My apologies, I only read the "Configure INSTEON Settings" "Make Micro Module a Controller" headings without reading the detail that was only doing a Set/Switch button link which obviously was not configuring the device. FYI, when you change the text in an existing post I do not get notified of the text change. It was not until this morning that I read the new post text and looked at the User Guide detail description. Luckily Michel and others corrected my query that it is not necessary to configure the 2443 for it to function as a Controller.

I don't have one of these yet but according to the User Guide it has to be configured to function as a Controller. Was this done?

Unfortunately there is nothing to be learned from the last event trace. When the ISY issues a Scene On/Off/Fast On/Fast Off that is all that is traced as far as actual commands issued. The ISY Scene xxx does not receive anything from the Scene responders so the event trace when the device was not acting correctly and after it was power cycled looks exactly the same. Unless there is something with the load the LampLinc is driving the LampLinc is defective.

Just some FYI, the initial trace in the first post shows the device was not responding to any command. There is a Fast Off/Fast On/multiple Queries, none of which got a response from the device. The 02 62 messages are outbound to the device. There should be an 02 5x inbound response from the device for each command. Don't know why the device was not responding at the time but that may have prompted playing with the sliders. Thu 04/04/2013 05:02:47 PM : [iNST-TX-I1 ] 02 62 1A E0 21 0F 14 00 Thu 04/04/2013 05:02:47 PM : [iNST-ACK ] 02 62 1A.E0.21 0F 14 00 06 LTOFF-F(00) Thu 04/04/2013 05:02:51 PM : [ 1A E0 21 1] ERR 1 Thu 04/04/2013 05:02:57 PM : [iNST-TX-I1 ] 02 62 1A E0 21 0F 12 00 Thu 04/04/2013 05:02:57 PM : [iNST-ACK ] 02 62 1A.E0.21 0F 12 00 06 LTON-F (00) Thu 04/04/2013 05:03:09 PM : [iNST-TX-I1 ] 02 62 1A E0 21 0F 19 00 Thu 04/04/2013 05:03:09 PM : [iNST-ACK ] 02 62 1A.E0.21 0F 19 00 06 LTSREQ (LIGHT) Thu 04/04/2013 05:03:18 PM : [iNST-TX-I1 ] 02 62 1A E0 21 0F 19 00 Thu 04/04/2013 05:03:18 PM : [iNST-ACK ] 02 62 1A.E0.21 0F 19 00 06 LTSREQ (LIGHT) Thu 04/04/2013 05:03:27 PM : [iNST-TX-I1 ] 02 62 1A E0 21 0F 19 00 Thu 04/04/2013 05:03:27 PM : [iNST-ACK ] 02 62 1A.E0.21 0F 19 00 06 LTSREQ (LIGHT)

I just read the post you did as I was posting mine. Are you moving the On Level slider? Moving it fully left is setting the On Level to 0% On Level which turns the device Off with an On command

Check the 'On Level (applied locally)' slider for device 1A.E0.21 The On command is directing the device to turn On to 0% On Level which is effectively turning the device Off Thu 04/04/2013 05:23:06 PM : [iNST-TX-I1 ] 02 62 1A E0 21 0F 11 00 Thu 04/04/2013 05:23:06 PM : [iNST-ACK ] 02 62 1A.E0.21 0F 11 00 06 LTONRR (00) Thu 04/04/2013 05:23:06 PM : [iNST-SRX ] 02 50 1A.E0.21 1E.80.B1 2B 11 00 LTONRR (00) Thu 04/04/2013 05:23:06 PM : [std-Direct Ack] 1A.E0.21-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 What ISY firmware is being used? Check Help | About and verify Firmware line and UI line have the same level.

Have not seen the symptom posted on the forum before that I remember. Please post back if it happens again.

The individual Responder On Levels live in each Responder device. Using the Adjust Scene is the technique for changing those values. A few points, it is not necessary to set the On Level to 100% to perform the Scene Off. A Scene Off command turns the devices Off regardless of the defined Responder On Level. Putting them back to 100% is of course necessary if the Scene should turn the devices On to 100%. There is no Insteon command that overrides the Responder On Levels on a Scene command basis. Adjusting the Responder On Levels is the way it is done. Could have a seperate set of Scenes, on that has 100% On Level and one that has 25% On Level and simply use one set of Scenes or the other.

Any recent upgrade of the ISY firmware or upgrade of Java? Click Help | About and insure both the Firmware and UI lines indicate the same level. What ISY firmware level is being used?

Thanks for the trace data. Check the On Level (applied locally) sliders for the two devices in the trace. The traced On commands from the Admin Console have an On Level of 0% which has the effect of turning the devices Off Wed 04/03/2013 11:50:41 PM : [iNST-TX-I1 ] 02 62 1A F2 21 0F 11 00 Wed 04/03/2013 11:50:41 PM : [iNST-ACK ] 02 62 1A.F2.21 0F 11 00 06 LTONRR (00) Wed 04/03/2013 11:50:41 PM : [iNST-SRX ] 02 50 1A.F2.21 21.31.E3 2B 11 00 LTONRR (00) Wed 04/03/2013 11:50:41 PM : [std-Direct Ack] 1A.F2.21-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Wed 04/03/2013 11:50:47 PM : [iNST-TX-I1 ] 02 62 21 8B 28 0F 11 00 Wed 04/03/2013 11:50:47 PM : [iNST-ACK ] 02 62 21.8B.28 0F 11 00 06 LTONRR (00) Wed 04/03/2013 11:50:48 PM : [iNST-SRX ] 02 50 21.8B.28 21.31.E3 2B 11 00 LTONRR (00)

The LampLinc responds to an On (100% On) from an ISY Program but does not respond to an On from the Admin Console? Run Tools | Diagnostics | Event Viewer at LEVEL 3. Run the ISY Program that turns the LampLinc On and issue an On from the Admin Console. Post the event trace.

Sorry you are having problems. The RX light on steady is an indication the ISY is not able to communicate with the PLM. Things to check, insure the PLM is not plugged into the Ethernet connection, insure the cable between the ISY Port A and the PLM is firmly seated (plugs click when inserted). How long is the cable run between the ISY and the PLM? Is the LED on the side of the PLM On?