Hellis81
(Hellis81)
February 3, 2022, 4:36pm
321
There is something using CPU right now.
Not sure what. It’s too far from the update
Edit.
Looking at the time it seems to be about when we casted the news on the kitchen TV
Olie
February 3, 2022, 4:39pm
323
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.
NathanCu
(Nathan Curtis)
February 3, 2022, 4:41pm
324
bmorgan:
from the Checker add-on:
Fatal error while loading config: [Errno 2] No such file or directory: '/usr/local/lib/python3.9/site-packages/multidict-6.0.2.dist-info/METADATA'
Failed config
General Errors:
- [Errno 2] No such file or directory: '/usr/local/lib/python3.9/site-packages/multidict-6.0.2.dist-info/METADATA'
I think I’ve gotten this before and just plowed ahead with no apparent consequences. Is it ignorable?
Confirmed had this in my pre-check - upgrade to 2022.2 proceeded without issue.
3 Likes
oxo42
(John Oxley)
February 3, 2022, 4:42pm
325
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?
The new WebOS works for me, just had to add a new automation to allow switch on with WakeOnLAN
Turn on Action:
3 Likes
Is it just me or is the “edit” button on cards no longer working. Can’t say it started with this release but it is the first I’ve noticed it.
EDIT: Nevermind. Seems to be a browser thing.
TryingHA
(James)
February 3, 2022, 4:57pm
328
I’ll have to give that a shot. I thought that was more of an example of how to use it in an automation and not what was needed to make it work.
BebeMischa
(Bebe Mischa)
February 3, 2022, 4:57pm
329
How do you control them? Which integration? There are more ways to work with Sonoff, we need more info…
Question: 2022.2 brings casting Plex to CCA’s which allows playing playlists from the google cast card, and that works great.
Is there a way to do the same (plex playlist) via an automation?
1 Like
Sp4wN
(Ozen)
February 3, 2022, 5:11pm
332
Follow the instructions here at the second reply and it will work, don’t use the host url, just use the MAC adres:
opened 10:59PM - 02 Feb 22 UTC
closed 05:21AM - 03 Feb 22 UTC
integration: webostv
### The problem
After the latest Core update, LG webOS integration lost its Tur… n On media player button, and calling the service directly also doesn't work.
### What version of Home Assistant Core has the issue?
2022.2.0
### What was the last working version of Home Assistant Core?
2021.12.10
### What type of installation are you running?
Home Assistant Supervised
### Integration causing the issue
LG webOS Smart TV
### Link to integration documentation on our website
https://www.home-assistant.io/integrations/webostv
### Example YAML snippet
_No response_
### Anything in the logs that might be useful for us?
_No response_
### Additional information
Configuration done from Home Assistant UI.
1 Like
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!
benzo
(benzo)
February 3, 2022, 5:17pm
334
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
TryingHA
(James)
February 3, 2022, 5:21pm
335
@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.
1 Like
Can you have both the new nest integration and the legacy nest integration setup at the same time?
BebeMischa
(Bebe Mischa)
February 3, 2022, 5:43pm
338
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:
opened 07:42AM - 03 Feb 22 UTC
integration: fritz
### The problem
After update of my homeassistant core installation on my Rasp… berry Pi, i noticed, that the device-tracker by the fritzbox integration does not work anymore. No devices were found.
In the Integration panel the following error is shown:
<img width="208" alt="image" src="https://user-images.githubusercontent.com/47830373/152299585-5464d95a-59a6-4852-bb75-bd9600883243.png">
Translation: retry Setup; check the logs
I already reinstalled the integration. The login to the Fritzbox works, but the error remains.
### What version of Home Assistant Core has the issue?
core-2022.2.0
### What was the last working version of Home Assistant Core?
core-2021.12.x
### What type of installation are you running?
Home Assistant Core
### Integration causing the issue
AVM FRITZ!Box Tools
### Link to integration documentation on our website
https://www.home-assistant.io/integrations/fritz
### Example YAML snippet
_No response_
### Anything in the logs that might be useful for us?
In the logs i just found some warnings regarding my Caldav-Configuration and the following entries:
`Detected integration that accessed discovery_info.__contains__('ssdp_location') instead of discovery_info.upnp.__contains__('ssdp_location') or discovery_info.ssdp_headers.__contains__('ssdp_location'); this will fail in version 2022.6. Please report issue for upnp using this method at homeassistant/components/upnp/device.py, line 78: if ssdp.ATTR_SSDP_LOCATION not in headers:`
`Detected integration that accessed discovery_info['ssdp_location'] instead of discovery_info.ssdp_location, discovery_info.upnp['ssdp_location'] or discovery_info.ssdp_headers['ssdp_location']; this will fail in version 2022.6. Please report issue for upnp using this method at homeassistant/components/upnp/device.py, line 81: location = headers[ssdp.ATTR_SSDP_LOCATION]`
I tired to dig a bit deeper and activated the debug logs for fritzconnection:
After a wall of Text it ends with a "response status: 500"
> 2022-02-03 07:34:44 DEBUG (SyncWorker_4)
> http://192.168.179.1:49000/upnp/control/hosts
> 2022-02-03 07:34:44 DEBUG (SyncWorker_4) [fritzconnection] b'<?xml version="1.0" encoding="utf-8"?><s:Envelope s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"><s:Body><u:GetGenericHostEntry xmlns:u="urn:dslforum-org:service:Hosts:1"><NewIndex>20</NewIndex></u:GetGenericHostEntry></s:Body></s:Envelope>'
> 2022-02-03 07:34:44 DEBUG (SyncWorker_4) [fritzconnection] response status: 500
> 2022-02-03 07:34:44 DEBUG (SyncWorker_4) [fritzconnection] <?xml version="1.0"?>
> <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
> <s:Body>
> <s:Fault>
> <faultcode>s:Client</faultcode>
> <faultstring>UPnPError</faultstring>
> <detail>
> <UPnPError xmlns="urn:dslforum-org:control-1-0">
> <errorCode>713</errorCode>
> <errorDescription>SpecifiedArrayIndexInvalid</errorDescription>
> </UPnPError>
> </detail>
> </s:Fault>
> </s:Body>
> </s:Envelope>
> 2022-02-03 07:34:44 DEBUG (MainThread) [homeassistant.components.fritz.common] Finished fetching fritz-192.168.179.1-coordinator data in 3.411 seconds (success: False)
### Additional information
FRITZ!OS: 07.13
bronco
(Rene)
February 3, 2022, 5:44pm
339
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,
Hi Mark
I had exactly the same issues. In the end I gave up.
My Nest Thermostat E with Google Account does not want to show up or make any entities.
Tried everything mentioned here.
I have now a working solution until Google/Nest gives us the API back again.
I am using HOOBS installed on the same Docker Instance where HA lives.
Within HOOBS I installed the Nest plugin with the same credentials.
Installed it this way in a shell on the host (Not in a Docker Container):
docker run -d -p 808…
BebeMischa
(Bebe Mischa)
February 3, 2022, 5:45pm
340
Homekit Controller is up and running on this release as I can confirm.
1 Like
bronco
(Rene)
February 3, 2022, 6:19pm
342
SOLVED by removing the Yaml for Device_tracker.
When I switch to the new version i get 3 major issues
The zones are there. Status person.user says unknown.
Home Assistant IOS says this:
Any ideas?
1 Like
pgreberg
(Peter Greberg)
February 3, 2022, 6:22pm
343
Thomas1509, same here. My graph is not updated in the dashboard but the sensor is. Nothing seems to update on that dashboard. My separate devices doesn’t update either.