Repository navigation
Please remove the migration notice while the HACS catalog replacement is disputed #116
Description
Hi @Olen,
Please remove the README notice introduced in commit 05ad64a that instructs users of slaxor505/home-assistant-openplantbook to uninstall it and install your integration.
The replacement of my repository in the HACS default catalog is currently disputed, and I have raised this with HACS. While that remains unresolved, the notice actively encourages users to leave my integration and presents the replacement as a settled transition.
My repository is maintained separately as OpenPlantbook Founder Edition and includes additional functionality, including sensor monitoring and optional warning notifications. Retaining the OpenPlantbook configuration when switching does not preserve those features. The current notice does not explain that consequence.
Please remove the migration notice pending resolution of the dispute. Your installation instructions can explain how to install your integration without directing existing users to uninstall mine.
I would appreciate confirmation when the notice has been removed.
Thank you,
Slava
Activity
Olen commentedon Nov 7, 2026
The paragraph in README needs to be there, as both integrations can not be installed at the same time. It will lead to conflicts and errors for the users.
When it comes to your notifications and alerts, I added proper "stale sensors" detection to the plant integration (where it belongs) a long time ago. And I recently added triggers for failed OPB-uploads to this integration.
I have also included blueprints to make setting up notifications and alerts easy for everyone.
slaxor505 commentedon Nov 8, 2026
Thanks for explaining. I agree that users need a clear warning that the integrations cannot be installed together.
My objection is to the instruction telling existing Founder Edition users to uninstall it and install yours. Avoiding simultaneous installation does not require users who already have a working installation to switch.
I appreciate that you have added monitoring and notification options. We may still differ in functionality and setup experience, and users should be able to choose.
Would you replace the migration directive with a neutral compatibility warning and make the switching instructions conditional on the user choosing to migrate? That would address the conflict risk while fairly representing both maintained projects.