untill now, the Cover: domain is still exposed as a switcn On/Off/Brightness
doesnt make sense offcourse, we need the open/close stuff
The Api is available, so the assistant component needs a smaill change
@balloob , i dont know how to make a request for the HA cloud edition , i am using that too? i have heard you manage that? Its a paid service, so it needs maybe priority?
I don’t care if I see a switch icon in the google home app. What I am telling you is that by TELLING google assistant to OPEN the door it works.
I am well aware of how it USED to act. I USED to have to tell it to turn ON the garage door. This changed at least a month ago. I did NOTHING to make it work.
yes , proper domain would be better, but still i dont get how @flamingm0e can say open/close , when at the moment the cover domain is exposed a a switch on/off
the cover domain, does excists now, i have posted the api in first post, the code should be changed, and cover domain added
I have no idea what changed in either Google or Home Assistant, but I can freely say Open/Close Garage Door and it just works. The response I get back from Google confirming the command is “Turning on/off the garage door”
Right now I’m using a custom tasmota (specific for rolling shutters) that exposes covers as lights, so i can say Turn on (accendi in italian) and set (imposta) to open cover at a specific percentage.
well, i cant controll my cover at a specific level, i can only do a cover open and close, and can do a stop command
but right now, i am exposing a test cover as a GARAGE
this my config, its a command line cover
just tested a new cover, named in “garage door” , but still
if i say : “Garage door ON” it works,
if i say “Garage door OPEN” , i get respond : it looks like this device hasnt been setup yet
yeah, somehow, it the google config, i need to take the friendly name
no idea why , but it works like that
i should actually make change friendly name to name, its the same
but it works like this
also has nothing todo with open/close on/off anyway