tmorse305

@Jimbo, Oh, do you mean the one you highlighted and underlined???? Please tell me you just added that! BTW the "README" link takes you to the V2 README not V3. Thanks EDIT: Disregard I found it

Hi @Jimbo, I just deleted the PG2 version and installed the PG3 version. I added the authorization code but it indicates that the NS is no running. Log file attached, there is an error being reported. It says KeyError is this in reference to the Auth code? I copied the one from the PG2 version. Thank you. WirelessTag_2-19-2022_74538_PM.txt

You seem to be following the correct steps. Is your Java up to date? Have you tried to reboot your 994 to see if that helps? Just throwing out some other ideas.

Thanks @Jimbo, I was able to come up with a band aid solution while I wait for the real deal. I created a NR for Telegram that will ping the Carplay display so at least I'm aware that there is a Push notification on my phone. I just made it a generic message so that I didn't have to duplicate every push that I already have.

Thanks @Jimbo, updated and working great!. I don't know if this is the right place for an enhancement request but here goes. Will you consider adding support for Telegram? Push works great except it does not work with Apple Carplay. When I plug my phone into the car it silences the audio notification part of the Push. The notification still comes through silently but only on the phone screen. Telegram notifications come through and appear on the dashboard car display including the audio notification. Thank you.

I used "localhost" in the IP field, port 8080, and http. This assumes of course that your ISY is running on Polisy not 994.

There is a Node Server called Virtual that allows you to create virtual devices. You can add it to the scene and use its status to trigger another program.

It did, thanks again for your help! No I'm not that brave, if it's not broken...

@io_guy, I did the upgrade, there were many errors, see the upgrade attachment. I can ping successfully to 93.93.128.193 from the RPi. The log islogfile_2022-02-06.txt attached but the first few lines are still missing. I ran the script again around 10:36. I screen shot the first few lines from putty. Thanks for your help. Upgrade.txt

@io_guy, I reran the script: sudo curl -sSL http://automationshack.com/Files/install.sh | bash to try and update to v0.11.2 but it had some errors, see the screen shot plus the log file. The connection to Envisa link is resetting and I could see there is a permission problem writing to the logger file. Right now I cannot access the browser interface, it just times out. Thank you for any advice you can offer. logfile_2022-02-06.txt

@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?