Thanks for creating this useful sensor!

In Sweden, every Sunday is considered as a holiday. This means that this sensor always returns 0-6 in "days until next holiday", and that the list of holidays is very long.

I am aware that I can explicitly list the holidays I want in my sensor, but I'd rather exclude the ones I don't want - such as the Sundays, in this case. Would you consider that?

Edit: I just saw some related discussion that referred to "include sundays" which can be passed when initializing the library. If it was possible to pass this parameter to the Holidays library it would solve my issue.

It is very nice to know, when the next holiday in future is (looking forward to the next holiday 😉)

Co-Authored-By: Niklas Stegmann [email protected]

Hi! I have an odd case: I have installed your sensor and i use attribute "today_is_holiday" as trigger condition in my automation: it will trigger only if it's false (so automation doesn't trigger when it's holiday). I entered automation via UI interface, and it never triggers. The cause is that automation assumes that result "false" is a string and creates this:

because this doesn't work:
condition: state
entity_id: sensor.next_holiday
state: 'false'
attribute: today_is_holiday

which doesn't work - automation ends with:

result: false state: false 
wanted_state: 'false'

If i correct it manually in YAML editor to this (note that false is without quotes):

condition: state
entity_id: sensor.next_holiday
state: false
attribute: today_is_holiday

Then it works. The point is that FIRST example is created by UI automation, while second is corrected in YAML editor. Of course with corrected automation HA complains with this error: The provided value for 'state' is not supported by the visual editor. We support (string) but received (false) Do you have any explanation for this behaviour or is it normal?

Hello,

The countdown of days in attributes is useful.

However, with an ISO8601 date time string exposed as an attribute for the next holiday, we can manually customise a countdown sensor or use it with other time related automations.

If it's not too difficult, it could be a nice to have extra attribute to expose with an optional config.