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

Blog
111

after upgrade to 2024.2 I get an error reauthenticating Tuya. invalid hex color: rgb (32,33,36)
image

112

Read the comments about this above. The solution is there.

1 Like
113

Read the thread!

114

Beat ya to it :stuck_out_tongue_winking_eye:

2 Likes
115

Use the default theme

116

Thanks for the release !
However with 2024.2 I can’t voice control my garage door anymore.
Created a topic there: 2024.2 - regression with garage doors?

117

As always, here for integrations.

118

Certainly, this time frame can be customized for our own requirements.

119

Thanks for clearing this up! That’s just the way I would want it to work. :+1:

120

proximity is a very strange update, why was it necessary to remove the proximity domain, it was convenient.
And it’s not clear why this is at all, there was one proximity entity with a couple of attributes, now this entity has been replaced with 5 sensors, or even more sensors, I have 13 or more, as a result, there is no optimization in the database. The question is why?

Deprecate ‘beat’ display option in Time & Date - what’s wrong with this sensor? If it’s not needed, people don’t add it, and if people use it, they add it. Do a couple of lines of code really interfere with the HA architecture that much? Those. additional sensors in proximity do not interfere (although they put a load on the database) but does beat (swatch time) interfere?

1 Like
121

This template will give you .beat time

{% set time = (utcnow() + timedelta(hours=1)).time() %}
{% set sec = time.hour * 3600 + time.minute * 60 + time.second %}
{{ sec // 86.4 }}

If you put it in a trigger based template sensor on a 20 second time pattern, it should give you a reasonable accurate equivalent of the depreciated sensor.

1 Like
122

I have tried updating from 2024.1.6 to 2024.2.0 and it fails each time. I use the UK Met Office, I tried disabling this, but still the update fails.

All these updates are quite tedious, what we need is a long-term suported version that just works with new released properly tested before release.

2 Likes
123

This ZHA ziggbe automatic update seems like a future I’m searched for long time but I have a few question

You could already edit the configuration yaml to add auto update is this the same? Or what about this futures

Where will the zha download firmware from?

124

Same issue here updating from 2024.1.6

125

It took me less than 15 minutes to update, including a backup of the previous version. You should look at your logs to see what is going wrong.

126

But what is the point of removing a working sensor that is in use and carries zero load in the system, especially for those who do not use it? To add load to the templates?

1 Like
127

Another Tapo custom component what you need for that!

128

I don’t know, I was not involved in the decision making here.
I just wanted to provide an alternative for after it is removed.

3 Likes
129

You could have a look at the HACS integration Places — it does lookups based on gps cords and returns very precise address data from OpenStreetMap. You could then filter by postal code, building names or whatever to define zones.

1 Like
130

I understand, but this is a very strange solution, if there were problems with this sensor, it would depend on other libraries that are outdated, but here is banal mathematics that only works for those who have it in the configuration.

1 Like