Logger: homeassistant.components.template.sensor
Source: helpers/config_validation.py:779
Integration: template ([documentation](https://www.home-assistant.io/integrations/template), [issues](https://github.com/home-assistant/home-assistant/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+template%22))
First occurred: 0:22:04 (4 occurrences)
Last logged: 0:22:04
The 'entity_id' option is deprecated, please remove it from your configuration
I have already replaced, it seems to me, where it was possible all āentity_idā to āunique_idā, tell me how to find the lines that swear HA
VScode is available only for 64bit HA (minority of installations I guess due to what is adviced by docs).
I would also like to see more verbose message in log. Current wording besides not pointing to exact entity which causes the issue, it not even gives a clue what it is about. It understable only for those who tracks release discussions
I know that but from discussion in release thread is obvious that for a lot of people itās hard to understand how to cope with this issue.
Iām not saying that people should not read changelog, but the log is not helping (itās not the only case - it has been rised in WTH)
Also some might start with HA using later version but use some code examples found on forum. I wouldnāt blame him for not reading changelogs from the past
So you use an example from the forum, add it to your setup and once you restart youāll see the error appear, then you know that itās coming from this example.
Iām not sure how much simpler you can get than this (direct quote from the release notes):
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.
This means you can now remove the entity_id option from your templates, as it is now deprecated.
I think it is more likely that people just didnāt read it.
You are absolutely right, I did not read it, since I started using HA only from version 0.117.
But I am grateful to you for showing me where to get to know this.
Iām pretty sure that itās only available on 64bit (and non-Arm Architecture, ie x86, at that)
If you run VSC on a separate workstation, then your options are many, you donāt necessarily need to use samba (I do however) but instead use ftp or ssh (probably others too) but all these are a lot more āfiddlyā
Regardless Iād say āwhat has this to do with the price of fish ?ā ā¦ but subsequent discussions talk about what newbies expect and Iāve learnt that you canāt put any level of scope setting on that.
my fault. It was meant 64b.
The point is that some users often suggest solutions which donāt work for majority. in this case, docs advices HA 32bit so not many users can gave VSC.
BTW I didnāt know I could instal VSC with HA integration on other machine than HA one. I cannot imagine a newcomer going for this option.
Except in that case it can work for just about anyone. You donāt have to use the addon, which is what was assumed. You can use VSCode on any PC and connect to home assistant (by any of the methods outlined above) to edit the files. Also I highly recommend it. Great editor.
The docs no longer ārecommendā 32 bit
Not sure what that means for the future, I always thought it kinda weird to run 32b software on 64b architecture and you canāt address anything above 4GB (so a Pi4 8GB would be a waste of money)
Still, everyone should start comming into line (ie reducing the number of āsupportedā installation methods and platforms which should streamline support and development).
I will await developments but would expect 32b to go the way of the dodo before too long, having said that in print, I will noe probably be proved wrong
Ahh I though VSC can help solving entity id issue. If not then I think every editor has search and replace function. But you one must know what and where to look at. Iām sure most users starting HA jurney after 0.117 will have no idea about what and why is happening.
BTW, recently I migrated to 64b HA which gave me opportunity to try VSC. Itās starting so slow on HA@rpi4 ā¦ it caused I returned to default editor very quickly.
Yes but VSC makes it easy to search ALL files (in your instance)
Can have āHome Assistant Context/Syntax Highlightingā
Bracket checking
Indentation checking etc.
ā¦ Probably others too
As Tom said : - Great Editor !
I didnāt know frenck had managed an Arm port - well done frenck
Try the install on a separate workstation, then itās only limited by your pc hardware
@tom_l, Iād not seen the mdi icons before, just went to install and there seems to be 3 of them.
Which is the preferred ?
Edit: I installed the āMaterial Design Icons Intellisenseā by Lukas Troyer. It does all I could ask of it, Suggestions, autocomplete and āaparentā enbeded preview (donāt worry though it doesnāt actually change the yaml file) Very Happy
I must admit it looks very useful.
It encourages me to try VSC on PC connecting to HA remotely.
BTW shouldnāt the message be āstring DOES match the pattern of deprecatedā ?
I am using Raspberry Pi OS Lite, and as I understand it is not available in the 64-bit version. Therefore, I use VSC on my laptop, and I connect to my Raspbery Pi4 via add-on Samba share
Very Happy 