Update to 5.0.1 release from the last 5.0 milestone broke my rules: fixed!

  • Platform information:
    • Hardware: Raspberry Pi/8GB/8GB
    • OS: Openhabian
    • Java Runtime Environment: Temurin 21
    • openHAB version: 5.0.1 Release
  • Issue of the topic: How I fixed my rules not triggering on events

Note: just posting this in case anyone has the same issues - when I updated from the 5.0.0 milestone release to the release version of 5.0.1, suddenly my rules wouldn’t trigger on astro trigger events, set time events, really any time based trigger. When I looked at my logs I saw they were all in CET time even thought the actual events where US central Base Openhabian/debian logs were all local time and such. Finally based on another old thread here I looked at my EXTRA_JAVA_OPTS in /etc/default/openhab and saw that somehow the -Duser.timezone was set to Europe/Berlin rather than America/Chicago. I changed this, restarted the Openhab systemd service and everything has been working properly since. I’m not sure how it got changed, but I thought I’d post this here in case anyone else was also having similar issues - just something to check.

Hope this helps.

We are not either but it’s under investigation. Based on what the code does this shouldn’t be happening. At most what should happen is the OS timezone is used if that parameter is added to that file. It’s still not clear why this is happening.

Ah, so this is a known issue? Hmm, is there a bug tracker somewhere I should have looked first? Sorry if I missed step. Still, hopefully for others that just look here in the community forum they’ll see this and have a pointer to a solution. I’ll look around here a bit more.

Just some history, I started with OH 1 way back when and have just been upgrading in place (with two platform migrations) over the years. It’s a testament to the community how there have been so few problems. Thanks for that - if this is the worst thing I ever encounter then I’m very happy! :grinning_face:

I can’t remember if a bug was filled or if it’s still open. We still are but sure which repo the bug belongs in so it may not have been filled yet. You can search for issues on GitHub but there are dozens of repos so for something like this it’s not always clear where the right repo to search is.

In this case it’s either openHABian or openhab-linux IIRC.

I did poke around in the Github repos after my last post, but didn’t see anything. I’ll check back again, but I’m just glad there’s awareness. Thanks!

Just a quick note that after an upgrade to 5.1M1, the problem is still there. I’ll try M2 soon.

Thanks Mick, I had the same issue, my lights wouldn’t turn off at night and I had only a simple rule, drove me nuts. I live in Australia, 10h difference to Berlin.

Thanks again for posting, very helpful!

Just an update: still a problem with 5.1 M3.

I just installed 5.1 release: it reverted back to Europe/Berlin from Australia/Sydney, so problem still persists.

Installer for release version of 5.1.2 still has this issue.

Hmm, I actually asked Gemini to dig through the repos looking for where the EXTRA_JAVA_OPTS was being set and it found out that there is a file /etc/openhabian.conf where the options are pulled from for the setting and I guess it is set on the very first install. I did check on my machine and it was set to: timezone=Europe/Berlin so that’s what the updater was using to build /etc/default/openhab. I’ve changed this to my local tz and we’ll see if that fixes things.

I’m on 5.1.4 and the fix to /etc/default/openhab seems to have taken care of this issue. Marking as solved.

Just upgraded to 5.2.0 and the fix held - one last post confirming the solution.