MWareman Posted October 11, 2021 Posted October 11, 2021 My Polisy is set to Chicago: However - the dashboard on ISY running on Polisy is using LA as my location for the timezone and sunrise/sunset calculation: The actual timezone settings of the clock are not available in the java UI for ISY on Polisy (unlike native ISY where there are options on this screen for setting the timezone). Isn't it supposed to inherit the timezone of the Polisy it's running on? Michael.
Michel Kohanim Posted October 11, 2021 Posted October 11, 2021 @MWareman, It should use whatever is the system time zone as set by Polyglot. This information comes from another service called udx (which is an abstraction layer for OS and used by both Polyglot and ISY). I suspect udx is back leveled. Please: sudo pkg upgrade udx sudo pkg upgrade isy sudo service udx restart sudo service isy restart With kind regards, Michel
MWareman Posted October 13, 2021 Author Posted October 13, 2021 (edited) @Michel Kohanim Fantastic - that resolved the timezone issue. Thank you so much! One minor issue does still remain. On physical ISY - we had the ability to set a custom location. In my case - I am ~50 miles west of Chicago and the sunrise and set times are ever so slightly different. Physical ISY: ISY on PolISY: ISY on Polisy is now learning the timezone from the underlying OS - but we appear to have lost the ability to put in a latitude and longitude for the sunrise/sunset calculation. Is this no longer possible (if not, can it be added back?) Thank you! Edited October 13, 2021 by MWareman 2
MrBill Posted October 13, 2021 Posted October 13, 2021 2 hours ago, MWareman said: (if not, can it be added back?) @Michel Kohanim Here's a second vote for hoping it's added back. (actually I said the same in a different thread months ago too). While the differences between custom and the nearest timezone city are not often great, they are still different... and there is a nerd factor here... that said I guess there are two nodeservers... Sun and TimeData that would do the job.
Michel Kohanim Posted October 13, 2021 Posted October 13, 2021 @MWareman, They shall be resurrected. The main issue is that, as you can see, we are trying to move things out of the Java Admin Console + want to make sure we use existing OS functionality as much as possible. For instance, we no longer manage DST calculations, months, days of the week, etc. In the meantime, if you have specific lat/long, please send to support@universal-devices.com and we'll include it in the list in Polyglot. @MrBill, yes, thank YOU very much. With kind regards, Michel
MWareman Posted October 16, 2021 Author Posted October 16, 2021 On 10/13/2021 at 9:00 AM, Michel Kohanim said: @MWareman, They shall be resurrected. The main issue is that, as you can see, we are trying to move things out of the Java Admin Console + want to make sure we use existing OS functionality as much as possible. For instance, we no longer manage DST calculations, months, days of the week, etc. In the meantime, if you have specific lat/long, please send to support@universal-devices.com and we'll include it in the list in Polyglot. @MrBill, yes, thank YOU very much. With kind regards, Michel Thank you so much! An email has been sent. I appreciate it. Michael.
SJK Posted November 7, 2021 Posted November 7, 2021 (edited) I was having the same issue. I'm on ISY v5.1.1 Tried a polisy update via the UI. Last reboot it changed to match the Polyglot settings, then reverted back after a few minutes to pacific time. Tried comandline update options without effect. Manually called to update udx and polisy as above, and it worked despite the output not saying anything was updated. But again, simply restarting the system worked for a while- so I'll keep an eye on it. However, while the current date/time are correct, the sunrise/sunset are off by an our (stating today that sunset is at 15:51:53) when it should be 16:52 according to reality. Today was the switch to standard time. Wonder if it will fix itself tomorrow- Not sure when those values are updated. While there's a checkbox for Daylight Savings in the ISY UI, it's greyed out- and currently checked (incorrectly). Date and time is hard. Edited November 7, 2021 by Scott Korvek
SJK Posted November 7, 2021 Posted November 7, 2021 (edited) Update: time just flipped to Pacific (LA) while hitting submit on the last reply. I'll also note I'm running the TimeData node server. From it's logs, the time/date information on polisy is correct, including DST status and my manually-input lat/long: 2021-11-07 16:35:13,534 Controller polyinterface INFO polyinterface:reportDriver: Updating Driver timedata - GV1: 35, uom: 0 2021-11-07 16:35:13,537 Controller polyinterface INFO polyinterface:reportDriver: Updating Driver timedata - GV9: 447395, uom: 0 2021-11-07 16:35:13,539 Controller polyinterface DEBUG timedata:season: dd: 7 md: 1107 2021-11-07 16:35:13,540 Controller polyinterface DEBUG timedata:getNodeUpdates: UTC offset: -5.0 2021-11-07 16:35:13,543 Controller polyinterface DEBUG timedata:getNodeUpdates: Old epoch days: 18938.89945601852 2021-11-07 16:35:13,544 Controller polyinterface DEBUG timedata:getNodeUpdates: Stripped date string is 2021-11-7 16:35, weekday 6, days since epoch: 18938.89945601852, hours this year: 7456 2021-11-07 16:35:13,544 Controller polyinterface DEBUG timedata:getNodeUpdates: Day of week 6, Week number 46, Day of Year 311 2021-11-07 16:35:13,545 Controller polyinterface DEBUG timedata:getNodeUpdates: Minutes in year to now 447395, hemisphere north, season 2, leap year 0, isDST 0 Edited November 7, 2021 by Scott Korvek
Michel Kohanim Posted November 7, 2021 Posted November 7, 2021 Scott, Are you referring to the Admin Console or anything else? With kind regards, Michel
larryllix Posted November 8, 2021 Posted November 8, 2021 (edited) On 10/13/2021 at 10:00 AM, Michel Kohanim said: @MWareman, They shall be resurrected. The main issue is that, as you can see, we are trying to move things out of the Java Admin Console + want to make sure we use existing OS functionality as much as possible. For instance, we no longer manage DST calculations, months, days of the week, etc. In the meantime, if you have specific lat/long, please send to support@universal-devices.com and we'll include it in the list in Polyglot. @MrBill, yes, thank YOU very much. With kind regards, Michel After finding sunset light programs not working correctly I found my polisy admin console displaying LA, California. My polyglot settings were for Toronto. Since the settings rejected any update (no change) I had to change the location to Ottawa and then back to Toronto to get it to change. Now my sunset and sunrise times are both 1 hour too early. Owen Sound would be the nearest major community for this area. Latitude: 44° 34' 1.81" N Longitude: -80° 56' 36.56" W Edited November 8, 2021 by larryllix
Michel Kohanim Posted November 8, 2021 Posted November 8, 2021 It's a bug. Should be fixed in a day or two. With kind regards, Michel 1
SJK Posted November 8, 2021 Posted November 8, 2021 (edited) Thanks! Just to add a bit more information: here's a screenshot. This AM I find it still thinks it's in CA, but is reporting the correct EST time. And sunrise/sunset makes no sense at all. It's 9:11AM EST at the time of the screenshot and bright and beautifully sunny. Edited November 8, 2021 by Scott Korvek JPG vs PDF
larryllix Posted November 8, 2021 Posted November 8, 2021 (edited) 6 hours ago, Scott Korvek said: Thanks! Just to add a bit more information: here's a screenshot. This AM I find it still thinks it's in CA, but is reporting the correct EST time. And sunrise/sunset makes no sense at all. It's 9:11AM EST at the time of the screenshot and bright and beautifully sunny. Enter your Polyglot settings and change the location to a temporary location. Save and then set back. The automatic location grab at boot-up or install, apparently isn't working properly yet. Mine were set to locate Michel also. My sunset and sunrise were off an hour (more than DST return to EST) but now seem to have corrected themselves (next day) somehow. Rebooting polisy didn't seem to help at the earlier point either. Still need a lat/long tweak as the times are off by about ten minutes but that is minor. Edited November 8, 2021 by larryllix
larryllix Posted November 10, 2021 Posted November 10, 2021 On 11/8/2021 at 4:06 PM, larryllix said: Enter your Polyglot settings and change the location to a temporary location. Save and then set back. The automatic location grab at boot-up or install, apparently isn't working properly yet. Mine were set to locate Michel also. My sunset and sunrise were off an hour (more than DST return to EST) but now seem to have corrected themselves (next day) somehow. Rebooting polisy didn't seem to help at the earlier point either. Still need a lat/long tweak as the times are off by about ten minutes but that is minor. Grrrrrrrrr..... My timezone, along with sunset and sunrise times, and event times shown for programs and variables just reverted back to LA again.
asbril Posted November 10, 2021 Posted November 10, 2021 1 hour ago, larryllix said: Grrrrrrrrr..... My timezone, along with sunset and sunrise times, and event times shown for programs and variables just reverted back to LA again. Maybe your ISY is telling you that for the winter it wants to move to sunny California. 1 3
Michel Kohanim Posted November 10, 2021 Posted November 10, 2021 @larryllix, Just to be clear, this is only for programs and not the clock at the top of the Admin Console? With kind regards, Michel
larryllix Posted November 10, 2021 Posted November 10, 2021 2 hours ago, Michel Kohanim said: @larryllix, Just to be clear, this is only for programs and not the clock at the top of the Admin Console? With kind regards, Michel The time zone at the top of the admin console changes back to LA Cal. Then program events in the summary tab and variables all show last run / modified based on the LA times.
Michel Kohanim Posted November 10, 2021 Posted November 10, 2021 @larryllix, Makes no sense. Please send me the following in an email to support@Universal-devices.com 1. Output of uname -a pkg info isy df -h 2. ISY Error Log 3. /var/isy/FILES/LOG/debug.log With kind regards, Michel
larryllix Posted November 10, 2021 Posted November 10, 2021 (edited) 1 hour ago, Michel Kohanim said: @larryllix, Makes no sense. Please send me the following in an email to support@Universal-devices.com 1. Output of uname -a pkg info isy df -h 2. ISY Error Log 3. /var/isy/FILES/LOG/debug.log With kind regards, Michel 3. /isy/ is locked permission. I cannot access this file or directory When using sudo, /FILES/ does not exist Edited November 10, 2021 by larryllix
SJK Posted November 11, 2021 Posted November 11, 2021 yup. Making the temp change in Polisy config doesn't work. A while (hour? went to put my kid to bed) after the change, my TZ was fixed, but my sunrise/sunset times are 3 hours off actual (Local sunset + 3 hrs) again. So any sunrise/sunset calculations in programs don't trigger correctly. My current workaround is to use the sun position nodeserver and key off the elevation parameter so set dusk, sunset, and sunrise as state variables to trigger programs. (fits anyway- most everything I am doing is llke a mini-state machine). Sent a support email.
Michel Kohanim Posted November 11, 2021 Posted November 11, 2021 @Scott Korvek, Thank you for the logs. Something keeps calling SetDateTime web service on ISY. I responded to your ticket. With kind regards, Michel
SJK Posted November 20, 2021 Posted November 20, 2021 So far after the removal of nodeservers, reboot, and re-adding each back one at a time my time settings remain correct. I'll probably never figure out what was calling that service.
larryllix Posted November 21, 2021 Posted November 21, 2021 (edited) @MWaremanSo far this seems to have worker for an approximate timezone setting. Whether it stays until @Michel Kohanim get it fixed on a more accurate location remains to be seen. You have to know the exact file pathname to your timezone to make the commands work. https://www.itbroker.com/set-the-timezone-in-freebsd/ Edited November 21, 2021 by larryllix
Michel Kohanim Posted November 21, 2021 Posted November 21, 2021 All, Definitely a bug. And, while crushing it, added time/lat/long configuration back to the Admin Console for Polisy. The only thing you won't be able to do is to set the Time Zone offset because the OS does not allow it: it has a list of time zone regions that you have to choose from. So, let's say you want to have a different lat long that's not in the list. What you do is to pick the nearest city, then change the lat/long and save. Other things that were fixed/enhanced: - SNI support for network resources - IPv6 web server - SMTP issues truncating messages and sending them as attachments instead - Z-Wave is very very very close Should be out mid week. With kind regards, Michel 6
MWareman Posted November 21, 2021 Author Posted November 21, 2021 1 hour ago, Michel Kohanim said: All, Definitely a bug. And, while crushing it, added time/lat/long configuration back to the Admin Console for Polisy. The only thing you won't be able to do is to set the Time Zone offset because the OS does not allow it: it has a list of time zone regions that you have to choose from. So, let's say you want to have a different lat long that's not in the list. What you do is to pick the nearest city, then change the lat/long and save. Other things that were fixed/enhanced: - SNI support for network resources - IPv6 web server - SMTP issues truncating messages and sending them as attachments instead - Z-Wave is very very very close Should be out mid week. With kind regards, Michel Awesome! Thank you @Michel Kohanim. Having the lat/long set separately from the timezone is most definitely a needed feature as some timezones are huge. I'm quite sure this is better than adding hundreds of locations just to account for sunrise/sunset times. Looking forward to the SNI and Z-Wave support - these two will help me complete my own migration. Only one final bugfix to confirm - triggering device substitution for # in NRs. 2
Recommended Posts