Those are the sensors that duplicate the plug’s attributes. This has been the situation for months in preparation for the removal of the attributes in version 2022.4.0.
In the August 2021 release, we deprecated all energy-related attributes from switches. The attributes are: current_power_w and today_energy_kwh. Those attributes should have been separate power and energy sensors instead.
All integrations affected were notified on July 22, 2021, of requiring a change.
There have been some fixes contributed and some in announced, that are coming in right now. We’ll make sure to include as much as possible in the next patch release (soon™ )
The MariaDB backup issues have recently been fixed/improved. They should be gone.
ok, thou i first started with this HA in November, i think, thou i actually read “some” of August release, but apparently “skipped” this part, … have 2x3 “warnings” … guess i have to remove those “Attributes” , have already made “separate” sensors
This may well be what I was seeing however even restarting MariaDB and rebooting did not appear to solve my issue. I did indeed think my DB was nuked…
To be honest, with all the performance/database/storage improvements from the past year… there isn’t much reason to use MariaDB/MySQL with Home Assistant…
(Sorry, bit of sidetracking).
Even with ~2000 entities? I guess I could simplify my maintenance if I can revert back to the regular DB.
I have honestly also started to think like-vice past month(Now that i got sqlite under control, good im not “The fastest snail in the forest” 
, i can “lean back” and enjoy the summer instead
Even with 2K entities 
I cannot find the new backup feature, am I losing it? 
Well there is one reason…
I use the Google Drive Backup, and no matter how efficient the sqlite database is, it’s still going to result in backups over 1GB+ surely?
My backups right now are about 15MB.
+-----------------------+-----------+
| Table | Size (MB) |
+-----------------------+-----------+
| events | 766.19 |
| states | 449.16 |
| statistics | 108.23 |
| statistics_short_term | 34.06 |
| statistics_runs | 0.05 |
| statistics_meta | 0.03 |
| recorder_runs | 0.03 |
| schema_changes | 0.02 |
+-----------------------+-----------+
Wow there has definitely been some improvements in recent releases, my MaiaDB used to be about 4GB.
I use Google Drive Backup too, and have both MariaDB and InfluxDB. My nightly backups are 1.1GB.
My MySQL is not on the same machine, I am not using the MariaDB addon, I host the database on a different machine on the network.
Right, using an external host I presume.
That can work in some cases, but it also means your backup isn’t complete (you took the DB out) 
No matter which Home Assistant supported database solution you can take the database out of the backup, E.g., by using MySQL or PostgreSQL externally (or an add-on), or by moving the SQLite database to a location that is out of reach for the backup process. All solutions will end up doing the same as you did (presumably).
That is unrelated to performance or handling of runtime performance
Saying your backup is faster or smaller is not completely true either, as the database is not part of the backup (or restore) either anymore.
In general, most people should just use the built-in SQLite database. It is tested extensively and its performance became really good (even better this release!)
Does backup not exist in HA Docker? That is the only thing I can think of as to why I cannot find it
While I don’t plan to move back yet (because if I lose the database in a catastrophic failure, that is not as important to me as losing Home Assistant - and thus things like being able to control my heating). The fact that the built in database, should be friendlier on SD Cards, means I should be able to take a copy of my my existing setup, run the beta on a Pi and restore my last backup to it, and then edit config to comment out the recorder - and I won’t have a clash with 2 instances writing to the external database. This will make it much easier to be a beta tester - so this is excites me greatly. Thank you.
Do you use Tibber:Custom ?
Thanks! Awesome, missed that
Maybe it is just the example the team chose to use but you could already use a template to show which entity triggered an automation as per the following:
- service: tts.google_say
entity_id: media_player.google_speakers
data:
message: "{{ trigger.to_state.attributes.friendly_name }} appears to have been left open.
Does anyone have a better example of how variables could be used to good effect in automations?
So I decided to try and move a backup from my virtualbox HAOS to a docker install.
It seems in the docker version, there is indeed a backup, but no restore?
In HAOS, I just click on the backup and restore it. In the docker version there is no dialog?
I tried making a backup on the docker box and then copied my existing backup to the folder and restarted HA.
The backups show in the list, but they are not actionable.