Persistence issue with OH5

I have an odd persistence/chart issue since upgrading to OH5 that I’ve noticed recently. For detail, my setup is OH5.0.2 on RPI5 (openhabian) using JDBC with a MariaDB instance on my NAS. I have 3 shelly H&T’s tracking temp/humidity. I’ve confirmed that the shelly H&T’s are accessible, functioning, and tracking temp/humidity. I’ve also confirmed the MariaDB instance has current rows for all the temp/humidity data points for each Shelly up to the minute. The data looks fine as do the devices.

So if I run my chart for this H&T temperature I get this

What the chart seems to do is set a flat line for the last 8 hours despite the fact that the last 8 hours of data points are present in the mariadb instance. It’s always about 8 hours flat line.

Thinking this a date/timezone config type issue Ive confirmed mariadb system time is correct. As is java system time, and systemtime on the rpi.

Any thoughts?

Just in case this is of use to anyone I determined the cause of my issue. The EXTRA_JAVA_OPTS in /etc/default/openhab setting was set to europe/berlin timezone. I'm not sure when this happened but I noticed the issue afterupgrading to OH 5 (now on 5.0.3 current). Fix was found while debugging an issue with using trigger channels from the astro binding to trigger rules that turn some lights on and off with sunrise/sunset etc..

The fix for both was to set the timezone in EXTRA_JAVA_OPTS to my correct local timezone.

Cheers

1 Like

This issue came up again after upgrading to 5.1.2, timezone set back to europe/berlin.

Anyone know if there is a way to stop this every upgrade?

Cheers