Skip to content
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

Help to figure out why sensor.watchman_last_updated changes so often #51

Open
dummylabs opened this issue Jun 13, 2022 · 1 comment
Open
Assignees
Labels
enhancement New feature or request

Comments

@dummylabs
Copy link
Owner

dummylabs commented Jun 13, 2022

Since watchman catches up every state change of every entity from configuration files, we can fire up a custom event with entity name, which was changed, and its context. The event can also be reflected in the HA event log. This feature should be optional due to enormous amount of possible events.

Inspired by #29 and #50.

@dummylabs dummylabs added the enhancement New feature or request label Jun 13, 2022
@dummylabs
Copy link
Owner Author

Another, and simpler, idea could be to add a reason attribute to the sensor, which can be set to (for example):

  • Home Assistant restart
  • configuration reload
  • entity {id} referenced by a config file has changed its state
  • etc.

@dummylabs dummylabs self-assigned this Nov 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant