larryllix

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

If you disconnect and then reconnect your ISY skill the pseudo devices you have created will have disappeared from existence and you will have to edit each routine, reconnect each device as a trigger and re-enable each Routine. Some have had success with disabling their ISY skill for a very short time before the updating process in the Alexa app wakes up and "ruins" the Routine triggers.

Then you have noise interfering with your communications. You will need to find the noise source and eliminate or reduce it first. Sent from my SM-G781W using Tapatalk

I haven't noticed a lot of rain triggers. However snow flakes will trigger the motion sensors as fast as the MS shuts off. Typically MS lights are on 89 to 90 % of the time while it is snowing. When the sensitivity is turned down lights typically will not respond to a human further than about 8 to 10 feet away. When visible light cameras with iR illumination see snow, a continuous sheet of moving white flakes on the front row are all you will ever see. They seem to glow in the dark and blind everything else. A cam in my garage sees the reflective strip on my snowblower hood and the rest of the view goes blank in the garage with iR illumination. I have cover the reflective strips or anything shiny metal or all the cams go blind to everything else. Possibly the HDR technique better android cams have now, with two different technology sensors could make a difference but then who wants to pay 500 or 600 dollars for every cam? Sent from my SM-G781W using Tapatalk

The cams using iR illumination attract many wild animals that see by iR. Lights up their world. Sent from my SM-G781W using Tapatalk

Looks like the motion sensing would be a waste of money here. There is a reason they use iR. Mine would always be on 24 x 7 with such sensitive settings, or they would see nothing at all at night, unless the moon moving triggered them. As it is using iR mine blink on and off all night with every snow flake and wisp of wind during temperature changes. My 8 cams are mostly disabled for motion if they are outside. Who can look through 20 to 30 events per day x 8 cams? My inside MSes are close to flawless though. They use iR. Sent from my SM-G781W using Tapatalk

Keep in mind that top end cameras use a separate motion sensors to detect motion. Visible light is not a good medium to detect motion, thus the usage of the iR spectrum in most motion detectors. Prepare for many false alarms.

I have read your post three or four times now. Maybe it is my accent or your font, but I still don't understand what you mean exactly.....j/k

There are two directions of "connection". Are you having trouble with the status getting into ISY, trouble with controlling things from ISY, or both? I believe the "connected" you see in PG2 is the connection to the end device and not related to ISY.

Are you running IoP or an ISY994? I had several random lights go on with IoP but they weren't repetitive, except for one particular light / scene. wrote it off to an OnOffLinc that went bad a few years ago and marked it for death this time. From your log, I see a lot of action around yur garage door system. I would try unplugging it (them) for a day and see what happens. I have two GDO from different technologies and they both interfered with my Insteon signals and HA. The latest one with DC motor and battery backup, drove my HA down to about 10% reliability and gave me the clue what was happening for the last few years. Two FilterLincs resolved those problems.

Since the beginning of IoP, mine originally sowed incorrect times and couldn't set time zones or lat/long properly. However UDI corrected that on the surface and all showed properly, but the internal time clocks were never correct and all based on being 5 hours out. [minutes since start of day], sunrise and sunset parameters in programs were all off by 5 hours. Also events, and variable change times were recorded by the same 5 hour off clock. When writing variable values manually, the times were correct. A ticket was opened on this issue by me and possibly several others so a fix should be coming soon, hopefully. With many other MAJOR problems, based on the last upgrade I gave up and went back to ISY994 and polyglot on RPi 3, for now.

Yeah, polyglot-v2 works just fine on a RPi 3. There is an install script on the github website that will do the whole thing for you. https://github.com/Einstein42/udi-polyglotv2 However I have found with three different installations it sets up some parameters incorrectly and the instructions for the .env parameter override file are incorrectly identified and have caused me a lot of grief over the years. The descriptions of the parameters are wrong and despite complaining they remian incorrect for the last few years. It appears to install Node server configurations in ISY994 with port 443 while the Polyglot node server expects port 3000. Not sure any more but HTTPS may be disabled in Polyglot and enabled inside the ISY NS configurations. None of my installations have ever functioned out of the box. The status will update and fool you but the controls never have worked. Here is a .env file with some corrections (in text descriptions) I have discovered after many weeks of hair pulling. Instructions to create it are found in the linked github page above, but I have corrected a few important lines. Biggest problem is many parameters affect two factors and not one as described in the github descriptions. # Overrides the IP address Polyglot listens on the local machine. #BIND_IP='192.168.0.163' # Overrides the IP address Polyglot tells ISY to send node commands HOST_IP='192.168.0.163' # Overrides the port Polyglot listens on for its webpage service & ISY control interface. HOST_PORT='3000' # Overrides the default mode HTTPS for Polyglot webpage service & ISY control interface. USE_HTTPS=false # Username used to login to the ISY. #ISY_USERNAME='admin' # Password used to login to the ISY. Careful this is clear text, I wouldn't recommend setting this here. #ISY_PASSWORD='password' # ISY IP address. This is automatically discovered on the initial run of Polyglot if you are on the same network. If you have multiple you can update it on the settings page of the frontend, or override it here. #ISY_HOST='192.168.0.161' # ISY Port #ISY_PORT='80' # ISY HTTPS: True/False This isn't fully tested so beware HTTPS at the moment. #ISY_HTTPS=false # MQTT Host is the IP address of the host running a MQTT server. This is built in to Polyglot so you won't need this unless you'd prefer an external MQTT server. #MQTT_HOST='127.0.0.1' # MQTT Port is the port used to connect to the MQTT server. Default is 1883 #MQTT_PORT='1883' # URI to access MongoDB. You might need this if you have an off-box Mongo instance. #MONGO_URI='mongodb://localhost:27017/' # To enable debug logging set the NODE_ENV override to 'development' #NODE_ENV='development' # To enable Custom SSL Certificates CUSTOM_SSL=true # Enable Beta Software Updates USE_BETA=true Now your Node server configuration in ISY needs to match and has never done so in my installs, so far (yesterday was the latest 24 hours of hair pulling). The red circled parameters need to match what is found in the polygot .env parameters override file (above). You will need to create this file from scratch. It probably doesn't exit and parameters are assumed incorrectly from my script usages. Best of luck. RPi 3 works just fine and may be a good stop-gap until the confusion falls aside and polisy is more reliable.

I think it is not the bios firmware, but rather the size of the early bios chips not being able accommodate both bioses until the flash burning is done and the old bios can be erased....or hidden? Sent from my SM-G781W using Tapatalk

Yup. Software tries and retries to erase chip using techniques for 4K, 8k, 16k, 32k etc.. size chips. When it cannot find a space left in the chip the flash process cannot continue. It then reports that the version 100 needs to be replaced. Then a partial v5.4 1 becomes unstable and refuses to function properly. Likely if I could reload an older IoP I could get back up but it contained so many crippling bugs, so I tried my polisy spare. It seemed to function for a while but got bad when I rebooted it. That one upgraded the bios ok but no previous version is available to manually load. Back to ISY994. In the words of Johann Sebastian.... ...I'll be Bach! Sent from my SM-G781W using Tapatalk