Review before submitting a new issue or feature request

Before submitting an issue, please check these frequent questions and known limitations

• Many of the submitted bugs are not really errors in the integration, but rather questions about the configuration of the Lovelace card, or issues with a custom card. Please note, that what this integration does is, it update the state and attributes of the sensor entity and the calendar entity. It does not do anything with the way it is presented on the screen. I am happy to help (if I can), but please open these issues as question, not bug (I spend a lot of time trying to replicate it and check the code for possible clues). Below are some clues that can help to recognize an actual bug. Thanks for your help!

• Blueprints: The Blueprints create automations, that are triggered by the event garbage_collection_loaded from entities configured for manual_update. So make sure the entity has this configured. The event includes data that is used by the automation. So these automation can only be triggered by the event. Calling them other ways will not work. The update happens when Home Assistant starts, once a day after midnight, and when the integration configuration changes. So to manually trigger the update (e.g. when configuring a new automation), you can open the Integration Configuration and click through the two screens. This will trigger the update (give it few seconds for the automation to run).

• Translations: the way they work is, the state sensor is in English, and it is translated by the front end to the language selected in the user profile (if the translation for that language exists). There could be a number of users configured at the same time, each with a different language - so this way each will see the state in his language (the sensor obviously cannot have multiple states at the same time, so this is why the actual state stays in English, independently of the user language setting). The other reason is, that the state should not change when you change the language, otherwise the automations would stop working. The actual sensor state should be all in lower case. The translated state usually has the first letter capitalized (yes, there is translation even for English).

• The custom cards can do the translations on their own (e.g. the custom:garbage-collection-card). In this case, please open the issue on the website of this custom card.

• The easiest way to recognize a bug in this integration from a problem with your front end config is to

1. go to Developer Tools and click on tab States
2. under Current entities, type the name of your sensor in the filter
3. You can see the actual sensor state (not translated) in the column State
4. click to the (i) icon before the entity name to check the sensor state translated by this integration (top right corner) and attributes. If you refer to the sensor state, always include a screenshot from this card please. Thank you!

• The picture-entity Lovelace card in the example in README needs the sensor state to be either 0, 1 or 2. So if you configure the integration to verbose_state, it won't work (as the state will include the date, not number 0, 2 or 3)

• Translation of the month or weekday names in the state is not possible, unfortunately. Theoretically, it could work, but currently, the Jinja 2 implementation used by Home Assistant does not support locales. There is nothing I can do about that.

• You can create multiple entities by just adding new Garbage Connection integration entries. It will group all devices under a single Garbage Collection panel. You can add as many entries as you want, there is no limitation.

• If you want to delete the integration, please first remove the configured sensors (if you have configured them from in Configuration/Integration)

• You have to restart HA after installing are removing the integration.

Please respect the following rules:

1. Before creating a new issue, search the issues if a similar issue did not exist.
2. If you are a developer, consider creating a pull request with your suggested change. This is especially the case for translations. There are 2 files for each language - one translates the sensor values, the other the web-based configuration.
3. Use the provided templates - leave the headers and replace the instructions with your text.
4. Please use the device DOWNLOAD DIAGNOSTICS to include the configuration detail with the ticket. Without this, I will not be able to troubleshoot it. For bugs, please enable debug log level detail for the integration and include the log. It will help a lot to know what is going on. Thanks.