Timezone issues on 4.3

[AndrewFG (Andrew Fiddian-Green)]

@mstormi

Well… if you overwrite EXTRA_JAVA_OPTS like @flpaoli did, you also lose all other options that used to be in there.

The current openHabian installation process seems to force overwrite “Europe/Berlin” in that place – even when it knows very well that the user is not in Berlin timezone. So in other words, the issue is not just to preserve the EXTRA_JAVA_OPTS values that openHabian does correctly provide but also to eliminate the timezone value that it wrongly provides.

[flpaoli (FLP)]

@flpaoli

@mstormi

Well… if you overwrite EXTRA_JAVA_OPTS like @flpaoli did, you also lose all other options that used to be in there.
At least if you’re on openHABian and Raspi, there’s quite some and that’s not clever at all.
Plus, you will not be obtaining future changes either. So “future proof”, no this is not.

So at the very least, you should keep the contents like in
EXTRA_JAVA_OPTS=“${EXTRA_JAVA_OPTS} -Dtimezone-blah”

Makes total sense. Hadn’t realized this would be used as basic shell script. Fixed.

Thank you!

Watch out! That doesn’t work!!! It causes openhab to continuously try to restart. Not even openhab.log gets updated. You can see the restarts happening by observing the changing output of:

sudo systemctl list-units | grep openhab

What worked was copying over the EXTRA_JAVA_OPTS from /etc/default/openhab to /etc/openhab/linux.parameters then changing only the timezone in it. My /etc/openhab/linux.parameters looks like this after the change:

EXTRA_JAVA_OPTS="-Xms192m -Xmx768m -XX:-TieredCompilation -XX:TieredStopAtLevel=1 -XX:+ExitOnOutOfMemoryError -Dxtext.qn.interning=true -Duser.timezone=America/New_York"