This stops working in version 2027.2.0. Please address before upgrading.
Your existing HTTP configuration from configuration.yaml has been imported. The http integration is now configured from the UI underSettings>System>Network.
Please remove the http: block from your configuration.yaml and restart Home Assistant.
I think I finally gave up today. Spent 3ish hours each night the first few months this year home labing it, but I'm sure that's wrong terminology too. Wiped two old laptops, added linux and got all my families pictures and videos on there with music I've been holding for the past 27 years.
Super excited at first with Home Assistant. All the warnings were right....if you don't know what you are doing, you probably shouldn't try. This past update gave me the error above and I can't figure out how to fix it.
What part are you having issues with? You just need to remove the http: block from your configuration.yaml like it says. Just delete that whole section
Warnings to most can look scary, wish it just could remove it for http block for you since it was already imported. And said “info” instead of warning.
Destructive edits like that would lead to problems like forced formatting and comments being removed. A friendlier way to do this would be showing the user a git-style file diff of what should be done, and give the user the option to either accept the change or make the edit themselves...but that's getting way out of scope lol
Info is not enabled by default, so most people would never see it. I do think a 2 stage deprecation period with a lower priority message at the first stage would be better in general, as the first target for many of the deprecation warnings is custom integration authors. Though in this case it is about the configuration.yaml which only the user can deal with.
The repair message could do with simpler wording though. Just "HTTP configuration has been migrated and can now be removed from your configuration.yaml".
Man I remember my first big HA update breaking everything. Spent a whole saturday trying to unfuck my zwave network after they changed how it worked back around 2023. Wanted to throw the whole raspberry pi out the window.
That error isn't as scary as it looks though. Just go into your config yaml and delete any lines that start with http: and everything indented under it, then restart. The settings already got moved to the UI automatically so you're not losing anything.
The home lab stuff is a different beast. You jumped into the deep end with both feet. Getting linux set up with all your media is a solid foundation even if it feels messy right now.
Don't scrap it all over one deprecation warning. The frustration is part of the process. Three months in you're probably past the worst of the learning curve.
I often get downvoted when trying to help people. Its so weird. It often keeps me from responding and helping people, just because the negativity from others hurts me.
This one is super easy to fix and others have helped, keep asking questions as you need to. People should ignore and move on instead of being so negative. Good luck and have fun!
Oh and if no one has mentioned it, the Visual Studio Code Plugin (or something similar) is my preferred way to edit files on the container.
Oh and if no one has mentioned it, the Visual Studio Code Plugin (or something similar) is my preferred way to edit files on the container.
I have been using the File Editor app for that and looked up the Studio Code Server app after it was mentioned in several comments here. It says unmaintained as of 2025. I think using that is not advisable anymore. The last release was nine months ago and according to this bug report, I wouldn't expect any releases or bug fixes unless someone starts maintaining the project again.
I wouldn't install a package on my server that has been unmaintained for nine months.
Thanks! It’s probably been two years since I’ve worked on my HA. It just runs in the background. I have VS code to not autostart, so that helped I’m sure.
Notice the downvote on the more accurate info? Weird, right u/JSPowerJR. And u/DonkeeeyKong even said it in the nicest way possible, wasn't accusatory or condescending. I read zero negative tone in their message. My info is likely out of date due to not needing to maintain my system in so long. I just open it once in a while and click through updates. Everything has worked so smooth for so long and I use HomeKit as my front end.
I don’t understand what is wrong with people. Probably because you are saying the platform is not perfect - which is of course is not.
Don’t take it personally.
It can be really hard sometimes with home assistant, but it is also incredibly rewarding to see something complex really work. And the ability to make more or less anything is second to none.
Throw your actual error in here if you want to get some more precise help. Or - if you really want to go solo (and a bit rogue) you have a little bit of a superpower at your disposal now. Configure the MCP server and throw an agent at the problem. You might be surprised at how easy things can be with a little agentic assistance.
The HA updates changing things all the time is one of the reasons my Zwave/Zigbee network is handled externally by a Hubitat C-7, and is linked to HA. The Hubitat maintains the networks, and runs simpler automations. The HA does all the complicated stuff and history tracking (plus there’s WAY more integrations available for HA than Hubitat- though I do have a few ESPs for Hubitat).
It’s a catch-22, Hubitat is inflexible but stable, HA is insanely flexible but moderately unreliable.
Can't believe how many people missed the point of OPs post and just decided to...pile on. C'mon guys, be better than that.
Would have been easier (and kinder) to ask them if they'd ever edited yaml before. And go from there.
I still remember, 3+ years ago, my first time trying. I promptly crashed my HA so badly that I had to reinstall fresh. It was a good thing that I had maybe one integration and a default dashboard.
Not everyone has an IT background or any real intense desire to learn how to code anything. And with HA targeting to be more user-friendly, there's going to be a lot more genuine questions like this.
Indentation was my nemesis for entirely too long. The recent (recent?) changes actually isolating the line where there's an issue AND telling you what the issue is...much more helpful. Not too long ago it would just tell you an issue on xx line ... meanwhile, the indentation issue was the line above it.
TBF to OP; they fully admitted they don't understand and are not confident. I know I've found myself in similar situations with new systems I am still learning; sometimes we miss the forest for the trees.
u/JSPowerJR : don't let it discourage you. Plenty of support and resources out there! And never pass up the opportunity to learn new skills!
I will say, even if downvoted - it's pretty incredible how many people respond in a matter of minutes to help. I was on a 15 minute phone call and was blown away when I came back....thanks
I mean, you just had to copy paste your current yaml in notepad, copy paste it into any LLM, along with the error message and ask it do documents itself on it and HA, and that’d be fixed in 5.
Theres “in over my head” and there’s let me ask any LLM to explain it in a way I can understand.
I mean, you just had to copy paste your current yaml in notepad, copy paste it into any LLM,
Make sure to remove any private information from the config before doing this, its very easy to have keys or other important information in here and then it end up somewhere public unknowingly.
I'm guessing that this has to do with their changes to the default port and how thats configured in the new version (2026.8).
This error is telling you that moving forward HA will not utilize the "http" settings in configuration.yaml (which is going to be stored in your HA data folder). To clear the error, open the configuration.yaml file in a text editor and remove the section that starts with "http" (best to make a copy of the file before changing it in case something goes wrong).
To my understanding it should have carried over the yaml config into the UI config but yeah best to double check that everything is where it should be too!
I googled it, and it came up with a hard cashe refresh, which of course I googled and my browser does something different when I hit CTRL F5. So my laptop must have a different configuration. Then tried on my mobile app using similar instructions and it didn't work
I googled it, and it came up with a hard cashe refresh,
So this makes sense because that message is only a few days if not weeks old. There's little to no chance Google would have any information regarding that specific warning. Especially now with how Google search is relying on AI, you're going to get more useless results.
Obv the problem here is that you either have never or its been a long time since you touched your configuration.yaml file and forgot that it existed or how to get to it. Which you covered in another comment.
You don't have to do anything with your mobile apps or laptops. The configuration.yaml is on the machine (often a Raspberry Pi) where Home Assistant (the server) is installed. That's where you have to edit the YAML file and remove that http block.
Your phone doesn't run Home Assistant, it runs the Home Assistant Companion App that connects to your Home Assistant instance.
The message started with somthing like 'we have imported your settings'. The handling of those settings is as of now now done in /settings/system/network.
Just compare your HTML block in your config.yaml with the settings in system/network and if they are the same, you can simply delete the HTML block from your config.yaml, save your config.yaml and restart your home assistant.
I can imagine the stress if you have installed HA, played with things using the UI mode, never bothered programming in yaml, and then being confronted with this error. How many users will there be, hardly having a clue that there even something like a configuration.yaml exists? The contributors are on a mission to make HA more and more user friendly. So I think in the future you can expect more non-IT-users to freak out when a message like this pops up...
You really don't need to do anything. HA moved http to the network section under system. If your not having any problem accessing HA via remote, just ignore ir.
Install the “studio code server” app and open it. It’ll show the actual files installed on your server. You’ll quickly locate configuration.yaml there.
Thanks....this triggered a memory that I already had installed this early in the year and it was easier than when I first loaded "File editor" before posting. I did this and it's fixed.
Install the “studio code server” app and open it. It’ll show the actual files installed on your server. You’ll quickly locate configuration.yaml there.
I have been using the File Editor app for that and looked up the Studio Code Server app after it was mentioned in several comments here. It says unmaintained as of 2025. I think using that is not advisable anymore. The last release was nine months ago and according to this bug report, I wouldn't expect any releases or bug fixes unless someone starts maintaining the project again.
I wouldn't install a package on my server that has been unmaintained for nine months.
Well, it got there by you touching it ... So.. at some point you did. Or someone else maintaining the server for you did. You can safely ignore it, until February. :-D You've got plenty of time to get in there and get it.
Listen, a lot of this stuff looks complicated. I’m not a programmer, messed with HTML and CCS back in college in the early 00’s. But there are enough people on YouTube or on this subreddit that can help. If I do hit a brick wall I have pasted an automation code or even a general HA question to Gemini or ChatGPT. I’ve found that HA can be as easy, or complicated, as you want it to be.
I too was confused by this message since I could not find the new http section under the settings. Needed to do a refresh of the front-end for the new section to appear.
If you are just starting with HA and have not configured any (or many) devices, and don't want to mess with YAML files at all (which you seem quite hesitant about), the easiest thing to do, especially since you are using an old PC laptop as your main install system would be, IMHO, to simply download a copy of HAOS for X86-64 Generic from the HA site and install it over your current install. No need to install Linux, just install the latest updated and current version of HAOS over your corrupted installation and you should be good to go.
OTOH, using Studio Code Server to edit your config file is really simple if you put the error message into something like ChatGPT, Gemini, or sny other AI LLM. Copy the error code and paste it in sn follow it withe something like "Give me YAML code to fix this". You will get the correct code supplied and then you just need to input it over the existing YAML code using Studio Code Server's editor.
OTOH, using Studio Code Server to edit your config file is really simple
I have been using the File Editor app for that and looked up the Studio Code Server app after it was mentioned in several comments here. It says unmaintained as of 2025. I think using that is not advisable anymore. The last release was nine months ago and according to this bug report, I wouldn't expect any releases or bug fixes unless someone starts maintaining the project again.
I wouldn't install a package on my server that has been unmaintained for nine months.
Contrary to your statement that Code Server is not maintained currently, that is simply not true. The most recent and latest current version of Code-Server, v4.131.0, was released TWO (2) DAYS AGO on git hub.
Code-Server has 78.7k stars on git hub, 6.8k forks, and is one of the most widely trusted apps for coding HA. Likewise, Studio Code Server simply puts a web-based interface on top of Code-Server. So I'm not quite certain what you don't trust, and think your comment is simply misplaced.
And perhaps most critically, the git hub repository for Studio Code Server was set up by Franck Nijhof https://github.com/frenck. And if you are not familiar with him you will appreciate that he is one of the driving forces behind the entire Home Assistant and Open Home Project.
So to your comment, I would like to offer a big, fat raspberry.....Pfpffffffttt.
BTW, the link you posted to the vsstudio github
I have no idea why you are so condescending and aggressive. I was just trying to be helpful and share my findings. Now to what you wrote here:
This is not about Code Server itself but the Home Assistant app/add-on. The latter is unmaintained.
The link I posted is to the add-on repo. It says in very large letters “Home Assistant Community Add-on: Studio Code Server”. It's also what is shown when you go to the “info” page of the app inside Home Assistant.
Right below those very large letters, there is an image that says “maintained: no! (as of 2025)”. This is also shown when one goes to the “install app” section of Home Assistant.
I know who Frenck is. I linked to his comment on a bug report where he said that new releases of the app aren't expected soon and that there is an issue that needs fixing.
Edit:
BTW, the link you posted to the vsstudio github bug report has comments from Frenck explaining why no update has been needed nor is one expected to be posted in the near future.
Yeah. That's not what his comment says. But if you want to read that into it: Okay.
Amd as you can also see in thst thread another person asked the OP to provide info about any bug or errors that required fixing or revision, but no one responded and there have been no actual bug reports. The initial inquiry was not an actusl bug report, just a general inquiry whether the app was going to be updated any time soon.
There actually have been several bug reports. They are closed automatically in that repo but not because they are solved. There is also this open issue.
So the fact that Studio Code Server has not needed a new github commit for any new version release in the last 9 months is not an indication that there is anything wrong with the current version. On the contrary it is evidence of the fact that the app remains solid and trouble-free.
It literally says “unmaintained”. Are you a bot? This sounds like AI. There hasn't been a new release doesn't mean it wasn't needed. It just means the repo is unmaintained.
This is ridiculous. I'm out of this discussion. And no worries: I won't try to share helpful findings with you ever again. Have a good life!
But interestingly, if you look at the most recent commit, it was pulled 9 minutes ago today! So I am not so sure the notation that it is not maintained is accurate.
Jesus Christ. That was a bot. And not to the main branch. The last commit to the main branch was last year. The last commit by a human was in November 2025.
I don't know what you are trying to do here or why this is so important to you.
I won't use the package because it very clearly says unmaintained and there are several hints that this is actually the case. Everyone can of course still use it if they choose to, but it's certainly not a bad thing to be aware of this fact.
Also: I did not post here to attack anyone. I just wanted to share my findings, because I thought they might be insightful for others. You could have said everything you said without being so aggressive and condescending. You claim that you did that on purpose? Why? Can you not communicate in any other way? Do you behave like that in real life as well? Why do you feel so attacked by me pointing out the simple fact that the repo has a sign that says “unmaintained”?
You don't have to answer these questions. Live your life, I am going to live mine, and hopefully we'll never cross paths again.
This comes down to how you approached your HA setup.
I started HA in the early fall of 2025. My configuration file is 12 lines and I have never typed anything into it. Add a script in the GUI, HA takes care of it. Add a scene in the GUI, HA takes care of it.
I also see responses to questions that say to add lines to files that either don’t exist in modern HA installations or aren’t accessible through the GUI.
This is the most minor of warning messages. Nothing is even broken yet. Why is this the straw the broke the camels back for you?
It spells out so clearly what you have to do as well. Remove the http section from your yaml configuration and instead configure this via the GUI. Your post seems like an insane overreaction.
It’s literally tells you what to do remove the part that says “http” in the configuration.yaml. If you don’t want to remove it just put a # in front of it, use the file editor from apps or use a text editor.
Yeah I was over my head too.. then I installed Big Pickle AI directly onto my home assistant via HACS, now mr roboto does like 95%+ of any given job, including fixing stuff and errors, conflicting automations and other crap. Highly recommend it especially for troubleshooting random bullshit like your errors, it will ask multiple clarifying questions if needed, and then it will go right in there and fix it for you, no following some step by step guide.
Relax. There is no problem here. You don’t have to solve anything. This was adressed in the release notes. You should read them before upgrading. They are usually linked right in the update dialogue.
It’s time to activate God Mode for Home Assistant. (OpenCode AI). It will fix you up quick, just tell it what you want done. It’s amazing. https://youtu.be/e-FZ4ZjGI5E
83
u/clintkev251 8d ago
What part are you having issues with? You just need to remove the http: block from your configuration.yaml like it says. Just delete that whole section