Is it possible to use the thermostat and humidifier without an actual hardware thermostat? I have a heater and cooling fan attached as a switch and a humidifier and dehumidifier attached as a switch. Set points and on/off thresholds are controlled by a combination of input numbers and threshold sensors.
I’d love to have the clean UI from the thermostat tile, but it looks like it relies on one unified thermostat device.
You can create a generic thermostat with a switch and temperature sensor. I do this for my 3D printer enclosure when I needed to keep it warm in my basement with a smart switch and a cheap plug in heater.
https://www.home-assistant.io/integrations/generic_thermostat/
So this marks the end of the year of the voice I guess?
2023 has been the Year of the Voice, and please stay tuned, as we will host a final 5th chapter live stream on our YouTube channel on 13 December 2023, at 12:00 PST / 21:00 CET! But that is not the end of the voice journey… Be sure to tune in!
I took their recommendation and removed “purge_keep_days: xx” from my config. For the one thing that I’m interested in keeping data for an extended time, it defaulted to 10 days and deleted all of my old data.
Looking into it further, I had to edit that particular sensor and add “state_class: xx” (measurement, total, or total_increasing) as described here to get long term statistics working.
Time will tell, but hopefully I can start collecting more data. I’m bummed I lost my nice long term graph, but in the end maybe this will be better.
Edit: Now I’m on a tear going through all of my custom sensors and making sure they have a state_class associated with them. I’m learning that in some cases, I can configure them through the UI as a helper instead of in YAML.
It might be worth keeping purge_keep_days configured to less than the default 10 days to keep the database size small and speed up backups etc, especially in setups running on low power hosts like a Pi and with large amounts of sensors.
HA is configured to log everything into MariaDB (which does not get backed up) so my backups are only 84MB including most add-ons. I use the “Home Assistant Google Drive Backup” add-on and tell it what to back up and what to ignore.
I do have one problem with the new humidifier cards. Some buttons got shuffled around and now turning a device off and on went from being a single click to three separate operations. Additionally, it is less reliable now, as it won’t send a turn on/off command instantly, rather only when the state of the device changes in HA. I don’t toggle them frequently, but when I do I want it to be fast. I’m sure there’s some workaround for it, but it just worked previously and now it just doesn’t.
The new climate cards have configurable features. Edit the dashboard and climate card, and buttons similar the old ones can be added back the card. I was confused by this at first when I updated and the on and off buttons for my heating disappeared. It feels like the modes buttons should be added by default.
I’d suggest reporting to the second issue to the team in a github issue, it sounds like it may be unintentional.
The first is less likely to be altered, but you’re right that you can likely work around it. May be a good idea to look into the config options in case there’s a way to change button options, and worse case you can do a full UI mod like card-mod. Wouldn’t hurt to mention it in a different issue either, though it being an intentional change may not result in an alteration.
Going from your suggestions I was able to find a workaround to change the device’s state with just one click, so thank you for that.
For the second problem, it seems that while HA sends a command instantly, it only actually changes states on the dashboard once the device sensors update, which seems to be hard coded to happen about every 30 seconds. I am using an integration from HACS (Custom VeSync) though, so I feel like the problem is more likely to do with my own setup. Then again HA would previously just send the requested command no matter what the state was before…
Either way I’m not really familiar with Github beyond reading release notes and readmes.
Edit: Reading further into the integration I’m using, I realized that it relies on cloud polling. I wonder if there’s a way to make Home Assistant assume that a command went through, change states immediately, and then confirm the change with the next polling cycle, rather than just waiting. Unfortunately I don’t know how to implement something like this.
Why did they make the change to ping, dropping the interval setting? I looked through the linked pages but didn’t see an obvious explanation. I assume there is a reasonably good reason for it.
The suggestion to remove the recorder days is interesting. I have mine set to just a few days, because the partition the database is on its low on space, and I haven’t gotten around to dealing with it. Storing more in the same space would be good. I didn’t understand how the database would be smaller despite having more info.
The last update broke zigbee for a month, so forgive me if I don’t jump on this bandwagon.
What went wrong for you? I didn’t have any problems with the last one or this one so far (I use Z2M)
Sorry, I forgot about this thread, but I was reminded today when I saw the new bug. The issue that originally affected me was https://github.com/home-assistant/core/issues/103208. It broke Xbee users, so not everyone. My Zigbee integrations didn’t work after the update so I had to roll back to a backup for my first time with HA. A patch was developed, but it didn’t get integrated into any of the 2023.11.x releases, which I found kind of frustrating but I figured I’d wait it out and eventually there would be a version that works again.
Fortunately I held off on 2023.12, because according to https://github.com/home-assistant/core/issues/105344 a bunch of people are having problems with this release too.
Well I’m glad that you were able to get it to work again then and that it is fixed now
