2022.2: Let's start streamlining!

frits1980 · February 12, 2022, 12:36pm

I can’t believe my way of getting my devices back is “the final” and “best” way. So as long as there is no “normal” / “good” way. I don’t see the point of putting it in documentation. There must be a better logical way of doing this.

frits1980 · February 12, 2022, 12:38pm

I hope you are indeed incorrect. But for now, this seems to be the only way.

petro · February 12, 2022, 1:45pm

There’s nothing to figure out. Integration issue → core. Ui → frontend. The issue bot will organize it for you.

Sp4wN · February 12, 2022, 3:41pm

@BebeMischa and @pergola.fabio I came back to check if I was the only one with Spotify problems, after your posts I was going to open a issue but it is already opened by someone else since my last post:

github.com/home-assistant/core

Spotify access token expired error

opened 11:10AM - 12 Feb 22 UTC

realthk

in progress integration: spotify

### The problem About 15-20 mins after upgrading to core-2022.2.6, Spotify inte…gration has stopped with "access token expired" messages kept repeated every 5 minutes. It has never ever happened before with any other version, and after restoring core-2022.2.5 it works fine again, so I guess it must be related to the reduced Spotify API use mentioned in changelog. ### What version of Home Assistant Core has the issue? core-2022.2.6 ### What was the last working version of Home Assistant Core? core-2022.2.5 ### What type of installation are you running? Home Assistant OS ### Integration causing the issue Spotify ### Link to integration documentation on our website https://www.home-assistant.io/integrations/spotify ### Diagnostics information _No response_ ### Example YAML snippet _No response_ ### Anything in the logs that might be useful for us? ```txt 2022-02-12 10:22:10 ERROR (SyncWorker_5) [spotipy.client] HTTP Error for GET to https://api.spotify.com/v1/me/player/devices with Params: {} returned 401 due to The access token expired 2022-02-12 10:22:10 ERROR (MainThread) [homeassistant.components.spotify] Error fetching realthk Devices data: 2022-02-12 10:27:10 ERROR (SyncWorker_5) [spotipy.client] HTTP Error for GET to https://api.spotify.com/v1/me/player/devices with Params: {} returned 401 due to The access token expired 2022-02-12 10:32:10 ERROR (SyncWorker_0) [spotipy.client] HTTP Error for GET to https://api.spotify.com/v1/me/player/devices with Params: {} returned 401 due to The access token expired 2022-02-12 10:37:10 ERROR (SyncWorker_6) [spotipy.client] HTTP Error for GET to https://api.spotify.com/v1/me/player/devices with Params: {} returned 401 due to The access token expired 2022-02-12 10:42:10 ERROR (SyncWorker_4) [spotipy.client] HTTP Error for GET to https://api.spotify.com/v1/me/player/devices with Params: {} returned 401 due to The access token expired 2022-02-12 10:47:10 ERROR (SyncWorker_0) [spotipy.client] HTTP Error for GET to https://api.spotify.com/v1/me/player/devices with Params: {} returned 401 due to The access token expired 2022-02-12 10:52:10 ERROR (SyncWorker_6) [spotipy.client] HTTP Error for GET to https://api.spotify.com/v1/me/player/devices with Params: {} returned 401 due to The access token expired 2022-02-12 10:57:10 ERROR (SyncWorker_3) [spotipy.client] HTTP Error for GET to https://api.spotify.com/v1/me/player/devices with Params: {} returned 401 due to The access token expired ``` ``` ### Additional information _No response_

Frenck knows about it and will be solved soon with a new release I guess.

nickrout · February 12, 2022, 8:36pm

Well you are lucky now able to look at the docs and click to get all issues in relation to your integration. That will tell you exactly where to place a new issue, how to tag it and whether there is a similar open issue.

BlackChart · February 13, 2022, 8:47am

Am I the only one that can’t use “all” anymore, to turn off all the lights?
Worked prior to 2022.2, doesn’t work anymore.
Read the release notes, but couldn’t find that change mentioned?!

 service: light.turn_off
 target:
   entity_id: all

tom_l · February 13, 2022, 8:50am

No, you are not alone:

github.com/home-assistant/core

"all" entity_id not working

opened 09:18PM - 03 Feb 22 UTC

pascalmtts

### The problem Calling Services like „light.turn_off“ or „cover.close_cover“… with target entity_id set to „all“ is not working anymore. ### What version of Home Assistant Core has the issue? core-2022.2.1 ### What was the last working version of Home Assistant Core? core-2021.12.10 ### What type of installation are you running? Home Assistant Container ### Integration causing the issue _No response_ ### Link to integration documentation on our website _No response_ ### Example YAML snippet ```yaml service: light.turn_off target: entity_id: all ``` ### Anything in the logs that might be useful for us? ```txt Logger: homeassistant.helpers.script.websocket_api_script Source: helpers/script.py:1375 First occurred: 22:18:09 (1 occurrences) Last logged: 22:18:09 websocket_api script: Error executing script. Error for call_service at pos 1: Template rendered invalid entity IDs: all ``` ### Additional information _No response_

The workaround is:

 - service: light.turn_off
   entity_id: all

BlackChart · February 13, 2022, 8:58am

Damn - missed that one. Thank you.

pszeremeta · February 13, 2022, 9:28am

Turn Off All Lights as in example below stopped working! Please help!

service: light.turn_off
entity_id: all

pve · February 13, 2022, 2:42pm

Does anybody now have the foobot integration working? I am getting an error
Tried to restart a few times.

2022-02-13 15:27:03 WARNING (MainThread) [homeassistant.components.sensor] Setup of sensor platform foobot is taking over 10 seconds.
2022-02-13 15:27:03 ERROR (MainThread) [homeassistant.components.foobot.sensor] Failed to connect to foobot servers
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/foobot_async/__init__.py", line 159, in _get
    resp = await self._session.get(

pve · February 13, 2022, 5:04pm

Hmmm, seems to work alright, but gives one error message at boot time. Maybe there is a pattern. No big issue now.

c_wolsey · February 15, 2022, 10:54am

Yep I am seeing those errors too. Looks like a known issue and a fix is coming… https://github.com/home-assistant/core/issues/66373

koying · February 15, 2022, 3:36pm

I was kinda assuming that shorthand conditions would work in a choose as well, but apparently not.

    choose:
    - conditions:
        - condition: "{{ is_state('trigger.to_state.state', 'Online') }}"

2022-02-15 16:25:43 ERROR (MainThread) [homeassistant.config] Invalid config for [automation]: Unexpected value for condition: '{{ is_state('trigger.to_state.state', 'Online') }}'. Expected and, device, not, numeric_state, or, state, sun, template, time, trigger, zone @ data['action'][0]['choose'][0]['conditions'][0]. Got None. (See /config/configuration.yaml, line 264).

Would be great if “choose” would accept shorthand as well, for consistency.

dennis84de · February 15, 2022, 3:44pm

That should work.

    choose:
    - conditions:
        - "{{ is_state('trigger.to_state.state', 'Online') }}"

123 · February 15, 2022, 3:47pm

These work (and are my preferred method for a Template Condition in choose).

    choose:
    - conditions: "{{ is_state('trigger.to_state.state', 'Online') }}"

    choose:
    - conditions:
      - "{{ is_state('trigger.to_state.state', 'Online') }}"
      - ... Other ANDed conditions ...

koying · February 15, 2022, 3:50pm

Nevermind. Should have checked the doc
Thanks

GeekVisit · February 15, 2022, 4:03pm

Easiest option would be the HACS implementation as mentioned above. I am not using GPIO at the moment but plan on doing so for an analog sensor I have. I know you said you weren’t a programmer, but I can think of at least 2 other solutions that would require a little scripting – simply to create you own template MQTT sensor and have a script running on the Pi monitoring GPIO that sends out an MQTT message which would trigger the sensor. Or use a NodeRed module - see Interacting with Raspberry Pi GPIO. Nodered might be a better option as programming might be a bit simpler. Home Assistant’s ability to interact with the operating system (using even bash commands) provides a ton of possibilities. Add NodeRed and there’s very few deprecations (if any) that can’t be worked around, though it may be uglier and harder to implement than the deprecated integration. I would add however, that I do find the dropping of GPIO support as disappointing and does worry me as to how deep the commitment is to the hacker community. This seems a further streamlining toward the consumer market.

pepe59 · February 15, 2022, 4:10pm

I have already solved the problem using my own GPIO integration in HACS

vdiogo · February 15, 2022, 5:00pm

I got them all working except the Solar

vdiogo · February 15, 2022, 5:56pm

Doing that to fix my issue (had measurement and replaced with total_increasing).
Since it’s KwH I’m giving it one hour to check if it fixed it