Same here. No idea why but at least something to work with now. I don’t know how to convert it from UTC time and to time/day of week either but it’s a little challenge to work on.
I did just this but there was no guided configuration. Can you help point me where the configuration is supposed to happen?
switch.zone_name operating incorrectly.
I have 3 zones (front lawns, back lawns and hanging baskets).
One program does the lawns, and it does front then back. Originally it did 20 mins each - but the switch.front_yard_zone stays on until the back yard zone turns-off (ie the switch.front_yard_zone stays on for 40 mins, whereas switch.back_yard_zone is correct at 20 mins.
Seems like a bug somewhere ??
@M3Power95 Can you share the automations you used to total your consumption?
Here’s how I do it:
alias: DxHyve - Drip Irrigation Direct Automation
description: ""
mode: single
triggers:
- entity_id:
- switch.drip_irrigation_zone
from: "on"
to: "off"
enabled: true
for:
hours: 0
minutes: 5
seconds: 0
trigger: state
conditions: []
actions:
- target:
entity_id: input_number.dxhyve_drip_irrigation_direct
data:
value: "{{ state_attr('sensor.drip_irrigation_zone_history', 'consumption_gallons') }}"
action: input_number.set_value
- target:
entity_id: input_number.dxhyve_drip_irrigation_direct_time
data:
value: "{{ state_attr('sensor.drip_irrigation_zone_history', 'run_time') }}"
action: input_number.set_value
- data:
summary: Drip irrigation ran
start_date_time: "{{ state_attr('sensor.drip_irrigation_zone_history', 'start_time') }}"
end_date_time: >-
{{ (as_timestamp(state_attr('sensor.drip_irrigation_zone_history',
'start_time')) +
(state_attr('sensor.drip_irrigation_zone_history','run_time')*60) + 5*60*60 )
|timestamp_custom('%Y-%m-%dT%H:%M:%SZ',true) }}
target:
entity_id: calendar.dxhyve_drip_irrigation
action: calendar.create_event
- target:
entity_id: input_number.dxhyve_drip_irrigation_direct_application
data:
value: >-
{{ state_attr('sensor.drip_irrigation_zone_history', 'run_time') *
states('input_number.dxhyve_drip_irrigation_application_rate') | float /
60 }}
action: input_number.set_value
- delay:
hours: 0
minutes: 0
seconds: 30
milliseconds: 0
- data:
value: 0
target:
entity_id:
- input_number.dxhyve_drip_irrigation_direct
- input_number.dxhyve_drip_irrigation_direct_time
- input_number.dxhyve_drip_irrigation_direct_application
action: input_number.set_value
It works as follows:
Trigger:
- Once the valve turns off for at least five minutes, it starts the automation. There are times where it’s going to do multiple waterings to limit runoff. So take that into consideration when setting up the delay/off timer. It’s state should go from “on” to “off” otherwise you’re going to get phantom triggers if your sensor ever goes unavailable.
Actions
- I created an input_number (input_number.dxyve_drip_irrigation_direct) outside of this automation. It takes the consumption_gallons attribute from the sensor.drip_irrigation_zone_history sensor provided by the BHyve integration and sets the input_number to that value. This tracks the total consumption.
- I created a second input_number (input_number.dxhyve_drip_irrigation_direct_time). It takes the run_time attribute from the sensor.drip_irrigation_zone_history sensor provided by the BHyve integration and sets the input_number to that value. This tracks the total runtime of that valve.
- I created a calendar (calendar.dxhyve_drip_irrigation) outside of this integration. It takes the date/time from the zone history sensor and creates an event on that calendar so I can keep track of the days it ran.
- I created a third input_number (input_number.dxhyve_drip_irrigation_direct_application) that is used to track the total inches I’ve applied to the area. This uses a bit of math from the sensor attributes: run_time * application_rate
- Finally, once all of that is done, it waits 30 seconds and then sets all of the input_numbers to 0. I do this because I have utility meters setup for each of these three input_numbers that track the totals and resetting to 0 tells the utility meters that the valve has cycled.
There are almost certainly more elegant and simpler ways to do this, but it’s what works for me.
You’ll definitely need to experiment and track for a few weeks to make sure your results are matching the actuals.
Hope this helps
Anyone know why, when running a program, the zone switches on then immediately off? The program runs, it’s just the zone switch in HA that turns off immediately. I have some other things within HA that are triggered by that switch being on, but get shut off immediately.
On the B-Hyve app disable smart watering for the zone.
Ok, make sure time run mode is not on AUTO. Set to off. Then include a copy of your automation if it still doesn’t fix the issue
Ahh you have misunderstood. I am scheduling through orbit, I am not using HA to run an automation to turn on.
My problem is with the zone switch, it turns on then off 2 seconds when my ORBIT program runs.
OOOHHHH!!! My bad, sorry about that! The only thing I can think of is the rain sensor. Even if you don’t have a rain sensor, it may be on and shorted. That can be disabled, but I couldn’t tell you how.
All good! If i can’t figure this out, I’ll be setting it up through HA completely though. Just like orbit because it’s easy and the weather delays work.
For the Orbit 57925 Irrigation Controller, each zone switch has an attribute “Next Start Time”. I recently added an Orbit 21004 Hose Timer and noticed that it is does not have this attribute. Is that a bug? An oversight? Or just not available for the timer?