Remove dalinicus/homeassistant-aerogarden

[dalinicus]

Repository

https://github.com/dalinicus/homeassistant-aerogarden

Checklist

• I understand that this form should only be used for repositories that needs to be removed from HACS
• I understand that a bug is not reason enough to have a repository removed
• The repository is currently shipped as a default repository in HACS
• I have tried to get the authors attention to the reason for removal

Why should this be removed?

On June 26th, Aerogarden launched their new Android and iOS app, replacing the old app. This came with the consiquence of a new backend API, replacing the old API that this integration used to gather information for Home Assistant. While the old API is still functioning, its returning stale data from the time that Aerogarden swapped over to the new system.

In October 2024, Aerogarden announced they would be shutting down operations.

With the old functionality broken, and the likelyhood that any new functionality would be non-operational after January 2025, I'll be archiving this repo.

I can open a PR to have it removed, but I can only find instructions that indicate opening an issue. If a PR is required from the author, if you can point me to documentation on what files need changed I would be happy to oblige.

Link to issue

I am the author

[hacs-bot]

Make sure you have read the issue guidelines and that you filled out the entire template.

If you have an issue identical to this, do not add comments like "same here", "i have this too", instead add a 👍 reaction to the issue description. Thanks! 👍

[dalinicus]

cc @doctorkb

[dalinicus]

@ludeeus just wanted to make sure its alright for me to archive the git repository. As I stated in October, I can open a pull request to have it removed, but the HACS documentation said I should open a issue instead.

The integration is permanently broken, so I'd like to take it down.

[ludeeus]

Archiving is a valid (undocumented) shortcut, it will be removed from all new instances.
And from everywhere else usually within a week.

[MrMcGyver]

@dalinicus Any chance you will revisit this integration since Aerogarden has reopened their doors?

[doctorkb]

@dalinicus Any chance you will revisit this integration since Aerogarden has reopened their doors?

Got a news link? My googles don't have any indication of this, and their website just errors out for me.

[MrMcGyver]

https://aerogarden.com/home/?srsltid=AfmBOooW0HR6QqgLabr9dpi6oIQZCV2onJVdHB_VQUR9eqx8NsA883UX

https://www.vegbed.com/blogs/news/aerogarden-s-2025-relaunch-what-it-means-for-gardeners-and-the-indoor-gardening-community?srsltid=AfmBOopYOgOxg2TGVuE2qsehjhpT4HiCDzEUVcHykjX5GsbKZSmEuTbA

[doctorkb]

The first one bounces me to a 403 (could just be a non-US thing):

The second one give me zero optimism that it's even remotely the same equipment or systems that they plan on using. If it were me, I certainly wouldn't be working on the current (undocumented, non-public) API with this news... it sounds to me as though it could be a completely different company that has licensed the Aerogarden name from Scotts MiracleGro. The coming months will tell, but don't be surprised if your current AG's app interface works even less than it does right now.

[MrMcGyver]

Perusing through the site, everything points to Scotts Miracle Gro as the owner. I even went so far as to call Scotts, and they confirmed they have brought the product back.

[dalinicus]

@MrMcGyver Aerogarden is coming back, but this wasn't the primary issue. They switched to a new app and API a month or so before shutdown, and my integration is not compatible. I looked into the possibility of trying to incorporate the new API but the new android/ios apps have their communication with the API locked down with SSH and a private cert unique to the app. Attempts to man-in-the-middle myself using self signed trusted android certs didn't yield results, and may be above my skill level to sus out when it comes to app development (I'm a DevOps backend engineer by trade).

The company deciding to cease operations was only the final nail in the coffin.

If the situation changes, or someone is successful in doing the ground work for the API reverse engineering, I'd be happy to take a second look and resurrect the integration.

[MrMcGyver]

@dalinicus Thank you for that clarification. I'll try and work with them to see about getting the API changed. They probably won't , but it can't hurt to ask.