DennisC

@glarsen I have Time Data running on both PG2 & PG3. Both are showing sunrise for today at 06:08 am and sunset at 17:57. According to google sunrise today was at 7:11 am and sunset at 7:01 pm. Same differences are shown for tomorrow in Time Data. PoI is showing correct current time and DST is set up for correct location on Configuration page.

@Michel Kohanim I have two Polisy running, one on version 5.4.1.1 and one on 5.4.1_2. The one running v5.4.1.1 is at my second location and handled the change to Daylight Saving Time without a problem, however, it has sunrise at 08:12:30 am and sunset at 08:00:17 pm. The one at my main location running 5.4.1._2 had an issue with the change to Daylight Saving Time. None of the scheduled programs ran this morning. A check of next run time indicate none of my scheduled programs were to run today. They were all set to run tomorrow. A reboot of Polisy corrected this issue. However, it has sunrise at 08:12:30 am and sunset at 08:00:17 pm. On both Polisy, the sunrise and sunset readings are taken from the banner at the top of the page. According to google, sunrise today was at 07:11 am and sunset is at 07:01 pm. Both Polisy have the correct time and the correct DST rule set in location on the Configuration page. Checking my programs that are scheduled to run off of sunset indicate the correct next run time based on google's time of sunset.

For my thermostat the value is shown as .0, however, the value is always shown as a whole number (70.0, 71.0). Having the picker open to the current value would be ideal.

@Javi, I received the update and checked out the functionality and here are my findings. 1. When changing setpoint with this update, without making any modifications with the edit screen, there is no picker and you must enter a value. This field is accepting an entered value since the previous update. 2. If you edit the Step value and enter a value of .5, you can enter changes by .5 however, there is no impact on the setpoint because a change of .5 rounds up to the nearest whole number. This ends up having no change. 3. If you edit Step value and enter a value of 1, the picker comes back, starting at 0 and going up to 120. Therefore, you need to scroll from 0 to the value you are looking to change the setpoint to. However, you can not enter a value directly by typing, you must use the picker. It appears you can either set the Step value to 1 and use the picker list and you then need to scroll from 0 to your setpoint, or leave it blank and just type your new setpoint (2 digits required) in to the field. Was this your expected behavior? While I appreciate your efforts, it is quicker and easier to leave the Step value empty and just type your new setpoint in now that the field once again accepts input.

It would help if you provided a little more information, such as: Version of PG IoP? - version of software (firmware & UI) Do they show up in admin console? Exactly what does "aren't working" mean?

Upgrading the bios is part of the upgrade. Most who have done the upgrade have had no problems. The few that have, were part of a group that took delivery of very early Polisy. A few post above is an in depth explanation from Michel at UD. I have upgraded two Polisy using ssh with no issue with the bios not upgrading.

At one time UD was offering owners of ISY a discount. You could ask if the discount is still available.

It's been a long time since I ran Polyglot on a RPI and I don't remember how to set up port number. I'm not sure if this will help, but I think PG2 was using port 443.

In the admin console, there are no values to select from, only an up/down arrow. When using the arrows, the values change by .1. However, the thermostat doesn't .1 -.4 values. Any value entered starting with .5 raises the thermostat to the next larger whole number (rounds up). Not sure what other information I can supply, but I am willing to test anything you want to try.

The IoP upgrade was more than 2 hours before I tried to use UD Mobile. I was doing programming in between. I did the upgrade to UD Mobile and I can now enter xx.xx values across the board. However, The list of values in the picker is no longer there. Now you must type your changes. Is that the intent?

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.