I’ve only been trying it in the UI. When I search for Flower, nothing shows. Hmmm. I just re installed it for fun and now I see it in HACS. At least it stays there but there is not Flower Card folder in the community folder. So that’s weird.
I’ll try adding the card manually.
I’m guessing you did refresh your browser cache as HA reminds you to
Yes I did.
Strangely enough. Adding it manually worked.
I still don’t see it in my HACS or in the card selection when in UI mode.
Still no Flower-Card folder in the community folder.
But it works so I’m happy.
Thanks for pushing me to try it manually.
Well theres definitely something strange going on with your config because it should show up in the UI.
Notice that it is called “lovelace-flower-card” in the community-folder.
Well this morning it’s everywhere to be seen! In the community folder and in the search UI section. All is good. Thanks Olen for putting this nice little card together.
Seems that @goatboynz has created a low cost DLI/Sunlight scanner. More details here: Spectrum Card
If this could be structured a bit better, would be a nice all-in-one device for our gardens. I’d love to see how much I torture my plants in South Florida over the summer…
Hi all!
New version of HASS - OpenPlantbook integration 1.4.0 available at:
What’s New in version 1.4
- Sensor monitoring warnings — Stale or missing sensor updates are flagged during upload runs.
- International common names — OpenPlantbook can return common names in your Home Assistant language.
Currently as beta so please consider to test and feedback if any issues.
I’m quite disappointed by this.
You have submitted several PRs to the integration, and I have provided concrete, constructive feedback on each of them:
- 1.4.0-beta3 by slaxor505 · Pull Request #67 · Olen/home-assistant-openplantbook · GitHub
- v1.4.0-beta2 by slaxor505 · Pull Request #64 · Olen/home-assistant-openplantbook · GitHub
Rather than addressing the issues I raised, you’ve chosen to post here announcing your fork as the “new version.”
This is open source, and you are of course free to fork the repo — that’s your right. But the spirit of open source is that we collaborate and build things together, not that we splinter off and position a fork as a replacement the moment a code review doesn’t go our way.
1 Like
Hey mate. Sorry, I did not mean to disappoint you. I positioned it as beta version but not release. I also did publish the same via other channels/forums much earlier. The intent was that people can get early access to new features while there are back and forth to fix PR stuff. The new features I believe were long requested and waited and since your PR review found no significant but rather superficial issues I see no problems here. Having said that the early testing can also potentially reveal something else so it can be fixed along in the next beta.
I invest almost all my time in Open Plantbook development and unfortunately I don’t have much spare for the integration development hence fixing all the superficial findings from AI agents takes toll on me and is less priority. Because of that I want the testing going sooner than later.