# \[App\]\[Pro\] football-data.org - automations based on football matches! **URL:** \ **Category:** Apps\ **Tags:** app, tools, homey-pro, advancedflow\ **Created:** [December 14, 2025, 6:14pm UTC](https://community.homey.app/t/app-pro-football-data-org-automations-based-on-football-matches/146908 "2025-12-14T18:14:21Z")\ **Posts on this page:** 20\ **Page:** 2
**Author:** ![pendojoshua](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/pendojoshua/32/116452_2.png) [@pendojoshua](https://community.homey.app/u/pendojoshua)\ **Post date:** [January 3, 2026, 1:43pm UTC](https://community.homey.app/t/app-pro-football-data-org-automations-based-on-football-matches/146908/21 "2026-01-03T13:43:31Z")
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. ---
**Author:** ![Patrick\_Dankers](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/patrick_dankers/32/94965_2.png) [@Patrick\_Dankers](https://community.homey.app/u/Patrick_Dankers)\ **Post date:** [January 3, 2026, 1:44pm UTC](https://community.homey.app/t/app-pro-football-data-org-automations-based-on-football-matches/146908/22 "2026-01-03T13:44:39Z")
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. ---
**Author:** ![pendojoshua](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/pendojoshua/32/116452_2.png) [@pendojoshua](https://community.homey.app/u/pendojoshua)\ **Post date:** [January 3, 2026, 1:46pm UTC](https://community.homey.app/t/app-pro-football-data-org-automations-based-on-football-matches/146908/23 "2026-01-03T13:46:46Z")
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. ![CleanShot 2026-01-03 at 14.45.40@2x](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/d/7dc7b6260ebe53313feb60038a19f6a9df1a1b3f.jpeg) ---
**Author:** ![pendojoshua](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/pendojoshua/32/116452_2.png) [@pendojoshua](https://community.homey.app/u/pendojoshua)\ **Post date:** [January 3, 2026, 1:47pm UTC](https://community.homey.app/t/app-pro-football-data-org-automations-based-on-football-matches/146908/24 "2026-01-03T13:47:47Z")
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. ---
**Author:** ![Patrick\_Dankers](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/patrick_dankers/32/94965_2.png) [@Patrick\_Dankers](https://community.homey.app/u/Patrick_Dankers)\ **Post date:** [January 3, 2026, 1:49pm UTC](https://community.homey.app/t/app-pro-football-data-org-automations-based-on-football-matches/146908/25 "2026-01-03T13:49:44Z")
Sure just checked that; ![CleanShot 2026-01-03 at 14.47.40@2x](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/6/969a564589bcbffa07d7fff6e05efafb8b12e9e9.jpeg) But since my reboot I get this result’; ![CleanShot 2026-01-03 at 14.46.32@2x](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/1/31ed0ab36ebbc58b749e8171e5416b191da9b6a1.jpeg) 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. ---
**Author:** ![pendojoshua](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/pendojoshua/32/116452_2.png) [@pendojoshua](https://community.homey.app/u/pendojoshua)\ **Post date:** [January 3, 2026, 2:00pm UTC](https://community.homey.app/t/app-pro-football-data-org-automations-based-on-football-matches/146908/26 "2026-01-03T14:00:28Z")
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? ---
**Author:** ![Patrick\_Dankers](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/patrick_dankers/32/94965_2.png) [@Patrick\_Dankers](https://community.homey.app/u/Patrick_Dankers)\ **Post date:** [January 3, 2026, 2:02pm UTC](https://community.homey.app/t/app-pro-football-data-org-automations-based-on-football-matches/146908/27 "2026-01-03T14:02:40Z")
Sure mate I will give that a shot and fire it on 15:10. Edit: I need a few minutes for the logging hahaha ---
**Author:** ![pendojoshua](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/pendojoshua/32/116452_2.png) [@pendojoshua](https://community.homey.app/u/pendojoshua)\ **Post date:** [January 3, 2026, 2:03pm UTC](https://community.homey.app/t/app-pro-football-data-org-automations-based-on-football-matches/146908/28 "2026-01-03T14:03:27Z")
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). ---
**Author:** ![Patrick\_Dankers](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/patrick_dankers/32/94965_2.png) [@Patrick\_Dankers](https://community.homey.app/u/Patrick_Dankers)\ **Post date:** [January 3, 2026, 2:06pm UTC](https://community.homey.app/t/app-pro-football-data-org-automations-based-on-football-matches/146908/29 "2026-01-03T14:06:25Z")
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; ![CleanShot 2026-01-03 at 15.12.09@2x](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/5/5/55f602e86cb14e6c0a76ea965f4a7fc8b4be63b1.jpeg) Results in; ![CleanShot 2026-01-03 at 15.12.41@2x](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/5/a/5a99b4b4c39905be728633b6d46d95e0767fc5f9.png) 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. ---
**Author:** ![pendojoshua](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/pendojoshua/32/116452_2.png) [@pendojoshua](https://community.homey.app/u/pendojoshua)\ **Post date:** [January 4, 2026, 1:41pm UTC](https://community.homey.app/t/app-pro-football-data-org-automations-based-on-football-matches/146908/30 "2026-01-04T13:41:29Z")
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! ---
**Author:** ![Patrick\_Dankers](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/patrick_dankers/32/94965_2.png) [@Patrick\_Dankers](https://community.homey.app/u/Patrick_Dankers)\ **Post date:** [January 4, 2026, 1:51pm UTC](https://community.homey.app/t/app-pro-football-data-org-automations-based-on-football-matches/146908/31 "2026-01-04T13:51:46Z")
Cool will try it in a bit mate and get back to you 🙂 **EDIT** : Confirmed fixed … you tha man @pendojoshua ! ---
**Author:** ![pendojoshua](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/pendojoshua/32/116452_2.png) [@pendojoshua](https://community.homey.app/u/pendojoshua)\ **Post date:** [January 4, 2026, 4:52pm UTC](https://community.homey.app/t/app-pro-football-data-org-automations-based-on-football-matches/146908/32 "2026-01-04T16:52:31Z")
I’ll add that to the wishlist! Must be do-able. ---
**Author:** ![Patrick\_Dankers](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/patrick_dankers/32/94965_2.png) [@Patrick\_Dankers](https://community.homey.app/u/Patrick_Dankers)\ **Post date:** [March 8, 2026, 11:09am UTC](https://community.homey.app/t/app-pro-football-data-org-automations-based-on-football-matches/146908/33 "2026-03-08T11:09:27Z")
Hmm today I noticed a quirk; I always have a “team is playing today check” setup. But today it noted; - PSV is playing Nec at 1845 … but that is their next match (scheduled for March 14th). Simply put … PSV are not playing today. - Barcelona is playing New Castle at 1845… but that is their next match (scheduled for March 10th) Simply put … Barcelona are not playing today. See the below flows and devices overview; ![CleanShot 2026-03-08 at 12.07.20@2x](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/2/023fed57d4b5d1c507cc2bceaf9dcd8a558ac7d2.jpeg) ![CleanShot 2026-03-08 at 12.07.40@2x](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/c/0c7b01fafc4838bb77acdcb5315ab0774a84112d.jpeg) ![CleanShot 2026-03-08 at 12.08.31@2x](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/4/4/4476b23c90183aed94642270edc5e3fcdf0cf124.jpeg) Any idea what could be the cause @pendojoshua ? As they are not playing today, they should never get to the next match card. ---
**Author:** ![pendojoshua](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/pendojoshua/32/116452_2.png) [@pendojoshua](https://community.homey.app/u/pendojoshua)\ **Post date:** [March 9, 2026, 10:54am UTC](https://community.homey.app/t/app-pro-football-data-org-automations-based-on-football-matches/146908/34 "2026-03-09T10:54:26Z")
I noticed two issues that could cause this bug, both are patched in a new version that is live already. It could either be caused by a cache mismatch - in case if the timing was off the collection of matches could still be old and contain more than just todays matches. Related to this the code also still used UTC time check here when fetching the matches instead of Homeys local timezone. And another was some code that was still missing in the check - it didn’t check the matches dates against today’s date. I’ve added date comparison to so that checks should be foolproof now. ---
**Author:** ![Patrick\_Dankers](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/patrick_dankers/32/94965_2.png) [@Patrick\_Dankers](https://community.homey.app/u/Patrick_Dankers)\ **Post date:** [March 9, 2026, 11:08am UTC](https://community.homey.app/t/app-pro-football-data-org-automations-based-on-football-matches/146908/35 "2026-03-09T11:08:06Z")
As always you are an absolute hero 🙂 Thanks again for looking into this. ---
**Author:** ![pendojoshua](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/pendojoshua/32/116452_2.png) [@pendojoshua](https://community.homey.app/u/pendojoshua)\ **Post date:** [March 9, 2026, 12:17pm UTC](https://community.homey.app/t/app-pro-football-data-org-automations-based-on-football-matches/146908/36 "2026-03-09T12:17:29Z")
Did you test the fix already? If not, let me know it it worked or not! ---
**Author:** ![Patrick\_Dankers](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/patrick_dankers/32/94965_2.png) [@Patrick\_Dankers](https://community.homey.app/u/Patrick_Dankers)\ **Post date:** [March 9, 2026, 1:19pm UTC](https://community.homey.app/t/app-pro-football-data-org-automations-based-on-football-matches/146908/37 "2026-03-09T13:19:32Z")
Not yet mate, will let you know once I know for sure 🙂 **Edit 20260314** - All seems to be working well again mate! Thanks again! ---
**Author:** ![John\_William\_Brekke](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/john_william_brekke/32/111887_2.png) [@John\_William\_Brekke](https://community.homey.app/u/John_William_Brekke)\ **Post date:** [June 13, 2026, 2:15pm UTC](https://community.homey.app/t/app-pro-football-data-org-automations-based-on-football-matches/146908/38 "2026-06-13T14:15:27Z")
Why does it say “wo”? **Iraq (U) - wo 17 jun 00:00** ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/0/005bb52d8c9ac4d8ce5fc926379f6d7458b2292f.png) ---
**Author:** ![pendojoshua](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/pendojoshua/32/116452_2.png) [@pendojoshua](https://community.homey.app/u/pendojoshua)\ **Post date:** [June 14, 2026, 7:22am UTC](https://community.homey.app/t/app-pro-football-data-org-automations-based-on-football-matches/146908/39 "2026-06-14T07:22:26Z")
Wo is the Dutch string for Wednesday (woensdag). Appears that there’s some locale baked in the code. I’ll check it asap! ---
**Author:** ![John\_William\_Brekke](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/john_william_brekke/32/111887_2.png) [@John\_William\_Brekke](https://community.homey.app/u/John_William_Brekke)\ **Post date:** [June 14, 2026, 9:56am UTC](https://community.homey.app/t/app-pro-football-data-org-automations-based-on-football-matches/146908/40 "2026-06-14T09:56:20Z")
Thank you! [Previous page](https://community.homey.app/t/app-pro-football-data-org-automations-based-on-football-matches/146908.md?page=1) [Next page](https://community.homey.app/t/app-pro-football-data-org-automations-based-on-football-matches/146908.md?page=3)