Really ? Lately i’ve been bombarded with HEMS/EMS/Energy widgets and Dashboards…
Perhaps the reason why Athom are making the request, to try and cut down on the crazy levels of app functionality duplication (which a lot of is probably AI generated stuff). It would be a lot better if developers collaborated and we had fewer apps with more functionality… and more devs working on fewer apps would also spread the debugging load. All in all a better end user experience.
Hi Robert, have you had a chance or found the time to take a look at this yet?
Regards, Wilfried
Hi there, yes it is great to open a PR. I recently did the same for Denmark. So shouldn’t be that big of a deal to fit it in. Just open a PR and/or issue on GitHub and we can handle it from there.
Yes, is waiting in the test channel already for some time ![]()
So you can install the test version from the store or wait a bit longer until everything has been fully tested ![]()
I used Claude to develop a web dashboard, but instead of submitting to Athom, I wrote a guide with all the prompts so it could be recreated. Post is in the dashboard section. @Drako74 maybe that’s another way to distribute, I thought it was a easier way with everyones differing requirements to a dashboard.
It’s a fair enough request from Athom, I just hope the work gets recognised somewhere along the way.
Ok is that /test after the store link or how do I get there? The latest version I see is from October 11 that is before I asked the question.
Ah, sorry, didn’t push it to the store I see… will check and let you know when it is pushed to the test channel.
I’m happy to hand over this app to you if you think your version is better. Saves me a ton of time ![]()
Sorry Robert, that wasn’t meant as a dig at you or your app! And no, I wouldn’t want to take it off your hands, you’ve built something really solid with all the provider lookups and that’s the bit I’d never want to maintain. The first PR is up (multiple collection days a week, robertraaijmakers/com.trashchecker#274 · Allow manual waste types to be…), nice and small, so have a look when you get a chance and let me know if the style’s ok before I send the next ones. Cheers, Simon
Thanks! Merged the MR, looks good! Clean and reusing of things that are there, like it!!
Will see if I can create a deployable package tonight for the test channel.
Thanks Robert, really appreciate you merging it so quickly, and glad the approach worked for you! ![]()
The second one is up now (#275), a different frequency for part of the year and a pause over winter, so garden waste can be weekly in summer and stop altogether in December. It builds on the same bits as the first, so hopefully it’s just as easy to review. No rush at all, whenever you get a chance.
Cheers, Simon
I noticed Danish isn’t in the locales yet now you’ve added the Danish providers, would a translations PR be welcome?
Hi Robert,
While #275 is waiting for you, I thought it best to check what you’d actually like in the app before I crack on with anything else, rather than throwing a load of PRs at you? So here’s what’s left from Bin Collections:
- Collected status: tap Collected on the widget or from a Flow and it moves on to the next collection, plus a “collection was marked as collected” trigger and an undo
- Reminders at a chosen time: “[bin] is collected tomorrow at 20:30” with your own time, including dual collection days
- Booked collections: one-off pickups like a sofa or a washing machine, shown on the widgets until the day has passed (it would build on your manual additions)
- Council calendar import (.ics): for councils that publish a calendar file, with entries matched to waste types
- Extra widgets: an upcoming agenda and a compact strip showing the next few bins
- Holiday moves: shift a collection ±1 or ±2 days for one collection, up to a date, or until switched off
- Translations: Danish, German, Spanish & Italian (as I asked just above)
I’m happy to do whichever you’d like, and to save us both some time I’d suggest grouping them into two or three bigger PRs, say Collected status & reminders first, then widgets & bookings, then calendar import. Does that work for you, or would you rather keep them small?
And if some of these don’t fit with where you’re taking the app, that’s absolutely fine, just let me know and I’ll leave those out ![]()
Cheers,
Simon
Hi Simon,
Sounds great!
-
Collected status: tap Collected on the widget or from a Flow and it moves on to the next collection, plus a “collection was marked as collected” trigger and an undo
—> Doesn’t make sense, why should I want to tap the ‘is collected’? But if you think this is a nice to have, sure, but make sure they disappear just like they do now (based on the today/yesterday widget settings). -
Reminders at a chosen time: “[bin] is collected tomorrow at 20:30” with your own time, including dual collection days ==> This can be done already through a flow, tags, etc. so no need to implement this
-
Booked collections: one-off pickups like a sofa or a washing machine, shown on the widgets until the day has passed (it would build on your manual additions) ==> I don’t think anyone is going to add this manually, otherwise they can already do so through the “bulky waste” which is basically everything that is bulky (sofa, washing machines
) -
Council calendar import (.ics): for councils that publish a calendar file, with entries matched to waste types ==> This might be a nice feature
-
Extra widgets: an upcoming agenda and a compact strip showing the next few bins ==> I think with the current configuration of the widget you can achieve a lot of this already, you can select what you want to see, how much you want to see etc. But if you have some nice ideas and can align them pixel perfect with the Homey style that might give people additional options

-
Holiday moves: shift a collection ±1 or ±2 days for one collection, up to a date, or until switched off ==> For all API providers this is already done (as they just provide the right collection dates). For schedule this can be done manually through the one-off / remove / addition. So what would the feature be here? If it would mean that you have to ‘check’ (as collected) your bins (feature 1) every time and otherwise it moves, then it doesn’t make much sense as it will involve a lot of manual clicks for the users. And holidays are a very, very small subset of collection days usually.
-
Translations: Danish, German, Spanish & Italian (as I asked just above) ==> I have to look, thought I did Danish already in the Danish branch, but otherwise, go ahead!
Hi Robert,
Thanks for going through the list, really appreciate the honest answers! It sounds like most of what’s left doesn’t really fit with where you’re taking Trashcan Reminder, which is completely fair, so I’ll hold off on any more PRs for now. #275 (seasonal frequency & pauses) is still there if you’d like it, so feel free to merge it whenever suits, or just close it if not.
The Collected button is a big one for us here in the UK, as councils do miss collections, so it’s handy to know the bin’s actually been emptied before the reminder goes away. With that in mind, and as Athom suggested, I’ve let them know and resubmitted Bin Collections as its own app for people who want to manage their bins that way.
Thanks again for being so welcoming, and for adding me to the contributors, it’s been a pleasure working on it with you! ![]()
Cheers,
Simon
Hi Robert, do you think you’ll still be able to publish the test version? I’m very curious and would love to test it out.
Kind regards, Wilfried
Sorry, been quite the week. It is in the test channel now
Trashcan Reminder 2.0 | Homey

