[APP][Pro] Trashcan Reminder 2.0

Apps
,
346

Same here. issue #255 is created. Thanks in advance!

1 Like
347

For people searching and finding this topic. There is something wrong with Omrin at the moment. Hopefully they will expose their (new) API soon so I can implement it again :slight_smile:

Follow this thread for more information: [API]: Afvalkalender Omrin not recognizing my postalcode Ā· Issue #255 Ā· robertraaijmakers/com.trashchecker Ā· GitHub

1 Like
348

Versie 5.3.1 ā€” Wijziging in Tilburg en Venlo, nieuwe aanbieder ondersteund.
Dank je wel. MrDutchfighter

1 Like
349

Thanks @MrDutchfighter for fixing the Afvalkalender Omrin issue!

1 Like
350

Great app!

I have the following ā€œproblemā€œ. When GFT is going to be emptied, it will say the full name instead of the color of the bin. Please advise.

351

Did you changed the name under settings of the app?
Can you place a screenshot of that part so someone can take a look at it.

352

I never changed anything, never had a reason for it. But I checked to be sure and I found two BINā€™s now with the orange color, Plastic and PMD. So my guess is that this changed a while back ago and I did not notice itā€¦ PMD had the full description instead of the color, so I changed it to the color again. It should be fine now.

Thanks!

1 Like
353

I watched it also before i did post my other answer and i saw also that there is a Plastic and a PMD.
But i have no idea if this was always there.
My Homey says the line i have wrote at the PMD.

354

Hi MrDutchfighter,

Iā€™m a Homey user and developer. I recently submitted my own app called Kliko Calendar to the Homey App Store for certification. During the review process, the Homey App Store Team suggested that I reach out to you to explore whether we could collaborate rather than maintaining two separate apps.

The reason I originally built my own app is that I live on a corner where two streets meet. This means my waste bins can be collected from either side, depending on the week. As a result, I need to be able to use the collection schedules for two different addresses simultaneously ā€” something that Trashcan Reminder 2.0 currently doesnā€™t support, as it works with a single address only.

I was wondering: would you be open to adding multi-address support to Trashcan Reminder 2.0? Iā€™ve already done some development work on this myself, so Iā€™d be happy to share what Iā€™ve built or contribute to your app directly if thatā€™s useful to you. ( Homey/nl.klikokalender at main Ā· jankeesder/Homey Ā· GitHub )

Looking forward to hearing your thoughts!

355

Wasnā€™t planning on supporting it, but you are more then welcome to create a pull request with support for multiple addresses. You can fork the beta branch and start from there. Circulus is already supported, so hopefully not to much work.

356

Hi MrDutchfighter,

Thanks for the quick reply and for being open to collaboration ā€” I really appreciate it!

I did take a close look at the Trashcan Reminder 2.0 codebase before reaching out, and I think itā€™s a great and well-maintained app. However, after analysing what multi-address support would actually require, I have to be honest: itā€™s not a small addition.

Currently, the address is configured at the app level through the settings page, with a single set of global tags. Adding proper multi-address support would mean moving away from that model entirely ā€” towards a device-based architecture where each address is represented as a separate Homey device with its own capabilities, flow triggers and settings. Thatā€™s a significant architectural change that would also affect existing users who would need to reconfigure their setup.

Given that this is your codebase with its own conventions, existing users and release cycle, I donā€™t feel itā€™s realistic for me to take on that kind of refactor as an outside contributor ā€” it would simply take more time than I have available.

For my own use case (two addresses on a corner property), the device-based model I built in Kliko Calendar already solves the problem well. Iā€™ll continue maintaining that separately for now.

That said, if you ever decide to move in that direction yourself and want to exchange ideas or reuse parts of my implementation, Iā€™m very happy to help.

Thanks again for the open and friendly response!