Lights go on and go on dim for no reason!

[rlanza1054]

Hi, 

I have had this problem for more than a year and was too lazy to ask for help.

I have a insteon wall dimmer and it gets triggered via two motion sensors. 

This is two hallway lights on the same Insteon wall dimmer switch. 

The reason for two motion sensors is that my hallway has some twists and turns. So there is a motion sensor near the hallway in the foyer.  So as you walk into the hallway it turns on. The other motion sensor is near my bedroom so that the hallway lights go on when I come out of my bedroom. The two motion sensors are not in visible range of each other. 

When I first setup everything I had these hallway lights,  I set them for 100% brightness. However, between the hours of 1am to 7am I would have the ramp rate set to 5 seconds and the brightness to only 20%. The dimmest it can go. 

It worked for a year or so. Then it stopped working. But I noticed that it was getting dim between 1pm - 7pm. 

When I realized what happened I checked the ISY and noticed that the clock was wrong. 

At least I think that was wrong. 

I also noticed that my program that triggers the dimming at night had an PM in the field it should have been AM. 

I fixed it thinking that would fix the problem. 

It did not. It still dims in the afternoon and not at night. 

I even disabled the program. 

And it still does it. 

I think I did reset the dimmer & motion sensors to defaults and reinstalled them. 

Still does it. 

So my question is this (and I haven't tried this yet) can the PLM itself be storing this info? Does the PLM itself have a clock chip inside. 

I wantes to set the PLM to factory defaults and then restore from backup. And do I even bother restoring from backup? Just the PLM? 

Thanks

Rob

[lilyoyo1]

The plm does not have an internal timer built into it so most likely there is an errant program somewhere.

I would also check the scene itself to ensure that you don't have one of the sensors set to turn the lights to the lower setting

[paulbates]

Agreed its likely a program. An additional thing you can do is wait for it to happen, and then go to the admin console, programs tab and then summary tab. Click the "Last Run Time" column heading twice so the arrow is pointing down. The list will show the most recently run programs at the top. If a program is doing this, it will have run recently and be near the top of the list.. look at those first as culprits.

Paul