I use the StyrBar from IKEA. I can switch the light on and off, dim it and change colors. Is it possible that a default color is always active when switching on?
Many thanks for your help
Hey, Iāve got my E2001 Styrbars working perfectly for a year or so, thank you so much for the blueprints !
I have a question tho, in light color mode, a right push means color temp decreases (towards 2700K), and a left push means color temp increases (towards 6500K). Would it be possible to swap these ? Left for - and Right for + makes way more sense in my brain, and Iāve looked into the blueprints / automations without great success at finding a way to swap/reverse the buttons
Thanks for the blueprints once again !
We need an integration to that basically a blueprint market place loads all blueprints from community forum but has reserved section for error free remarkable blueprints
1 Like
Iām not sure where EPMatt is (OP), I hope he is fine. Since the announcment of being back in 2025, he sort of dropped off again, his last post here was on April 1st 
Well, I wasnāt planning to come back to my fork from his Repo but Iāve had some time on my hands.
Iāve updated my fork, cleaned it up (No Security Vulnerabilities at least according to the github tab on top, which you probably wonāt see anyways 
)
Iāve rolled in and fixed many issues that were reported on EPMatts Repo and folded in some pull requests that EPMatt didnāt get around to, and also added additional devices that donāt exist in his repo.
Iāll try to keep my fork updated as much as possible, but Iām the sole maintainer so Iāll get to things when I get to them 
.
For now, just enjoy.
Ohh, you may ask why in the world Iām doing this. Well I learned so much from EPMattās Repo, and itās a way to give back.
1 Like
I think I fixed this in my fork. See my last recent post.
I did come across that in my research but we need a legit blueprint store thats easily searchable this. So i was developing that until :
The scrapper stopped working.
Im gonna have to see if itās pulling too many request from community site and restructure the backend of the integration to poll data every hour and save it to a SQLite database, Instead of on every load-up/search it scrapes the entire community blueprint forum lol. Also rework the ui to look more like hacs integration.
Honestly the way we share blueprints should change, it sucks so bad i totally overlooked blueprints for months but its definitely a good feature. Im sure theres tons of new people who really need blueprints and dont even know it exist.
I think the most valuable thing for Blueprints would be an automatic version checker so at min, HA can notify a user (and maybe an auto install option) when a newer version is posted.
A unified UI Blueprint āStoreā would be nice for visibility / searchability and to see what BPs may exists that do āthe same thingsā. Create a common header format for the BP code and scrape that; Iād do it in my BPs.
1 Like
Blueprints should be folded into HACSā¦
That started a year or so ago but was axed for reasons that I didnāt understand.
I do believe that interface would be awesome, howeverā¦
To be honest we as a community could change the way we share blueprints using github as a database instead of polling the community website which blocks to many incoming request from the same ip, thatās the issue im running into right now. I have some fix ideas if i continue this method but the best scenario is reach out to HA team and request them to take on this project for us. Its such an underrated under developed part of HA
I was working on this, it would compare your current blueprint yaml to the on on the listed github and alert you if a change is present. But as of now im reworking this integration to an addon for a few reasons. Gonna be seriously delayed i cant release the integration as is, gonna be embarrassing lol.
Dear Awesome HA Blueprints community,
First of all, thank you so much to all of you for the incredible support, energy, and dedication youāve shown over the past months. Your pull requests, issue reports, and maintenance work across forks have kept this project alive and thriving. Itās inspiring for me to see how much this community brings, and how this project is growing. 
@yarafie Iām doing well, though life has once again caught up with me (this time in the form of my Masterās thesis!). That meant I had to step back for a while, but seeing the continued activity and ideas from the community here has given me back motivation.
The concept of a Blueprint Store is great - actually, this has kept coming back to me for a long time: a place where blueprints are easy to find, share, maintain, and update.
We were already slowly moving in that direction. However, I feel it has come the time to fully steer this project from just a collection of blueprints, to the shape of a collaborative Blueprint Community Store.
Design Goals
To move toward that vision, here are the guiding principles I see for the next phase of this project:
Centralized Codebase:
A single, trusted repository is key to ensuring high-quality, reliable, and secure blueprints. Blueprints directly control automations in peopleās homes, so allowing code to spread across random external repositories would introduce unnecessary risks and make quality control nearly impossible.
A centralized approach enables strict version control, consistent formatting, automated testing, and clear contribution workflows, without the overhead of maintaining lists of āapprovedā repos, as HACS does. Itās the most reliable path toward safety, simplicity, and scalability.
Decentralized Ownership
The future of this project cannot depend on a single person, not even me. Each blueprint should have one or more maintainers who can directly update and improve it through a simplified review process. This structure ensures that development and maintenance continue seamlessly, even if Iām unavailable.
The documentation site should reflect this ownership clearly, giving proper credit and visibility to each maintainer. My goal is to enable a self-sustaining ecosystem where contributors have both the responsibility and the freedom to move the project forward without waiting on me as a bottleneck.
Integration-less Setup (if possible):
Maintaining custom integrations takes time and focus away from what really matters - building great blueprints. Iāll be experimenting with ways to simplify setup and to enable automatic updates or update notifications without relying on a custom integration.
Native Versioning & Better Sharing:
Home Assistant currently lacks native versioning for blueprints, and the import process is far from ideal. The current forum link system also limits our ability to update shared blueprints, as the GitHub links shared in the forum are pinned to a specific commit SHA, making delivering updates via forums impossible. We need a smarter, more flexible approach to distributing and versioning them. I have already done some work to enable this in Awesome HA Blueprints, and more updates will follow.
Your feedback and contributions are what make Awesome HA Blueprints what it is today. And what will shape what it becomes next. Even with a packed schedule and limited time available, Iām committing to pushing this project to the next level and experimenting with new ideas to make this vision real.
Letās take the next step together and level up Awesome HA Blueprints! 
Matteo
Founder, Awesome HA Blueprints
3 Likes
Quick update: Iāve just opened a Discord server for the project. Not entirely sure yet how it will evolve, but for now, weāll use it to coordinate efforts on the next phase of Awesome HA Blueprints.
Feel free to hop in and say hI!
@epmatt I read your vision post. It would be great to have everything you are envisioning but Iām not sure it will gain traction since it does not work with the hundreds of existing blueprints posted on github. Most authors will not want to do any real work to update or move code. Many widely used blueprints are published and not maintained - some the authors have not even been on the forums for years.
I recommend first building a āregistryā where authors can do 2 simple, nearly zero effort things, to make it workā¦
- use a common header format in the blueprint
- provide the Github link to your system
ā¦ then your system scrapes the URL provided, grabs version data, blueprint description data, etcā¦ adds it to your registry which is an add-on available in HA to the users.
Once that is working perfectly, then look at expanding the feature set.
1 Like
Welcome back to the Virtual World 
Great to see youāre back! Your original Awesome HA blueprints taught me a lot and I have since made and published one myself for the INNR RC250. Iām surely willing to integrate and maintain that in the future Blueprint , I donāt have the bandwidth to help you set it up ATM, sorry.
I think blueprints are underutilised in HA, and they are a crucial step in making it more user friendly so I fully support this initiative.
1 Like
Right for red should be easy to remember 
Hi,
Iām using the Controller IKEA E2001/E2002 STYRBAR together with Light Hook. It works, but there doesnāt seem to be any way to toggle between white and RGB modes?
Right now it stays in RGB mode, and I can only change colors with the left/right buttons.
Ideally, a double-click on the left or right button could switch between white and RGB modes ā with white mode adjusting brightness/temperature, and RGB mode adjusting colors.
This is a great idea and I really love the vision! I am quite certain you might have stumbled across tihs at some point in time as someone who is invested in Smart Home: Mabye Proxmox VE Helper-Scripts could be an inspiration towards that project.
Take a look at my fork. Done a bit of work on it lately, hopefully towards your vision, mostly under the covers.
To whomever is watching this post especially @epmatt.
Following EPMatts vision, Iāve done some refactoring under the hood.
The notable changes from EPMattās site is, After you are presented with a list of controllers, when you choose one you will be taken to a Device page with General information about the device . At the bottom of the page you will see a table of āLibrariesā If you choose EPMatt Library then you will see the familiar Controller page. All current Controllers will be in the EPMatt Library (The Original Blueprints)
Now to see something different, go to controller IKEA e2001/e2002, this will have an additional Library called yarafie Iāve added a blueprint there, which personally Iāve been using, different than EPMattās version. Also multiple versions through a version selector. I hope you all are catching on the grander implications.
Below is the link to my fork of EPMattās Repo.
Take it for a spin. Kick the tires, look under the hood.
I know there are a few kinks, Iām sure.
This is just the beginning and lays down the foundation. I wonāt tell you what Iām planning next, just wait.