1 hour ago, DennisC said:

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

@Michel KohanimI am experiencing the same thing on both of my polisy's which are on the latest firmware. Both ISY994's are showing the correct time

ISY and IoP have the same current time but different sunrise and sunset. Both are set to Miami local time 

Polisy : Current time : 12:49 pm

Sunrise : 08:33:07 am

Sunset : 08:28:42 pm

 

ISY : Current time : 12:49 pm

Sunrise : 07:33:37 am

Sunset : 07:28:12 pm

 

Same issues here as @DennisC, @Bumbershoot, @TUhl01, @lilyoyo1. and @asbril.

I have Lat/Long set to specific area. My DST offset changes to -4. If I change it back to closest city (Atlanta) it changes back to DST offset -5,  but after admin console restart it still shows sunset to be at 8:43pm (should be 7:43pm).

Noticed also after closing and relaunching admin console that my custom lat/long are selected again, with the DST offset back to -4. 

So it's not correctly storing the location update. 

Seems since my "customs" location was setup during Standard Time (-4) that's what's stuck in the coding. Cannot change DST offset for custom location.

@DennisC, @Bumbershoot, @TUhl01, @lilyoyo1, @asbril and others...

Seems this is a bug (UI only - according to support ticket reply). Should be fixed this week.

Thanks @Michel Kohanim for the confirmation!