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

Sprinkler Tracking #458

Open
cappa88 opened this issue Jul 29, 2024 · 5 comments
Open

Sprinkler Tracking #458

cappa88 opened this issue Jul 29, 2024 · 5 comments
Assignees
Labels
do-not-auto-close Label to make sure it's not auto closed by stale bot enhancement New feature or request

Comments

@cappa88
Copy link

cappa88 commented Jul 29, 2024

I would like to propose an idea.

Would it be possible to include the entity of the respective sprinklers for each zone? This way, the integration could track the seconds each zone is irrigated and update the bucket accordingly. This could avoid the need to reset the bucket and also account for any manual activations of individual zones.

@cappa88 cappa88 added the enhancement New feature or request label Jul 29, 2024
@jeroenterheerdt
Copy link
Owner

jeroenterheerdt commented Jul 29, 2024

that's a great idea! Very interesting, let me see if I understand what you mean:

  1. add optional entity for each zone
  2. if entity is provided, automatically update bucket to reflect changes based on throughput * activation duration. this will cover then for automatic irrigation as part of the normal behavior as well as manual activations of the entity.

did I get that right?

@jeroenterheerdt jeroenterheerdt added the do-not-auto-close Label to make sure it's not auto closed by stale bot label Jul 30, 2024
@cappa88
Copy link
Author

cappa88 commented Jul 30, 2024

Yes, that's exactly what I mean! By adding an optional entity for each zone and updating the bucket based on throughput and activation duration, the integration would become more accurate and efficient. The bucket would be adjusted according to the calculation of millimeters of water replenished by the irrigation. This would account for both automatic and manual irrigation, making the system more reliable.Thank you for considering this idea. As I'm not familiar with the development of integrations, I wasn't sure if this was feasible

@dadino
Copy link

dadino commented Jan 23, 2025

This would solve my problems with an unrealiable water resource. My only source is a tank, which could be empty, meaning the sprinkler is activated, power is given to the pump, but the pump's floater is not high enough to allow the pump to run.

I have an entity in Home Assistant that checks the power consumption of the pump and the switch for the sprinkler, if both are valid, then I consider the sprinkler to be actually working.

It's a binary sensor, so if you implement this change (which would be a very good addition), don't limit it to switches or input_boolean, please.

Discussed in #510

@jeroenterheerdt
Copy link
Owner

@dadino sounds like you'd need the ability to specify multiple entities or would you be able to wrap them into one?

@dadino
Copy link

dadino commented Jan 24, 2025

I'd just need one. Even if I had multiple (which some people might use), I could just create a group helper. It's just an on/off sensor, groups are easy for those.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do-not-auto-close Label to make sure it's not auto closed by stale bot enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants