Hi
actually im trying to control WLED effects with an automation. but actually it is not working.
code loocks like this.
action:
- service: light.turn_on
entity_id: light.wled_haus_master
- service: light.turn_on
data:
entity_id: light.wled_haus_segment_3
effect: "Halloween"
brightness: '255'
speed: '255'
intensity: '255'
i get this message in the log
While executing automation automation.halloween_timer_eingangstur_licht_an_wenn_tur_auf_oder_bewegung
21:32:12 – Automatisierung (ERROR)
HALLOWEEN - Timer Eingangstür Licht an wenn Tür auf oder Bewegung: Error executing script. Invalid data for call_service at pos 2: extra keys not allowed @ data['speed']
21:32:12 – Automatisierung (ERROR)
what is wrong??
I think you might need to use the wled.effect service rather than light.turn_on according to the docs:
The light.turn_on service might work with just the brightness but not when you are trying to also set the effect, speed, and intensity which are specific to WLED.
i changed the code to this:
action:
- service: light.turn_on
entity_id: light.wled_haus_master
- service: wled.effect
entity_id: light.wled_haus_segment_3
data:
#entity_id: light.wled_haus_segment_3
effect: "Halloween"
brightness: 255
speed: 255
intensity: 255
but still the same log entry.
I got it to work on my setup by playing around in Developer Tools:
If you look at the docs and parameters listed above then brightness is not supported, this is specified as service data with the light.turn_on service:
This kind of makes sense as brightness is already catered for in light.turn_on service and the new wled_effect service is specifically for the ‘effect’ only.
ok thanks for this.
i hope it will work, we will see:
action:
- service: light.turn_on
entity_id: light.wled_haus_master
- service: light.turn_on
data:
entity_id: light.wled_haus_segment_3
brightness: 255
- service: wled.effect
data:
entity_id: light.wled_haus_segment_3
effect: Halloween
speed: 255
intensity: 255
entity_id: timer.eingang_kurz
An update along the way fixed this for me. I got my wled sunrise alarm working with the info below in my automation action block.
service: wled.effect
data:
speed: 1
effect: sunrise
intensity: 1
target:
entity_id: light.counter
why I cannot find the service wled.effect?
Oggymator
(Oggymator)
August 10, 2023, 8:54pm
9
where can I find the weed.effect service?
@Oggymator
Did you resolve this?
Same here, everything works with the integration but I am missing wled services.
looking for wled.effect and it isn’t listed under services, in fact nothing starting with wled.xxxxxx
edit : OK found this:
home-assistant:dev
← home-assistant:frenck-2021-3105
opened 11:22AM - 29 Nov 21 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.effect` and `wled.preset` services have been removed.
For both services, full replacements are available as normal entities in Home Assistant.
If you are still using these services in your automation or script, please replace them with service calls to their native entities instead.
## 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 removes the last bit of custom services from the WLED integration. All of this has been replaced with entities over the past releases; making these services obsolete.
## 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.
-->
- [x] Dependency upgrade
- [ ] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [ ] 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/20501
## 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] 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
- [x] 🏆 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:
- [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
<!--
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
but still wondering why it doesn’t show up in the HA config UI:
but it does show in dashboards:
K9aK
(K9a K)
December 21, 2024, 12:35pm
12
I’ve got the same problem here. I cant find any “effect” entity. However, all possible and the current effects are listed under the corresponding light entity for the WLED-Device. Dont know how to change the current effect though.
The active effect is listed as an attribute to the segment entity. But there is no control entity for effect.
It can be set either by clicking on the segment control (see my previous post) or via the light.turn_on action parameters.
cooljimy84
(James Crook)
March 27, 2025, 11:23am
14
so i can’t get mine to breathe red, the service call ignores the colour i’ve told it to turn on as (either RGB or colour name) and only applys the effect.
I’m loosing my mind here.
Not enought coffee
danishru
(danishru)
April 4, 2025, 3:21pm
15
Hey!
If you’re struggling to set specific colors along with effects — I totally get the frustration
The default light.turn_on
call in HA doesn’t always apply color + effect reliably, especially with complex WLED setups.
If you want full control over effect ID, colors, brightness, palette , and more — check out my custom integration:
WLED Live View Proxy for Home Assistant
It lets you send raw JSON API commands directly to WLED over WebSocket — like this:
service: wled_liveviewproxy.send_command
data:
targets:
entity_id: light.wled_strip
command: {"seg":[{"id":0,"on":true,"fx":2,"col":["ff0000"],"bri":255}]}
This way you can activate the “Breathe” effect (fx: 2
) with solid red color (ff0000
) — and it won’t be ignored
1 Like
This sounds like it would be perfert. Sometimes it works, most of the time it doesn’t. I’ve even changed automations to turn off the effect before doing things so its always “soils” ready for the next light.
1 Like