App doesn’t work for Limburg.net… cant choose any fractions.
@s73nm
Great question, and good news: what you’re describing already exists as condition cards.
First, the timing of the WHEN triggers:
- “Collection today” fires once on the collection day at 06:00 (and catches up if your Homey was offline).
- “Collection tomorrow” fires once the day before, at the hour set by that location’s Reminder setting in the app (default 12:00).
I’ve added these notes to the trigger hints in v2.3.5 so it’s clear in the app itself.
But for exactly your use case, use the condition cards instead:
- “There is a collection today at [location]”
- “There is a collection tomorrow at [location]”
Pair them with any trigger you like, a time of day, arriving home, a button, so the check runs when you want and the WHEN timing no longer matters. For example: WHEN I arrive home AND there is a collection tomorrow → notify me to put the bin out.
@GertCorstjens
Good news, Gert: Limburg.net is now supported as of v2.4.0 (test build). When you add a location, pick “Limburg.net” as the data source, then choose your municipality, street and house number. Reminders, Flow cards, the dashboard widget and iCal export all work the same as for Recycle! addresses. (The recycle-park action stays Recycle!-only.) Give it a try and let me know if your pickups show up correctly.
Thanks for the app!
Unfortunately, for Limburg.net, the wrong fraction is proposed: tomorrow should be “Tuinafval” while “Keukenafval” is proposed.
Regards, Chris
Thanks Chris, good catch, that was a real bug. Your municipality collects one combined organic fraction that the data calls “GFT” (groente-, fruit- en tuinafval, so including garden waste), but the app was relabeling it as “Keukenafval”. Fixed in v2.4.1 (test build): GFT now shows as its own “GFT” fraction. Municipalities that split Keukenafval and Tuinafval are unchanged. Update to the test build and it should be correct. Let me know if anything still looks off.
Thanks for the screenshot! In v2.4.2 (test build) the widget has more space below the last row, so it no longer sits against the bottom edge of the card.
Thanks for the quick reaction.
Indeed, 1 week they collect the GFT Container, the other week they collect the seperate plastic bags with Restafval, PMD, Keukenafval, Tuinafval (for those who don’t have a GFT container) and Textiel.
I’ve updated it but so far it keeps saying Keukenafval for today. Maybe it updates only overnight?
Thanks for explaining, that makes it clear. You’re right: the calendar is fetched once a day, so after the update your Homey still had the old data. To fix it now, open the app settings and press “Alles vernieuwen”, or wait until after midnight. From v2.4.3 on, the app fetches the calendar again right after every update, so this won’t happen again.
Also note that on the bag weeks Limburg.net really does list Keukenafval and Tuinafval, so on those days “Keukenafval” can be correct. If you have a GFT container and only want reminders for that, untick Keukenafval and Tuinafval in the fraction filter of your location. Then you only get GFT, Restafval, PMD and Textiel.
Looks like something is going wrong with Limburg.net
{
“app”: {
“id”: “be.recycle”,
“version”: “2.5.3”,
“sdk”: 3
},
“homey”: {
“language”: “nl”,
“timezone”: “Europe/Brussels”
},
“locationCount”: 1,
“locations”: [
{
“idx”: 0,
“name”: “Vincent Ducate”,
“provider”: “limburgnet”,
“language”: “nl”,
“bringInHour”: 18,
“customPickupCount”: 0,
“reminderHours”: 12,
“earlyReminderHours”: 24,
“urgentReminderHours”: 4,
“quietStart”: null,
“quietEnd”: null,
“trackedFractionCount”: 0,
“fractionOverrideCount”: 0,
“cacheCount”: 0,
“lastFetchedAt”: “2026-10-18T16:15:42.388Z”
}
],
“events”: [
{
“ts”: “2026-10-18T12:20:42.650Z”,
“kind”: “scheduler”,
“msg”: “Scheduler starting”
},
{
“ts”: “2026-10-18T16:15:30.510Z”,
“kind”: “api”,
“msg”: “Limburg.net month 2026-10 failed: Limburg.net 500: {“error”:“Er is iets mis gegaan”}”
},
{
“ts”: “2026-10-18T16:15:33.423Z”,
“kind”: “api”,
“msg”: “Limburg.net month 2026-11 failed: Limburg.net 500: {“error”:“Er is iets mis gegaan”}”
},
{
“ts”: “2026-10-18T16:15:36.823Z”,
“kind”: “api”,
“msg”: “Limburg.net month 2026-10 failed: Limburg.net 500: {“error”:“Er is iets mis gegaan”}”
},
{
“ts”: “2026-10-18T16:15:39.584Z”,
“kind”: “api”,
“msg”: “Limburg.net month 2026-11 failed: Limburg.net 500: {“error”:“Er is iets mis gegaan”}”
},
{
“ts”: “2026-10-18T16:15:42.387Z”,
“kind”: “api”,
“msg”: “Limburg.net month 2026-12 failed: Limburg.net 500: {“error”:“Er is iets mis gegaan”}”
},
{
“ts”: “2026-10-18T16:15:42.391Z”,
“kind”: “scheduler”,
“msg”: “refreshed Vincent Ducate: 0 collections”
},
{
“ts”: “2026-10-18T16:15:42.392Z”,
“kind”: “trigger”,
“key”: “calendar_refreshed”,
“locId”: “loc-8nr7lko0mq8950zq”
},
{
“ts”: “2026-10-18T16:15:54.339Z”,
“kind”: “api”,
“msg”: “Limburg.net month 2026-10 failed: Limburg.net 500: {“error”:“Er is iets mis gegaan”}”
},
{
“ts”: “2026-10-18T16:15:57.123Z”,
“kind”: “api”,
“msg”: “Limburg.net month 2026-11 failed: Limburg.net 500: {“error”:“Er is iets mis gegaan”}”
},
{
“ts”: “2026-10-18T16:16:52.003Z”,
“kind”: “api”,
“msg”: “Limburg.net month 2026-10 failed: Limburg.net 500: {“error”:“Er is iets mis gegaan”}”
},
{
“ts”: “2026-10-18T16:16:54.753Z”,
“kind”: “api”,
“msg”: “Limburg.net month 2026-11 failed: Limburg.net 500: {“error”:“Er is iets mis gegaan”}”
}
],
“generatedAt”: “2026-10-18T16:17:02.365Z”
}
@Vincent_Ducate
Thanks Vincent, the diagnostics made this easy to find. Limburg.net only accepts digits as the house number. Something like “12A”, “12 bus 2” or “1-3” makes their server fail with exactly that error. Version 2.5.4 sends the number and the letter separately, the way their own website does. Could you tell me if your house number has a letter or a box number in it? Once 2.5.4 is live, open the settings and tap Save on your location (or just wait for the nightly refresh) and the calendar should fill again.
Yes, the number is 21a
Changed 21a to 21 and now it works perfectly. Thx
@Vincent_Ducate
Great, thanks for confirming! That was exactly the cause. With 2.5.4 you can also put “21a” back if you like: the app now sends the 21 and the “a” separately, so both work. In practice the calendar is the same for 21 and 21a, so if it works now there’s no need to change anything.
