Yep… Same boat. Although my wife is trying. My father gets it, my mother just doesn’t listen and tries whatever comes to her head.
They are right … technology has to adapt to people not the other way around
1 Like
I tell them if they don’t start turning off lights I’ll automate them off 
I think Google handles requests like your mother’s better than Alexa, I’ll have to try it today.
I did that, and since my room presence is far from perfect (xiaomi PIR sensors mainly), they are cursing me all the time: lights go off many times when they are in the room.
I really hope for a easy fast and secure room presence solution
I’m sure it does. Alexa is a pain in the ass but I don’t think I could switch. It would be a pain to reteach myself to say ‘okay google’. I already have issues with alexa listening to me. Also, I don’t think google home would play amazon music. Gotta love that feud.
1 Like
Where is that?
OOPPPSSS problem was not Google Asisstant, problem was in the script, just now I realized that this script in HASS is (since I made the transition to script editor)
script.3645635645362 !!!
'3645635645362':
alias: guest_room_tv_on
sequence:
- entity_id: switch.guest_room_tv_power_plug
service: switch.turn_on
- delay: 300 ms
- entity_id: media_player.yamaha_receiver
service: media_player.turn_on
- data:
source: Shield
entity_id: media_player.yamaha_receiver
service: media_player.select_source
- entity_id: switch.panasonic_tv
service: switch.turn_on
I reply to them with “Tough, deal with it 
” 
Oh man this script editor sintax is so complicated to me … is the below correct syntax? Is the dleay correct (300ms) as it is written?
Because as below is not working
'guest_room_tv_on':
alias: guest_room_tv_on
sequence:
- entity_id: switch.guest_room_tv_power_plug
service: switch.turn_on
- delay: 300ms
- entity_id: media_player.yamaha_receiver
service: media_player.turn_on
- delay: 300ms
- data:
source: Shield
entity_id: media_player.yamaha_receiver
service: media_player.select_source
- entity_id: switch.panasonic_tv
service: switch.turn_on
'guest_room_tv_off':
alias: guest_room_tv_off
sequence:
- entity_id: switch.panasonic_tv
service: switch.turn_off
- delay: 300ms
- entity_id: media_player.yamaha_receiver
service: media_player.turn_off
- delay: 300ms
- entity_id: switch.guest_room_tv_power_plug
service: switch.turn_off
switch entity_id with service
since when has this ever worked?
- delay:
milliseconds: 300
That’s not the automatic editor
yah you don’t need to swap them around. Order doesn’t matter. But those delays look wrong.
I don’t define a name and don’t use aliases either. It just uses the friendly name in Google then.
If I did use Aliases I’d want to define them in HA rather than Google though as I find that easier to just sync rather than having to change stuff in the home app… I likewise define rooms in HA rather than Google. Makes it way simpler if I have to unlink/relink the app.
The format I posted is correct…
I do this as well, except I do define the name.
I might have missed it, but in case you need to update; Operating System, Supervisor and also Home Assistant - what would the correct order be then?
Don’t think there is correct order, doesnt matter 
Supervisor updates itself. The other 2 - it doesn’t matter. My preference would be to update HA first then HassOS but that’s just a preference…
1 Like