The mentioned issue with Fritz!Box is fixed by 2022.2.1
Can anyone privide details on how to use shorthand condition notations with chose option? I’ve tried several combitanions but keep logging error requesting value_template and template type to be specified…
Done, thank you very much.
Thank you for this update
Just a question. My FGS224 FIBARO build in light switch stoped working.
Looks fine and responding to on/off but nothing happens.
Any idéa how to fix?
Have a nice day.
Hi ,
After this HA update , I have the following errors in the log
Logger: homeassistant.helpers.frame
Source: helpers/frame.py:74
First occurred: February 3, 2022, 12:04:18 AM (10 occurrences)
Last logged: February 3, 2022, 12:04:21 AM
Detected code that uses str (diagnostic) for entity category. This is deprecated and will stop working in Home Assistant 2022.4, it should be updated to use EntityCategory instead. Please report this issue.
Detected code that uses str (config) for entity category. This is deprecated and will stop working in Home Assistant 2022.4, it should be updated to use EntityCategory instead. Please report this issue.
What i have to do about this ?
Thanks
For anyone having trouble with the Energy Dashboard after the update, here seems to be the solution.
Will now also test whether it works again afterwards.
No problem with my update
Is there a dedicated thread about moving integrations to UI?
I dislike a trend of replacing yaml-config by UI-config.
IMHO adding a UI-config should not mean a disabling of yaml-config.
The latest HA moved a Version integration to UI; with yaml I could use a “scan_interval” , now I cannot.
This is a small example of “UI has less opportunities than yaml”, there are many of them with other integrations.
That ship has sailed my friend. It’s up to the maintainer of the integration to keep yaml or not when transitioning to the UI. It’s part of the ADRs.
have you found a solution to this mine is the same. it runs fine from the command line
This is the way.
Have you fixed or located this problem? I have this as well. Like 75 times sometimes.
I have managed to solve it with a bit different approach: windows subsystem for linux - Auto starting home assistant in WSL2 - Super User
Decision is done and dusted a long time ago, it isnt going to change so any posting about it will just be noise and wont do anything. Suggestion, move on
Yes just add diagnostics to your config. I also opened a ticket to silence it when we don’t have it enabled and they fixed that. Which should be in one of the next releases.
Have the same issue with scan_interval.
Guys, is there an issue with 2022.0.2 , the google assistant component now gives an 404 not found, so cant link the app again, if i go to :
https://xxx.duckdns.org:8123/api/google_assistant
i get 404 , while it should be 405
when i revert back to 2021.12.10 , everything works as expected?
You and @Ildar_Gabdullin can turn off polling on the integration, then make an automation that polls the entity in question at a defined period using homeassistant.update_entity
.
trigger:
- platform: time_pattern
seconds: "/30"
action:
- service: homeassistant.update_entity
target:
entity_id:
- list
- out
- entities