[Solved] Problem with timezone/rule

---

I am experiencing a little inconvenience with a time based rule, my first guess is that it is timezone (conversion) related.
I have the following rule: “Rene Nexus 5 is present and its after 17.00” to turn on some light (if I arrive at home after 17h, obviously).
While testing this by switching my phone’s wifi off an on again after 17h this rule did not trigger. Though setting the rule to “before 17h” it did trigger, somewhat to my surpirse.
Digging a bit deeper; I checked the system time of my BananaPi running raspbian, which correctly showed the time to be a few minutes past 17h. The time displayed in the events tab is correct as well.
Then even deeper digging: the timestamp in pimatic-deamon.log is 2 hours earlier than in the interface. My guess it is displaying UTC? I have my timezone set to Amsterdam.

Not sure what would be the correct solution or setting to correct this, does anyone have an idea?

As a (temporary) workaround I could off course set my rule two hours earlier, but I think we can all agree that this is not the most convenient solution

@Rene-Arts As you say you have set the tz to Europe/Amsterdam the date command on BananaPi should prompt the local time with timezone code CEST. Make sure you have a system wide setting of the timezone (tzselect will only set the time of your current shell and tzconfig appears to be deprecated). If you have a different timezone set or in case of doubt, you should perform the following steps on a Debian system.

sudo dpkg-reconfigure tzdata
# follow the instructions to select Region/Country
sudo service cron restart

@mwittig Thanks a lot! The date command already showed the right time, but running the commands solved the problem! Seems to working as expected now