Skip to content

Review before submitting a new issue or feature request

Jump to bottom
Vaclav edited this page Feb 9, 2022 · 5 revisions

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

  • The next_date attribute is not a text. It is a datetime value. The way it is displayed is controlled by HA, and it is consistent with other datetime attributes, such as last_updated. But because it is a value, you can show it in screen in whatever format you want. You can either use some custom Lovelace cards. Or format the value in whatever way you want using templates. For example, the next_date of entity calendar.england_holidays might show a datetime value 2022-04-15 00:00:00+02:00. Using a template {{ as_timestamp(state_attr('calendar.england_holidays','next_date')) | timestamp_custom('%a, %d %b %Y') }} it will show as Fri, 15 Apr 2022. Yes, it is a bit advanced, but if you are digging into entity attributes, I suppose you are on that level (and if not, then just don't do it).

  • In the holidays attribute the dates are formatted in an international standard format (ISO). They are not in any country-specific format, but in an international standard format that is unambiguous so that I can say what the date is, without clarifying the country format. I needed to do that as this is used in the automation blueprint for the integration with other entities. And without having a common standard format they just would not work. So I am not going to change that. Again, if you are looking at this attribute, this is quite an advanced topic, so I suppose you'd know how to convert them from the ISO format back to the date value and from there to whatever country-specific format you need.

  • You can create multiple entities by just adding new Holidays integration entries. It will group all devices under a single Holidays 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.

  • The integration is a backend component, that updates the device state. This means that all users see the same device state, and the updates happen even if there are no users logged in. In contrast, the way you display the sensor on the screen (Lovelace) depends on the user. For example, each user might have a different language configured, and you might therefore present the state in different formats.

  • Translations: The states are in all lowercase letters (and are in English), the English translation typically has the first letter capital. For example, a binary sensor might have the actual state off (to be used in automations), if you configured English as your language, on your screen, it will show as Off (the English translation). But if you chose Spanish for example, it will show as Apagado. This is how it works, please do not ask me to make the state to have first letter capital.

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.
  3. 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.
Clone this wiki locally