2022.2: Let's start streamlining!

Blog
920

Getting a negative number now:

image
image580×558 34.5 KB

This is my template sensor:

  • sensor:
    • name: solax_energy_grid
      state: “{{ states(‘sensor.solax_total’) }}”
      unit_of_measurement: ‘kWh’
      state_class: total_increasing
      device_class: energy
      attributes:
      last_reset: ‘1970-01-01T00:00:00+00:00’
922

It has been that way since 2021.9.

924

I just came to do the same thing. Been getting hundreds of errors with Spotify lately, and after reinstalling the integration, I found this.

925

It was working until 2021.12 :man_shrugging:

1 Like
926

Probably becasue of a bug that was fixed.

2 Likes
927

After 5 full hours of fixing and cool down just a moderate note for everyone possibly running into the same issue:

Problem:
Since updating to HA 2022.2 my Energy Dashboard stopped working. It‘s been in that state for more than 2 days and unfortunately I discovered this only 5 1/2 hours ago.

Reason:
This: https://github.com/home-assistant/core/issues/65773#issuecomment-1030628857

Fix:

  • I changed the state_class to total after being measurement before - as it was from the very beginning in July/August when Energy Dashboard / long-term statistics were introduced.
  • Then I fixed all data in the database which took me ~ 4 hours.

Summary:

Makes me feel a bit uncomfortable as I never read about “measurement” being deprecated. A warning in advance would have been nice. I’m just wondering as

Not sure how to avoid this in future. Maybe there was something implemented/fixed/changed without proper communication. Just a thought.
So even waiting for a .6 (2022.2.6) release is no guarantee for a bug-free update, learned my lesson :smiley: Probably need to postpone updates even further in future (1 month +) - which still is no guarantee for no corner-case bugs.

Take care - and always have a look at the Energy Dashboard 2 hours after updating Home Assistant. :wink:

1 Like
928

Same for me. I get this message: https://api.spotify.com/v1/me/player/devices with Params: {} returned 401 due to The access token expired

929

Release core-2022.2.7 does fix the Spotify session token refresh issue.

2 Likes
930

I have noticed that the binary sensor updater no longer works for me. The sensor indicates up-to-date but there is an update available. I think I have seen this since version 2022.2.3 or so…

931

I was on 2022.2.6 up until yesterday, when I got notification that the sensor indicated 2022.2.7 was available, which happened around 2:20PM EST. I was at work at the time, so didn’t update until around 6:15PM EST, when I ran my core venv update commands, which pulled down 2022.2.8. Apparently they released .8 only about 20 minutes earlier, lol. So it seems to be ‘working’ for me. I know it checks https://www.home-assistant.io/version.json once a day, but I’m not sure how the time of day is determined (possibly by the last restart of HA?).

932

Thanks! So it could be a timing issue and not a state change trigger…

933

or check specific version here : https://version.home-assistant.io/stable.json

1 Like
934

The updater binary sensor integration I use (and which I assume @Ih8rain2 uses) doesn’t check the version.home-assistant.io/stable.json url, it checks https://www.home-assistant.io/version.json.
(source: https://github.com/home-assistant/core/blob/f8d38a10253eab163c6527f395e6a82ff752a9f5/homeassistant/components/updater/__init__.py )

I’m pretty sure version.home-assistant.io urls (stable.json, beta.json, dev.json) are for Home Assistant OS and possibly Supervised, which have their own update check mechanisms.

935

Totally new to me. Previously not an issue but now after the updates it is. So what has changed? Still using the same updater checking the version somewhere in the same way. It did work and now it doesn’t …

936

How are you running HA (OS, Supervised, core)?
Do you see 2022.2.8 at https://www.home-assistant.io/version.json ?
Are you using the updater integration (may be part of default_config I believe) or another way of creating your binary sensor (e.g. is it a REST binary sensor you created)? If your not sure if it’s the integration, it should appear in your server info (Link to Info – My Home Assistant). Not sure if any of this will help…just throwing stuff out there to see if we can spot anything.

937

There were changes to the source code of version two days ago. I suggest you post an issue in GitHub.

EDIT. Remove the version setup in configuration.yaml if it is set up there. Then set it up again via ui.

938

yes I do see 2022.2.8 at(https://www.home-assistant.io/version.json)
Updater must be part of the default config. I created nothing.
.HA_version contains 2022.2.8 too.

No version setup in the config.yaml…

There is a version integration in my info list!

F4DF34B3-B837-4227-8549-45B978E8B396
F4DF34B3-B837-4227-8549-45B978E8B396960×2079 197 KB

20966F2A-02CE-4D23-B87C-746B7A58641F
20966F2A-02CE-4D23-B87C-746B7A58641F960×2079 161 KB

940

How do you say that? Have you looked at the docs? Version does not appear on the list.

941

The version integration does not appear in those pictures. Edit: Maybe I can’t quote both your pics, but I am referring to both of them!

942

The convo is confusing, but updater is indeed part of default_config
See core/manifest.json at dev · home-assistant/core (github.com) for the list (it’s just a list of dependencies)

1 Like