Faut deplacer le command_line, tu la copier dans la partie sensor:
.
colle le tout en bas de ton confirugation.yaml.
1 « J'aime »
Merci pour le conseil ca marche niquel! Il me manque plus que ce message d’avertissement :
Logger: homeassistant.helpers.template
Source: helpers/template.py:684
First occurred: 11:16:43 (6 occurrences)
Last logged: 11:16:43
Template variable warning: ‹ dict object › has no attribute ‹ server_name › when rendering ‹ {{ ((states(« sensor.speedtest_cli_data ») | from_json).server_name) }} ›
Template variable warning: ‹ dict object › has no attribute ‹ server_host › when rendering ‹ {{ ((states(« sensor.speedtest_cli_data ») | from_json).server_host) }} ›
Template variable warning: ‹ dict object › has no attribute ‹ url › when rendering ‹ {{ ((states(« sensor.speedtest_cli_data ») | from_json).url) }} ›
rajoute les lignes manquantes:
value_template: >-
{{
{
"ping": value_json.ping.latency,
"download": value_json.download.bandwidth,
"upload": value_json.upload.bandwidth,
"server_name": value_json.server.name,
"server_host": value_json.server.host,
"url": value_json.result.url
}
| to_json
}}
Master of solutions:
value_template: >-
{{
{
"ping": value_json.ping.latency,
"download": value_json.download.bandwidth,
"upload": value_json.upload.bandwidth,
"server_name": value_json.server.name,
"server_host": value_json.server.host,
"url": value_json.result.url
}
| to_json
}}
j’ai une erreur de syntaxe:
missed comma between flow collection entries (134:9)
131 | « server_host »: value_json.ser …
132 | « url »: value_json.result.url
133 | }
134 | | to_json
---------------^
135 | }}
136 |
1 « J'aime »
Par contre tu devrais refaire tes template sensor avec le nouveau format parce que le tiens risque de ne plus marcher prochainement
1 « J'aime »
Surtout que le tutorial est a jour et les sensors template son au nouveau format depuis la création du tuto.
1 « J'aime »
home-assistant:dev
← home-assistant:cmd_line-manual-updating
opened 04:22PM - 11 Jun 23 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO N… OT DELETE ANY TEXT from this template! (unless instructed).
-->
## 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.
-->
Adds `async_update` so it's possible to update data from `homeassistant.update_entity` service call.
## 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
- [x] 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 #94270
- 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.
-->
- [x] The code change is tested and works locally.
- [x] Local tests pass. **Your PR cannot be merged unless tests pass**
- [x] There is no commented out code in this PR.
- [x] I have followed the [development checklist][dev-checklist]
- [x] I have followed the [perfect PR recommendations][perfect-pr]
- [x] The code has been formatted using Black (`black --fast homeassistant tests`)
- [x] 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:
- [x] 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
home-assistant:dev
← home-assistant:cmd_line_reload
opened 07:19PM - 11 Jun 23 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO N… OT DELETE ANY TEXT from this template! (unless instructed).
-->
## 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.
-->
Fix reload service for Command Line.
## 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
- [x] 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 #94202
- 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.
-->
- [x] The code change is tested and works locally.
- [x] Local tests pass. **Your PR cannot be merged unless tests pass**
- [x] There is no commented out code in this PR.
- [x] I have followed the [development checklist][dev-checklist]
- [x] I have followed the [perfect PR recommendations][perfect-pr]
- [x] The code has been formatted using Black (`black --fast homeassistant tests`)
- [x] 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:
- [x] 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
Plus cas attendre la sortie du core 2023.6.2
Ah cooooool !!! vivement la 6.2 alors
C’est bon, ca fonctionne a nouveau avec la 2023.6.2.
Bizarre, chez moi c’est toujours pas fonctionnel…
Tu passes par le service homeassistant.update_entity ?
service: homeassistant.update_entity
data: {}
target:
entity_id: sensor.speedtest_cli_data
Oui, j’ai fais un appel dans service. Par contre j’ai pas vue appeler le service qui passe en vert quand tu clique dessus et de message comme quoi le service c’est lancer avec succès.
Après un reboot c’est tout bon
Bonsoir tout le monde,
Quelqu’un saurait-il comment récupérer l’adresse IP externe en IPV4, car speedtest l’a retourne en IPV6?
Bonjour,
avec l’intégration de ta box internet , tu peu récuperer l’ip externe.
Pour les Livebox , faut utiliser l’intégration custom GitHub - cyr-ius/hass-livebox-component: Livebox Component for Home assistant
Bonsoir, merci pour la réponse rapide.
Par contre l’integration depuis GitHub ne fonctionne pas.
![Livebox_integration_erreur|562x227](upload://1bDaz7QmZqaNfWcbHHlSPWp01zT.png)
Je suis sous la dernière version HAOS.
Merci à vous
Faut l’installer a partir de HACS ( https://hacs.xyz/ ), dans intégration , recherchez Orange Livebox Router
et installer.
Configuration
The preferred way to setup the Orange Livebox platform is by enabling the discovery component.
Add Livebox module via HACS
Add your device via the Integration menu