Sure. Make a feature request about it. Or if you feel strongly about it, make a PR to change the syntax.
I’m seeing a few issues . . .
Sonos / devices_entities() Issue
I’m seeing an odd issue where device entities are not showing up when using the devices_entities() jinja function. This is definitely true for Sonos devices (and seems to be true for Hue Motion Sensor). For example:
This definitely worked previously since it is the basis for my Sonos alarm blueprint. And the HA UI for the Sonos speakers does show the various entities mind you under it (e.g. alarms, cross-fade, etc).
I did move back to the previous version and the issue stuck. So not sure what the issue is. I see no explicit errors in the logs (though it is possible something bad happened on upgrade and so long since gone).
Lutron Error
2022-05-05 12:30:19 INFO (MainThread) [homeassistant.setup] Setup of domain fan took 0.0 seconds
2022-05-05 12:30:19 ERROR (MainThread) [homeassistant.components.binary_sensor] Error while setting up lutron_caseta platform for binary_sensor
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 249, in _async_setup_platform
await asyncio.shield(task)
File "/usr/src/homeassistant/homeassistant/components/lutron_caseta/binary_sensor.py", line 33, in async_setup_entry
entity = LutronOccupancySensor(occupancy_group, bridge, bridge_device)
File "/usr/src/homeassistant/homeassistant/components/lutron_caseta/__init__.py", line 310, in __init__
identifiers={(DOMAIN, self.serial)},
File "/usr/src/homeassistant/homeassistant/components/lutron_caseta/__init__.py", line 339, in serial
return self._device["serial"]
KeyError: 'serial'
Not sure what it is entirely impact so far, but haven’t tested all devices.
Version Error
Others reported this one:
2022-05-05 12:30:27 ERROR (SyncWorker_5) [root] Uncaught exception
RuntimeError: module compiled against API version 0xf but this version of numpy is 0xe
The device_entities helper expects a device ID to be passed in. Are you sure you weren’t doing something like this before?:
{{ device_entities(device_id("media_player.master_bedroom")) }}
I’m a bit confused by the Sonos breaking change. It says:
The sonos_group attribute on Sonos media players has been renamed to group_members to align with other integrations.
and links to the documentation Sonos - Home Assistant
where ‘group_members’ is not mentioned at all and the sample code explicitly refers to ‘sonos_group’:
{{ state_attr( trigger.entity_id , ‘sonos_group’)[0] == trigger.entity_id }}
So should that now read
{{ state_attr( trigger.entity_id , ‘group_members’)[0] == trigger.entity_id }} ?
It wasn’t an explicitly documented attribute in the documentation. It’s primarily used by custom frontend cards and user-created templates.
Thanks for pointing that out, the remove_from_queue example should be updated for the new syntax. Doing that now.
If you mean this blueprint I see this:
i.e. what jjlawren is showing and not what you have in your screenshot.
Hey petro,
I am current with HA versions
I’ve tried to install 2022.5
I’m running into problems… here is check-config.txt
/tmp/configINFO:homeassistant.util.package:Attempting install of aiohttp_cors==0.7.0
INFO:homeassistant.util.package:Attempting install of spotipy==2.19.0
INFO:homeassistant.util.package:Attempting install of zeroconf==0.38.5
INFO:homeassistant.util.package:Attempting install of pyalmond==0.0.2
INFO:homeassistant.util.package:Attempting install of sqlalchemy==1.4.36
INFO:homeassistant.util.package:Attempting install of fnvhash==0.1.0
INFO:homeassistant.util.package:Attempting install of lru-dict==1.1.7
INFO:homeassistant.util.package:Attempting install of netdisco==3.0.0
INFO:homeassistant.util.package:Attempting install of aiogithubapi>=21.11.0
INFO:homeassistant.util.package:Attempting install of home-assistant-frontend==20220504.0
INFO:homeassistant.util.package:Attempting install of pillow==9.1.0
INFO:homeassistant.util.package:Attempting install of PyTurboJPEG==1.6.6
INFO:homeassistant.util.package:Attempting install of av==9.2.0
INFO:homeassistant.util.package:Attempting install of icmplib==3.0
INFO:homeassistant.util.package:Attempting install of bt_proximity==0.2.1
INFO:homeassistant.util.package:Attempting install of pybluez==0.22
INFO:homeassistant.util.package:Attempting install of pygatt[GATTTOOL]==4.0.5
INFO:homeassistant.util.package:Attempting install of geojson_client==0.6
INFO:homeassistant.util.package:Attempting install of psutil==5.9.0
INFO:homeassistant.util.package:Attempting install of qnapstats==0.4.0
INFO:homeassistant.util.package:Attempting install of python-forecastio==1.4.0
INFO:homeassistant.util.package:Attempting install of pycryptodome>=3.6.6
INFO:homeassistant.util.package:Attempting install of mutagen==1.45.1
INFO:homeassistant.util.package:Attempting install of gTTS==2.2.4
INFO:homeassistant.util.package:Attempting install of ha-ffmpeg==3.0.2
INFO:homeassistant.util.package:Attempting install of scapy==2.4.5
INFO:homeassistant.util.package:Attempting install of aiodiscover==1.4.11
INFO:homeassistant.util.package:Attempting install of hass-nabucasa==0.54.0
INFO:homeassistant.util.package:Attempting install of async-upnp-client==0.29.0
INFO:homeassistant.util.package:Attempting install of pyudev==0.22.0
INFO:homeassistant.util.package:Attempting install of PyNaCl==1.5.0
INFO:homeassistant.util.package:Attempting install of pyiss==1.0.1
INFO:homeassistant.util.package:Attempting install of python-kasa==0.5.0
e[1;37mFailed confige[0m
e[1;31mGeneral Errors:e[0m e[31me[31m
- Integration error: updater - Integration 'updater' not found.
e[0m
e[1;37mSuccessful config (partial)e[0m
this shows up–> - Integration error: updater - Integration ‘updater’ not found.
any ideas??
Thanks
Remove updater: from your configuration.yaml
hmm ok… is it not supported any longer?
I’m using version fine for what i previously used updater for
Oh ok I must have missed that in previous release notes thank you!
Just wondering why I didn’t get the error earlier? This new version 2022.5 broke it?
Yeah it was only deprecated before, my entities actually disappeared in the last 2022.4 update though so I already switched over
ok cool… did you select the “Home Assistant versions” ? or local?
I’m on core so I went for PIP, it depends what your install is
hmm I’m on Rasp Pi 4 with Argon one m.2… what would you suggest then bc I’m half confused. haha
Are you using HAOS or pios ? how did you install HASS?
HassOS install
I think you want either “Home Assistant Versions” or “Home Assistant Website” either should be fine but probably the first one. BTW Can you PM me some info about your argon / fan control etc? 
I’m about to set one up
Awesome thanks for the help… I know it’s a busy topic today …lol
I just got mine up and running. I can PM you, but the only thing I did was use this add on
I hope Adam gets back to me about scraping the current temperature from the add on bc only sensor if the fan speed
1 Like
Should consider adding something to the Breaking Changes about the change to the HASS OS DNS forwarders no longer forwarding .local hostnames. I went around in circles all day about why my configs that used local hostnames stopped working, till Mike informed me of the change. Switching from .local to .home.arpa for my internal FQDNs fixed the issue
2 Likes