As an FYI for those moving your MQTT Integration config using YAML to UI config flow for this release…
Be aware that you will need to manually enter your configs in the UI config flow in order for the data to actually be stored (stored in ./storage/ that is); as the data needs to be stored before you remove your mqtt config from your yaml. I only bring this up, because my prior experience has been that moving an integration’s config from yaml to UI config flow, would have the data migrated automatically for you, whereas this is not the case for mqtt integration.
There are several references in the full changelog at: Full Changelog for Home Assistant Core 2022.3 - Home Assistant
It looks like the ecobee changes ended up getting pulled back before release: https://github.com/home-assistant/core/pull/67474
Hello,
Weird display issue happens in device search bar if the prefiltered criteria is long (I think it used to truncate):
Believe it or not, in the above screenshot, I have typed the word ‘curtain’ in the search. You can tell the search is still working, it’s just not displaying what you’ve typed in the search bar.
I could only reproduce this within ZHA device search (because of the length of the filter criteria). When searching devices in any other integration with filter criteria not as long or just searching all the devices, it works/displays fine:
I would if i could, my hassos instance does not even bring it up if i search for it. If i Try and set up via the web, i get the error
Error
Config flow could not be loaded: [object Object]
further error in logs
Error occurred loading configuration flow for integration mjpeg: No module named ‘homeassistant.components.mjpeg.config_flow’
What is PHU icons?
Quick question (I hope) … Why do my manual switches (switch.yaml) disappear (not get created as entities) on update?
LOL Because teenagers unplugged all the Broadlink controllers …
2 Likes
That is not a core feature. You need to take it up with the third party developer. https://github.com/elax46/custom-brand-icons/issues
Please don’t post unreadable pictures of something you could easily describe or provide a link to.
Also https://github.com/elax46/custom-brand-icons#dont-see-the-icon
The migration from paper elements to MWC doesn’t seem to be complete at all, more like halfway done.
This updated HA version seems to use a mix of different elements now, which doesn’t really set a good example for custom card developers to follow.
Package.json still lists the current dependencies:
What is the direction forward? Will the migration continue in upcoming updates?
How can I update my custom cards to be future-proof?
3 Likes
Does the Salus iT600 integration work?
Changes made at DLNA server not reflecting or updating in Media brower.
There is no Salus iT600 integration Integrations - Home Assistant
Unless you are referring perhaps to a custom component?
My Shelly Integration in no longer functioning as of 2022.3. I get this error msg at the Configuration :: Integrations page:
The Shelly device itselve is perfectly working from the Shelly interface and the buttons.
Upgrade this morning to 2022.3.1 did not solve the problem.
I have only one Shelly device, a Shelly Dimmer. The Shelly firmware is at the latest level, i checked.
Is there a reason you are using a custom one and not the one built into core?
I had to add media_source: under configuration.yaml to get it visible.
IP Webcam issues are here:
Maybe the mjpeg cam integration related stuff killed it… Cam can be used with that mjpeg integration but the switches or sensors will not work. Mjpeg url with Android IP Webcam: http://IP_ADDRESS:PORT/video