Bonjour quelqu’un a t’il déjà essayer se genre de contrôleur led ?
Cloom
Août 9, 2024, 12:14
2
J’ai un Athom:
Mais je sais pas si WS2812B c’est compatible avec WS2812.
C’est top, avec WLED, j’ai celui avec le micro intégré pour avoir les effets avec le son.
Bémol, c’est une image custom de WLED et home assistant a besoin de WLED 0.14.0 désormais:
home-assistant:dev
← home-assistant:frenck-2024-0452
opened 07:46PM - 17 Jul 24 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO N… OT 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.
-->
The WLED integration now requires a WLED device running at least [WLED 0.14.0](https://github.com/Aircoookie/WLED/releases/tag/v0.14.0)
## 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.
-->
Updates `wled` to 0.19.1
Release notes:
- https://github.com/frenck/python-wled/releases/tag/v0.19.0
- https://github.com/frenck/python-wled/releases/tag/v0.19.1
- https://github.com/frenck/python-wled/releases/tag/v0.19.2
Diff: https://github.com/frenck/python-wled/compare/v0.18.0...v0.19.2
This change is rather large, as the upstream library:
- Has now been put on top of Mashumaro
- Now requires WLED 0.14.0 or newer
- Now relies on the light capabilities provided by WLED (which are translated to our color modes in this PR)
- Separates WLED releases/version check handling from the device logic
These upstream changes have been implemented as minimally as possible in this PR.
Some things could be replaced/made prettier now, but opted to do that later.
In a similar fashion, the upstream library can now make its models more strict (eventually resulting in less `if None` logic on our end).
## 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)
- [x] 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:
- closes #101029
- fixes #110478
- 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 Ruff (`ruff format 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:
- [x] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [x] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [x] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
<!--
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
L’autre bémol que je peux émettre c’est que c’est l’antenne wifi sur le PCB de l’ESP. Pas un problème mais si tu veux des effets synchronisés et qu’il y a beaucoup d’info qui passe, ça peut planter. Le wifi avec les ESP ça peut perturber le SoC. C’est un problème que j’ai également avec mes dev board ESP, j’ai mis une antenne externe sur un mais je n’ai pas encore testé.
Mon but c’est de faire une discothèque chez moi alors que je danse pas et ne fais pas de fête
1 « J'aime »
J’utilise des esp8266 avec wled mais je cherche s’il n’existe pas d’alternative en zigbee
1 « J'aime »