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

Implement the ability to dynamically disable the sensor (preferably with a rate) #119

Open
3 tasks done
skinkie opened this issue May 7, 2024 · 4 comments
Open
3 tasks done

Comments

@skinkie
Copy link

skinkie commented May 7, 2024

Checklist

  • I have filled out the template to the best of my ability.
  • This only contains 1 feature request (if you have multiple feature requests, open one feature request for each feature request).
  • This issue is not a duplicate feature request of previous feature requests.

Is your feature request related to a problem? Please describe.

Sometimes I don't need TGTG to be active, why keep polling. Sometimes I would like to poll it more frequently.

Describe the solution you'd like

I would like to have the ability to set the polling to a very high or a lower interval. On the sensor configuration something like a slider that I can set with an automation.

Describe alternatives you've considered

Updating the config and manually restarting and

Additional context

None.

@blowk
Copy link

blowk commented Jun 8, 2024

If there is a service to call tgtg to update this would allow to change the polling through automatisation.

Is this duplicated to the question #34 ?

@skinkie
Copy link
Author

skinkie commented Jun 8, 2024

I think it is different, I would like to change an internal variable, for that it needs to be exposed.

@blowk
Copy link

blowk commented Jun 13, 2024

Sorry, I don't quite understand.
Do you want to change/update each sensor by own chosen interval like fir example you could stop polling during the night?

@skinkie
Copy link
Author

skinkie commented Jun 13, 2024

Exactly. But the interval now is also 'choosen' but it is hardcoded in the configuration file. So what needs to be available is to be able to update it, without restarting home assistant

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants