haroldunger

Are you running any Insteon I3Dial switches? If so, update to the latest UD release.

Since everything seems to be working properly and the log shows minimal errors, I'm back to trying some programming to turn on certain lights at sunset +"x' random minutes or +/-6pm +"x' random minutes if sunset is later (spring/summer) and visa versa if sunset is earlier (fall/winter) following dbwarner5 examples. Tonight will tell the tale.

Problem resolved with the latest UD release...no more crashes.

Unfortunately, still not back. We haven't yet resolved the crash problems. Please stay tuned or add comments if anyone has any ideas. We've been working with Michel. We've ruled out Verizon Fios because we've placed a Dream Wall between the Verizon modem and the entire system and it shows that Fios has not gone down. We're not giving up!

Oh, one good thing came out of this frustration. Most of the bulbs I had tried had some flicker when running at <100% brightness or a periodic "flick" when running at 100% brightness. I was about to install capacitators sold by Insteon to maintain a constant load on the switch, and, theoritcally, solve the problem. But, at the last moment, I was pointed to Murray Feit BR30 bulbs with variable Kelvin temperatures (switch on the bulb) and different flood diameters on the PAR30 bulb (again a switch on the bulb). They worked - essentially no flicker/flick and smooth 10%-100% brightening. Yippee!!!!

Still troubleshooting... According to Verizon, it might not be the PLM, nor the EISY, nor my programming. It might be that the Verizon FIOS "channel" is not through putting a clean strong signal to my home due to congestion. So Verizon switched my channel to a less used one that was supposed to cure the numerous issues. Waiting to see if they are correct... BTW, Michel and his team have been wonderful trying to help me track down the problem. It has been nothing short of frustrating for all of us. So, please stay tuned. Once I'm back, I'll start testing the program that was the reason for starting this entire string.

Sorry for not yet responding... Having been having a major issue with a new PLM that is failing - just replaced it. Will get back to working with the lighting programs shortly. Thx again.

Got it. Thx.

Big meal to digest here... Please give me a bit of time to understand what you have done. Thank you very much.

Okay and thx. I’ll reread ur email many times and try to create a program for a progressively brighter light that doesn’t all of a sudden go to/-100% from 60%, or so.

Ty! I’ll give it a go and will report back. BTW, ur roadmap is very impressive.

If I turn off the light during this period, the program will turn it on again. I could try fade up, but there doesn't seem to be a max level and time frame for this option - I don't want 100%. Thanks.

I have several different programs that turn on lights at various hours and at different levels. If I happen to have one of these lights turned on before the program executes, then it will change the light level to that indicated by the program. I've tried writing several programs to disable the program if the light is already on, but I have been unsuccessful. I would appreciate help in creating a program script that would avoid this issue. Thanks.

I had a similar loop problem. To attempt a fix, I unplugged the eisy and PLM from 110v, then - in order - plugged the eisy into 110v and then (20 seconds later) did the same for the PLM. The program was still in a loop. So, for no reason at all, I decided to add an Insteon device and see what would happen. For some reason, that immediately stopped the loop. Didn't actually add the device and don't know why this stopped the loop... Oh, the program also advised me to upgrade to 5.8.4.1. That's another story and it created issues.

Many of my scenes have on and off commands in just one program. However, I can see dividing the on and off functions into two programs. I do have a program that turns off everything at 2:30am.