Also, @athan and anyone using his fork (or their own version) with more than 8 zones be aware that I had to create a new group for each cycle. You will have to add to the groups as appropriate for your extra zones.
I will put one new file and four updated files up now.
New file - I decided to keep all the dynamically created groups in one place garden_globals_groups.yaml
Four updated files garden_globals_cycle1/2/3.yaml and garden_globals_zone_days.yaml
I’m going to be honest and say this is not well tested but the changes are pretty small, the groups all get created correctly in my HA. I think the biggest risk is of typos as there was a fair bit of copy and pasting needed!
Hi klogg i loaded the new files up and encountered a problem (see below), i decided too trouble shoot and reverted back to my back up file, then loaded the new files on one by one, the 'garden_globals_groups.yaml and the four updated files 'garden_globals_cycle1/2/3.yaml loaded fine with no errors in the ui, but once i load the garden_globals_zone_days.yaml is where i encounter the issue, i’ve no ideas what is happening but thought i would let you know.
And the HA logs are stating …
ERROR (MainThread [homeassistant.components.automation.irrigation_create_groups] irrigation_create_groups: Error executing script. Service not found for call_service at pos 1: Unable to find service group/set
and
ERROR (MainThread) [homeassistant.components.automation.irrigation_create_groups] While executing automation automation.irrigation_create_groups
It seems to be saying the service group.set doesn’t exist.
Can you go to the Services tab in Developer Tools and see if you have that service available. Also copy the first template in the automation irrigation_create_groups into the Template Editor and check it resolves to a list of entities.
Also, did you do a full restart of HA or did you reload certain components?
I did a full reset from the HA Server Controls panel and no difference, theres was no service referring to service group.setin the Server tab, and a bunch of entities appeared when i pasted the automation into the Template Editor with a few referring the the irrigation etc.
Then i thought lets reboot the vm as i’m running proxmox and voila, happy chappy and thanks for those pointers they may come in use for other things as well.
Yep it sure was but all seems good to go now, been playing around with the rain integration for weather sensors, as i got a cheap weather station (Netatmo) from a well known auction site.
I copied the code in the thread written earlier on about making a binary sensor for yesterday, and time update changes, it seems to populate ok, now i’m playing around to see which entity plays well with the rain graph yaml to make it look good, and display correctly in the graph.
I have been using Version 1 for a LONG time. I actually ended up re-writing a bunch of the backend in Node Red (just so that there was very little duplication across such a large environment). Now it controls 50+ valves across 30 zones with 180 different cycle runs (hehehe). Yes … it does a lot but it has been ROCK SOLID for a long.
After taking the summer off I come back to find there is a Version #2 with many of the enhancements I was looking at building into our system!! Yippy!
So I fired up a virtualbox, installed everything, followed the various guides (bbogdanmircea & Koggy prerequisits) out there but for some reason I can’t seem to get anything to come up. So what do I mean by this, my screen is completely blank.
After looking at the log file I am getting the following error (s):
2020-09-23 18:20:50 ERROR (MainThread) [homeassistant.components.automation.irrigation_master_control_switch_off] Irrigation Master Control Switch OFF: Error executing script. Service not fou
nd for call_service at pos 3: Unable to find service switch/turn_off
2020-09-23 18:20:50 ERROR (MainThread) [homeassistant.components.automation.irrigation_master_control_switch_off] While executing automation automation.irrigation_master_control_switch_off
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/automation/__init__.py", line 426, in async_trigger
await self.action_script.async_run(
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 944, in async_run
await asyncio.shield(run.async_run())
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 198, in async_run
await self._async_step(log_exceptions=False)
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 206, in _async_step
await getattr(
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 413, in _async_call_service_step
await service_task
File "/usr/src/homeassistant/homeassistant/core.py", line 1265, in async_call
raise ServiceNotFound(domain, service) from None
homeassistant.exceptions.ServiceNotFound: Unable to find service switch/turn_off
PS - I have download the most recent code today.
Can you point me in the right direction where I might try and diagnose what is causing the issue?
Thanks. I look forward to playing with the new version and seeing how it works :).
I have some bugs in Manual mode when I click Stop between proccesing. Something about websocket.
Logger: homeassistant.components.script.irrigation_cancel_irrigation
Source: helpers/script.py:1056
Integration: Script (documentation, issues)
First occurred: September 23, 2020, 2:27:45 PM (14 occurrences)
Last logged: 10:43:04 AM
irrigation_cancel_irrigation: Error executing script. Invalid data for call_service at pos 2: not a valid value for dictionary value @ data[‘entity_id’]
It’s reverted back to a bug again, tried a new install as well as my nearly created back up that was working yesterday to no avail, so going back to my working backup for now.
it seems to keep pointing to the groups but not sure what’s happening myself.