Bj
la team c’est quoi le souci pour censuré ??
pour cela ???
Makai
Août 21, 2023, 8:02
2
Commentaire non constructif sûrement, non ? A ma connaissance le genre de commentaire que l’on trouve partout sur le forum jeedom et qui pourri l’ambiance…
Il aurait mieux valu ne rien dire ou aider vu qu’on est sur un forum d’entre aide.
(Ce n’est que mon avis et ce n’est pas moi qui ai signaler le post)
7 « J'aime »
Hello
ouais l’époque sous jeedom , j’ai donné avec leurs forum de M…
Salut,
Signalé par un utilisateur donc par précaution, ça masque jusqu’à décision.
Décision que j’ai prise : remise de la réponse après édition des commentaires qui ne sont pas nécessaires
Un petit bonjour, un message courtois, c’est à cette condition que l’ambiance ne virera pas au cauchemar.
Merci à tous de d’agir dans ce cens.
8 « J'aime »
@Pulpy-Luke
tu sais après lecture de certain post , je dis pas bonjour car la demande y’a pas de bj et ou merci et autre donc je répond ainsi.
autre poste qui dis bj , la je commence par Bj* aussi (*bonjour)
et juste un autre délire j’ai fait une recherche avec le mot M…R.DE la vous avez du boulot la team , mdr…
mais surtout ne devenais ce qui devenu la modo sur le forum jeedom
au passage, merci de ton intervention
Comme quoi la censure n’est pas si omniprésente que ça
3 « J'aime »
Euh, surtout que c’est moi qui ai signalé, mais pas pour le dernier message de @Nothing , mais pour que le sujet soit fermé, comme tout ceux traitant de l’alerte de modifications MQTT.
Je pense qu’il y a eu maldonne.
Il n’y a pas mal donne, il y a eu plusieurs signalements (3) sur plusieurs messages (me suis demandé si c’était pas un jeu) en quelques heures…
mais pour que le sujet soit fermé, comme tout ceux traitant de l’alerte de modifications MQTT.
Alors pour le coup, ça peut paraitre bête mais un rapide survol du forum et je n’ai pas vu de message traitant du sujet. Je pense que tu parle de l’alerte sur " Entités MQTT découvertes avec un nom commençant par le nom de l’appareil".
J’ai cette alerte et je ne m’en suis pas trop soucié a part venir vite fait sur le forum ici pour voir si j’étais le seul. Bon quand j’ai vu la date d’application, je me suis dit : plus tard !
Mais ça m’intéresse si tu a des liens sur le sujets.
Hello @Babidi
Sujet abordé dès la sortie de la version 2023.8
Entre autres ici :
Bonjour à tous,
Ce n’est pas vraiment un problème mais je viens d’effectuer la mise à jour d’home assistant et j’ai deux messages de corrections dans Home assistant.
Mon problème
[image]
[image]
Que suis-je censé faire? Tout renommer?
Merci d’avance pour votre aide et bonne soirée
Ma configuration
[center]## System Information
version
core-2023.8.0
installation_type
Home Assistant OS
dev
false
hassio
true
docker
true
user
root
virtualenv
false
python_version
3…
2 « J'aime »
Makai
Août 22, 2023, 7:12
12
Le message disparaîtra avec la prochaine petite mise à jour (2023.8.4). Un retour arrière a été fait pour tout ce qui découvert automatiquement. Plus d’info en anglais ici :
home-assistant:dev
← home-assistant:frenck-2023-1166
opened 05:26PM - 21 Aug 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.
-->
This PR reverts/removes the creation of repairs issues for the MQTT integration, on entities that are created by MQTT discovery, as introduced in Home Assistant 2023.8.
- These repair issues seem to cause/trigger quite a lot of fuzz that should not be needed; there are quite a lot of topics across different socials on this.
- This repair issue is mostly misunderstood as a breaking change, while it is not breaking at all. The original intent was to inform and to get people to report issues upstream to third-party software that integrate with Home Assistant over MQTT. It is currently handled gracefully and in a backward-compatible manner for the end-user.
- Repair issues must be fixable by the user; however, in this case, it currently isn't actionable by most users as most discovery payloads aren't created by users but by the third-party software.
- One of the bigger pieces of software triggering this issue, is Zigbee2MQTT. An adjustment for this missed their release cut, meaning these users get these repairs too (which is a big part of our community).
- The goal of getting MQTT naming up to par with the rest of the Home Assistant integrations remains; This in order to support a better and more standardized naming of entities and devices across Home Assistant (so we can provide better naming depending on the user context in the future).
ℹ️ Marking this PR for the 2023.8.4 patch release that is planned for the 24th of August.
## 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 #
- 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`)
- [ ] 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
2 « J'aime »
Remarque non constructive et inutile (Y’en a des centaines comme ça sur le forum jeedom - ça vire au cauchemar).
Une bonne censure est souvent très utile à la qualité des échanges…
1 « J'aime »