petro
March 4, 2022, 7:20pm
247
You can make an automation that looks for the error and creates a notification. Many people won’t want a pop up (myself included) and you have to option to create one for yourself through an automation.
jbouwh
March 4, 2022, 7:44pm
248
You are right, I messed up. I just tested your config and it seems you always will get the send_if_off deprecated warning. I think is a bug. There is a default value set during validation, and that needs to change.
nontijt
March 4, 2022, 8:22pm
249
… before the update ofcourse. Did you get my intent on this?
After the update i get: 1 complaining wife, 1 notification from HA. Thats automation enough.
But never mind.
jbouwh
March 4, 2022, 8:24pm
250
See PR to fix this:
home-assistant:dev ← jbouwh:mqtt-climate-warnings
opened 08:17PM - 04 Mar 22 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO N… OT DELETE ANY TEXT from this template! (unless instructed).
-->
## Proposed change
<!--
Describe the big picture of your changes here to communicate to the
maintainers why we should accept this pull request. If it fixes a bug
or resolves a feature request, be sure to link to that issue in the
additional information section.
-->
MQTT climate config parameters `SEND_IF_OFF` and `HOLD_MODES` were deprecated, deprecated with the HA 2022.3.0 release. There config parameters had default values in the schema causing deprecation warnings even when they were not configured. This PR removes the defaults from the schema and respects them later.
The issue was reported here:
https://community.home-assistant.io/t/2022-3-select-and-play-media/398201/218
## Type of change
<!--
What type of change does your PR introduce to Home Assistant?
NOTE: Please, check only 1! box!
If your PR requires multiple boxes to be checked, you'll most likely need to
split it into multiple PRs. This makes things easier and faster to code review.
-->
- [ ] Dependency upgrade
- [x] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [ ] New feature (which adds functionality to an existing integration)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- This PR fixes or closes issue: fixes #
- This PR is related to issue:
- Link to documentation pull request:
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [ ] The code change is tested and works locally.
- [ ] Local tests pass. **Your PR cannot be merged unless tests pass**
- [ ] There is no commented out code in this PR.
- [ ] I have followed the [development checklist][dev-checklist]
- [ ] The code has been formatted using Black (`black --fast homeassistant tests`)
- [ ] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [ ] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [ ] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- [ ] Untested files have been added to `.coveragerc`.
The integration reached or maintains the following [Integration Quality Scale][quality-scale]:
<!--
The Integration Quality Scale scores an integration on the code quality
and user experience. Each level of the quality scale consists of a list
of requirements. We highly recommend getting your integration scored!
-->
- [ ] No score or internal
- [ ] 🥈 Silver
- [ ] 🥇 Gold
- [ ] 🏆 Platinum
<!--
This project is very active and we have a high turnover of pull requests.
Unfortunately, the number of incoming pull requests is higher than what our
reviewers can review and merge so there is a long backlog of pull requests
waiting for review. You can help here!
By reviewing another pull request, you will help raise the code quality of
that pull request and the final review will be faster. This way the general
pace of pull request reviews will go up and your wait time will go down.
When picking a pull request to review, try to choose one that hasn't yet
been reviewed.
Thanks for helping out!
-->
To help with the load of incoming pull requests:
- [ ] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone+-status%3Afailure
<!--
Thank you for contributing <3
Below, some useful links you could explore:
-->
[dev-checklist]: https://developers.home-assistant.io/docs/en/development_checklist.html
[manifest-docs]: https://developers.home-assistant.io/docs/en/creating_integration_manifest.html
[quality-scale]: https://developers.home-assistant.io/docs/en/next/integration_quality_scale_index.html
[docs-repository]: https://github.com/home-assistant/home-assistant.io
Deprecation warnings for send_if_off or hold_modes are logged regardless of there presence in the config. This is cause by default values in the schema, causing the values to be configured.
3 Likes
chriscon
March 4, 2022, 8:29pm
251
Could be as simple as browser cache. I had to clear site data for my HA domain, re-login and hard refresh (ctrl+F5) the Automations Dashboard in order to see the new option.
@Fifke This might also be the solution for your post 2022.3: Select and play media - #238 by Fifke
nickrout
March 4, 2022, 8:45pm
252
I think the answer may lie in this extract from the release notes
Your Cameras! Your Lovelace Dashboards! You can just pick one of your cameras or Lovelace dashboards and “Play” them on a **supported device ** (like a Google Nest Hub or television).
lovelace sharing works on my chromecast, not on my other devices.
+1 same here … “The Samsung integration can detect my TV, but no device or entity is created after I complete the setup.”
That Samsung TV bug seems to be confirmed and will not be removed until 2022.4 apparently.
1 Like
please add a +1 or extra comments to https://github.com/home-assistant/frontend/issues/11938
Dev tools states shows friendly_name instead of entity_id
5 Likes
Just added an example from my post . Vote for restoring of “entity_id” displaying.
Many thanks for quick fix!
nickrout
March 5, 2022, 1:59am
258
For those with sabnzbd not starting issue, I have posted a (non permanent, hacky) solution for now.
opened 09:23AM - 03 Mar 22 UTC
integration: sabnzbd
### The problem
I updated Home Assistant OS to 2022.3 and now the sabnzbd integ… ration has stopped working, I get the following error upon restarting: The following integrations and platforms could not be set up: sabnzbd.
Log:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/setup.py", line 228, in _async_setup_component
result = await task
File "/usr/src/homeassistant/homeassistant/components/sabnzbd/__init__.py", line 218, in async_setup
await async_configure_sabnzbd(hass, conf, use_ssl, name, api_key)
File "/usr/src/homeassistant/homeassistant/components/sabnzbd/__init__.py", line 196, in async_configure_sabnzbd
if await async_check_sabnzbd(sab_api):
File "/usr/src/homeassistant/homeassistant/components/sabnzbd/__init__.py", line 170, in async_check_sabnzbd
await sab_api.check_available()
File "/usr/local/lib/python3.9/site-packages/pysabnzbd/__init__.py", line 93, in check_available
await self._call(params)
File "/usr/local/lib/python3.9/site-packages/pysabnzbd/__init__.py", line 41, in _call
async with timeout(self._timeout, loop=self._session.loop):
TypeError: timeout() got an unexpected keyword argument 'loop'
### What version of Home Assistant Core has the issue?
2022.3
### What was the last working version of Home Assistant Core?
2022.2.9
### What type of installation are you running?
Home Assistant OS
### Integration causing the issue
Sabnzbd
### Link to integration documentation on our website
https://www.home-assistant.io/integrations/sabnzbd/
### Diagnostics information
_No response_
### Example YAML snippet
_No response_
### Anything in the logs that might be useful for us?
_No response_
### Additional information
_No response_
1 Like
aladin
March 5, 2022, 2:07am
259
Is there any problem related to previous version and package loading ?
nickrout
March 5, 2022, 4:13am
260
Logs! This is not a help desk.
avd706
March 5, 2022, 4:59am
261
strange, not on my cromecasts, wonder if I need to set it up somewhere else… .
nickrout
March 5, 2022, 5:39am
262
There is no context to your massage. What are you responding to?
Hi ,
The supervisor 2022.1.1 has not been updated to 2022.3.1 in my HA production system . This update has been performed in my HA test system.
try to update by ssh “ha supervisor update” … error : no supervisor update available - 2022.1.1
Any advice ?
Are you updating HA supervisor or HA core? Current version of supervisor is 2022.1.1.
Command for updating core would be ha core update
The update issue is related to HA Supervisor.
I just realized that my HA test system is Beta so may be this is normal that supervisor version is 2022.3.1 in this system
1 Like
