DennisC

I am not currently at that site and don't leave ssh active for remote sessions. However, I did run that command earlier in the week after the previous upgrade and all was good. I am trying to determine if the command needs to be run, or to leave it alone. For know, it will need to stay the way it is.

I am currently back at my main residence and not at the location that I experienced the error from. Currently, I can access both locations through UD Mobile with no error. When the error appeared, it was a notification and when pulled down from the top on Android, it was impossible to see the full message. After a short period it disappears on its own. I used UD Mobile prior to the IoP upgrade and all was fine. I updated IoP at the site I was at this morning to the following: udx – 2.6.0_7, isy – 5.4.1.1, pg3 – 3.0.45. Shortly before leaving, I tried UD Mobile and received the error. I did check the Portal and both Polisy had active & on line licenses. I have not upgraded my current locations Polisy and won't until tomorrow to know if it is associated with IoP v5.4.1.1.

Everything was updated this morning and I was in admin console all morning with no issues. The Portal was not showing any issues. I was all so in PG3, connected to Portal and viewing paid subscriptions. Everything was fine, 5 minutes after closing out of admin console I opened UD Mobile and got this error. I just left site.

@Javi Now I am getting a UD Subscription error 404, contacting subserver The rest of is cut off, but some of it appears to be Etimedout - can't read the rest of it

@Michel Kohanim I updated this morning to IoP v5.4.1.1, udx is v2.6.0_7, and PG3 is v3.0.45, using ssh commands. After the update, I saw the following notice: "you can disable uftdi driver by adding isy_load_uftdi=NO in /etc/rc.conf 7 1 0xffffffff81d12000 8320 uftdi.ko" Is this something that needs to be done?

@JimboAutomates, @bpwwer, Today, I updated PG3 to version 3.0.45 and the Elk Node Server to version 3.1.4. I am still seeing Sky Battery on the Elk Controller page. The only change is that it now indicates True instead of False. Please see screenshot below:

Thank you!

@bpwwer, Hi Bob, This is just a reminder, not trying to rush you. I noticed in the known bug issues for the PG3 v3.0.45, there was no mention of the backup function not working. I just tried and it is not working. If you already knew that, just disregard this note.

Your assumptions are mostly correct. This didn't start with yesterday's update, but 4-5 updates ago. I am running Android and the device is a Zwave thermostat. I just ran the update and now see whole numbers to choose from ranging from 0.0 to 120.0 F. Values of 0.5 are not present. Also, previously you could either select from the list or type in your value. Now you can only select from list. I am not positive but I believe when you went in to setpoint before it broke, you were at a spot in the list equal to your setpoint. Now you are at 0 and need to scroll through the whole list. It's minor but inconvenient. The same list also appears for customizing color for battery voltage on Tempest, but with only whole numbers it's not going to work well. The range you are dealing with is small, so you need to be able to enter decimal place values (.01 - .09).

I'm afraid I don't understand the question pertaining to "edit text"? Setpoint currently says "enter value" when you try to adjust. This happened some time ago, but it was this year.

@Javi I have been meaning to bring this to your attention for awhile and since I just updated to the latest version now seems like a good time. It has gotten very hard to change thermostat set points in the last several versions on Android. The list of predefined values that you could select from is gone. In addition, UD Mobile no longer excepts the "." character. Attempting to change temperature often results in a change that goes to the thermostat limit, in my case 80 degrees. I just tried to set a custom color for Tempest battery voltage and could not enter the value of 2.40 volts because the app wouldn't accept the period character.

Thanks

Thanks for the update. I rebooted Polisy again, verified with ps -uaxww | grep python that no instance of Notification Node server was running, and that the Current Status was still failed. I couldn't get it running, so I hit stop Node server, waited about 15 minutes, verified with ps -uaxww | grep python again and then hit start. This time the Node server came on line without error. I have no ides what happened, the only thing I did differently this time was wait about 15 minutes.

@JimboAutomates I am trying to get Notification Node server setup at my 2nd location. I am seeing failures in the Node server log indicating port 8199 is already in use. I then ran: ps -uaxww | grep python and found 5 instances running. I tried rebooting Polisy with no change. Next, I killed all 5 instances and rebooted Polisy. The Node server Current Status indicates "Failed" and I am still seeing port 8199 is already in use in the log. I re-ran ps -uaxww | grep python and this is the output: [admin@polisy ~]$ ps -uaxww | grep python polyglot 1533 0.3 0.9 69056 38072 - I 15:44 2:24.45 python3 ./weatherflow.py (python3.8) polyglot 1532 0.0 1.1 82880 43832 - I 15:44 2:27.11 python3 ./wirelesstags-poly.py (python3.8) polyglot 1648 0.0 0.7 57948 30596 - Is 15:44 2:04.58 python3 ./camera-poly.py (python3.8) polyglot 1675 0.0 1.0 84656 40848 - I 15:46 3:46.71 python3 ./elk-poly.py (python3.8) polyglot 1724 0.0 0.7 52532 27036 - Is 16:04 1:12.60 python3 ./timedata.py (python3.8) admin 4128 0.0 0.1 12824 2436 0 S+ 11:45 0:00.01 grep python [admin@polisy ~]$ I should mention that I purchased and installed this Node server yesterday and it was version 3.2.3. I now see version 3.2.4 in the store. I can't seem to get the Node server to run. Should I try uninstalling and reinstalling?

I think you can check the configuration page. There is a switch for it to turn on when time comes.

The account in question is dedicate to my ISY. It is used for nothing else. I have an account for each house. The only thing accessing the account is ISY to send notifications. I only go in to account 2 or 3 times a year.

Thank you, Michel, ticket has been submitted.

@Michel Kohanim, After installing v5.4.1, I went to take a back up and received the error below. I have tried closing and reopening admin console and rebooting Polisy with no success.

There is a lot going on, we will need to be patient.

The message I received is different, it starts with: "You may lose access to some of your third party apps... On May 30, you may lose access to apps that are using less secure sign-in technology" Hopefully, when I make the change all will be good.

It is my understanding that the way to update Node server's on PG3 is to restart the Node server and it will automatically pull the latest version. If you select install button you would be installing it in another slot.

@JimboAutomates, Some time during the last hour Sky Battery changed from false to true.

First, sorry for the delay. I wanted to wait until I was at the site before trying the updated. I completed all updates today, with the exception of updating Elk Node server to version 3.1.3 available in the store. No matter what I try, I am not updating and I am still on version 3.1.2. I tried restarting several times, logged out/in to PG3, restarted Polyglot, rebooted Polisy both by command and pulling the plug. Every time I restart the Elk Node server I am still on v3.1.2. Oh, and I am still showing Sky Battery False under Elk Controller. What do you suggest?

I believe you would need permission from the owner, their stations #, and they would need to provide you with an authorization key.

That's been a problem as you indicate, but that's not what this is. Some Nodeservers have so much information on a single page that even at @100% the information doesn't fit on one screen with admin console maximized. Weatherflow Node server for Tempest comes to mind. On the 994 admin console there is a scroll bar to move down the page. The scroll bar is missing in the IoP admin console for Nodeservers making it impossible to all nodes.