That is expected and correct, the default date (UTC 13:42 right now) is corrected by Europe/Amsterdam (UTC+01:00 => 14:42). That’s how timezones work. So setting wise I see no issues.
1 Like
I just noted the tags did not reflect anything proper as they are the default examples btw. That’s on me mate. I’ll get back to you in a few moments if a reboot helped at all.
I have an idea where the issue can be. Could you go to your device list and then see the data it currently holds? So the screen below. There is a slight chance that the code holds 2 seperate variables for the match time and only one is correctly transformed into your timezone.
Ah right, that had me debugging for about 2 hours as well a few weeks back. The cards indeed show just the placeholder (example) value for the variable and not the actual current value for your team.
Sure just checked that;
But since my reboot I get this result’;
Which does not make sense … unless I hit the API limit. I will give that a shot again in a few minutes.
EDIT: Tried again but it now thinks FC Barcelona is not even playing today. So in testing I have to skip it but the get next match card, then still provides them playing at 20:00.
I’ll try re-adding Barcelona as a device, and restart the app.
So then I had to re-add the above cards. But still it doesn’t even think they are playing today anymore as the card always turns to false.
Did you manually trigger the flow? If so, it uses card defaults and not actual values. Would you be so kind to try and set the start trigger to 15:05 for example and add notification/logging to all cards that fetch and process data to see what the actual data is you get?
1 Like
Sure mate I will give that a shot and fire it on 15:10.
Edit: I need a few minutes for the logging hahaha
Hopefully that gives the correct data, I have to go to my nieces birthday now. I’ll check back later today (and hopefully find out it works).
1 Like
Sure by all means dude.
It just ran as I was still adding logging, so testing indeed screws up some things.
But still noted 20:00 instead of 21:00.
I will add logging to return all the data to the timeline, which also logs everything to Google Sheets on my end and get back to you.
Edit;
Logging as done as following;
Results in;
Which was also sent to my Homey Full Timeline at Google Sheets;
Jan 3, 2026 3:10:01 PM
Aftrap tijd 20:00 | Competitie Primera Division | Dagen tot wedstrijd 1 | Datum 2026-01-03 | Is thuiswedstrijd ⨯ | Locatie Away | Tegenstander Espanyol |
So I am unsure why I have a time difference between what the Next Match Card says and the Device info Next Match states.
But whenever you find the time to look into it mate, already appreciate all your efforts.
I’ve pushed an update for the app. The “fetch next match card” returned the UTC date instead of the one transformed to the correct timezone. Feel free to try again, but I’m sure this fixes the issue!
1 Like
Cool will try it in a bit mate and get back to you 
EDIT: Confirmed fixed … you tha man @pendojoshua !
1 Like
I’ll add that to the wishlist! Must be do-able.
1 Like
