Page 1 of 1

Nano SD Local Dashboard Fatal Error Sun **solved**

Posted: Sat Nov 23, 2019 6:09 pm
by augiedoggie49
I have the 'Fatal Error uncaught exception' for the sun position in the Weather34 dashboard. My timezone selection in the system tab is 'Los_Angeles.' I think the '_' is causing the problem. I tried changing the timezone to one that is one word and rebooted, but the Weather43 page still sees the old Los Angeles timezone. Can anyone help?

Re: Nano SD Local Dashboard Fatal Error Sun

Posted: Sun Nov 24, 2019 12:07 am
by weatherist34
should be America/Los_Angeles

reference here https://www.php.net/manual/en/timezones.america.php

make sure no spaces before or after .

Re: Nano SD Local Dashboard Fatal Error Sun

Posted: Sun Nov 24, 2019 9:25 pm
by augiedoggie49
I understand that the space would be a problem. The problem is that the Sun Position panel in Weather34 local dash shows the Fatal Error: Uncaught exception because of a problem when I select America/Los_Angeles in the System tab of meteobridge Nano SD. I don't know how to fix or edit or whatever is needed.

Re: Nano SD Local Dashboard Fatal Error Sun

Posted: Sun Nov 24, 2019 10:53 pm
by weatherist34
augiedoggie49 wrote: Sun Nov 24, 2019 9:25 pm I understand that the space would be a problem. The problem is that the Sun Position panel in Weather34 local dash shows the Fatal Error: Uncaught exception because of a problem when I select America/Los_Angeles in the System tab of meteobridge Nano SD. I don't know how to fix or edit or whatever is needed.
don't need to edit system or change anything system tab use the setup menu in dashboard itself example below
Screenshot at Nov 24 23-51-33.png
Screenshot at Nov 24 23-51-33.png (19.74 KiB) Viewed 2140 times

Re: Nano SD Local Dashboard Fatal Error Sun

Posted: Mon Dec 09, 2019 5:40 pm
by augiedoggie49
I did use the system tab and selected America/Los_Angeles as in your screenshot. It didn't fix the problem, so I selected America/Tijuana because that location is still in my timezone, and this selection does not include an '_' . This worked for me. I believe I read a post where someone else had this problem but they did some editing to fix it. Sorry I don't know where that post is now.
Thanks