I got 60 errors on this latest update which includes this, Note: If you are using sensor: !include <filename>.yaml in configuration.yaml , remove the sensor definition from the included <filename>.yaml . it wants me to put on my templates in the configuration file which will make a mess of the file please correct me if I am wrong on this, I have folders for scenes, media players, switches, sensors, remotes
First of all, it is not an error but a warning. Second: the instruction given is one of dozens of ways to include templates in the config. The one suggested is what most people use. If you know yaml and any of those dozens methods to include things you are welcome to use them.
The organization possibilities for the template platform are the same as the ones you can use for sensor, cover, switch, light, etc.
1 Like
from what I gather I can no longer keep my templates seperate from the Configuration file and have to clutter the crap out of the Configuration file according to what I copied and pasted on my OP
That is simply not true. Apart from !include you can use this:
and if you want in combination with this:
Which leaves you with more then 10 ways to split things up to your liking.
But either way, the move of a sensor from one place to another does not change the options you have.
well that is even more confusing where am I moving them too now?
Show us what you have, and we’ll help. But we cannot do much with what you’ve told us so far. Is there already a template: line in your config, and what does it look like?
Anywhere you want, as long as it’s under the template top-level key and follows the rules of the inclusion method you have decided to use.
1 Like
this is what I have to point to my various folders for templates
sensor: !include_dir_merge_list sensors/
climate: !include_dir_merge_list climates/
cover: !include_dir_merge_list covers/
switch: !include_dir_merge_list switches/
# remote: !include_dir_merge_list remotes/
media_player: !include_dir_merge_list media_players/
# modbus: !include_dir_merge_list modbus/
group: !include_dir_merge_list groups/
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include_dir_merge_list scenes/
input_boolean: !include_dir_merge_named input_booleans/
this is what is in sensor folder
and this is a typical template in my setup
#Smart Gate
- platform: template
sensors:
smart_gate:
value_template: >-
{% if is_state('sensor.gate_node_status' , 'alive') %}
Online
{% else %}
Offline
{% endif %}
friendly_name: "Smart Gate Status"
Then I would suggest to add this to configuration.yaml:
template: !include_dir_merge_list templates/
Then create the templates folder next to all the other folders you have, and create files in there the same way you do for sensors.
You can copy the yaml from the repair to a file in that folder, but you need to remove the template: line that is on top of what the repair suggests.
I am not following
You did get the repair messages? If you open them, you get a completely ready piece of yaml you can copy to replace the old sensor.
Only for template sensors the new version need to be in the template folder, not the sensor folder. It does not seem like you have that folder yet, so what I suggested above is how you change configuration.yaml to read that folder.
When you create that folder then you can create new files with the content from the repair, as long as you remove the first line from it.
Remove the old version, add the new one and reboot. Then the migration is done.
1 Like
yeah I got the repair messages from what I gather it no longer supports putting stuff in different folders it wants to dump everything into the configuration file and get rid of include feature that allows seperate folders and files
No, that is not what it says. You can still do what you used to (plus the 9 other ways from the docs, yours is one of them). It is just impossible to explain all ways in one message without people being even more confused. What you use is a more advanced way than most people use.
if I can still do what I been doing then why the error message that states needs repair?
all of my templates switches, covers, binary sensors as well
Please read the deprecation notice @Sir_Goodenough linked above, it explains the changes to Template entities that will be taking effect in 6 months.
At this point pretty much every possible way to handle this repair has been discussed in that thread.
I did and that did not help at all
The warning is because the legacy format of writing template sensors, covers, lights, etc. will be removed, and you’ll need the new yaml format for templates instead. It does not change any of the ways to organise your yaml.
so then I can nolonger have covers and switches and sensor seperate?
So you added what I said to configuration.yaml, you created the templates folder, created files in them, copied the suggestion to it, removed the old version and rebooted?