its by design, i asked in beta and was told its a fyi
that’s not really a huge surprise isn’t it? 
1 Like
yeah, saw it too late 
@perjury1 I’m running Home Assistant OS, and know it’s been on Python 3.9 for some time, so not finding this path is a bit of a concern. I’m wondering if it’s the check that’s flawed?
I am not able to install 2022.2.0
22-02-03 13:23:29 ERROR (SyncWorker_3) [supervisor.docker.interface] Can’t install ghcr.io/home-assistant/qemux86-64-homeassistant:2022.2.0: 404 Client Error for http+docker://localhost/v1.41/images/ghcr.io/home-assistant/qemux86-64-homeassistant:2022.2.0/json: Not Found (“no such image: ghcr.io/home-assistant/qemux86-64-homeassistant:2022.2.0: No such image: ghcr.io/home-assistant/qemux86-64-homeassistant:2022.2.0”)
Is someone else getting this error ?
personally, I really wish we had an option to allow new device_trackers to be enabled upon discovery. since https://github.com/home-assistant/core/pull/63328 newly discovered device_trackers are disabled,
and have no attributes in the entity_registry_updated event_type resulting in:
using:
- alias: New device registered config
id: New device registered config
mode: queued
trigger:
platform: event
event_type: entity_registry_updated
event_data:
action: create
condition: >
{{trigger.event.data.entity_id.startswith('device_tracker')}}
action:
- variables:
data: >
{{trigger.event.data}}
entity: >
{{trigger.event.data.entity_id}}
name: >
{{state_attr(entity,'friendly_name')}}
host: >
{{state_attr(entity,'host_name')}}
ip: >
{{state_attr(entity,'ip')}}
mac: >
{{state_attr(entity,'mac')}}
source: >
{{state_attr(entity,'source_type')}}
id: >
{{device_id(entity)}}
config: >
- entity: {{entity}},
- name: {{name}},
- host: {{host}},
- ip: {{ip}},
- mac: {{mac}},
- source_type: {{source_type}}
- id: {{id}}
time: >
{{now().timestamp()|timestamp_custom('%X')}}
title: >
{{time}} - New device registered: {{name}}
message_body: >
New device config: {{config}}
(devices that are enabled upon discovery according to the new device_tracker logic do show all/most of these fields populated.)
after enabling the tracker we can see all attributes are in fact there:
either bring back the enabled option, or, if possible, also provide details on disabled device_trakcers…
1 Like
Do you have enough spare disk space?
What are your DNS settings?
This is a possible upgrade path, but its more complexity.
Big shame that its necessary - IMO the WWN component should be marked deprecated but with indefinite life.
If it breaks then it breaks, but should be kept until that point.
After the update the VLC stopped working for me:
[725cf600] http stream error: cannot resolve homeassistant.local: Name does not resolve
[725cf600] access stream error: HTTP connection failure
[725cf600] main stream error: cannot resolve homeassistant.local port 8123 : Name does not resolve
[725cf600] http stream error: cannot connect to homeassistant.local:8123
[727245d0] main input error: Your input can’t be opened
[727245d0] main input error: VLC is unable to open the MRL ‘http://homeassistant.local:8123/media/media/Disarmed.mp3?authSig=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiI4ZWRkYTZhNmViMTk0YzdjOWRjM2FkN2JlNmU5ZDZlNCIsInBhdGgiOiIvbWVkaWEvbWVkaWEvRGlzYXJtZWQubXAzIiwiaWF0IjoxNjQzODg4OTU4LCJleHAiOjE2NDM5NzUzNTh9.TlVweec10EmTiNrv2Vi-4azCFJHn2uaNxjYvHyP9FJ4’. Check the log for details.
What could be the problem?
Fyi, I disabled the backup before update… and it worked fine !
I needed to exclude certain things like zeroconf. They can be overridden but not excluded.
Is anyone having issues with google cast changing how it works? Seems like a breaking change but I haven’t seen one listed.
For example, device states for my android tv within google cast (dont confuse with androidtv please its a different integration) now show ‘idle’ instead of ‘off’ when they are off.
Also I am having a very weird thing happening in that my android tv device (unknown if this is home assistant but its the only thing that has changed) powering off randomly while I am watching it. Anyone else feel the wife and kids frustration with me?
1 Like
Since upgrading I’ve noticed my Shelly devices integrated via MQTT now have status unavailable for shortpush, longpush and overload.
Any idea what I need to fix where?
The problem is that each time I post an issue on github, I get “this has been broken on purpose, you were warned” or “we won’t fix that” or “your OS is not supported”. I am under the impression this whole project is based on the “it works for me” principle. Like another user mentions, I wouldn’t be surprised if this is heading to some kind of proprietary stuff.
2 Likes
You can’t fix something you can’t replicate… how are you supposed to know it’s fixed or verify your fixed worked? If you can’t supply enough information to replicate the problem, then the problem won’t get fixed. Can a car mechanic fix your car without your car? No. How do you expect any developer to fix a problem without the problem?
OK…wouldn’t necessarily agree with you, but anyway…I was only saying here that Netatmo works for me on latest version and if you wanted some input saying more than ‘it doesn’t work’ might get better feedback…will leave it with you 
2 Likes
Small question. I’ve tried the new IFF example from the documentation, but Dev Tools give me an error “state is undefined”. Have I overlooked something?
yes, states is the correct method name.
I only copied the doc examples into Dev Tools. I don’t know how to handle “UndefinedError: ‘state’ is undefined”.
Then there’s a typo in the docs
1 Like