GSpitale01

I am now on my 2nd whole home setup using this product: https://www.backstreet-surveillance.com I have a variety of the cameras depending on the location (front door, driveway, back yard, etc) and have been extremely happy with the entire system.

I have the Tempest - it's been operational for a year now and flawless. The app is awesome, the node server makes bringing data into ISY/eisy easy. And, I'll add that if you have a Rachio irrigation controller, it can directly use the Tempest feed for micro climate level controls.

I chose a "rolling average" method + hysteresis for this application. For exterior lights I trigger them on when $s.avg5.lux drops below 400, and off when it rises above 550. I have two sets of interior stairwell lights that I trigger similarly but with different on/off values that I chose to minimize unwanted on/off cycling. Main program: Lux avg count - [ID 000A][Parent 0001][Run At Startup] If $s.lux.enable is 1 Then Repeat Every 2 minutes $i.count.lux += 1 Run Program 'Lux1' (If) Wait 5 seconds $i.avg5.lux.temp += $i.lux1 $i.avg5.lux.temp += $i.lux2 $i.avg5.lux.temp += $i.lux3 $i.avg5.lux.temp += $i.lux4 $i.avg5.lux.temp += $i.lux5 $i.avg5.lux.temp /= 6 $i.avg5.lux = $i.avg5.lux.temp $s.avg5.lux = $i.avg5.lux.temp Else - No Actions - (To add one, press 'Action') Then there are 5 Lux programs that assign the sequential values used to store the individual contributing parameters used to calculate rolling average: Lux1 - [ID 000C][Parent 0001][Not Enabled] If $i.count.lux is 1 Then $i.lux1 = 'WeatherFlow / ST-00124605' Illumination lux Else Run Program 'Lux2' (If) Lux2 - [ID 000D][Parent 0001][Not Enabled] If $i.count.lux is 2 Then $i.lux2 = 'WeatherFlow / ST-00124605' Illumination lux Else Run Program 'Lux3' (If) Lux3 - [ID 000E][Parent 0001][Not Enabled] If $i.count.lux is 3 Then $i.lux3 = 'WeatherFlow / ST-00124605' Illumination lux Else Run Program 'Lux4' (If) Lux4 - [ID 000F][Parent 0001][Not Enabled] If $i.count.lux is 4 Then $i.lux4 = 'WeatherFlow / ST-00124605' Illumination lux Else Run Program 'Lux5' (Then Path) Lux5 - [ID 0010][Parent 0001][Not Enabled] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then $i.lux5 = 'WeatherFlow / ST-00124605' Illumination lux $i.count.lux = 0 Else - No Actions - (To add one, press 'Action')

The load is 3 outside coach lights. I have not seen an uncommanded on event since I did the factory reset this morning ... fingers crossed. I do have some noise issues - several UPS devices in the house. I'd forgotten about the FilterLinc devices until someone reminded me on here last week, so they're on order and will be installed in next day or so. Appreciate the assist here - so much knowledge in this forum!

@Techman Thank you, very helpful for understanding. This morning I did a factory reset on the device that was giving me random on trouble - we'll see if that fixes it. I usually like to understand "why" before I start trying fixes, but it this seems like a reasonable corrective action step to take.

General config info: - IoX v5.8.0 - UI v5.8.0 - PLM info says v9E - It is a new setup with a new PLM and eisy that was purchased within last 6 months - I have been an ISY994 user for more than 10 years so relatively familiar, but this issue is a new one for me Separating the two topics: 1. The random on that I'm trying to figure out is a 2477D dimmer. I do not know exactly how old it is, but I have purchased all of the devices in the last 4 years. It says v.45 in the admin console. This device is not a member of any scenes or activated or monitored by any programs. 2. The link discrepancy was present on ~10 of my devices. Some of them legacy Insteon and some the new I3 devices. The screenshot was an I3 4 button keypad.

I'm having an issue with random on events for one - only one - of my devices. My system is 52 instead devices, eisy, USB PLM. As part of my troubleshooting, I checked all my device links and compared to the ISY Links and found many errors. I started restoring the devices, and then rechecked some of them after about 30 minutes and found that the link discrepancies reappeared. Here's a screenshot of the comparison after I restored the device only a few minutes earlier. Is this normal?

I don't have any issues with commands not executing ... I have issues with un-commanded action with the IOLinc/2450 controlling the garage door. I do remember from my setup on a previous home, years ago, that I had to use FilterLinc devices on some of my noisy electronics to help with dropped commands - but have never seen this un-commanded action before.

I had completely forgotten about the filterlinc. I do have a bunch of UPS’s in the house, so certainly could be line noise. Appreciate the help and suggestions. I’ll do some troubleshooting this weekend.

@SMorgan apologies for hijacking your thread. @Techman I did read the INSTEON link and I don't have any of those circumstances. I am using the IO Linc as a garage door control/sensor, and had a bunch of random open/close events so am trying to hunt down potential causes. I'm aware of the security risks but want to figure out why the random events are happening.

Is there a known PLM "batch" that has this removed, or is there another way to update PLM firmware?

I'm interested in learning more about the 2450 behavior mentioned here, but my searches here don't return anything. Can you point me to any resources on this spontaneous activation?

I poll Tempest every 5 minutes and keep a rolling average of last 5 polls. Most of my brightness routines I trigger on the rolling average, but some things I might trigger on the instant poll. The thought above about setting up "zones" is interesting and might be future evolution for me.

My problem is that the sunrise/sunset times are displayed correctly, but the program schedule run times are off by an hour. Screenshots attached here - the stated sunset time of 4:52PM is correct, but the program scheduled run time is 6PM.

I'm on eisy v5.7.0, and have some light programs based on sunrise/sunset. After DST ended, the scheduled run times did not adjust to the standard times corresponding to sunrise/sunset. It seems to be still using the DST sunrise/sunset times. My time zone is correct, and the check box for Daylight Saving [US-Canada] is greyed out so I cannot uncheck it. Is this a bug, or a setting somewhere that I'm missing? Screenshots show the issue I'm having - the Front Porch Evening program is supposed to run at Sunset, eisy knows sunset is at 4:52PM, but the program shows a next scheduled run of 6PM.