thats is just the thing, that video is no longer happening, the value now is on the handle, and only appears when sliding. At which point it is no longer showing the static value is was before sliding…
I see what you mean. I think it would be best if when you clicked the color temp option, instead of showing a percentage for brightness at the top it should show the color temp. This is the way its working right now
I did a “like” for your issue filed on github and posted this .gif as well
3 Likes
this is new, why would this have happened, a spontaneous restart in the middle of the night, and apparently it wasn’t shutdown nicely because:
Logger: homeassistant.components.recorder.util
Source: components/recorder/util.py:332
Integration: Recorder (documentation, issues)
First occurred: 03:21:02 (1 occurrences)
Last logged: 03:21:02
The system could not validate that the sqlite3 database at //config/home-assistant_v2.db was shutdown cleanly
no obvious issues were recorded (mem % peaking, processor out of resources etc).
only thing that happened during that time was an auto-update of the Ubiquiti UDM pro.
could that have incurred an auto-restart to the HA instance? Note it wasnt a reboot of the device, only a restart of HA.
maybe the Unifi integration had an update that causes this (I mean we’ve havent seen this on earlier Unifi updates I believe)
The new thermostat cards extremely slow done UI in the web browser and iOS. Android looks still old and is performing well.
same here. It is a regression. The most important information is not easily readable any longer !
I start to be seriously tired of constant changes on Homeassistant !
This is no longer the case, the latest version shows those controls. If you don’t see them, that means you control your UI and you just have to add the feature. Edit the card and answer HVAC modes feature.
1 Like
core update 2023.12.3
Breaks my ZHA on my yellow. If I role back to version 2023.12.1 it works perfectly well but once update it seems like all my zigbee devices timeout should I be doing something? Like restore a zha back up or whatever.
edit
So far whatever reason when trying for a third time so i could get some logs etc it seems to be working ok for the moment. I have no idea whats changed but it works so Im not sure I care.
Installed version 2023.12.4… Big increase in memory usage on my two HA instances when moving from 2023.12.3 to 2023.12.4 (about 40% increase in one and nearly 60% increase on the other one, see graphs below… The version seems heavier (and slower) to load in my browser…
Update: I rebooted my two VM running HA, memory usage went back to the previous level (before upgrading to 2023.12.4) but slowness remains…
Problem is coming from firefox and card_mod (will open an issue), Google browser seems working fine with HA:
2023-12-27 13:47:33.752 ERROR (MainThread) [frontend.js.latest.202312082] Uncaught error from Firefox 121.0 on Windows 10
TypeError: Illegal constructor.
n (/hacsfiles/lovelace-card-mod/card-mod.js:1:10144)
_/< (/hacsfiles/lovelace-card-mod/card-mod.js:1:9380)
r (/hacsfiles/lovelace-card-mod/card-mod.js:1:15236)
_/< (/hacsfiles/lovelace-card-mod/card-mod.js:1:9380)
n (/hacsfiles/lovelace-card-mod/card-mod.js:1:32733)
_/< (/hacsfiles/lovelace-card-mod/card-mod.js:1:9380)
o (/hacsfiles/lovelace-card-mod/card-mod.js:1:45566)
C (src/scoped-custom-element-registry.js:388:6)
J (src/scoped-custom-element-registry.js:236:10)
ie/t/< (/hacsfiles/lovelace-card-mod/card-mod.js:1:39893)
I had a similar issue this morning with EDGE browser but I haven’t upated to 2023.12.4 yet. I clicked on the 3 vertical dots & reloaded resources and it self corrected.
In releas 2023.12.4 any news on the thermostat card?
I am still on November release.
Agreed- for what it’s worth, I use these and I see no reason to change all of my configuration- I don’t see any harm in leaving them in. if you don’t use them, you don’t use them.
No.
From what I can see on Github there is a PR to make the current temperature configurable as the primary information displayed on both the climate and humidifier cards. I also recall seeing a PR discussion about making the name clickable to allow removal of the more info button for extra real-estate for longer names.
Although these were merged last week, they don’t appear to have made this point release.
@Ih8rain2 - They appear to be in the 2024.1 beta - there is now (will be) a configurable option to pick the primary temperature displayed as being either the current temperature or the target temperature
1 Like
As you have been told (repeatedly) it may be in the January release.
2 Likes
I’ve had some issues with 12.4 as well (“had” as I’ve downgraded to 12.3 since).
In 12.4 a bunch of my automations for whatever reason include “delay” of 60secs when running, even the most basic ones => i.e. pressing a button on switch should turn on 5 lights; on 12.3 this automation lasts for 0.xx secs, on 12.4 it lasts for 60.xx secs (4 lights turn on immediately, 5th turns on after a 60 secs delay and whole trace lasts as said 60.xx secs). It’s not only when triggered by switch event, happens in different automations and with different triggers (movement, time, illuminance…) but it’s always 60secs delay. Quite funny.
Same hardware?
Everything is exactly the same, just different HA version. I’ve left it running 12.4 for 3 days with various restarts (of HA and Pi) to see if it would eventually “settle in”, but no luck.
What I’m asking is whether the devices (lights and switches) being acted on are all the same kind of hardware (brand) and thus using the same integration.
All zigbee, all in ZHA integration, but might not be all of the same brand.
Restored pre-update version immediately. All command_line sensors defined in configuration.yaml disappeared.