2021.9.0: More energy, USB discovery, template ❤️

loving the new area_id() function for templates (and the pipeline of developments Balloob discussed in the release party), I cant get my head around the new template entities 2021.9.0: More energy, USB discovery, template ❤️ - Home Assistant

What do we use that for? Can anyone provide an example of real life usefulness other than the given Wled examples. Are the new number and select replacing input_number and input_select, but now based on template value instead of user input? Trying to visualize the use cases , but fear I need a simpler example to graph its potential. thanks

I changed the value for “state_class” from “measurement” to “total_increasing” for my “solax_total” sensor by editing the “customize.yml” file.

Can you show me you’re exact yaml lines? I did try this but didn’t seem to work

No it isn’t.

That would be 2021.9.0

Make a backup then go for it. I did with zero major issues (some zwaveJS errors but all is still working)

The new features are ‘Energy’. Water has been able to be added as a consumption for a long time, but it isn’t Energy. Add your own Water consumption tracking, it’s not hard. The Integrations already exist.

1 Like

Ummm, just don’t update until the version gets to the ‘level’ you are happy with. No one forces you to update at 2021.x.0

2 Likes

No problems with the upgrade here. Running on Pi4 and seems to run smooth.

But I don’t understand why it’s made this difficult for people to use the Energy tab.

If you don’t have a straight out of the box solution (liking buying that meter) a lot of us got a headache to get everything to work.

Even making a simple input_number to use to calculate your costs is way too much work, specially with all those extra attributes that seems useless . How difficult can you make this thing to set up?

I’m still using my own take to get my energy monitored, all works great (without last_reset and other things that seems useless for a lot of us… Now the first update and suddenly you need total_increasing…), water included. Cause even after a month I don’t get it to work like my own stuff. And for sure not without a lot of reading.

It seems nice, but if you are new to HA and have to make new sensors, add attributes,… It would scare me away for sure.

image

The last_reset can be left out by the way because it’s not necessary anymore with this class, see: New sensor state class: total_increasing | Home Assistant Developer Docs (home-assistant.io)

1 Like

There is an easier way to do this.

  1. Create a Linux boot USB stick (Ubuntu / Debian / whatever)
  2. Boot the machine using the above USB stick
  3. Format the eMMC using whatever method within the above OS you prefer
  4. Install Etcher in the OS on the USB
  5. Download the latest HA version or copy from a second USB
  6. ‘Etch’ HA to the eMMC
  7. Remove USB stick
  8. Reboot
1 Like

:joy:Thank you for the laugh, have a great day!

same problem with example wled

Hi Fleeman,

I had the same issue. HA is restarting endless. I had to new install HA and restore my backup.
Regards
Speedy

No worries, I’ve had a few beers! :rofl: (typical Aussie)

2 Likes

I have the same error. Issue on Github:

Wondering since 2021.9.0 have not shown as of now or still on unstable version, is there away to force installation?

HA core update --version 2021.9.0

I am glad to not have updated my HA yesteday :slight_smile:

1 Like

Totally agree with you.
I think the name of the dashboard was poorly chosen, should have been the utility dashboard where of coarse energy plays an important role.
We have utility meters in home assistant so why not call the dashboard as such too?

I find this a great idea, I was thinking about the same for the monthly delivery fees in the Netherlands.
If this can be added, it would be appreciated to add an option to choose Daily, weekly or Monthly fixed cost.

I have a error when check config. No error on previous version

TypeError: ‘<’ not supported between instances of ‘SensorEntityDescription’ and ‘SensorEntityDescription’