Home Assistant Support

I would really like to be able to add my GeoDrops to Home Assistant so I can use them with my other (and various) smart devices.

5 Likes

Home Assistant is on our roadmap. I’ll let the engineering team provide the answer on the timeline. We will be implementing support for Rachio first followed by Hunter Hydrawise and B-Hyve given the breakdown of irrigation controllers of the GeoDrops Insiders program participants.

Thanks for writing in!

Stanley
Marketing PM
Team GeoDrops

1 Like

Makes sense most people would have proper irrigation controls…we use Meross tap controls and OtO Smart Sprinklers. Nothing works together, so I’m hoping to do it with Home Assistant (eventually). Thanks for confirming it’s on the roadmap.

1 Like

On another note, there is one thing that you can do to help. While we can get the IFTTT and Home Assistant to work in the near future, they can be pretty cumbersome to use. If it’s possible for you to reach out to these companies and ask them to support GeoDrops Cloud’s interface, it would be fantastic, as the native integrations are much smoother to use.

We’ll make an announcement on both fronts when they are ready.

Thanks for your support and patience,

Stanley
Marketing PM
Team GeoDrops

Hi Stanley,

Home Assistant is a community-driven platform with easy integration options. For users who care enough about their soil, landscape, and plants to even buy Geodrops, Home Assistant (HA) can unlock far more data, control, monitoring, and automations than Google Home, IFTTT, or Alexa, which lack a full GUI and many of the granular events or controls your customers likely want.

I’m happy to build a simple, free integration for HA that delivers core sensor data. More advanced functionality like historical reports, OOTB control of existing irrigation controllers that already have HA integrations (Rain Bird, Hunter, Rachio, Orbit B-Hyve, Hydrawise, Yardian, etc.) or countless complementary HA integrations (weather, forecasts, yard-task calendars, ChatGPT or Gemini, water-usage dashboards, cost tracking) can be added much more easily down the line by your team..

What would be needed

  • API & connectivity details

    • Preferred protocol: WebSocket push (best) or REST polling (acceptable)
    • Authentication flow (token, OAuth, key exchange, etc.)
    • Rate limits or quotas
    • Endpoint list (soil-moisture, soil-temperature, soil-type, pH or EC, battery, firmware, etc.)
    • Sample payloads or a sandbox/test account for development
    • Any existing SDKs or Postman collections
  • Entity catalogue & data formats

    • Complete list of sensors you expose (for example soil_moisture, soil_temperature, soil_type, ai_status)
    • Units, ranges, or enums for each (percent, °C or °F, text labels, numeric codes)
    • Recommended thresholds or logic (for example moisture < 20 % → dry, > 90 % → over-saturated)
    • Planned AI or insight states (for example hot, dry, watering_needed) so I can map them to HA sensors, binary_sensors, or selects

With those two pieces, a basic integration could

  • Log in via your cloud or LAN API
  • Create HA sensor entities for every raw value
  • Derive a friendly soil_status (Dry :warning: / Perfect :white_check_mark: / Wet :droplet: / Over-saturated :prohibited:)
  • Let users build automations manually in minutes, such as “If Zone 3 soil_status = Dry and no rain is expected, run Zone 3 irrigation for 3 min.”

I’m not sure why IFTTT would be chosen first instead of HA:

  • No paywall – IFTTT charges for more than one applet, while HA is free and unlimited to everyone.
  • Deeper control – HA can combine your sensor data with weather, water-usage costs, energy dashboards, voice assistants, and more.
  • Developer community – over 100 000 active contributors to integrations, documentation, and testing feedback (and many more users).

IFTTT, Google, and Alexa support can still be layered on later (and reuse the same API), but HA gives power users immediate value at zero cost to users or to you.

After rereading this, I realized it sounds like a sales pitch, but I’m simply an HA enthusiast and contributor in both my personal and professional life. I’m not looking to be paid; just offering to help because I’d love to see this integration sooner rather than later.

Just let me know :slight_smile:

5 Likes

You brought up some interesting points. I have tagged the engineering team about this, and one of them will respond to you.

cc: @Engineering

Thanks for writing in!

Stanley
Marketing PM
Team GeoDrops

The HA community is SO amazing…and you’ve really well-articulated all the reasons I use HA to begin with! Thanks for answering the call :rofl:

3 Likes

Would be very interested in such a powerful integration. Hope you get the support you require to advance your HA proposal.

This is why the HA community is the best, please allow him to create this. My garden, yard, and well pump will be very thankful for this.

Did a little digging, and for one, local API is impossible at this time - the sensors are not always on, they wake up and report at a set interval (and possibly only if enough change warrants the report) - while they may measure more granularly, they only report around every 3h. There is no local resource that can be connected to at this time, maybe the geodrops station would be a good candidate for a local API with it being the edge controller for all sensors. The app uses protobuf and json to communicate to the servers (aws). It appears that the reports sent from the devices are of different types at different times as well as partial - i.e. one report will provide device status (but not moisture levels) - other reports will provide temperature (but again, no moisture levels) - heck, I even think sometimes they report one of the three moisture levels alone. Not sure why that is, but that’s what I could “sense” from not peeling my eyes off of the app :smiley: This leaves us with just cloud API for HA, which is still a good thing. Moisture is a slow moving measurement, there is no need for websockets, I feel, unless a local API is possible via the future Station. Websockets are expensive on the server side. Just my 2c.

PS: I’ll stand behind the HA feature ask, too.

1 Like

Thanks for all your comments, @ady624 , @rcrabby , and @petehami . I appreciate them and will follow along with future developments.

Stanley
Marketing PM
Team GeoDrops

Meant to link my post here for the benefit of those who haven’t seen it, but are still looking for HA integration - I’ve put together a python script that integrates the GeoDrops data available in Google BigQuery into Home Assistant using MQTT. More details here: Integrating GeoDrops Soil Moisture Sensors with Home Assistant

2 Likes