larryllix

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

'covered patio'? Shouldn't that be 'alligator fencing'? Sent from my SM-G781W using Tapatalk

Yup. Version 100 appears to be the shortcut message the Bios writing code was installed with to describe v1.0.0 when the bios upgrade fails. Sent from my SM-G781W using Tapatalk

Thanks Michel. I am getting my ISY994 back working for now. PG2 is giving me trouble though. I have had to implement the .env file again to force ports to where they should be though. Even the webport was not configured as stated in the docs but now it responds to a browser. Only snag I have left is ISY994 cannot issue commands without failing and there seem to be no way to discover what port should be used. 443 doesn't function. Statuses are all reporting into ISY OK but no commands. Been here before. With polisy, I will wait until the BIOS chip comes and see how it performs before attempting a long days work to switch back again. For my polisy-spare, which reported the BIOS upgrade OK, I will wait until I can get a complete image from factory reset. I don't know what kind of mess is inside. Somebody sold it cheaply and it appears to be a run away for the same reason. When it refused to receive Insteon data via USB PLM, I figured some hardware crashing is going on. Frustrating, but time should figure it out. Thanks again.

Yeah. I found it referred to by both version names in different spots. I assumed V100 was v1.0.0.

Apparently there are two BIOS chip sockets with a selector switch beside them. Original sounds welded in and the other replacement coming has a socket for it. When the update software script runs it attempts t run some erasing software for a 4KB space, then tries 8K, 16K, 32K and 64KB? When they all fail, the software script gives up. Mine reports there is no more space left in the chip...it's bricked, so a new chip is being sent. I am not sure if the chip size was just too small to hold the replacement BIOS firmware until burned into the eprom or how that works. I think once you get v5.4.1 installed and your BIOS isn't upgraded the interlocking UDI tried to install locks you out. With a good BIOS one should be able to stop all the IoP stuff and reflash the bios from there, or downgrade the IoP firmware. Mine had way too many serious bugs to be kept though.

Make sure you do not have the version 100 of the BIOS chip. I have one polisy bricked here, waiting for a new BIOS chip, and a used polisy that UDI got working, but it slowly degraded, losing it's UUID, then Port won't connect and PG2/PG3 will not connect, and later it stopped accessing my PLM properly. I bought it used so who knows, even though the BIOS chip shows updated. Currently going back to ISY994 but cannot get install script to show the polyglot port number to set it up on a RPi again. 3000 doesn't works despite all indications it is running and should. 48-60 hours of hair pulling has me out of the polisy game for a long time now. I've had enough.

Anybody seeing their polisy uuid reseting to 00 00:00:00:00 01 ? When this happens ISY portal disconnects because it connects by uuid. Michel fixed that with a udx update or correction but it has since gone back to the 01 again.... on both polisys too. Too weird. My bad chip spare polisy has just been sitting untouched. Sent from my SM-G781W using Tapatalk

Thanks! Sounds exactly what I was seeing. Michel remote sessioned in, and found a bricked BIOS chip (old version 100). However I have a spare polisy and have flipped over to it (Michel did). Works fairly well but am currently trying to get PG3 working, and have given up with it refusing to add or find any ISY, and refusing to accept and new settings due to "no backend connection. Settings unchanged". I tried Edge browser and things seemed a little different, so I disabled firewall things for Firefox (GD MS!). Didn;t make any difference, so far. I am currently deleting PG3 and attempting to return to PG2, where it worked well for a few years now. I wonder if IoP v5.4.1 will allow that at all.

Thanks! "Version 100 is old and needs to be updated"

I upgraded via the SSH sudo..... method. Total crash. Currently I have no access to IoP. I can access polisy admin console page but it always just shows it cannot access ISY and creds should be updated from polisy. After attempting that a few times, it rejects connections completely. Polisy has been power cycled a few times, polyglot has been rebooted about 7-8 times. ISY finder finds ISY at :8080 only but will not display falldown connection options. I am stuck. After power cycling, polisy left green LED comes on immediately and then after about 60 seconds, polisy makes some grinding noises and then the two rightmost LEDs begin fast blinking. Single poke of reset doesn't change anything. @Michel KohanimHelp!

I am about to dive into the same scenario, possibly. After reading so many disasters in forums for the last 40 years, I am really trying to avoid this problem. I have excluded my Home Automation system from the sale, despite the barking of the Realestate Agent. My excuse is, it is too complex for the average person but if they want to make a fuss, wanting it, I will restrict the amount of hours of help they get. It is still attractive,as a bargaining chip but only to certain techie people, and then they usually don't want somebody else's mess.

When I really need to access wild buttons in my admin console, I minimize my admin console and right click on my desktop to set my Windows 10 screen magnification back down to 100%. When I am done squinting, I reverse the adjustment back to 150% so I can read other screen things. This has only been a problem since about 2006 and should be fixed any time. Sent from my SM-G781W using Tapatalk

I haven't done any testing since the _03 upgrade. I was busy trying to find proof it installed at all. My routines still appear to be functioning despite several ISY and polisy SSH reboots, trying to make the update version display somewhere.

I have never had to redo anything inside the alexa app after many reboots and power cycling polisy yet. But hey! as you pointed out, things change. I will watch for that, and thanks for the warning, and the fix, temporary or not. Fixing these routines takes me about 30 to 45 minutes, each glitch, so I try to avoid disabling my skill as much as possible.

It seems (by logic) in the end this was all caused by Amazon "blacklisting" some device packets from ISY Portal, so that no routines using them would function again until refreshed. That is a whole 'nuther kettle of fish. It doesn't sound like ISY was even involved since it doesn't talk to Amazon directly, but through the ISY Portal bridge system. Sounds like we still need fixes at the ISY Portal and Amazon end. "You send me bad packets and I will destroy ignore you"

Maybe you missed my previous posts. That is what I already reported before updating my IoP version. However, I have been using "Messaging" for years and it is listed under the IFTTT title with the other action techniques. Now, I think we have been reading this incorrectly! IFTTT was formerly in a solid grey band, as a title, above all the action methods listed below it. Now IFTTT appears as just another entry with a distinctly different font! grrrrrr.... I believe I have been trying to tell @oberkcthis (falsely) based on the old screen layout that has fooled many people. OK I take back all the IFTTT crap I have been spouting. Most of us are not likely using IFTTT at all. Just a bad app screen layout. Sorry for that confusion.

Thanks! I used pkg version | grep isy Yes, I am running v5.4.0_3

OK Thanks. They definitely have changed the app a fair bit and I have trouble finding these items again. I set most of my routines up a few years ago. I have some that use "Say" and IFTTT for multi-speakers but looking at them again didn't reveal where IFTTT was used. I did find the small IFTTT title at the top of the bottom grouping of outputs though. BTW: I did try your disable / enable skill with the shortest time period I could manage and it didn't disconnect my pseudo devices for the routines. Nice find! I wonder if the timing is related to the success of this. I am still running IoP v5.4.0. This has been a PITA for a long time with routines and I have placed several support complaints with amazon over the last few years only to achieve no response, yet....but things do seem to clear up after each complaint...so far. hmmmm...maybe that is not completely true. IIRC they responded a few months later once. Also. I have now tried the sudo service....etc to update my IoP but I cannot find any trace of any firmware updated version. Is there some place to find a clue what actual version is installed? My Help | About pulldown and ISY Finder always show "5.4.0" Thanks again!

Only one speaker can be involved with "Say". To announce on your selection of multiple speakers Alexa uses IFTTT. Check the title of the sections above your selections where it is revealed. Some of the menus have changed recently. I don;t even see "make an announcement" anymore???