That did the trick with the sensor config thanks once again guys…
I forgot to add in my previous reply that you can get all the times back if you press F5 to refresh the browser.
I just uploaded two files to correct the ‘Next Run’ information. It would report the next scheduled run time even of there was no watering in any zone on that day.
section_status_header.yaml
garden_globals_zone_days.yaml
Thanks to @woody4165 for spotting this (and a couple of other small issues that will be resolved over the next day or two)
I’m sorry about all these changes but it is still called a beta 
1 Like
Hi Klogg,
in your GitHub repository description page the link to the prerequisites page is wrong.
You have changed the filename but not the link.
Thank you! 
1 Like
I got the same, finally i reinstalled the whole system. Followed the manuals. And at the end, i got the same error.
I realized if i cut from the view_garden_version2.yaml i got different errors but the ui works, there is no more unknown api error. So i can use the other parts of the ui.
For example view_garden_version2.yaml includes at 18. line the page status. It works till this not calls the section_status_current_status.yaml
In the section_status_current_status.yaml there are lot of
include - item_status_current_activity_line.yaml.
If i comment out all of these includes the api error disappears again.
Emptying of item_status_current_activity_line.yaml doesnt help, only if i comment out all !include phrases.
So its look like the source of api error problem is in hui-element, but at this part i have to give it up. 
I have installed one of the latest update during last 4-5 days from scratch, verifying that all the HACS integrations and frontends are installed properly (in resources: and in configuration.yaml).
Then, I just copied all the files in the repo and followed the prerequisites and readme, and all is working fine.
Now, there is no need to edit any files in this project, except copying the lovelace view in the ui-lovelace.yaml
Many thanks for your help.
I read again what you wrote, and i got an idea, if its necessary to put browser_mod: in configuration.yaml maybe the lovelace_gen: is necessary as well.
So it caused all of my problems, now its running.
Thanks again.
1 Like
@klogg I love your work here… How about we team up? Your awesome interface and intelligent scheduling would make my smart Irrigation based on evaporation shine… Https://github.com/jeroenterheerdt/HAsmartirrigation. I have no idea what the best integration point would be,though,but if you can somehow allow my component to pass the values to yours and your component can render the interface and control the irrigation happening that would be awesome! Let me know! Happy to work on it together!
Ha! I’m the one who asked you a while back about uninstalling your component!
But as I explained then, it was only because I was working on this and I had wanted to just have a play with what you had made.
Anyway, thanks for the kind words. As ever I just stood on the shoulders of giants…
I always had at the back of my mind how cool it would be to build a system around your ‘intelligent watering’. I don’t know how deeply you’ve looked at my system but it does have some very rudimentary adjustments possible for weather conditions. There is no science to mine, just some basic algorithms I played around with until they ‘felt like they gave the right adjustments’.
In principle teaming up seems like good idea but I do need some time and space with this project as I only got to a point yesterday where unless anyone tells me otherwise, I consider it finished (ha ha!), and I am expecting at least some questions, queries and probably some bugs. At least that was my experience with my original Version 1.
Also I need to understand better how your component works although from memory and my brief play with it it seems pretty straight forward from a user perspective.
Maybe there is a Version 3 in the air…
that would be so awesome. Well, I am thinking that if you would create some way of using different ‘calculating engines’ for the required calculations, you could keep your ‘basic algorithms’ around or allow users to user some other solution (like mine). I would think the only thing your component needs is the daily run time based on the bucket that the component keeps track off. So, as long as you can take that runtime, run the watering system for that amount of time and then tell my component you’re done (by calling reset_bucket) we’re good. For my component it would look like just another automation, since my component does not interface directly with valves I think this would be a good fit. Now, for your component the calculations would just be done elsewhere, not inside the component itself. Not sure how easy it is. Looking at the code I think what you would need to do is plug the daily adjusted run time provided by my component in here: https://github.com/kloggy/HA-Irrigation-Version2/blob/7c45bc41b77fb655943d598bc81978dd738e7bf5/package/garden_irrigation_start.yaml#L88 and then of course finish of by calling reset_bucket.
Yes I think that is all that is needed. The duration you’ve pointed to in the code could choose to get it’s number of seconds from anywhere.
I think your component has changed (improved) a bit since I looked. Is it now able to specify times for individual zones?
Also, wouldn’t most of the UI be redundant as the user never needs to choose how long to water for. Maybe a separate/different UI is needed?
I’m just thinking out loud here (so to speak) and actually as I wrote that I just considered that there might be a need for a mix of sources of duration? For example I plan to have a spray for a tree fern which just likes to be made wet every day… and does your method treat all garden area types the same? Grass, flower beds, vegetable gardens etc…
Hi @klogg i’ve just create a little help how to integrate your beautiful system in HA for italian users. I hope to help someone here https://www.domoticadiy.it/2020/06/irrigazione-smart-my-garden-irrigation-home-assistant/
Meanwhile i see you started try to do some select language option 
Btw any idea how to insert the pulsetime tricks compatible with tasmotized switches? (maybe only a select = use pulsetime / don’t use pulsetime in settings?
1 Like
Thank you!
Your Italian guide looks nice (but I don’t understand it! 
)
Languages… yes I started and came up with quite a simple way to do it (but it will take a lot of code changes) but there is a problem with the service input_text.reload. I have raised an issue on GitHub for it and in the meantime I am also thinking about alternatives. We’ll see…
It wouldn’t be a bad idea to include Pulsetime as an option, I can probably lift it straight out of Version 1… I’ll think about doing that…
I’d need someone to test it though as I don’t use sonoff anymore for irrigation 
1 Like
No problem… I can test it 
After this, my wish list terminate with last important request :
A select yes/no to use an external rain sensor (like the one i’ve built in my other tutorial) to check state before start a cicle. If it is on then ignore cycles
1 Like
multi-zone support is done by adding the component multiple times, so that should just work.
I think a UI would still be useful to ‘control’ when the irrigation happens - my component just calculates - it is up to the user to set up something that will actually make the irrigation happen - I can see people wanting to not irrigate every day, but only 3 times a week and at that moment take whatever the daily adjusted run time is that my component provides.
all garden types are the same for my component, because it is just about ‘refilling the soil’ with moisture that was lost (if any). So, if you have multiple zones with different characteristics in terms of number of sprinklers, throughput, etc, you just add the component multiple times and will get specific calculations for each zone.
I upgraded HA to the latest 0.111.0 version and the ui for my irrigation has changed from being three row’s too two, so i rolled back my HA from a back up from a working config to no avail, it does roll back but it does not roll back to the original working os version, it stays on the latest version of 0.111.0 and only rolling back the addons and configs ? it still works but in the ui it wont let you select any settings ie temp, rainfall etc, it looks like this below and i can’t find a way to roll all the way back including the os version previously, luckily i have another instance / vm of HA, but wondering if anyone else has come across this issue since the update.
original 3 rows
After upgrade 2 rows
PS:- going too try re-installing the components to see if that solve the issue.
I think the only way around this will be to use layout-card.
After you’ve installed layout-card you can change the view:
title: Garden
path: garden
icon: mdi:sprinkler-variant
panel: true
cards:
- type: custom:layout-card
layout: horizontal
cards:
# INDENT EVERYTHING BELOW HERE LIKE THIS
#==================
#=== SYSTEM STATUS
#==================
- !include templates/garden/status/page_status.yaml
I’m still on v0.110 but I’ve had this issue with other views before.
1 Like
Thanks Klogg, think i will leave it tonight as it works even tho i can’t change any setting, but it will do for now and probably wait for a fix with the next HA update as my knowledge dose not extend that far as yet.
Could’nt resist myself so i found the yaml file and commented out what you stated above and the view is back, phew … just got to sort out why the temp, rain, clock set, text to name a few bits, why the selection buttons are not working ? but time to chill now.
I use the irrigation system with 4 zones and the last zone when the irrigation ends does not turn off … do you have any idea what it could be?
No. none I’m afraid…
First the obvious question, have you told the UI you have only 4 zones?