Mon problème
Bonjour à tous,
je viens vers vous car mon entité Portail venant de HA s’affiche comme un Garage dans Google Home.
Le même portail intégré depuis Jeedom s’affiche bien comme un Portail.
J’ai l’impression que la gestion des « Trait Google » dans HA ne tient pas compte de la class Gate(portail).
Sauriez vous si cela pourrais être corrigé car c’est le dernier équipement à migrer pour me séparer définitivement de Jeedom ?
Etant donné que Jeedom envoi bien le bon « trait » à Google Home, je suppose qu’il manque juste cette prise en compte du coté de l’intégration Google-Assistant de HA.
Merci à vous.
Concernant HA, j’ai bien paramétré mon entité en tant que Portail (device_class: gate).
Voici ma configuration.yaml qui concerne ce sujet :
google_assistant:
project_id: xxxxxxx
service_account: !include SERVICE_ACCOUNT.JSON
report_state: true
expose_by_default: false
entity_config:
**cover.portail_virt:**
**name: Portail (HA)**
**room: Accueil**
**expose: true**
cover:
- platform: template
covers:
portail_virt:
unique_id: cover.portail_template
friendly_name: "Portail"
device_class: gate
position_template: "{{ 100 if is_state('binary_sensor.ouvrant_portail_porte_5', 'on') else 0 }}"
open_cover:
service: cover.open_cover
data:
entity_id: cover.portail
close_cover:
service: cover.close_cover
data:
entity_id: cover.portail
stop_cover:
service: cover.stop_cover
data:
entity_id: cover.portail
icon_template: >-
{% if is_state('binary_sensor.ouvrant_portail_porte_5', 'on') %}
mdi:gate-open
{% else %}
mdi:gate
{% endif %}
Ma configuration
System Information
version | core-2024.5.2
-- | --
installation_type | Home Assistant OS
dev | false
hassio | true
docker | true
user | root
virtualenv | false
python_version | 3.12.2
os_name | Linux
os_version | 6.6.29-haos
arch | x86_64
timezone | Europe/Paris
config_dir | /config
<details><summary>Home Assistant Community Store</summary>
GitHub API | ok
-- | --
GitHub Content | ok
GitHub Web | ok
GitHub API Calls Remaining | 5000
Installed Version | 1.34.0
Stage | running
Available Repositories | 1399
Downloaded Repositories | 9
HACS Data | ok
</details>
<details><summary>Home Assistant Cloud</summary>
logged_in | false
-- | --
can_reach_cert_server | ok
can_reach_cloud_auth | ok
can_reach_cloud | ok
</details>
<details><summary>Home Assistant Supervisor</summary>
host_os | Home Assistant OS 12.3
-- | --
update_channel | stable
supervisor_version | supervisor-2024.05.1
agent_version | 1.6.0
docker_version | 25.0.5
disk_total | 30.8 GB
disk_used | 13.0 GB
healthy | true
supported | true
board | ova
supervisor_api | ok
version_api | ok
installed_addons | Samba share (12.3.1), Mosquitto broker (6.4.0), Zigbee2MQTT (1.36.1-1), File editor (5.8.0), Node-RED (17.0.12), AirSend (1.2), Terminal & SSH (9.13.0), Grafana (9.2.2), Studio Code Server (5.15.0), Matter Server (5.6.0), Let's Encrypt (5.0.18)
</details>
<details><summary>Dashboards</summary>
dashboards | 4
-- | --
resources | 2
views | 8
mode | storage
</details>
<details><summary>Recorder</summary>
oldest_recorder_run | 28 avril 2024 à 22:26
-- | --
current_recorder_run | 8 mai 2024 à 23:34
estimated_db_size | 2345.97 MiB
database_engine | sqlite
database_version | 3.44.2
</details>
Bonjour,
clique sur ton entité portail et va dans la roue cranté. Change afficher en tant que
et peu être ouverture ou porte.
Bonjour et merci pour ton retour rapide.
En effet que je choisis porte j’ai bien un icône de porte dans Google home.
Ce que je souhaiterais c’est avoir un icône de portail.
J’ai bien choisi portail dans afficher en tant que…
Le choix « Ouverture » ne m’est pas proposé sur ce cover.
J’ai le choix ouverture pour mes binary_sensor mais pas pour le cover template.
J’arrive toujours pas à afficher un icône de portail sur Google home.
Si quelqu’un a une solution je suis preneur.
Merci en tout cas.
Bonjour à tous,
j’utilise l’intégration google_assistant afin de piloter mon portail (gate) depuis Google Home.
Mon problème est simplement que mon portail est afficher dans Google Home « en tant que Garage » alors qu’il est bien afficher « en tant que Portail » dans HA.
En fouillant dans le code de l’intégration google_assistant sur github, j’ai découvert cette portion de code qui semble être responsable du mauvais type d’appareil remonté dans Google Home concernant mon portail.
Serait-il possible pour un développeur d’essayer d’améliorer l’intégration et de permettre que le bon type d’appareil (Gate) soit signalé dans GooGle Home ?
Merci d’avance.
J’ai vérifié coté documentation Google et il accepte le type Gate de leur coté.
Bonjour à tous,
Pour information, j’ai réussis à trouvé la solution et j’ai ouvert une issue sur le git homeassistant :
opened 02:06AM - 20 May 24 UTC
integration: google_assistant
### The problem
**Description of the issue**:
In the Google Assistant integrat… ion, the device class of the entity "Gate" is incorrectly assigned as "Garage". This results in improper handling of the device by Google Assistant.
**Technical details**:
I believe I have identified a part of the code that might be responsible for this issue:
- **File**: `core/homeassistant/components/google_assistant/const.py`
- **Lines**: 173 and 174

**Steps to reproduce the issue**:
1. Configure an entity of type "Gate" in Home Assistant.
2. Sync the entity with Google Assistant.
3. Observe that Google Assistant recognizes it as a "Garage" instead of a "Gate".
The entity "Gate" should be correctly recognized by Google Assistant as a "Gate".
**Current result**:
The entity "Gate" is assigned as a "Garage".
Thank you for your assistance in correcting this issue.
### What version of Home Assistant Core has the issue?
core-2024.5.4
### What was the last working version of Home Assistant Core?
_No response_
### What type of installation are you running?
Home Assistant OS
### Integration causing the issue
Google Assistant
### Link to integration documentation on our website
_No response_
### Diagnostics information
_No response_
### Example YAML snippet
_No response_
### Anything in the logs that might be useful for us?
_No response_
### Additional information
_No response_
Bonjour,
J’ai finalement réussi à faire mon premier PR.
Fork > Créer ma branche > mettre à jour/modifier le fichier > commit > pull request
home-assistant:dev
← Bygood91:google_assistante_gate_device_type
opened 09:44PM - 25 May 24 UTC
Update const.py for correctly send Gate device type to Google Assistant.

<!--
You are amazing! Thanks for contributing to our project!
Please, DO NOT DELETE ANY TEXT from this template! (unless instructed).
-->
## Breaking change
<!--
If your PR contains a breaking change for existing users, it is important
to tell them what breaks, how to make it work again and why we did this.
This piece of text is published with the release notes, so it helps if you
write it towards our users, not us.
Note: Remove this section if this PR is NOT a breaking change.
-->
## Proposed change
<!--
Describe the big picture of your changes here to communicate to the
maintainers why we should accept this pull request. If it fixes a bug
or resolves a feature request, be sure to link to that issue in the
additional information section.
-->
## Type of change
<!--
What type of change does your PR introduce to Home Assistant?
NOTE: Please, check only 1! box!
If your PR requires multiple boxes to be checked, you'll most likely need to
split it into multiple PRs. This makes things easier and faster to code review.
-->
- [ ] Dependency upgrade
- [ ] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [ ] New feature (which adds functionality to an existing integration)
- [ ] Deprecation (breaking change to happen in the future)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- This PR fixes or closes issue: fixes #
- This PR is related to issue:
- Link to documentation pull request:
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [ ] The code change is tested and works locally.
- [ ] Local tests pass. **Your PR cannot be merged unless tests pass**
- [ ] There is no commented out code in this PR.
- [ ] I have followed the [development checklist][dev-checklist]
- [ ] I have followed the [perfect PR recommendations][perfect-pr]
- [ ] The code has been formatted using Ruff (`ruff format homeassistant tests`)
- [ ] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [ ] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [ ] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- [ ] Untested files have been added to `.coveragerc`.
<!--
This project is very active and we have a high turnover of pull requests.
Unfortunately, the number of incoming pull requests is higher than what our
reviewers can review and merge so there is a long backlog of pull requests
waiting for review. You can help here!
By reviewing another pull request, you will help raise the code quality of
that pull request and the final review will be faster. This way the general
pace of pull request reviews will go up and your wait time will go down.
When picking a pull request to review, try to choose one that hasn't yet
been reviewed.
Thanks for helping out!
-->
To help with the load of incoming pull requests:
- [ ] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone+-status%3Afailure
<!--
Thank you for contributing <3
Below, some useful links you could explore:
-->
[dev-checklist]: https://developers.home-assistant.io/docs/development_checklist/
[manifest-docs]: https://developers.home-assistant.io/docs/creating_integration_manifest/
[quality-scale]: https://developers.home-assistant.io/docs/integration_quality_scale_index/
[docs-repository]: https://github.com/home-assistant/home-assistant.io
[perfect-pr]: https://developers.home-assistant.io/docs/review-process/#creating-the-perfect-pr