Then please make one! Joking. It is really useful to keep track of modifications and move them between users.
Probably it also makes people dumber as they can use things without thinking so much about what they really do and how they work.
LE: actually klogg integrated this as I pulled from his repo, but still not working for me.
Maybe I’m testing it wrong.
This is the Logbook, I start manually for 7 minute my zone1 - pump, 2 minute my zone2 - onboard_led.
I see now that at some point both my pump and on_board_led become unavailable, could this be the cause why the history is not working ok?? LE: moved my ESP32 close to the router, but still history is not working.
I’ve just downloaded new version from repo and installed without any modification and it’s working for me.
When watering, check value of input_text.irrigation_zoneX_switch_entity_id where X is the zone number that is actually watering, it should contain the real name of your switch that control that pump.
And check also the value of sensor.irrigation_sensor_zoneX_switch corresponding to that zone, that should be ‘on’ during irrigation.
input_text.irrigation_zoneX_switch_entity_id is ok sensor.irrigation_sensor_zoneX_switch is nok, if update it manually from the Developer Tools to on, then the history is also updated accordingly.
Any idea where should I look?
Hi @klogg a little idea to better organize your project.
Is is possible you insert all file actually saved in “package” folder, to a subfolder like “my_garden_irrigation”?
Why?
Cause people mainly use “packages” folder to insert other packages from web…
So it will better organized if you migrate from:
Also, most of tutorial on internet refer to “packages” folder (with s) (used with include_dir)… instead you use “package”.
Changing to “packages” and using sub directory maybe can help people with only a drap/drop from zip to root to update it, without problem and more fast.
This makes no sense to me.
The only problem is that klogg’s work is called package, but it is a package inside packages, so the folder is ok, you can have other folders in packages without conflict.
But it would be nice if package would be renamed to garden_irrigation_v2 maybe.
I compared the folders and they are identical to the repository (which is identical to yours).
Something is really strange.
I restarted HA and now the error is no longer there.
But now I enable the afternoon cycle and I can no longer see the starting time for both the Morning and Afternoon cycle in the dashboard.
klogg -> as I said I am a SW Engineer, can you tell me how you debug the scripts while running, I am used to seeing the values of the variables while running, should I use the Dev Tools to see the values of various things? My problem is that I have no idea to understand what the scripts should do, as I can’t understand the syntax of the yaml files, so it is really difficult to debug where the problem is.
LE: I rechecked now and I think where the problem is, at least for the dashboard not working: I saw that some changes were made in the lovelace folder in the latest pull from klogg, so I reversed the lovelace folder to the state before the pull, and now the dashboard is ok.
Now the question is, is some specific naming needed that is done in the newest lovelace modifications for the zones or the switches that is crashing my dashboard?
If it helps, from time to time i do have some crashes (i believe these are from the custom components, but i could be wrong) and if you just refresh (from the top right menu) everything are fine again.I usually have these crashes (if i recall correctly) when i have 2 tabs of Home Assistant open