Automations copied works while original does not

Configuration Zigbee
1

Hi, I have 112 Automation rules ; 110 are DeConz-related.
Last week, DeConz gave me an error. After reconnecting de Conbee II, it looks like the IP-address of DeConz has changed. So I had to remove the old Hub and add the new Hub (all the devices paired with DeConz have the same name AND device-id !).
But none of the automations work !!!
To make them work, there is a simple bypass : open an automation, copy the name, duplicate the automation, save the new with the copied name (paste), exit the new one, exit the old one and delete the old one. But doing this 110 times… that’s asking for problems !
Strange thing… If I keep the old automation and I go into automations.yaml, the complete yaml for these two automations are exactly the same (except for the ‘id:’-number).
How can I make the old automations working without supidly copy-pasting them all one-by-one ?

2

Are you absolutely sure about this part?

What does a trace say on one of the ‘bad’ ones.

Also I assume you’re using devices in your automations - good time to edit them alm to use entity id’s instead (if the entity ID od the same it survives reinstalling or swithching integrations)

3

I’m more than sure !

  • id: ‘1711908841585’
    alias: LivInk-b-2k EetZ 0%
    description: ‘’
    trigger:
    • device_id: 5b6a62cc034932ea244f3cc961006dee
      domain: deconz
      platform: device
      type: remote_button_short_release
      subtype: button_2
      condition:
      action:
    • service: light.turn_off
      target:
      entity_id:
      • light.eethoek_zone
        data:
        transition: 1
        mode: single
  • id: ‘1712166735318’
    alias: LivInk-b-2k EetZ 0%
    description: ‘2424’
    trigger:
    • device_id: 5b6a62cc034932ea244f3cc961006dee
      domain: deconz
      platform: device
      type: remote_button_short_release
      subtype: button_2
      condition:
      action:
    • service: light.turn_off
      target:
      entity_id:
      • light.eethoek_zone
        data:
        transition: 1
        mode: single
        The first does NOT work ; the second (which is a copy of the first and to identify I added ‘2424’ to the description).

I found something else (which a normal living being should not check) in core.entity-registry :
{
“aliases”: ,
“area_id”: null,
“capabilities”: {
“id”: “1711908841585”
},
“config_entry_id”: null,
“device_class”: null,
“device_id”: null,
“disabled_by”: null,
“entity_category”: null,
“entity_id”: “automation.livink_b_2k_eetz_0_2”,
“hidden_by”: null,
“icon”: null,
“id”: “1d476f71e3ffbd7f16e07c0f6b61dd5e”,
“has_entity_name”: false,
“labels”: ,
“name”: null,
“options”: {
“cloud.google_assistant”: {
“should_expose”: false
},
“cloud.alexa”: {
“should_expose”: false
},
“conversation”: {
“should_expose”: false
}
},
“original_device_class”: null,
“original_icon”: null,
“original_name”: “LivInk-b-2k EetZ 0%”,
“platform”: “automation”,
“supported_features”: 0,
“translation_key”: null,
“unique_id”: “1711908841585”,
“previous_unique_id”: null,
“unit_of_measurement”: null
},
and
{
“aliases”: ,
“area_id”: null,
“capabilities”: {
“id”: “1712166735318”
},
“config_entry_id”: null,
“device_class”: null,
“device_id”: null,
“disabled_by”: null,
“entity_category”: null,
“entity_id”: “automation.livink_b_2k_eetz_0”,
“hidden_by”: null,
“icon”: null,
“id”: “7af9c41cca2d201c2d7bceb1c7731d67”,
“has_entity_name”: false,
“labels”: ,
“name”: null,
“options”: {
“cloud.google_assistant”: {
“should_expose”: false
},
“cloud.alexa”: {
“should_expose”: false
},
“conversation”: {
“should_expose”: false
}
},
“original_device_class”: null,
“original_icon”: null,
“original_name”: “LivInk-b-2k EetZ 0%”,
“platform”: “automation”,
“supported_features”: 0,
“translation_key”: null,
“unique_id”: “1712166735318”,
“previous_unique_id”: null,
“unit_of_measurement”: null
},
and
{
** “config_entry_id”: null,**
** “entity_id”: “automation.livink_b_2k_eetz_0”,**
** “id”: “52eaafa46d07cf3545fbcff70a8a93c5”,**
** “orphaned_timestamp”: 1711908891.5437758,**
** “platform”: “automation”,**
** “unique_id”: “1711652846244”**
** },**

4

The yaml before copy-paste :
alias: LivInk-b-3k ZitZ 100%
description: “”
trigger:

  • device_id: 5b6a62cc034932ea244f3cc961006dee
    domain: deconz
    platform: device
    type: remote_button_short_release
    subtype: button_3
    condition:
    action:
  • service: light.turn_on
    target:
    entity_id:
    - light.zithoek_zone
    data:
    color_temp: 350
    brightness_pct: 100
    mode: single

the result in LOG

image
image1088×352 47.3 KB

the YAML after copy-paste-deleteold :
alias: LivInk-b-3k ZitZ 100%
description: “2424”
trigger:

  • device_id: 5b6a62cc034932ea244f3cc961006dee
    domain: deconz
    platform: device
    type: remote_button_short_release
    subtype: button_3
    condition:
    action:
  • service: light.turn_on
    target:
    entity_id:
    - light.zithoek_zone
    data:
    color_temp: 350
    brightness_pct: 100
    mode: single

and its log now :

image
image1093×420 57.4 KB

(with extra attention at the automatisation that starts)

5

and it keeps being stranger… I just renamed the automatisation. After saving, the automatisations works again !
(so I have to rename my 110 automations to make them work).

6

Please format the automations using the preformatted text function when you paste so we can maintain spaces etc. It’s important in YAML.

Sounds like something got jacked up i the save and. You know the workaround. But id still STRONGLY suggest you over time change out your device references to entity id’s to prevent this kind of issue in the future.

7