DAE51D
April 13, 2025, 6:08pm
41
I came here to find, what I presumed to be an “easy solution” only to find out this is not even possible (yet)? Seems very strange. Or at the very least, it should inherit the color already assigned the calendar (such as my Google Calendar). Consider this my upvote too please.
hellodosi
April 25, 2025, 8:08am
42
It is unbelievable that such a function does not yet exist. Every calendar can do this. It must be possible.
Lootre
May 28, 2025, 9:31am
44
Please think about the color blind people ! Being able to change the color of calendars or events is crutial for us.
1 Like
iona
June 5, 2025, 6:09pm
45
Seems like an simple request, hopefully someone picks it up soon!
callit
August 8, 2025, 12:23am
46
It’s close - there’s a PR out there that’s been stalled for a month or two. Looks like the contributor got busy, but it is (theoretically) coming soon
dev ← Misiu:color
opened 06:37AM - 26 May 25 UTC
## Breaking change
## Proposed change
Add a color property to Calendar… Entity.
Architecture discussion got approved: https://github.com/home-assistant/architecture/discussions/883 🎉🎉🎉
## Type of change
- [ ] Dependency upgrade
- [ ] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [x] 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
- This PR fixes or closes issue: fixes #
- This PR is related to issue:
- Link to documentation pull request:
- Link to developer documentation pull request:
- Link to frontend pull request:
I need to know how to change the config flow to display the actual color picker. I saw there is `ColorRGBSelector` (and color_rgb_to_hex), but I'm not sure if this is the right way to do it.
## Checklist
- [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:
- [ ] 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.
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+-status%3Afailure
[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
1 Like