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
Template reload causes sensors to trigger #266
Comments
Not sure what will break if I put a check to see if old_state is null. I'll have to look into that but in the interim, you can easily filter it out with a switch node.
|
Yep, figured that one out thanks. I'll leave this open in case you figure out a way to solve, but if you can't feel free to close. |
The above changes were reverted and I added some predefined ignore types to the event state node. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I have a few sensors that are template sensors. With the update to version .115, if I take advantage of the new "Reload Template Entities" service, it causes all the templates (sensors/binary sensors) to be reloaded, which in turn causes the state nodes I have in NR to trigger. I have them set to "output only on state change" and they still output. I'm not sure if there's a way to filter those out based on how the sensor is updated but it's slightly annoying as a few spit out a bunch of notification messages.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Ideally no output based solely on reloading the sensor.
Screenshots
Example Flow
Environment (please complete the following information):
Other (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: