-
-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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! #891
Comments
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. |
The problem still exists and unfortunately has not been addressed yet. |
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. |
Still open and unfortunately no reaction. |
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.
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.
Actual behavior
Steps to reproduce
Proposed changes
Workaround: Close all files in Sudio Code Server, stop the addon once and then start it again without opening any files again.
The text was updated successfully, but these errors were encountered: