Thanks for a awesome script.

When using Danish unique letters (Æ, Ø & Å) the sensor breaks. I'm not sure if there exists a official way to handle that issue regarding writing codes, but Home Assistant transform them to: æ: ae ø: o å: aa

Config

---
# https://github.com/mf-social/ps-date-countdown
alias: "[System] Date Countdown"
trigger:
  - platform: time
    at: '00:00:01'
  - platform: homeassistant
    event: start
action:
  - service: python_script.date_countdown
    data:
      name: Juleaften
      type: anniversary
      date: 24/12/1981
      icon: "mdi:pine-tree"
  - service: python_script.date_countdown
    data:
      name: 'Nytårsaften'
      type: anniversary
      date: 31/12/1981
      icon: "mdi:pine-tree"

Log

Log Details (ERROR)
Logger: homeassistant.components.python_script.date_countdown.py
Source: core.py:736
Integration: Python Scripts (documentation, issues)
First occurred: 4:01:51 PM (1 occurrences)
Last logged: 4:01:51 PM

Error executing script: Invalid entity id encountered: sensor.anniversary_nytårsaften. Format should be <domain>.<object_id>
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/python_script/__init__.py", line 205, in execute
    exec(compiled.code, restricted_globals)
  File "date_countdown.py", line 50, in <module>
  File "/usr/src/homeassistant/homeassistant/core.py", line 954, in set
    context,
  File "/usr/local/lib/python3.7/concurrent/futures/_base.py", line 435, in result
    return self.__get_result()
  File "/usr/local/lib/python3.7/concurrent/futures/_base.py", line 384, in __get_result
    raise self._exception
  File "/usr/src/homeassistant/homeassistant/util/async_.py", line 53, in run_callback
    future.set_result(callback(*args))
  File "/usr/src/homeassistant/homeassistant/core.py", line 994, in async_set
    state = State(entity_id, new_state, attributes, last_changed, None, context)
  File "/usr/src/homeassistant/homeassistant/core.py", line 736, in __init__
    f"Invalid entity id encountered: {entity_id}. "
homeassistant.exceptions.InvalidEntityFormatError: Invalid entity id encountered: sensor.anniversary_nytårsaften. Format should be <domain>.<object_id>

I'm aware of the use of friendly_name, but many names in Denmark fx have special letters.

Hi there,

since last update for some reason the "years" attribute became a negative value.

I have checked now the configuration and documentation to see if there was something new I wasn't aware of but it doesn't look like.

The config it's fairly simple, the only difference is that I am using the secret file to store the dates:

  - service: python_script.date_countdown
    data:
      name: Andrea
      type: birthday
      date: !secret andrea_birthday

Any clue?

Thanks :) Andrea

It’s not clear to me exactly how I define the birthdays... I see from the readme which fields you expect but what’s not clear to me is where I define these... Do they go in the configuration.yaml ?

HA 0.116.4 with python 3.9.0 Reminder - Refresh date countdown sensors: Error executing script. Unexpected error for call_service at pos 1: Unknown slice type: <ast.Constant object at 0x51578490> While executing automation automation.reminder_refresh_date_countdown_sensors

Hello, I think it would be great to allow appending 'years' to a sensors friendly_name, so for example... John's Birthday - 122 days would become... John's Birthday (50) - 122 days This way it's easier to spot milestone events

Cheers, James

Just made some small updates:

• If the date of event is more than 1 year in the future (like 2021 if current year is 2019), use the event date to calculate distance to event.
• add apostrophe to the friendly name of the sensor only if the event type is birthday. easy to change if desired.

Having

      - platform: time
        at: '00:00:01'

In the example automation means the sensor isn't created until that time. Best to remove that and have the sensor created on HA restart. Helpful for noobs like me.

With this commit, years will never be negative again.

• If the date is in the past, the diffrence between the next occurence year and the initial year is the number of years
• If the date is in the future, it has never happened so years will always be 0

Should fix #8