Hardware abstraction layer for broken devices to achieve uninterrupted data collection

[haaahaha]

Problems

When a device is swapped due to breakdown, I face these challenges:

1. Having to redo my automation
2. Energy monitor loses previous data

How do you guys overcome this?
Is there anything like a hardware abstraction layer?

[ShadowFist]

Here you go.

@haaahaha

Having to redo my automation

Why and how to avoid device_ids in automations and scripts

Background When you start writing automations, a device trigger seems the obvious choice. Everybody knows what a device is and it comes at the top of the UI dropdown list. [image] It works… but it is certainly not a “great way to start” because it is storing up problems for the future. Far better to use an entity, with state or numeric_state. This topic is part of the community-driven cookbook where you can find other topics you might be interested in or might like to contribute to. Devi…

@haaahaha

Energy monitor loses previous data

Adding new devices and replacing devices

The biggest favour you can do yourself is to rename entities to a functional name when you add new devices. Let’s say if you’ve added a new device, such as a smart switch to control a light and monitor its power. Let’s also say that the integration that allows you to add it to Home Assistant provides you with a technical entity ID such as switch.shelly_1pm_2f4dee. You should rename this to (for example) switch.living_room_lamp, which describes its purpose. Doing this will ensure that should yo…

[haaahaha]

Thanks, I eventually settled on using templates, so all my cards/automations will target AbstractLight

template:
  - light:
      - name: AbstractLight
        state: "{{ is_state('light.actual', 'on') }}"
        turn_on:
          action: light.turn_on
          target:
            entity_id: light.actual
        turn_off:
          action: light.turn_off
          target:
            entity_id: light.actual

[haaahaha]

Actual Light

Abstract Light

1. On my card, if I select an actual device, there is a 2nd line that tells me the device
2. But I can’t do the same with the AbstractLight, I was hoping it could show the ID of the actual device

Any ideas?

[ShadowFist]

@haaahaha

Any ideas?

Yes, follow the advice I linked to in my previous post.

You ignored the recommended way of dealing with your issue, came up with a convoluted way of dealing with it and marked it as a solution, despite the fact you will still need to rename light.actual if you change devices. Now you want me to help with a problem entirely of your own making?

I’m not willing to provide any further advice since this thread is apparently solved. Maybe someone else will stumble on this thread and help you fix it. In the meantime, you can (and should) do this.

[haaahaha]

You shared 2 links

1. 1st uses the template similar to what I did, maybe mine is more verbose than his, other than that, I don’t see the difference

2. 2nd link had no code, no idea how it helps

@ShadowFist

you will still need to rename light.actual if you change devices

Are you saying there is a way to replace a device without any renaming? Coz I don’t see it.

In my case, yes, I rename only in 1 template aka 1 place to rule them all, all automation and cards rely on the template name/id and not the actual entity/device IDs

Perhaps showing me a counter example to my template will help convince me I’m missing something

[ShadowFist]

@haaahaha

1st uses the template similar to what I did, maybe mine is more verbose than his, other than that, I don’t see the difference

No, the first just warns you not to use device IDs in automations and to use entities instead. You don’t need a template for it - you just have to get into the habit of not using device IDs in your automations.

@haaahaha

2nd link had no code, no idea how it helps

There is no code because you don’t need code. All you need to do is follow those 4 steps. You don’t need the template either. All you have to do when adding a replacement device is to rename it the same as the old one, so it’s still

@haaahaha

1 place to rule them all