Although the Home Connect integration is mentioned as “not really a breaking change” it broke mine in this case. A restart of Home Assistant did not help. This is the error I get:
Logger: homeassistant.config_entries
Source: components/home_connect/api.py:163
First occurred: 07:55:35 (1 occurrences)
Last logged: 07:55:35
Error setting up entry Configuration.yaml for home_connect
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 383, in async_setup
result = await component.async_setup_entry(hass, self)
File "/usr/src/homeassistant/homeassistant/components/home_connect/__init__.py", line 269, in async_setup_entry
await update_all_devices(hass, entry)
File "/usr/src/homeassistant/homeassistant/components/home_connect/__init__.py", line 293, in update_all_devices
await hass.async_add_executor_job(hc_api.get_devices)
File "/usr/local/lib/python3.10/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/src/homeassistant/homeassistant/components/home_connect/api.py", line 99, in get_devices
{CONF_DEVICE: device, CONF_ENTITIES: device.get_entity_info()}
File "/usr/src/homeassistant/homeassistant/components/home_connect/api.py", line 353, in get_entity_info
program_switches = self.get_program_switches()
File "/usr/src/homeassistant/homeassistant/components/home_connect/api.py", line 163, in get_program_switches
return [{ATTR_DEVICE: self, "program_name": p} for p in programs]
TypeError: 'NoneType' object is not iterable
Very good move. Another way is to reduce the size of stored data. I’m quite new in home automation but quite old in industrial automation (1980s, blast furnace) in that time computer was incredibly low powered and storage space incredibly low too.
After few weeks my home assistant database reach several GB so I delete everything and filter all analog data before stored. Found no way to do it easily in home assistant itself so I do it in Node-Red:
1- Apply a real (time relative) 1st order Low Pass Filter (filter in home assistant is event relative) to remove noise in measurement and comply to Shannon Théorem (as I will resample data at lower rate):
where “dt” is delta time between event, “tc” is time constant (configurable) of filter
2- Transmit only few event for storage:
Transmit event to recoder
IF
( filtOutput variation greater than a configurable threshold
OR
last recorded event since more than one hour )
AND
last recorded event since more than one minute
This way I have maximum one data recorded every minute (this is the resampling rate for Shannon Theorem) and minimum one data recorded every hour (to avoid days without any data recorded for measurement that never change like setpoints)
As the result, I divided the size of my database by 1000. (Before some very verbose sensor flooding my database with events every second for a very low, no significative, value change)
If this kind of filtering was added natively to home assistant I think it should be a great improvement
Thank you for the update.
Everything is fine.
My 2GB database took 2h during night with Pi4.
For those having huge data, just consider to call purge recorder service before, that would reduce the size.
All are fine, really happy on that release with DB enhancements.
I’m not using card-mod (not so much) but well mushroom and plenty of hacs custom which are fine.
After teh update, I have a problem with ONVIF integration. I get the error message below:
The date/time on Kamera Kert (UTC) is ‘2023-04-06 05:41:53+00:00’, which is different from the system ‘2023-04-06 04:41:53.617908+00:00’, this could lead to authentication issues
If I check the time, every device have correct time. (Cam, Home Assitant, Virtual Machine)
Guys, can’t express my feelings on how happy I am using Home Assistant. Great thanks to all of you for all hard work done to get the project moving!
Questions, is this alarm control panel entity something new? can it be hooked up to existing motion and camera entities and send notifications, activate alarm?
In addition, also noted while not all do, more than a few fan controls feature 4-speed fan control to adjust fan speed from max, high, medium, low, to off (as in, they need four fan-speeds + an on/off button). Ex:
I’m getting lots of [SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert handshake failure (_ssl.c:997) errors after the upgrade. Have not found the cause of those yet. Help would be appreciated.
The alarm control panel integration is not new and to clarify that is only a UI interface for the “alarm control panel” integration (a virtual “panel” to activate or deactivate an alarm system, as in a representation of a physical alarm control panel device), so it is not a whole “alarm system”.
You can however connect it to your own DIY alarm system based make one yourself from scratch using the “Manual Alarm Control Panel” for base it on “Alarmo” (custom integration by nielsfaber)
Regarding Polymer removal: in the documentation we can see:
In Home Assistant 2023.4, we will log a warning every time Polymer is accessed. If you got a log message, find the custom card, panel, or more info that uses Polymer, and notify the author of this deprecation.
and indeed I now see several entries in the log file, that looks like:
WARNING: Polymer will be removed from window in Home Assistant 2023.5. More info: https://developers.home-assistant.io/blog/2023/04/04/deprecating_polymer
So I guess I’m in the same shoes as plenty of us using custom cards that use Polymer yet. Would be nice thoigh, if message posted in the log point us to the proper place where the Polymer was called from. Having 7 such messages and 34 different custom cards in my config, it is really hard to find where to go to to for support. Obviously waiting for 2023.5 and checking what stopepd to work is a solution… but not THE solution. Otherwise we can also wait for developers to realise that changes need to be made, but as highlighted several times in this thread sometimes it takes time… or even components are no longer in active development.
Thanks for the update. I noticed that none of the entity states are being translated to my language (Swedish) anymore. They are all in English. The rest of the UI is in Swedish though.
I really wish HA team decides to split the Dashboard and Core components (frontend and backend), so we can update them separately and its features. Don’t get me wrong: the Dashboard looks a lot better than a few years ago, with many added features, however, I don’t agree with some of its choices and keep having to update my Dashboard to maintain my own desired look. I want to use the Core updates, but I want to use my own take of the Dashboard.
I would really love te see the HA Core and the Dashboard to be separate so users can still update Core, but keep their Dashboard version. And yes, I know that custom cards are the ones that break, but guess what: without all the hard work of those devs, the community would have been a lot smaller. Also, I don’t like the way all new dialogs work (lots of wasted space also on mobile) and don’t agree with the design they’re going for. Which is fine if HA team thinks is best for their own vision. This is why I would see the Core and Dashboard as separate parts the way to go.
P.S. this is not criticism to the HA team by any means. But thinking back I realize that the most of my time now that goes into HA, is after an update messes things with how Dashboard (Lovelace) operates. My system is very robust and actually rarely I need to tinker with anything. But after each major release I’m holding my breath what changes the frontend has, since it will completely break stuff with forced changes. Even small things like force adding borders suddenly, which means I need to first find out what is happening and why, and then solve it updating themes, which is a core component, is just not the way to go on the long term.
Anyway, as I said: all love to the HA dev team for all their hard work. Just hope this is something they will think about as the community keeps growing and HA keeps getting new features/updates and HA team itself will probably grow as well.
Perhaps this means I need to find my own way of creating a standalone Dashboard, instead of the HA built-in one using API’s (which is probably what many would say as a reaction).
When i restart HA, i now see this in my log, this was not before in < 2022.3
Probaly the integration is still loading up upon restart, and value is unknown at that time, seems the utility meter is too quick in processing data?
2023-04-06 10:01:15.237 WARNING (MainThread) [homeassistant.components.utility_meter.sensor] Invalid state (unknown > 0.021)
- name: Water Usage l to m3
unit_of_measurement: "m³"
icon: mdi:water
state_class: measurement
state: >
{{ states('sensor.water') | float(0)/1000 }}
water_usage_hourly:
source: sensor.water_usage_l_to_m3
name: Water Usage Hourly
cycle: quarter-hourly
delta_values: false
unique_id: water_usage_hourly
Then HA could no longer guarantee that Core and Frontend versions work together. If something is changed in the internal APIs of Core that the Frontend needs, the setup would be broken. So a user might update only the Frontend and it would no longer work, because wrong Core version. Or vice cersa (user updates Core which changes APIs and old Frontend version does not work anymore).
Would introduce a lot of issues and additional work (some kind of compatibility logic between the versions) that is just not worthwhile from my POV.
