Okay thanks.
I am having some issues with automations in the new packages, hoping you or someone can help. I can manually run the zones but none of the trigger automations are working. When the set time comes, nothing happens and nothing shows in the logs. Here are some observances I have all dealing with cycle 1 as it is the only cycle I use, maybe you can help:
When I change the “Actual Time” start time, nothing appears in the logs.
When I change either the Sunrise or Senset offset options, I do see an automation triggered in the logs but the cycle does not run when the time comes.
When I change individual zone run times, I see automation run entries in the log.
When I change day to run, nothing in the logs.
I have tried with and without the “Adjust for rain/temp” settings checked. I have ran a full host reboot. I have completely removed the package, rebooted, deleted all entities related to the package, re-installed the package, rebooted the host, and re-configured which gives me the same results.
Any help would be appreciated.
Yes I am on that version. 2021.7.4 to be accurate. You have id’s set in the irrigation_triggered.yaml file already though. Do they need to be elsewhere too?
Part of the problem as well. If I scroll down through the Automations page in HA, I see nothing that got triggered or started at the time I have set for the cycle start time. I hope that makes sense.
I mean in Configuration>Automations. I see the automations are there but none of them get “triggered” at the time I have set for the cycle to start. There is also no errors in the HASS log stating that there was an attempt to run an automation and could not find one, had an error, or anything.
Sorry for the dumb question. I’m fairly new to lovelace, and don’t understand how I’m supposed to install this package. I’ve followed the instructions and copied the two directories from github into the \config folder, but nothing happens. I’d highly appreciate it if someone could explain how to get this to show up on the UI?
@ Sumi Have a look here for a more detail instruction about packages etc and how to install the integration to show up in the ui, i must admit it took me a while to get my head around it, but once it’s done you wont regret it as it works like a charm, also take note that these instruction is mentioning about the old package / files but it will be the same principle i believe to set up.
"ButtonCardJSTemplateError: TypeError: Cannot read property 'state' of undefined in 'return states['input_text.irrigation_ui_font_family'].state'"
Error, that has never been answered what causes it:(( So I’m stuck.
I don’t want to sound rude/mean, but why isn’t there a proper installation instructions on github? I see this with a lot of HASS stuff, and it drives me crazy… All they write is “Installation is easy” (just figure it out yourself out of nowhere)
I assume it is correct, because other custom elements seem to be working on the main dashboard (for example the first, the fkf-garbage-collection-card)
Okay, found out how to turn on the Resources tab (needed to enable advanced setting under my profile)
This is what it looks like - I assume this is correct:
You have to also make sure that somewhere in your configuration.yaml file you are specifying another location to look for package files. Something like this
packages: !include_dir_named packages/
Then the Garden Irrigation folder from Klogg will go inside that location like this:
The issue I am having is tied directly to the “Ignore Schedules if Raining” option. I have verified that my raining now sensor is set correctly and is returning an “off” state right now yet the schedules will not run with it enabled. What yaml file is that state held or defined in? What automation uses it as a condition other than iriigation_triggered.yaml? I see this condition in that file:
#=== Check it is not raining if that option is enabled. NOTE: don't check this for cycle 3
- condition: template
value_template: >
{% if is_state('input_boolean.irrigation_ignore_schedule_if_raining', 'off') or
trigger.entity_id == 'input_boolean.irrigation_cycle3_running' %}
True
{% elif states('input_boolean.irrigation_ignore_schedule_if_raining') == 'on' and
states(states('input_text.irrigation_external_sensor_raining_now')) == 'off' %}
True
{% else %}
False
{% endif %}
BUT, if it check that template in the Dev tools area it returns true which is correct if the option is enabled AND it is not currently raining, right?
I have never used that I added it as a feature request a while back and as far as I know it should work ok. I’ll try to find time to look into it later.
Just to really quickly count out the easy things…
I assume you have it set in the ‘Weather Sensors’ pop up?
Also what do you get if you copy this into the Dev Tools template page?
I do have it declared in the Weather Sensors box and the template returns “off”. This switch/option worked great before I installed your latest iteration of the package that had the complete re-write. When I get home from work, I will try to find some time to compare some files to see if I can spot any differences unless you have an idea of where I can look…
As always, we appreciate all your hard work and willingness to share and support this project.