For those using UniFi Protect from HACS before this update, I’m curious what the recommended upgrade path should be?
After upgrading to 2022.2, my UniFi Protect integration still had the custom component icon. In an effort to remove it, I uninstalled the HACS-based integration, removed it from HACS, reinstalled it via the native integrations page, and then rebooted. It initially still had the custom components icon, but appears it was removed after a few hours. I’m thinking these steps weren’t necessary, but wondering what’s recommended when integrations move from HACS to the core system.
Have there been any changes to the Energy Dashboard other than moving the settings? Since the update, the graphical representation no longer seems to update. However, the entities are up to date and also react to changes…
So to try and fix for the broken/incomplete implementation or the new WebOS integration I rebuilt the media player for the TV as a universal media player. So far this is working for me. There still may need to be some adjustments to be made.
Personally, I first deleted the integration from the Integrations page, then removed the HACS custom integration and restarted.
I then installed the core version (by clicking the + Add Integration button from the Integrations page), entered my gateway username/password combination - and all my cameras were back as they were before.
When an integration has a single device, clicking on the “1 device” link will now navigate to that device directly and skip the addition page with a table showing 1 item.
How do I get to the device addition page for the integration if I have only one device?
Yeah I’ve checked the commits and it should be sorted for 2022.3. It’ll be a nicer solution than the template sensors I’ve used for the last few years!
Is there a way to create a Button for weblink?
I need this to be able to send notify on clicked button. With all these changes i don’t understand if now possible.
Thanks
@Holdestmade
Thanks to both of you. The automation add worked. I did have to included the broadcast address as it is on another VLAN. It is working as intended now and I will delete my universal media player.
All of the dev’s, chapeau! I just updated and found only one issue.
Fritz!Box integration failed.
But, all of the other stuff I use (and it is A LOT) works fine. When i saw the amount of changes, I got scared after my older collisions with HA updates, but this time it went almost smooth.
So kudos for you, dev’s!
For those affected with the Fritz!Box integration, there is a issue to be found here:
Simply switch to HOOBS. Works fine for me already for two years and can confirm it works in this version very well also Nest Protect. Look here for a tutorial I made nearly two years ago.
The new version of the Plugin for Nest is even more easier to configure. It does it all for you. It will take 15-20 mins to do this,