- platform: template property platform is not allowed

edwardtich · January 23, 2022, 4:25am

Hey

after the next update I get this error in all templates
^{- platform: template property platform is not allowed}

I have output to external folders like this

how to fix and in which file to create templates now?

where to read public relations in NA?

now you need to redo all the templates?

tom_l · January 23, 2022, 5:53am

skynan · January 25, 2022, 7:03am

Is it the same with “Property platform is not allowed” message, after updating to HA Core core-2021.12.10 and the following setup:

includes within configuration.yaml (sensor → several files)

results in error messages within one of these files

Kjoere · January 25, 2022, 12:02pm

see what tom_I said.
I have this too. Quite scary lol
everything works and no errors on reloading or checking config.
Suppose there will be an update that fixes this bug

GeertV · January 27, 2022, 7:51am

Same here with Visual code. But as said, everything works

TNT_Larsn · January 28, 2022, 5:10pm

There’s an open Issue at github:

github.com/keesschollaart81/vscode-home-assistant

Multiple (>800) syntax errors found in working code after installation of HA addon code server 4.1.0

opened 06:46AM - 17 Jan 22 UTC

closed 05:43PM - 23 Mar 22 UTC

SirGoodenough

yaml

![Screenshot_2022-01-17_00-22-53](https://user-images.githubusercontent.com/47349533/149720370-5123a9fa-ae65-4c16-88ed-adf0d83c5c9f.png) I updated The home assistant community addon and after this repo loads, I have ~800 lines of code that it says is not fitting the schema, like the pictures attached. All this yaml was fine with the prior version of the addon. I have rebooted and restarted the addon. I will be re-instaling it next, but it appears to be a problem that I think is here (not sure). The 4.1.0 version of the addon looked to be mainly an update to this software to add templates highlighting (which works in every file, btw...) Opening all the yaml files, it showed over 800 syntax problems. My system restarts without error and the config checker passes with no errors, and none of this was there before the addon update, I'm informing you in case it a missed issue. I run Home Assistant Supervised Debian bullseye all patched up to date. Removing and re-installing the the code server addon did not help. ![Screenshot_2022-01-17_00-32-23](https://user-images.githubusercontent.com/47349533/149719177-28919b2e-aa5f-4f8c-8afd-ce99ac6983d5.png)

@frenck: I know, I’ve been returning to the issue a couple of times now to investigate, I fail to understand the source of the problem until now.

jazzyisj · January 28, 2022, 5:44pm

Is this just an issue with the old style templates? I use vscode but I’m not seeing this error.

Any idea if the old style will eventually be deprecated? Seem kinda redundant to have two methods of declaring sensor templates.

tom_l · January 28, 2022, 9:35pm

It’s only an issue with the VSCode addon. If you are using VSCode on a desktop PC (via SAMBA or SSH) it isn’t an issue.

GeniePlumb · February 19, 2022, 7:51am

Hi Tom, Didn’t know I could use VS via Samba or SHH is there any info on how to set up the SHH gig.

many thanks

D

tom_l · February 19, 2022, 8:24am

I’ve never used it via SSH only SAMBA.

borob · February 22, 2022, 2:54am

You just need an sshfs extension, for example this one:

edwardtich · February 22, 2022, 6:09am

I still haven’t solved this problem

please any help

OscarHanzely · February 25, 2022, 11:21pm

Yes the problem still persists as there was no patch released yet. There is nothing a user can solve, the schema is completely valid. This appears to be the issue of HA helper used in VSCode Addon.

I just downgraded the addon back to version 4.0.0 by changing the version in addons.json file and it reverted to working condition. turn off automatic updates if you do so.

lasseruud · March 5, 2022, 10:03pm

Care to elaborate? I’ve edited /usr/share/hassio/addons.json. “4.1.0” appears two places in that file (under “user” and “system”). I’ve tried to replace them both with “4.0.0”, but still at version 4.1.0 after reboot.

OscarHanzely · March 7, 2022, 2:52am

I am not the official developer, so they should be able to provide more details and troubleshooting but this is what I did if I remember correctly:

turn off automatic updates for the vscode addon in HA interface
get docker image locally, so when the container start is requested it will be present. (on the host machine run docker pull ghcr.io/hassio-addons/vscode/amd64:4.0.0 for PC or ghcr.io/hassio-addons/vscode/arm64:4.0.0 for Pi)
edit file /usr/share/hassio/addons.json its owned by root, so you must run the editor with sudo f.e. sudo nano /usr/share/hassio/addons.json and change the line "version": "4.1.0", to "version": "4.0.0",. I actually did it only for the one under user section and that was enough, I am not sure where system is used, but feel free to change it in both places for consistency.
reboot the host machine. I did it not via the interface because the supervisor may correct the versions. I just run reboot command on my shot machine and next time it came back it was reading values from the json and used the pulled docker image to recreate old container.

lasseruud · March 7, 2022, 8:42am

Thank you. I was unable to make this work. Maybe because I rebooted through Supervisor - I don’t know.

However I found another way:

Did a partial backup, only backup of Studio Code Server 4.1.0.
Downloaded the backup
Edited backup.json and coder.json inside tar and tar.gz. Changed version from 4.1.0 to 4.0.0
(When using my default packer, restore failed. Had to use 7zip to edit the json-files)
Uninstalled Studio Code Server
(- Restart)
Uploaded edited backup
Restored edited backup
(- Restart)
Version 4.0.0 is back.

This might work with other addons as well.

edwardtich · March 7, 2022, 9:24am

this does not work
I checked now

lasseruud · March 7, 2022, 6:38pm

Using the backup? I just did this and it worked for me. Where did it fail? Any error messages?

tinkererer · May 27, 2023, 8:37pm

This issue seems to still persist. Has anyone tagged the Studio Code Server dev? @frenck
edit: scratch that, it appears to have been resolved somehow. Perhaps I got an update?

WJ4IoT · December 8, 2023, 12:49pm

Working with Visual Studio Code and like the fact that I get slapped on my fingers when my syntax is incorrect. I experienced the value_template error when I moved the entity from the mqtt.yaml file into my first packages. Needless to say this put me on the wrong foot.

HA-version: 2023.11.0 (installed in a Docker Container)