He’s gonna use the automation editor … !!!
Does the automation editor, store the automation’s in automation.yaml, in the config folder?
Yeah I think so, the early version tried to put it all in configuration.yaml but later versions come with redirectors for automations, scripts, customization etc. with the necessary blank files already in place.
I’m 85% sure that’s the case anyway. One of them even had a strange [] entry, now I know that’s automation editor speak for “nothing to see here, move on”
How about you get him to install samba. navigate to the file. copy it, and then send it to you.
(you could pm him your email)
You could edit it, check the config and the logic, and send it back for him to paste back in place of his existing. ???
That is a good idea @RemcovanKuilenburg are you getting all of this, you on board for something like that?
Error loading /home/homeassistant/.homeassistant/configuration.yaml: while scanning a quoted scalar
in “/home/homeassistant/.homeassistant/automations.yaml”, line 31, column 16
found unexpected end of stream
in “/home/homeassistant/.homeassistant/automations.yaml”, line 39, column 1
Guys guys. I’m using the text editor on my mac. I connect to the PI and go to the
root@hassbian:/home/homeassistant/.homeassistant#
After that I’m using nano automations.yaml to enter the file and I can change tekst. That is what I do all the time.
What I mentioned is that first I started the automation trough the UI and that gives the result that the beginning of my yaml file is strange and generated trough the UI. So that why it looks like a mess. Like I mentioned I will change those after we have nailed this gate part.
So no hard feelings we all want to help.
k tell me what is at line 31 and line 39
Funny enough line 39 is not there.
- id: '1566418818385'
alias: GoGoGate open licht aan
trigger:
platform: state
entity_id: cover.hek
from: "closed"
to: "open"
condition:
- condition: time
after: '00:00:00'
action:
- service: scene.turn_on
entity_id: scene.garden_lights_bright
- service: switch.turn_on
entity_id: switch.qubino_goap_zmnhbdx_flush_2_relays_switch
- id: '1566423130786'
alias: GoGoGate dicht licht uit
trigger:
platform: state
entity_id: cover.hek
from: "open"
to: "closed"
condition:
condition: and
conditions:
- condition: time
after: '00:00:00'
- condition: state
entity_id: sun.sun
state: 'below_horizon
action:
- service: scene.turn_on
entity_id: scene.garden_lights_dim
- delay:
minutes: 1
- service: switch.turn_off
entity_id: switch.qubino_goap_zmnhbdx_flush_2_relays_switch
This is missing it’s closing quote, should be this:
state: 'below_horizon'
Jus for me. How do you count lines?
1 - id: '1566418818385'
2 alias: GoGoGate open licht aan
3 trigger:
4 platform: state
5 entity_id: cover.hek
6 from: "closed"
7 to: "open"
8 condition:
9 - condition: time
10 after: '00:00:00'
11 action:
12 - service: scene.turn_on
13 entity_id: scene.garden_lights_bright
14 - service: switch.turn_on
15 entity_id: switch.qubino_goap_zmnhbdx_flush_2_relays_switch
16
17 - id: '1566423130786'
18 alias: GoGoGate dicht licht uit
19 trigger:
20 platform: state
21 entity_id: cover.hek
22 from: "open"
23 to: "closed"
24 condition:
25 condition: and
26 conditions:
27 - condition: time
28 after: '00:00:00'
29 - condition: state
30 entity_id: sun.sun
31 state: 'below_horizon
32 action:
33 - service: scene.turn_on
34 entity_id: scene.garden_lights_dim
35 - delay:
36 minutes: 1
37 - service: switch.turn_off
38 entity_id: switch.qubino_goap_zmnhbdx_flush_2_relays_switch
Or do you skip line 16 because it is blank?
Changed it and now rebooting
The number are right, and you count the blank lines. The error tells us there is an issue with line 31 and above I showed you how to fix that.
YESSSSSS that is working and check config is green. So happy.
YEEEEEEEAAAAAAAAAHHHHHHHH!!! Time to party.
So when I test the automation GoGoGate open the garage lights are going on. But the Gate lights are not going from dim to full.
When I’m testing the GoGoGate close the Garage lights are going off after one min and the gate lights stay dimmed. It is random and tested it now several times and one time worked
Where the hell is @Mutt at, time to celebrate.
On thing that I did notice, we probably should change is:
condition:
- condition: time
after: '00:00:00'
to
condition:
- condition: time
after: '00:00:00'
before: '06:00:00'
If I’m right it is not after Midnight there yet right?
No it is 22:50 at the moment. But I triggered the automation manual and now it is working but not all the time. Will see what is what.