I was thinking of using these RGBIC LEDs for a project, but I wanted to know if Home-assistant had a way of properly supporting RGBIC so I could set different parts of it to be different colors.
Here’s the LEDs I was looking at.
Amazon.com: GIDERWEL Smart WiFi DreamColor RGBIC LED Strip Lights16.4ft Kit,Work with Alexa&Google Assistant,APP/Voice/Music Sync Control 150LEDs 5050 Addressable Alexa LED Strips(Not Support 5G WiFi) : Tools & Home Improvement
I think the Flux LED/MagicHome integration will control it, but I don’t know if it can set different segments to different colors.
I’ve already looked into Govee and Kasa, but their APIs don’t even have a way to do it. I’m hoping MagicHome’s API does, but it doesn’t appear to…
Then I saw the LIFX Color Zones Strip and thought that could work since the integration appears to support the zones, but the most recent reviews for it are rather discouraging.
Any suggestions? I don’t want to do any soldering if it can be avoided.
bdraco
(J. Nick Koston)
December 4, 2021, 9:41pm
2
WLED
WLED is going to be your most flexible options as it allows splitting up each segment into a separate light entity
flux_led/MagicHome
There isn’t support for multiple light entities for each segment
Support is expected to land in first release of 2022 via
home-assistant:dev
← bdraco:flux_led_zones
opened 11:38PM - 05 Dec 21 UTC
Requires https://github.com/home-assistant/core/pull/61070
## Proposed chan… ge
<!--
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.
-->
Add zones support to flux_led
The Address v3 (0xA3) models allow setting a color effect per zone. The length of each zone is the number of pixels per segment divided by the number of colors.
| Service data attribute | Description |
| ---------------------- | ----------- |
| `entity_id` | The entity_id of the LED light to set the effect on. |
| `colors` | List of colors for each zone (RGB). (Max 2048 Colors) |
| `speed_pct` | The speed of the effect in % (0-100. Default 50) |
| `effect` | The effect you would like. Valid options are `static`, `running_water`, `strobe`, `jump`, or `breathing`. (Default `static`) |
Example
```
service: flux_led.set_zones
target:
entity_id:
- light.addressable_v3_8e2f7f
- light.addressable_v3_8ebdeb
data:
colors:
- - 255
- 0
- 0
- - 0
- 255
- 0
- - 0
- 0
- 255
- - 255
- 255
- 255
speed_pct: 80
effect: running_water
```
## 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!)
- [x] New feature (which adds functionality to an existing integration)
- [ ] 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: https://github.com/home-assistant/home-assistant.io/pull/20584
## 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.
- [ ] 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]
- [ ] 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:
- [x] 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`.
The integration reached or maintains the following [Integration Quality Scale][quality-scale]:
<!--
The Integration Quality Scale scores an integration on the code quality
and user experience. Each level of the quality scale consists of a list
of requirements. We highly recommend getting your integration scored!
-->
- [ ] No score or internal
- [ ] 🥈 Silver
- [ ] 🥇 Gold
- [ ] 🏆 Platinum
<!--
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
<!--
Thank you for contributing <3
Below, some useful links you could explore:
-->
[dev-checklist]: https://developers.home-assistant.io/docs/en/development_checklist.html
[manifest-docs]: https://developers.home-assistant.io/docs/en/creating_integration_manifest.html
[quality-scale]: https://developers.home-assistant.io/docs/en/next/integration_quality_scale_index.html
[docs-repository]: https://github.com/home-assistant/home-assistant.io
The linked Magic Home controller is the older 0xA1 model but it is well supported in 2021.12 and later
If you go the Magic Home route, the 0xA3 controllers that look like this are probably a better choice as the built-in effects are more interesting.
The newer controllers are
or
DC12V Can use for WS2811, UCS1903, SM16703 LED strip. Connect your phone or tablet to a 2.4G WIFI network. (does not support 5.0G). IP30/IP65 Strip Have Double side Adhesive Tape On The Back. Strip Length: 5m.
LIFX
AFAICT, there isn’t support for multiple light entities for each segment
There is a service to set the color on each of the 8 zones: LIFX - Home Assistant
There are much cheaper options available on the market as well that don’t have the wifi setup issues
1 Like
kicker10BOG
(Jason L Bogle)
December 4, 2021, 11:00pm
3
Thanks for the advice. I’ll look into WLED.
For LIFX, I dug into the code on the github and saw there is a service that lets you set states for each zone. It’s not mentioned on the integration page though.
bdraco
(J. Nick Koston)
December 4, 2021, 11:41pm
4
I just tested with an MagicHome 0xA3 controller and verified it can support multiple zones. There isn’t support for it in Home Assistant though.
The 0xA1 and 0xA2 might support it but its not possible in the app
The message looks like this:
# outer message
# b0b1b2b3000101 07 header with counter (07)
# 0034 - leading bytes
# a00006 - start of message 0xA0 6
# rrggbbrrggbb
# 0001ff00000000ff
# 0002ff00000000ff
# 0003ff00000000ff
# 0004ff00000000ff
# 0005ff00000000ff
# 0006ff00000000ff
# af - end of inner message
#
# 61 - end of outer message
1 Like
kicker10BOG
(Jason L Bogle)
December 4, 2021, 11:46pm
5
Thanks for testing that. I could probably use pyscript to make it work since I know it’s at least possible. A good fallback plan if my poor motor skills fail me in getting the WLED stuff to work. Should be able to get that working though without too much issue.
bdraco
(J. Nick Koston)
December 5, 2021, 11:47pm
6
Zone support for Magic Home 0xA3 should hopefully land in the first release of the new year
home-assistant:dev
← bdraco:flux_led_zones
opened 11:38PM - 05 Dec 21 UTC
Requires https://github.com/home-assistant/core/pull/61070
## Proposed chan… ge
<!--
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.
-->
Add zones support to flux_led
The Address v3 (0xA3) models allow setting a color effect per zone. The length of each zone is the number of pixels per segment divided by the number of colors.
| Service data attribute | Description |
| ---------------------- | ----------- |
| `entity_id` | The entity_id of the LED light to set the effect on. |
| `colors` | List of colors for each zone (RGB). (Max 2048 Colors) |
| `speed_pct` | The speed of the effect in % (0-100. Default 50) |
| `effect` | The effect you would like. Valid options are `static`, `running_water`, `strobe`, `jump`, or `breathing`. (Default `static`) |
Example
```
service: flux_led.set_zones
target:
entity_id:
- light.addressable_v3_8e2f7f
- light.addressable_v3_8ebdeb
data:
colors:
- - 255
- 0
- 0
- - 0
- 255
- 0
- - 0
- 0
- 255
- - 255
- 255
- 255
speed_pct: 80
effect: running_water
```
## 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!)
- [x] New feature (which adds functionality to an existing integration)
- [ ] 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: https://github.com/home-assistant/home-assistant.io/pull/20584
## 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.
- [ ] 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]
- [ ] 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:
- [x] 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`.
The integration reached or maintains the following [Integration Quality Scale][quality-scale]:
<!--
The Integration Quality Scale scores an integration on the code quality
and user experience. Each level of the quality scale consists of a list
of requirements. We highly recommend getting your integration scored!
-->
- [ ] No score or internal
- [ ] 🥈 Silver
- [ ] 🥇 Gold
- [ ] 🏆 Platinum
<!--
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
<!--
Thank you for contributing <3
Below, some useful links you could explore:
-->
[dev-checklist]: https://developers.home-assistant.io/docs/en/development_checklist.html
[manifest-docs]: https://developers.home-assistant.io/docs/en/creating_integration_manifest.html
[quality-scale]: https://developers.home-assistant.io/docs/en/next/integration_quality_scale_index.html
[docs-repository]: https://github.com/home-assistant/home-assistant.io
1 Like