For conditions in Trigger Based Template Sensors: Error message "Property condition is not allowed". Side effect of very high RAM usage and increased CPU usage!

[alexsaas]

I made use of the option with Core 2024.10 to also use conditions in a trigger based template sensor. Unfortunately, the error message "Property condition is not allowed" is then displayed in the condition line in Studio Code Server.

The screenshot shows the error message (separate template.yaml):

PS: conditions (plural) does not change the error message and is not yet supported in Trigger Based Template Sensors.

In addition, with this error message, the RAM usage increases extremely and the CPU usage also increases significantly. I also noticed the same behavior with the syntax changes with Core 2024.09 and Core 2024.10, such as the change from platform to trigger, or the new syntax to plural like triggers instead of trigger. I can only stop the high resource usage if I close all files in Sudio Code Server, stop the addon once and then start it again without opening any files again.

(Why the issue was filed)

There should be no error messages with native core syntax or, as promised, old syntax that can still be used, and these error messages should not put too much strain on hardware resources.

(What you expected to happen)

Actual behavior

(What actually happened)

Steps to reproduce

(How can someone else make/see it happen)

Proposed changes

Workaround: Close all files in Sudio Code Server, stop the addon once and then start it again without opening any files again.

[jeremiebidault]

Same here. Raspbery pi 5 with HAOS
After having installed 2024.10.4, high cpu/ram usage. And after having stopped vscode (5.17.2). Cpu/ram goes normal.