larryllix

It is not removable. Not sure why but it is the basis of some commercial systems apparently, related to TOU (time of use) metering and energy conservation.

The original name of the scene wasn't "Auto DR" was it?

So how many times did you turn his TV on at 2:00 AM? How did his wife like the porn?

I watched at nights to see who had some light flashing on and off for a few weeks but finally gave up on co-operation. After a a few days or weeks? I stopped and used that same house code again and never had a problem with it again. ...but I was nervous about using other X10 House codes then. I figured somebody switched away from my house code. IIRC I was getting an All House On commend though, likely some unlabelled X10 remote control. It worked anyway..

Years ago I wrote a program to turn all on and all all off every 15 minutes , every day, and my neighbour problem went away. They must have changed house codes.

Older may make it worse as components age. I have an old AC motor model and a DC motor unit with battery backup. The newer one kills my Insteon almost 100%. Turning the power off may not be a good test. They can still suck signals while plugged in.

Garage Door Openers. Chamberlain makes most of the brands in North America

You need some hysteresis in your programs. Try using 41F to turn on cycling and 39F to turn on 100% run. When the pump runs the sensor see an immediate temperature rise and the season changes for you programs. Add hysteresis in the form of temperature differential and/or time delays, or use MrBills method with a variable and temperature hysteresis. Either way this is going to take at least two programs to accomplish the differential hysteresis, and one or two cycling programs that don't interfere with each other.

When you test, ISY has to always be powered up so I would look more seriously at the circuit the PLM is on. GDOs are known to be really bad, especially the Chamberlain models.

I do the opposite marking only State variables. However I also mark integer variables with c for constants that never change eg. $cTrue I comment programs that need to stay disabled in the IF section at the top. Sent from my SM-G781W using Tapatalk

As a pioneer, let others know how it goes. I used a more recent backup to port over to IoP and it took a lot of fixing but mostly worked. With a new polisy there shouldn't be much to lose. Sent from my SM-G781W using Tapatalk

polyglot v2 is not being advanced any further but still functions just fine on my RPi 3. PG3 still has many bugs yet. Sent from my SM-G781W using Tapatalk

You too ? Sent from my SM-G781W using Tapatalk

I also noted (later) that the displayed time on the admin console, top left, displays the year 1952.

The idea was to unplug the GDOs and then test other devices, not power cycle the GDOs. They are known Insteon signal killers and your MSes may not function either while they are swamping the whole environment with RF and/or power grid noise. You may have lost Insteon links in your devices, especially if you have had comm noise while operating devices. Insteon signals are not data signal secure. Have you tried to Restore each device? You may have to "write updates to device" after each Restore select. UDI has changed things in the admin console and made it more complicated to do any of these things.

I would use "set" uppers to 20%. It is much more effective in Alexa lingo. also "Turn On Uppers to 20%" I also use Turn ON and Turn OFF for almost everything. Create a few programs with different results like this Turn On dim uppers Turn On bright uppers Turn On very dim uppers Turn Off uppers. Make Alexa think they are all different devices. I found the percentages were always flakey.

Try removing the light bulb from the GDO. The lamp goes on when opening the door, but may be off when closing the door, if left to time out first. Try unplugging both GDOs and then test the MSs. My Chamberlain GDO destroyed most comms on my ISY. The older unit with AC motor interfered and I never could figure it out, until I got a newer unit with battery backup and DC motor and it killed my Insteon comms down to about 25%. Then I knew the problem and I remembered reading about dozens f complaints about those units. Two FilterLincs basically fixed it 99%.

Are the programs in a folder with conditions?

Installed great with a single click of the reset button. Wrote a test program to set a variable to [minutes from start of day] based on a trigger from another variable. Bugs still exist in variable "last change time" and [minutes from start of day] value [minutes from start of day] returns the value since midnight plus the UTC offset = 23 hours x 60 minutes = 1380 @ 7:00 PM EDT. This has changed since last IoP version but still not calculated correctly. "last change time" displays the time changed at UTC or four hours too early from EDT. Double the UTC Offset still. No change from previous IoP version.

Try throwing an extra carriage return at the end of each http GET call packet. Writing some webpage code a few years ago I found that chrome and edge browsers would not trigger some get packages in my software. However the next get call would show up double then after it was sent. I found Firefox never did this but I then found many servers just acted immediately when I sent them a second blank line at the end of get calls and data responses. CR = EoL = 0x0D Sent from my SM-G781W using Tapatalk

404 error

Mostly a capacitor but possibly a series or parallel resistor also. Resistors take power to make them work and that produces heat and shows on energy and power meters. Capacitors draw current at 90 degrees ahead of the applied voltage which consumes volt-amperes, but very little power / heat / losses, while still drawing current to make the dimmer function properly. The rating shows 1.4 watts so there is mostly only a capacitor inside.

After bricking two polisys with the latest upgrade I have noticed a few different lighting devices turning on at random in the middle of the night. Now I have transferred back to my ISY994 and noticed some still happening. Unplugged the "not-quite functioning" polisy and the random events have stopped. Not 100% yet, and time will prove it, one way or another but, WoLs didn't work at all, still modulus function errors on fractional variable values (existing from ISY994), and internal time clocks are still offset by double the UTC offset. I have found work-arounds for most of it but the random stuff on WiFi bulbs and Insteon Switchlincs had me perturbed. Those I didn;t know about until switching back to ISY994 again (and another f%$ckin' days work and still finding upgrades that I have to recreate in my head ). Currently on hold for commitment point again, until better successes are heard consistently here. IIRC the original IoP was less buggy and no way to undo upgrades yet.

While that seems to work well, once his routines are all destroyed they won't heal automatically and the routines will need to be touched up. Sent from my SM-G781W using Tapatalk

Is it zWave? That's the way all my limited experience with zWave has been so far. However, I found parameters that can control what power levels my devices will start reporting changes at. Most of these settings were not made user friendly by UDI updates and reading the tech manuals becomes necessary to make some zWave modules useful. Once you discover how and write a program to send the coded numeric messages the devices will act more like Event triggered devices, not needing queries constantly. Sent from my SM-G781W using Tapatalk