2021.3: My Oh My

Blog
143

Was it ever?

I didn’t realise we had column edit.

144

Since at least 0.96 when i start play with HA

1 Like
145

Well I hope we get it back. Open a front end issue.

1 Like
146

I converted my numeric state triggers to template triggers and the issue went away:

- alias: 'GPIO Bridge 1 Memory Monitor Alert'
  trigger:
    # platform: numeric_state
    # entity_id: sensor.gpio_bridge_1memoryuse
    # above: 75
    # for:
    #   minutes: 5
    platform: template
    value_template: "{{states('sensor.gpio_bridge_1memoryuse')|float > 75 }}"
    for:
      minutes: 5
147

After updating the only devices synced to Google with Nabu Casa are 2 locks. I have 10 exposed items showing on the Google Assistant settings under Home Assistant Cloud. I’ve tried reconnecting, unlinking, relinking and restarting everything.

148

Hmm, the heater entity exists and works fine…thats why this log entry is strange

149

It probably is not available at the moment of startup

150

ok, fine. but how do i get my tasmotized sonoff ifan with off|low|mid|high functionality over mqtt to work again?
btw: axis cameras streams still don’t work, even the xhttp bug was fixed for months now.

151

I guess I’m not understanding this correctly … But so far, automations that are reporting these errors, seem to work fine.

Error in 'Radiator living room 25°C (if below 20°)' trigger: In 'numeric_state' condition: state of sensor.living_room_temperature is unavailable

For an instance, this automation opens my radiator valve if living room temperature drops below 20°C (numeric_state) - both devices are reporting via MQTT. I get this error (only) after restarting HA, but the automation still works, if the temperature drops afterwards.

I guess this should work too:

If you still think, I should create an issue (if you need examples/use cases), I’ll do that.

152

Is this really an issue? My automations gave the same errors on startup (also using RPI system monitor), but work fine afterwards.

153

Please do.

154

I signed up for the free account at Climacell. Using the Token from their website in the Home Assistant integration is giving “Invalid API Key”

Is “Token” on the Climacell site the same thing as “API Key” in the Climacell Home Assistant integration?

155

I have tried twice this new core version, coming from the previous version.
And I had the 2 same issues twice. So I rollback to previous.

The first one was almost expected reading the changelog : I’m using ZWaveJSMQTT with MQTT. I have 17 cover zwave modules. With this new core, I lost position for all my covers.
I’m a little bit suprised. Reading the changelog :
" MQTT cover value_template is deprecated to use for extracting position, support will be removed in Home Assistant Core 2021.6.
Instead of using value_template , position_template should be used. "
So I expected the current value_template to be still functionnal with this version.
But that’s no big deal, and as I said almoost expected !

My second issue however is a little bit more annoying and I’m surprised that nobody reported it yet ! This new core version broke the recorder when using MariaDB as database. After HA Core restart it works for a few minutes, write data in DB (I checked with PHPAdmin addon) and then I get this error in MariaDB logs :
“2021-03-04 12:05:18 24 [Warning] Aborted connection 24 to db: ‘homeassistant’ user: ‘hass’ host: ‘172.30.32.1’ (Got an error reading communication packets)”
and just after, nothing get recorded anymore in MariaDB db until I restart the core again and it works for a few minutes.
Nothing in HA logs.
Did anybody observe this ? or is this just me ?

156

Its functionality provided by the Supervisor, not the Core. The version number you shared is Home Assistant Core, which is not related to the Supervisor.

157

The thing is, this issue has always been there, it is just now telling you about it.

1 Like
159

After the update, Shelly Button 1 only shows one Entity - Battery percentage. Nothing more.

Someone with this device have the same problem?

160
  1. Not a user. Thousands of users.
  2. You nor devs should not rely on the fact that every user reads release notes.
    I understand the need of refactoring things and constant moving forward, but not for the price of user experience. Such changes should be done as transparent as possible.
161

I don’t care whether other people read release notes or not. And I disagree, in my opinion it should be expected from the end user to read release notes for an open source system that controls their home.

But as I said here, I don’t wanna discuss this anymore.

1 Like
162

Ah I see.

Good improvement then. :+1:

As it has enabled me to rectify it.

I think.

Or maybe I’ve just hidden the issue again. :thinking:

1 Like
163

Oh boy, this looks like a fantastic update! The UI changes are just what the doctor ordered and all the other updates are going to be so fun to explore and play with.

Thank you HA team and all the contributors!!! :heart: