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…