is a custom component.
You should report issues within the repository of this integration 
If you’re just looking for an argument, perhaps take this somewhere else, or get your hands dirty and contribute to the project. Either way, you’re trivialising this. Simple, fast, risky and efficient isn’t all the same.
In really big databases that must be online 24/7 it is not that simple. Actions like these will lock up a system with table/page/row locks (for one). If downtime cannot be scheduled, then you’d use tricks such as operating on a copy of a table (underneath a view), or drop your indexes to make the alter faster before re-adding the indexes (and/or the FK like they’ve done here). Even for an offline migration that can be too much. In the case of HA, people don’t run their systems on commercial hardware, even though a 10-100GB DB doesn’t seem that big.
Partitioning would’ve made no difference: When doing an alter, your DB needs to be fully consistent before you resume operation. It’s not like you can change one partition by itself. You can fake things under a view, but that adds a lot of complexity.
I think part of the challenge is that ideally you’d want to redesign the whole DB from the ground up, but that will make migrations very hard (changing a flying plane and all that). HA also supports many engines, which means you need to account for the quirks of each, and that you cannot fully utilise the specific strengths of certain engines.
7 Likes
hm… this could already be done.
You can add your individual water meters to the water usage dashboard, and they will be shown individually…
(Just similar, as you could also add your individual devices to the main electrical energy usage graph)
This should work just similar as in this screenshot
Looking like a nice release
I saw that the Energy dashboard now supports adding a “total” device that monitors the home power consumption as a total and it is then compared to the rest of the devices.
Does anybody know how/where to define that device?
In my case I have a Shelly 3EM monitoring total. I have been abusing the dashboard and set the Shelly 3EM to grid consumption and the individual devices as return to grid. That also gives me the delta. But the update should make that obsolete
So I would guess that somehow I need to tell HA to use the three Shelly 3 EM entities as total?
And does anybody know it the ista ecotrend integrations need some kind of manual input to pull the old data?
I do not see my old data after the update. One of my favorite updates of this release 
.
yes, this is - unfortune.
the best Idea I would have about this is - not to ‘replace’ the entity in the Dashboard Settings.
It really depends on the setup - if you get your measurements from the Meter via an IR reader, you could probably just replace the meter, and the IR reader will still continue to work - and continue counting.
If you are using something like a shelly, and this needs to be replaced, I would expect that the integration would probably create a new, additional device with its entities.
In this case, I would just add the new entity to the dashoard and also keeping the old one for the history.
If you need to replace a meter, which comes from your solar installation, it might be a bit more complex, ad it would depend on the integration if it will just use the existing entity with some ‘new’ values - or if it would create new entities…
With the help from @bdraco I managed to find key and the key slot from my old backup, and set it manually with new integration in my current installation:
I did a complete reset (factory reset) and set everything up again with a new account. The key is therefore out of date - I tested it from a backup.
Hi dev,
thanks again for your hard work!
I noticed that with 2024.9 release i was unable to start and stop motion detection on my camera (unifi video integration). i’ve test trough developer option calling the relate action!
Maybe this issue ?
In my case is unifi video integration, not unifi protect.
And the issue start from 2024.9, revert back to last 2024.8 release fix the problem
1 Like
Agree. But it’s not applicable every time.
I had sensors, lets say: house_1 and house_2 (because of 2 sections of the building). Both used to be assigned to the dashboard for total consumption.
Now I have wattsonic_meter.
I really don’t want to
- loose old sensors, because are still useful
- rename wattsonic_meter sensor to anything else, because the name indicates where it belongs (Regardless it’s impossible to cover 2 previous sensors with the new single one)
As long as an entity had a unique ID, it can be renamed. It’s not an issue in most cases.
Not sure about that. If an entity is created by an integration, the integration will reference it by its original name. It doesn’t know that HA changed the id. Obviously, it would fail in such a case.
IMO unique id is used mainly by FEs, to map original names with their user-friendly alternatives. But may be wrong of course.
Still, I see no big issue with creating “meta sensors” that would collect data from sensors assigned to Energy dashboard, making the dashboard independent from those source sensors. But it would have required coming up with this usecase (pretty obvious IMO) in advance, before the implementation of the Energy Dashboard.
Exact same issue here on NSPanel Pro… sections view doesn’t display anymore and browser gets stuck…
Peter is correct. Unique_id actually just ties entities to a config entry that holds parameters and settings for the entity that are managed by the UI. Things like unit’s, show as, name, entity_id, etc. All of which can be modified while still maintaining it’s original link to a configuration. It’s not just for friendly name.
Ok, does it mean, that after change of entity name, an integration which created it is still able to refer it by its original name? while the rest of the system (Energy dashboard) uses the new name?
Integrations don’t know entity_id’s, they create the object that HA stores in the state machine. So for all intents and purposes, nothing is changing.
If you’re asking about integrations where a user chooses a source entity, that still works because that system uses config entries first, then entity_id second. So if the entity has a config entry, you can rename things (entity_id) to your hearts content and all entities that use it as a source will be fine.
1 Like
Is there any documentation on how to specify a device as the total home power consumption meter?
it’s the one(s) you specify under " Grid consumption" on the energy dashboard, no?
Is there any documentation on how to specify a device as the total home power consumption meter?
“Consumption” is generally not specified, it’s calculated. Energy dashboard allows you to define all the energy coming into your home (grid consumption, solar), and all the energy going out of your home (grid return).
Grid In + Solar - Grid Return = Total Home Consumption.
Or if you don’t have solar, than simply Grid In = Consumption
1 Like
hey, does anybody have a clue why my tibber integration won’t work since this update? already tried reloading it, deactivated and activated it but it won’t work.
Thank you, but from the release notes I understood that if I have individual devices tracking grid consumption and in addition have a global grid consumption meter (e.g. the house meter), then the dashboard would now show how much grid consumption is not being individually monitored.
So with no solar and hence no return, all meters monitor consumption.
Or did I misunderstand the release notes?
We can’t all have energy tracking for every device, and if you have whole-home energy tracking (like a smart meter or something more DIY) the updated graph will calculate the difference and show your home’s untracked usage.