You’re using the standard history view.
@bigscience uses the custom:history-explorer-card.
There you have these functionality and even more.
For everyone with battery reporting issues
Battery values are extracted from the device information from the bhyve API. The bhyve-home-assistant integration periodically (every 5 minutes) polls the b-hyve api to fetch an updated set of values. So it stands to reason that the response is returning either bogus data or in a format which is not being handled properly.
It would be helpful if you could upload your device diagnostics to the following github ticket where this is being tracked:
Do not upload these diagnostics to this thread.
Here is what I just did:
- platform: statistics
entity_id: sensor.back_yard_battery_level
name: max_back_yard_battery_level
max_age:
hours: 24
state_characteristic: value_max
Which is giving me this:
You can see that the current battery is 0% but it grabbed the max of 93%. I may need to adjust the hours in case it doesn’t update in a day and I get a 0%. Another potential issue is if for some reason the battery takes a dive in a day, I’d get the highest value but really, my only real concern is if the batteries totally died in the 4 months I use the system. No need to water plants all year in the PNW.
Hope this helps
1 Like
Thanks…looks like my sensor doesn’t pick up in the same way on the Statistics:
This is disappointing. May be due to the fact that mine is a Orbit 24639 and it’s not one of the units “recognized” according to @sebr in the notes. Bummer.
Nope, that’s the same one I have and it looks like you are getting values from your graph. Did you create the new sensor with the code I posted? What you are doing is making a new entity that gets the max of your real battery level.
- platform: statistics
entity_id: sensor.back_yard_battery_level ### This is the sensor that jumps up and down
name: max_back_yard_battery_level ### This is the new entity you are creating
max_age:
hours: 24
state_characteristic: value_max
Make sure you restart and give it a little time to catch it when it actually shows the value. Oh, also make sure you have it set up in your recorder if you’d put excludes in there.
Brilliant! Works a treat with a gauge as well:
Much appreciated! (I didn’t even know there WAS a Statistics integration…)
There is now. My gawd, this weather and climate changes. Our lawn is dead before June (Saint Helens, OR. on the Columbia River). When we arrived 23 years ago it rained occasionally in Summer. Not now. Our B-Hyve drip water systems are critical for keeping whats left of our garden stumbling along until winter when the lawn returns, just before it freezes and goes dormant only to die shortly later in late spring. 
I’m from Sedona, Arizona. That’s why I came here. I’ve seen this movie. I know how it ends. 
I was using this integration last year and took it offline over the winter. Well fast forward, I just got back around to re-installing the Devices and they are working great with the app, however the integration!
only show the diagnostics? I’m missing the control and configuration? Any ideas on how to fix this??
I recall having to create a zone to get a valve switch to show up. But it has been a while since I set mine up. Worth trying it…
Thanks for the quick reply, unfortunately that didn’t solve the problem. I’m stumped!
Does anyone know if the wifi hub 96505 model will work with the b- hyve intergration
Curious if anyone has tested this with the newer Orbit 21606 Smart Hose Watering Timer (Gen 2) units?
I’m not sure if that’s the same as the BH1-0001 module. The pictures look the same. I’m using the latter succesfully with HA.
Is there any way to get this integration to be local? It works over bluetooth right? Is there any way we can avoid the cloud all together?
1 Like
Valve to hub is bluetooth. Hub (to HA) connects via WiFi.
The HACS Orbit B-hyve component for Home Assistant relies on Orbit cloud connection.
Anyone know how to get alerted/notified of the next watering schedule a day or several hours prior?
Or better yet, how to integrate these schedules with Home Assistant calendar? That way I could have the visual display of when the watering will occur plus have alerts on calendar event with offset. Thoughts?
Hi! I am new here.
I am considering the Orbit products to automate my garden. The Orbit site mentions that none lf their products work with soil humidity sensors.
Could I use HA and the b-hyve integration to work with third-party sensors and instruct my controller not to irrigate if the soil is humid enough, regardless of timers?
In Canada, we have a lot of days that are cooler and even if it doesn’t rain, the soil stays wet for days and days.
Thanks!
Indeed. I have three Orbit bHyve valves and have never used any of Orbit SW.
My irrigation is managed by HA, using the soil sensors from my weather station (Ecowitt)