reset bucket by service

[raul811]

Good project thank you for the integration it's super for my needs.

I'm not understand why the integration resets the bucket intervals times every day at 10pm but I not use the integration with the valve all inform monitoring.

Last source service_reset

[drake69]

Thanks for the kind words, and sorry for the long silence on this one.

On the reset you are seeing. NeverDry has no scheduled reset. With no valves configured it runs in monitoring mode, where the only timed jobs are two checks every 6 hours: the "irrigation needed" notification and the anomalous-deficit alert. Neither of them touches the bucket. In that mode the deficit can only go down through rain, or through one of the explicit actions below.

service_reset is written in exactly one place in the code: the handler of the never_dry.reset service. So the value you are reading means that service was called by someone - most likely an automation, a script, or a dashboard button. Worth knowing too: the Last Source sensor is sticky. It keeps the last value that was written, so it is not evidence that a reset happened at 22:00; it may well be an older one.

Two things would let me tell for sure:

1. Which entity do you see dropping at 22:00 - the system "Dryness Index", or a zone "Deficit"? Its history graph for a couple of days would help.
2. In Settings > Automations & scenes, is anything calling never_dry.reset? (Developer tools > Actions > never_dry.reset also lists what is wired to it.)

On your actual request - resetting the bucket by service. That already exists, per zone as well as globally:

• never_dry.mark_irrigated - optional zone_name. With a zone, it zeroes that zone only; without it, every zone. This is the right one for your case: you watered by hand and you are telling NeverDry about it, so the water is credited to the zone counters. Each zone also has a "Mark irrigated" button, same effect.
• never_dry.set_deficit - deficit_mm plus optional zone_name. Use it to set any value, including 0.
• never_dry.reset - system-wide: it zeroes the reference deficit and every zone at once. This is the blunt one, and probably not what you want if you water one zone at a time.

If you are watering manually, mark_irrigated is the action to automate, not reset.