HomeAssistant ignoring some automations

Tags: #<Tag:0x00007f7399a4afb0> #<Tag:0x00007f7399a4ae20>

I set up a few (four) automations to start playing with HomeAssistant, one to switch on a Zigbee switch at a fixed time every day, one to switch it off at anoter fixed time every day, and two analogous automations for a Z-Wave switch.

Both the Zigbee automations have been working seemingly OK. The Z-Wave automations also started working fine, but then suddenly the “off” automation stopped working: the switch is switching on and off a test light and the light remained switched on when it was supposed to be off.

I looked at the Home Assistant log and found the following error message:

2020-10-17 19:12:05 ERROR (MainThread) [homeassistant.components.automation] Platform automation does not generate unique IDs. ID 1602794051632 already exists - ignoring automation.hotwateroff_3pm

I had created all my automations using the GUI, and the automations.yaml file, they are each assigned a different, unique, ID:

- id: '1602793646465'
- id: '1602793792422'
- id: '1602793996528'
- id: '1602794051632'

Finally, grep -r 1602794051632 . in the ~/.homeassistant directory only finds these matches:

./automations.yaml:- id: '1602794051632'
Binary file ./home-assistant_v2.db matches
./.storage/core.entity_registry:                "unique_id": "1602794051632",
./home-assistant.log:2020-10-17 19:12:05 ERROR (MainThread) [homeassistant.components.automation] Platform automation does not generate unique IDs. ID 1602794051632 already exists - ignoring automation.hotwateroff_3pm

So I cannot see any duplication of this ID.

Any idea what is going on? Since this automation is eventually meant to run hot water, it’s important that the “off” automation does reliably trigger when it’s supposed to. Many thanks.