I get this warning in the log
Logger: homeassistant.components.template.sensor
Source: helpers/config_validation.py:796
Integration: Template (documentation, issues)
First occurred: 4:43:12 PM (1 occurrences)
Last logged: 4:43:12 PM
The ‘entity_id’ option near /config/configuration.yaml:82 is deprecated, please remove it from your configuration
and mi code is this one
I tried the excluded line but the sensor didn’t work
How can I fix it to avoid the warning in the log
I believe you want to remove what appears to be line 84 in your YAML file.
Comment it out with a ‘#’ sign, first. Then if it works, remove it.
You may still need the value later, for something else.
I know but I defined that sensor to publish an attribute and I use it.
So maybe I am exposing this attribute with an old methodology and there is a new way to do it that I don’t know.
123
(Taras)
January 7, 2022, 5:39pm
4
Did you recently upgrade from a very old version of Home Assistant?
The entity_id
option was eliminated from Template Sensors over a year ago:
home-assistant:dev
← bdraco:auto_analysis_can_not_longer_fail
opened 01:41PM - 29 Aug 20 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO N… OT DELETE ANY TEXT from this template! (unless instructed).
-->
## Breaking change
<!--
If your PR contains a breaking change for existing users, it is important
to tell them what breaks, how to make it work again and why we did this.
This piece of text is published with the release notes, so it helps if you
write it towards our users, not us.
Note: Remove this section if this PR is NOT a breaking change.
-->
It is no longer necessary to provide a list of entities to monitor for each template platform as automatic analysis can now find all entities that affect the state in the template without manual setup.
The template is now re-evaluated whenever an entity that can affect the template state changes. New entities that can affect the template state are automatically discovered each time the template is rendered. This change solves a performance issue where the template would be re-rendered unnecessarily.
Please review the `Working without entities` section on the `Binary Sensor Template` documentation for alternative ways to force templates entities to re-evaluate.
If this change means you need to make adjustments, we have made it easier by making template entities reloadable in the `YAML configuration reloading` section under `Configure Home Assistant` `Server Controls`.
Additional details about this change are available at https://github.com/home-assistant/architecture/issues/208
## 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
## Example entry for `configuration.yaml`:
<!--
Supplying a configuration snippet, makes it easier for a maintainer to test
your PR. Furthermore, for new integrations, it gives an impression of how
the configuration would look like.
Note: Remove this section if this PR does not have an example entry.
-->
```yaml
# Example configuration.yaml
```
## 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: https://github.com/home-assistant/home-assistant.io/pull/14343
## 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.
-->
- [x] 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`.
- [ ] 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-asc+-review%3Aapproved
<!--
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
finity
January 7, 2022, 7:16pm
5
I’m not sure why it wouldn’t if you only eliminated the “entity_id:” line.
everything else looks OK.
the only thing that “entity_id:” did was to give something for the sensor to update on since it wasn’t smart enough at that time to extract entities from the template.
It is now so that’s why it was removed and deprecated.
Sorry I didn’t understood you the first time, now it works
123
(Taras)
January 7, 2022, 9:07pm
7
You should mark FredTheFrog’s post with the Solution tag (not mine) because it was the first to identify the problem and how to fix it.
2 Likes