[BUG][SCENES] scene time bug

Configuration
1

Hello,

I just noticed a bug in the trigger time in the scenes since the time change.

I have a scene that only works from 4:30 PM to 6:00 PM. However, it now works from 6:30 PM to 9:00 PM, a two-hour shift.
The Raspberry Pi time is correct and in the CET+0100 (Paris) timezone. Gladys is in the same timezone in its configuration.

gladys: version 4.6.0

2

Oh interesting!

You can try restarting Gladys/your Pi and see if you still have the bug after?

I don’t know how Node.js/dayjs (the library we use) handles time changes, it might be a cache issue on their end.

3

I just rebooted my pi and it seems to no longer have the bug. ( well, next time I’ll apply the Windows saying )

Oh yes, my zigbee2mqtt is marked as created 8 days ago ( is it the 4.6.0 update that went through and bad luck it started at 2:59 am and daylight saving time change … )

4

Great! It’s still not normal, I admit I’ve never looked into the issue, I don’t know how the time change works with Node.js/this lib :slight_smile:

5

I also had a bug, but it was related to the time range selected: 9:00 PM - 5:00 AM.
It didn’t work like that, but 9:00 PM - 11:59 PM and 12:00 AM - 5:00 AM did.

6

I had replied to you on GitHub, it’s not a bug!

7

Oops, I didn’t see that :innocent:

8

I confirm it’s not a bug, it’s just not planned. I had already raised the issue.

https://community.gladysassistant.com/t/probleme-scene-avec-detecteur-de-mouvement-et-ampoule/6443/4

Otherwise, no more bugs after the reboot. It can be closed. To be put in a FAQ/issues.

9

I added an option in the issue card: