Need Help or Advice / About to go bald from hair pulling.

[Melor]

This weekend was to be the weekend I was going to fix/update my ISY99 setup. Originally, I had it set up exactly to my liking. Timed events, occupancy sensors, rotating scenes on a button push, etc. Was cool. An update to the firmware ( at least a year ago ) appeared to kill the rotating scenes, but I accepted as everything else worked. Then my other scene buttons seemed to die, but as long as my lights came on and off when I wanted, I accepted.

 

A week ago, my lights stopped coming on and off when I wanted rendering the most important single feature unavailable. I logged on to my ISY and found an error msg that my PLM died. Replace, restored modem, restored devices. I can control the switches from the ISY panel, but I cannot seem to get a single scene to work. When I visit the scene, for example in the following images, the desire is to have all the lights at 100%. They are at 0% and when I set the light to be at 100% I get the error shown in the second image.

 

Any help would be appreciated.

 

Paul

 

 

 

[LeeG]

Melor

 

Under Tools| Diagnostics | PLM Info does it show the correct Insteon address for the PLM and indicate Connected?

 

What ISY firmware are you running?

 

Run Tools | Diagnostics | Event Viewer with Device communications events selected (most important option). Make a change to one of the Responder On Level values to 100% and post the Event Viewer trace file.

 

Lee

[Melor]

Melor

 

Under Tools| Diagnostics | PLM Info does it show the correct Insteon address for the PLM and indicate Connected?

 

What ISY firmware are you running?

 

Run Tools | Diagnostics | Event Viewer with Device communications events selected (most important option). Make a change to one of the Responder On Level values to 100% and post the Event Viewer trace file.

 

Lee

 

First, THANK YOU.

 

PLM INFO from console: 19.72.37 v98 / Connected

This matches my PLM

 

Sun 11/06/2011 02:33:45 PM : [iNST-ACK ] 02 62 08.3D.87 0F 11 FF 06 LTONRR (FF)

 

Sun 11/06/2011 02:33:45 PM : [All ] Writing 0 bytes to devices

 

Sun 11/06/2011 02:33:46 PM : [iNST-SRX ] 02 50 08.3D.87 19.72.37 27 11 FF LTONRR (FF)

 

Sun 11/06/2011 02:33:46 PM : [standard-Direct Ack][08.3D.87-->ISY/PLM Group=0] Max Hops=3, Hops Left=1

 

Sun 11/06/2011 02:33:46 PM : [ 8 3D 87 1] ST 255

 

Sun 11/06/2011 02:34:00 PM : [ Time] 14:34:07 0(0)

 

Sun 11/06/2011 02:34:00 PM : [iNST-ACK ] 02 62 00.00.1D CF 14 00 06 LTOFF-F(00)

 

Sun 11/06/2011 02:34:00 PM : [ 8 3D 87 1] ST 0

 

Sun 11/06/2011 02:34:01 PM : [iNST-ACK ] 02 62 00.00.18 CF 14 00 06 LTOFF-F(00)

 

Sun 11/06/2011 02:34:01 PM : [iNST-ACK ] 02 62 00.00.1E CF 14 00 06 LTOFF-F(00)

 

Sun 11/06/2011 02:34:02 PM : [iNST-ACK ] 02 62 00.00.1A CF 13 00 06 LTOFFRR(00)

 

Thanks again.

 

Paul

 

 

EDIT

 

Forgot to post ISY firmware version: 2.8.16

[LeeG]

It turned the device On successfully (08.3D.87) so the PLM is working but made no attempt to write a new Responder On Level to the device link database. Try setting an On Level to 50% and see if that takes. Turn the Scene On/Off after changing to 50% and the progress bar and system status in lower left corner shows Ready. Despite what the Admin Console is showing it looks like it thinks the Responder On Level is already 100%.

 

If changing to 50% does not work try deleting the device from the Scene and adding it back.

[Melor]

Here are the results of 50%

 

Sun 11/06/2011 02:48:16 PM : [iNST-ACK ] 02 62 08.3D.87 0F 11 82 06 LTONRR (82)

 

Sun 11/06/2011 02:48:16 PM : [All ] Writing 0 bytes to devices

 

Sun 11/06/2011 02:48:16 PM : [iNST-SRX ] 02 50 08.3D.87 19.72.37 23 11 82 LTONRR (82)

 

Sun 11/06/2011 02:48:16 PM : [standard-Direct Ack][08.3D.87-->ISY/PLM Group=0] Max Hops=3, Hops Left=0

 

Sun 11/06/2011 02:48:16 PM : [ 8 3D 87 1] ST 130

 

Sun 11/06/2011 02:48:31 PM : [iNST-ACK ] 02 62 00.00.1D CF 14 00 06 LTOFF-F(00)

 

Sun 11/06/2011 02:48:32 PM : [ 8 3D 87 1] ST 0

 

Sun 11/06/2011 02:48:32 PM : [iNST-ACK ] 02 62 00.00.18 CF 14 00 06 LTOFF-F(00)

 

Sun 11/06/2011 02:48:32 PM : [iNST-ACK ] 02 62 00.00.1E CF 14 00 06 LTOFF-F(00)

 

Sun 11/06/2011 02:48:33 PM : [iNST-ACK ] 02 62 00.00.1A CF 13 00 06 LTOFFRR(00)

 

It did not take. Will remove device from scene and add it back in and report results in a minute or two...

 

Thanks again.

 

Paul

[LeeG]

You are changing the Scene Responder On Level and not the individual device node further up the My Lighting tree. The change to 50% did not change the device link database. There is a Scene being triggered that is setting some devices Off with a Fast Off. Is a Program being triggered by the device On Level change? If so disable that Program for now until the Responder link record not being updated is resolved.

[Melor]

I have been busy removing the devices from each scene and reinserting. Has been working like a champ. Found you can control click and add a bunch at a time...

 

Thanks a lot for your help, I do appreciate it.

 

Paul

[Melor]

I have been busy removing the devices from each scene and reinserting. Has been working like a champ. Found you can control click and add a bunch at a time...

 

Thanks a lot for your help, I do appreciate it.

 

Paul

[Melor]

There is still some odd behavior with some of my programs and I will be debugging them as I go along, but the timers that control my exterior lighting seem to be working well. I know there are other scenes that need the delete and restore treatment, and I have yet to go through all of them. Is it possible that there is a refresh function of the ISY software that I am not aware of that will prevent the need to go through each scene? Thanks.

 

Paul

[LeeG]

It should not have been necessary to do the device delete/add for each Scene. Don't know if the issue was the result of the failed PLM itself or something during the adding of the new PLM that resulted in the lost device control at the Scene level. The Restore Device normally resolves any link record issues but you indicated that had been done.

 

I know of nothing else other than what you are deing at present.

[Melor]

I am running a restore device command again in case I did that before I restored the PLM. Afterwords, I will check the other scenes and see what happens. Next on my debug ritual will be to figure out why some of my programs are not running during a KPL button press.

 

Thanks a lot for the hand-holding. In 2008 or so when I installed my ISY, I played around a bunch, but having the system run without modification/inspection for a few years has caused me to basically start over again with figuring out how it all works.

 

Paul

[LeeG]

Melor

 

When a Program does not trigger from a paddle/button press that can mean a different variant of a link record problem. Run Tools | Diagnostics | Event Viewer with Device communication events selected (most important option) and see if the button/paddle press results in Insteon messages being traced.

 

If not either a Controller link record in the device pointing to the PLM is missing or the PLM Responder link record pointing to the Controller is missing. If this is the case something unusual happened during the PLM replacement process that corrupted the link records. A Restore Device normally resolves this but if not the only solution to basic device link records missing/corrupted (not Scene related links) is to Delete the device and add it back to the ISY. These link records were created when the device was originally added to the ISY and if Restore Device does not fix it a device Delete/Add sequence in the next solution.

 

Lee

[Melor]

I just restored all devices and still have the same problem with the scenes where I havent deleted the device and re-added. I am going through my scenes. Once this is done, I will tackle the keypress not activating programs as desired.

 

Somewhere along this path, I want to update to the latest beta firmware as I bought one of the wireless 8 button controllers and I understand only the latest betas will respond or be able to be programmed to work with that device.

 

Paul

[LeeG]

The support for RemoteLinc 2 devices was added at 3.1.10.