My Garden Irrigation

Hello @klogg , I know you’re really busy, btw thumbs up for the great job.
Thanks to @cecet23 and @jgosnell I was able to solve some issues on my HA 2021.3.1 which I reassume as follow:

  • problem with layout and WiFi signal strength. If not populated with a correct device which gives the signal, afaik the default value breakes the module and the page is not loaded correctly
  • problem with popups not opened anymore. Due browser_mod update, the deviceID: - this needs to be commented / removed.
  • problems with scheduler. The scheduler is not shown due the date is taken wrong. @cecet23 explained well how to solve it on post #1244.

You could implement those mods in your repo, as soon you have time of course!

I’m still on the way to test my personal rain sensor which would be great if a semaphore would show if the next irrigation cycle would start if the sensor is in wet status. I’ll test it soon.
Same for weather forecat, actually not really tests.

for the rest, for now it works mostly very well!

Thanks a lot!

Simon

1 Like

Update: rain sensor works as expected. If the “ignore schedules if it’s raining” is enabled, the raining sensor is set to my device and the sensor is wet, the scheduler is not executed.
On aside, nice would, as previous written, not only a semaphore that shows if the raining sensor would stop the schedule or not, but even in the logs, a line that actually tells you that the programmed schedule was skipped due the raining sensor.
I paste here my sensor and it’s state as wet, and so that prevents the irrigation schedule:

entity: binary_sensor.sensorepioggia_contact
state: on
battery: 91
contact: false
linkquality: 152
voltage: 2985
friendly_name: SensorePioggia contact
device_class: moisture

Hope that helps somebody!

Bye, Simon

1 Like

Hi,
I installed it on Home Assistant 2021.3.4, but this is the result:
Ipoup-up doesn’t work…

Hi
Let me introduce myself, I’m from Cape Town and have been tinkering with electronics for many years.
I’ve been trying to implement HA-Irrigation V2 for the past 4 days, restarted from scratch 3 times but am always coming up with and error that blocks HA from loading.
Latest version of HA OS ( 2021.3.4 ).

I’m more thank likely missing something stupid, can anyone assist?

Many thanks
Charles

config ha core check
Processing… Done.

Error: Testing configuration at /config
Failed config
homeassistant:
- expected a dictionary for dictionary value @ data[‘packages’][‘automation’]
- packages: [source /config/configuration.yaml:3]
automation: [source /config/packages/garden/garden_weather_temperature.yaml:10]
- action: [source /config/packages/garden/garden_weather_temperature.yaml:31]
- data_template: [source /config/packages/garden/garden_weather_temperature.yaml:33]
entity_id: input_text.irrigation_external_sensor_forecast_high_temp
value: sensor.dark_sky_daytime_high_temperature_0d
service: input_text.set_value
alias: Irrigation Set Default Forecast High Temperature Sensor
condition: [source /config/packages/garden/garden_weather_temperature.yaml:20]

default_config:

homeassistant:
packages: !include_dir_merge_named packages/

frontend:
themes: !include_dir_merge_named themes

browser_mod:

lovelace_gen:

lovelace:
mode: storage
dashboards:
lovelace-irrigation:
mode: yaml
filename: irrigation.yaml
title: Irrigation
icon: hass:flower
show_in_sidebar: true

sensor:

  • platform: time_date
    display_options:

    • “time”
    • “date”
    • “date_time”
    • “date_time_utc”
    • “date_time_iso”
    • “time_date”
    • “time_utc”
    • “beat”
  • platform: emoncms
    api_key: 8ad5f5882eb30cac77091bc71f65a4ce
    url: http://192.168.0.10/emoncms
    unit_of_measurement: “C”
    id: 101

  • platform: mqtt
    name: geyser1_temperature
    state_topic: /geyser1/temperature
    unit_of_measurement: °C

  • platform: sun2
    monitored_conditions:

    • sunrise
    • sunset

binary_sensor:

  • platform: sun2
    monitored_conditions:
    • elevation

switch:

  • platform: mqtt
    name: geyser1
    state_topic: /geyser1/relay/0
    command_topic: /geyser1/relay/0/set
    payload_on: 1
    payload_off: 0
    availability_topic: /geyser1/status
    payload_available: 1
    payload_not_available: 0
http:
  # Uncomment this to add a password (recommended!)
  # api_password: PASSWORD
  # Uncomment this if you are using SSL or running in Docker etc
  # base_url: example.duckdns.org:8123

# Checks for available updates
updater:

# Discover some devices automatically
discovery:

# Allows you to issue voice commands from the frontend in enabled browsers
conversation:

# Enables support for tracking state changes over time.
history:

# View all events in a logbook
logbook:

# Track the sun
sun:

Try to lose the forward slash in your package include.

I use the following.

‘packages: !include_dir_named packages’

Hi Hantrax, I have fixed the issue. It’s related to new version of browser_mod.
Follow this steps:

  1. search in the repository github project of @Koggly (https://github.com/kloggy/HA-Irrigation-Version2) all occurrences of deviceID:

The result is 17 files.

  1. for each file, delete the entry
 deviceID:
   - this
  1. in each file, search:
tap_action:
   action: call-service
   service: browser_mod.popup
   service_data:

and replace with:

tap_action:
   action: fire-dom-event
   browser_mod:
     command: popup
1 Like

Hi Mertz
Many thanks, I mentioned it would be something stupid, The documentaion does mention one can put the packages anywhere in subfolders under the packages directory if one uses the merge include, I’ve put them in the root packages dir and used the normal named include and no more errors (Well ha core check doesnt pck anything up!)
Irrigation panel still blank and errors in my log file which I’m going to check now.

I have tried this solution but many errors come out.

I finally solved it. Thanks to pask23.

FIX LAYOUT: (in file “view_garden_version2.yaml”)
change:

  # Display columns correctly using layout-card
  - type: custom:layout-card
    layout: horizontal
    cards:

with:

  # Display columns correctly using layout-card
  - type: custom:layout-card
    layout_type: custom:horizontal-layout
    cards:

Fantastic. Thanks lion06.

Just a quick note here to apologise at my lack of responses but I am still finding it hard to make any time for HA at the moment.

I do definitely plan to address all the issues in the coming weeks but until then thanks to everyone who is responding with answers to queries.

Also I should add that I brought my system out of hibernation last week in preparation of the good weather and my setup seems to be running as expected, so if you are having issues and want to persevere it should work.

Note that I have not yet updated layout-card because as @gianni_Barin and @lion06 have seen it is a breaking change.

So apart from the strange date issue which doesn’t cause me a problem but is solved for those where it does (and is better code which I will incorporate!) by @cecet23 and the removal of deviceID: this there is nothing else that should prevent the system working.

2 Likes

Hello. I just installed this project and after several corrections the only thing that it’s not working is the scheduling start, even selecting every day, the start time and end time are correct but it doesn’t start, if I select the manual start it works. Can someone help?
My HA is at 2021.3.4
Regards

I’ve updated the code on Github for correct start date/time as suggested by @cecet23.

I think that is the issue causing most problems especially to people finding this project recently for the first time. To be honest I don’t know why it was causing some people problems. It can’t be a simple time zone issue as I know people in different time zones to me are using it successfully. If anyone does know the answer I’m very interested!

I’m pretty sure that everything else is down to breaking changes in Lovelace custom cards.

2 Likes

I’m my case the end time is correct but the irrigation doesn’t start and it imediatly updates next run time.

Thanks for the work you do.

Wrong end time.
immagine

1 Like

I have this issue and cannot solve it.

have you tried to change “Maximum Time to Run a Zone” in general settings?

If you could just please try your V1.0 and see if it’s still working for you…
…probably it’s just something in water time calculation that doesn’t work anymore, but I can’t figure it out :worried: