2024.2: More voice, more icons, more integrations, more... everything!

For me the update from 2024.01.06 to 2024.02 resulted in the Honeywell Total Comfort (EU) integration not starting anymore : “Error during setup of component evohome”.
Rolled back and it’s working again. Unfortunately I lost the log message :frowning:

For the new proximity integration it doesn’t look like there is any option to select different units (miles and/or feet). Is it intentional or an oversight?

I’m fairly sure I know the answer will be to just create a new template sensor for the miles sensor. But I figured I’d ask just in case.

You can change the units of every numerical sensor in the cog wheel.

mi is miles.

EDIT: On the ‘nearest device’

EDIT EDIT: Make sure you’re not looking at the old proximity entities that are still being imported. Those won’t have this functionality, only the new entities.

1 Like

How much free disk space I need to perform the update? (Home Assistant OS - Generic x86_64 image)

This is my first time using Tuya so I’m not sure if it’s user error or a bug in the way Tuya is added but I have a fan that I want to integrate with HA and the light portion of the fan works but the fan entity does not.I can see it but it’s greyed out and not usable.

image

Check the entity, if you had the fan before in HA, it most likely is added with an additional _2 , or it could be disabled for some reason

All state icons in Dwains dashboard are gone in this latest release.
How to get them back?

roll back to the “optional” backup , and report it in Dwains github repo

This particular fan is new and the first time being added to HA and the first time using the Tuya integration. I don’t see anyway in the Tuya app to have it enabled but I could be missing something.

edit: Looks like a known issue. Found this in Github Tuya: Fan with light fails to add/poll the fan properly, light works correctly · Issue #97538 · home-assistant/core · GitHub

1 Like

Thanks, would never thought of that, I’m now connected to Tuya again.

I got the Tuya QR time-out while thinking (too long obv.) of a way to scan the QR as displayed on my phone with the Tuya app on my phone :sweat_smile:
In order to get a new QR, I rebooted HA several times which obv. didn’t help.

So, is it possible to add this workaround as a tooltip / sidenote or something similar, to the QR code screen?
Like
“When Tuya says ‘QR code is expired’, just hit ‘Submit’ to start all over”

Thanks!

1 Like

We will lose accuracy, here we need either 86.4 or it goes out at least once per second (but this will increase the load, although not significant), it turns out to leave the sensor as is, a more optimal solution. Both from the point of view of ease of configuration in the GUI, and from the point of view of performance.

1 Like

Listen, I said I don’t want to discuss this. Please respect that, thanks.

2 Likes

As of the update my GARMIN and LG integrations stopped working. The publisher of the LG integration says, that I have an outdated PIP version and should upgrade it.

Can this be so? I have no idea how to go about the upgrade.

Running HA in a PROXMOX (all updates done) VM.

Best regards from Germany

If they are custom integrations, make an issue in the integration. They just need to bump the version inside the manifest files. They’d need to bump it to a version that works in Python 3.12.

3 Likes

While you can change the units by customization it doesn’t look like you can have more than one sensor for the same person/zone combo.

right now I have one for miles and one for feet. I can’t do that now with the new integration. If I try then it gives me an error that device is already configured.

And I’m still not sure if it does the recalculation yet tho

For example if the calculated distance is 5280 feet and I change the units to miles does the sensor value change to 1 mi? or does it now say 5280 miles?

I haven’t updated my production instance to the new version yet and I don’t have any geolocation sensors to track in my test instance so I can’t test that functionality.

1 Like

You can. It will create an _2.

It recalculates. Just try it. Takes 2 seconds to flip it and look at the result. This is standard for all unit conversions now. Been like this for some time.

If you have any unit conversion sensors in HA like a temperature, it’s the same behavior. You can try it on those just to see how it works. We are no longer held to the old days of unit conversions. It’s been like this for about a year now, maybe more.

1 Like

All these unit conversions you see on this page are supported and recalculate, without updating, you can try it on any of these entities if you have one:

1 Like

Icons Everywhere! Except everywhere they used to be. Custom button cards, mushroom cards and more all lose their icons. I now have to define a lock icon and separate unlock icon based on the state of my door lock. That used to happen automatically. None of the mushroom icons are there unless specifically defined. Huge pain to re-code everything when the icons should be there already.

no, you have to update those custom cards
button-card has been fixed during beta, not sure about the others, though I suppose Mushroom was also updated given who the author is.

as said, update your cards. Painless.

4 Likes

Running HA Core VENV on Python 3.11.5, upgraded to 20224.2.0 and HA is randomly restarting. Anyone else seeing this?