Recent events list is one hour ahead of system time and ups time.

[tri-fin]

Recent events is one hour ahead of system time and ups time.

Power flow timezone= Europe/London
Nutmanager target timezone= Europe/London

if power goes off at 22.00 Recent Events records 23.00

I think this might be affecting Notifications from events.

I have removed Nutify, deleted its folder, reinstalled and setup but the problem remains.

[tri-fin]

Further testing: I was interested in daylight savings so thought would try a different timezone.

I removed Nutify and deleted directory.
Set rpi system time to Europe/Lisbon.
Setup Nutify with Europe/Lisbon.
Confirmed timezone settings were correct in both places in Nutify but still events are one hour ahead of actual events. And no notifications are received.
This is so odd as others say it works fine for them. I am not sure what I am doing wrong.
Thanks.

[tri-fin]

I found the problem.

If single monitor is selected in the monitoring profile then settings in the event matrix do seem to have any effect.
However when I selected multi monitor then settings in the event matrix work.

I am only using one ups so I never get to select my ups in the top bar - it's always there.

I'm so happy this app is brilliant.
I hope this information helps.

Note. The events list is always an hour ahead for me.

[telecomguyML]

I just had a similar issue, although seems even stranger. I am in Eastern US time. Had an on-battery event at 14:53:35 UTC/10:53:35 EDT:

Event shows it as 6:53:35:

I do have my timezone set properly:

[DartSteven]

Please, I have created the 0.2.2 build.

Try one of these images and let me know if it fixes the issues you were experiencing. If the problem persists, please let me know so I can investigate further.

Warning

Version 0.2.2 is not backward compatible with previous releases.

The database must be recreated from scratch.

To avoid incompatible or dirty data, it is strongly recommended to start from a completely clean environment using a new empty folder.
Do not reuse files or data from older versions.

docker pull dartsteven/nutify-internal-testing:0.2.2-mac-arm64
docker pull dartsteven/nutify-internal-testing:0.2.2-amd64
docker pull dartsteven/nutify-internal-testing:0.2.2-raspberrypi4-armv7
docker pull dartsteven/nutify-internal-testing:0.2.2-raspberrypi5-arm64

[tri-fin]

Hi,
I am sorry for being so slow - I have been swamped at work - but i should able to check things straightaway now. If you want anything in particular testing - just let me know.

I just checked 0.2.2 and now in Single mode notifications for events with ntfy work but unfortunately Recent Events now no longer records anything.

I am using rpi4b.

A little point - is there any point in developing Single mode? I mean if you just use Multi everything works fine and it is one less step for you to worry about and it makes installation easier for the end user because they don't have to choose. I am probably overlooking something important but I thought I would say. This is such a great tool. Kind regards, Brendan.

[Sevyn13]

My event time is 6 hours off.

[DartSteven]

Please, I have created the 0.2.2.3 build.

Try one of these images and let me know if it fixes the issues you were experiencing. If the problem persists, please let me know so I can investigate further.

Warning

Version 0.2.2.3 is not backward compatible with previous releases.

The database must be recreated from scratch.

To avoid incompatible or dirty data, it is strongly recommended to start from a completely clean environment using a new empty folder.
Do not reuse files or data from older versions.

docker pull dartsteven/nutify-internal-testing:0.2.2.3-mac-arm64
docker pull dartsteven/nutify-internal-testing:0.2.2.3-amd64
docker pull dartsteven/nutify-internal-testing:0.2.2.3-raspberrypi3-armv7
docker pull dartsteven/nutify-internal-testing:0.2.2.3-raspberrypi4-armv7
docker pull dartsteven/nutify-internal-testing:0.2.2.3-raspberrypi5-arm64