Closed atallo closed 2 years ago
Hi, integrations are not responsible to what is exposed within Google Assistant, Alexa, and Home Kit. I guess there is something wrong in your Google Assistant configuration within HA. Please have a look to the documentation.
I don't think it's a problem with Google Home.
I've been doing more tests, I think this component could be improved (a little more) but you can close this issue.
Google Home needs the device to be of type "cover" and this component creates it as "shutter", whereas the old integration did it as "cover" and that's why it worked correctly.
I just changed the type manually, and now Google Home detects it correctly.
Thank you and sorry.
You can see the device classes description here. We tried to respect it as much as possible.
I add a couple of screenshots so you can see the difference.a.
Using this integrantion:
Using old integration (work in Google Home)
Change type in HA, using this integration (work in Google Home)
To be honest within the Somfy integration, I didn’t be really accurate within the device class. Somfy didn’t send anything special to distinct the type of cover. But it’s the case here.
Can you please attach here the diagnotic information related to your device if you are using the "offial" overkiz component or the debug log if you are still using this custom component (not recommanded anymore if you have only cover)?
Is this product: https://www.somfy.es/productos/persianas-y-estores-motorizados/persianas-motorizadas Working video https://www.youtube.com/watch?v=8Gp6lgSkzWs (tipical used in Spain)
Did you read the instructions?
The request
I have several Sonfy automatic covers. When I use them in HA using "https://www.home-assistant.io/integrations/somfy" I can use them from Google Home. Instead when I add them to HA using "https://www.home-assistant.io/integrations/overkiz" in Google Home they appear differently and I can't manage them from the app.
Which gateway / hub do you use?
conxion
Device model (optional)
No response
Device type (optional)
No response
Additional information
No response