tmorse305

@io_guy, thanks for the new version 0.11.2 which fixes the case issue with IoP. I seem to be stuck at rev at 0.10.6. When I try the 'Check for Update' I get this: 2022-02-05 16:50:36 - Auto-Update: Checking for program update... 2022-02-05 16:50:37 - Auto-Update: No web update available How do I update my NodeLink? Thank you.

I'm glad you got it running. I don't know if you follow the Polyglot developments on this forum but in case you don't just a heads up that future development of Polyglot and the Node Servers is rapidly moving to V3. V3 will not run on a RPi, you will need a Polisy to run it. V3 importantly will provide a mechanism to compensate the developers for their hard work that we have all been enjoying for years free of charge.

From the github page:

If you run the command multiple times and it's always 7ms, then I suspect that it runs for 7 ms crashes and then restarts only to crash again. I saw this on the github page: # Watch the logs real-time tail -f ~/.polyglot/log/debug.log Did you try that? My expertise is limited here so others may have to jump in to help you with this issue.

Maybe its not running, check: sudo systemctl status polyglot-v2.service There are log files that might point to the problem if it's not running. The github page has more info on all of this. https://github.com/UniversalDevicesInc/polyglot-v2

Check to make sure INSTEON is enabled on the configuration screen in AC

@Jimbo, @bpwwer, thanks for the advice. Rather than try to move everything right now I think I'll wait and just load a couple of new ones(not on my PG2) onto PG3 so I get get some mileage on it before I take the plunge.

So I'm getting ready to migrate my NSs from PG2 to PG3. I have purchased all of the PG3 licenses that I need but have not installed anything yet. If I do a restore from a PG2 backup I don't need to install anything right? They will be restored in the proper locations based on the PG2 backup and they will install because I already have the licenses. Just want to be sure before I push the button! Once restored it seems there will be 2 NS with the same configuration trying to talk to IoP. Is that a problem? Do I just stop the duplicate PG2 NSs? Thanks.

Ah ok, not sure how to change that one.

Yes, you can change it on the File Tab, see screen shot. Don't forget to update it in PG2 and PG3 if you have them and any NS that needs it.

I wanted to document this issue in case anyone else runs into it. When the upgrade reset the credentials to admin/admin it also cleared the INSTEON Support check mark on the configuration page. It also of course invalidated the credentials stored in PG2, PG3, NodeLink and any other NS that needed them. That didn't dawn on me right away... That resulted in a lot of noise in the log files as Michel was trying to help me solve the problem. My Portal connection was also impacted which Michel had to fix on his end. THANK YOU @Michel Kohanim for your help in getting to the bottom of this!

I was able to shut them off from the AC but I tried the rest call anyway. It was successful but no change. I'll put a ticket in today. Thanks to you and @Jimbo for the suggestions.

@Javi,The problem now is that when I ask about updates it says the my polisy is up to date. Do I need to force the update via ssh?

I ran an update to my polisy tonight using the Check for Polisy updates then Update Polisy. I think it said there were 100 items to update. After completion both PG2 and PG3 came back up, but the ISY Launcher failed to find ISY. I played around with the cache and downloading the launcher and finally got my ISY to appear. When I went to log in the password was changed back to admin (@asbril also reported this in an earlier post). The AC came up and I can see my devices but the system is in a long endless loop of the system being busy. Once completed it just starts over. I tried rebooting polisy, even unplugging it and the PLM, but the result is the same. The Portal reports ISY to be offline. Suggestions? Thanks in advance.

Thanks for the reply @io_guy. See screen shot, I have auto update enabled but I tried a manual update. The log indicates that I'm up to date. Also I clicked the node update as well. In the log you can see that it appears to have updated successfully but when I reboot is still says the files are out of date. Maybe it's related to Michels comment about case sensitivity?

Does the banner at the bottom of the Dashboard point to the ISY on Polisy? It sounds like it's working especially if it updated. Maybe the banner is related to PG3? I don't have PG3 installed yet. Is the configuration on PG3 correct?

It sounds like your ISY is not configured correctly in PG2. Here is what mine looks like.

Thank you @Techman, I ran right past 'ISY', looking for 'Query...' in devices. @dbwarner5, my situation was the same, the 'then' statement was replaced with a comment referencing the UUID of my 994. Easy fix when you know where to look!

I just moved my ISY to Polisy and I'm having some issues with NodeLink communicating with that platform. I get several error messages when NodeLink boots. One is that the Node definitions need updating but the auto update does not seem to work. The manual link takes me to a broken url. How do resolve the 3 file not found errors? Is there a new link to the manual file update? Thank you for your help.

I also lost my Query Routine. How do I restore it?

What a strange problem. Are there any other devices listed in Alexa that have the word 'kitchen" in them? Is it just the kitchen scene that's a problem or are there other scenes/lights that don't work? I have 2 ecobee5 thermostats and they seem to work identically to any native Echo that I have. I have both skills enabled as well. I haven't tried it but I wonder if the skills are even necessary for the Alexa part of the ecobee to work. I would think no but not sure. Do you have multiple Amazon accounts? Maybe they not on the same account? Just throwing out ideas... A call to Amazon may be the only way to sort this out.

The power cycle and factory reset see this link: http://cache.insteon.com/documentation/2477D-en.pdf The restore process is as you described.

You could try a power cycle on one of the affected switches. Next try a factory reset and then restore it from your ISY. Hopefully they just got scrambled from the power glitch and not damaged.