Guys If i see another tutorial that starts with Pi this and pi that im going to cry. I followed all instruction how to install home assistant on windows 10 but can not find a why to find or config the yaml file. WINscp can not log into the 192.168.8.103:8123 default address since its not a remote linux pc its that same machine.
Please point me to the page where setup has to do with windows and windows only. Im trying to setup a mqtt client on the windows server that will communicate with a lora linux based gateway.
Iām constantly reading docs and posts that seem like nonsense because āThings have changedā. Is there a doc that can tell me what docs are still true?
Youāre replying to a 3 year old thread, that was ancient history the last time it was exhumed 9 month ago, in homeassistant terms thatās prehistoric. Follow the official documentation and keep your homeassistant up-to-date, the docs always refer to the latest version.
Iām starting to think 10 minutes is ancient history in HA land. I mean, this āconfiguration.yamlā file in the subject of this thread, a file referred to in a billion spots in that āancientā documentation ā does that file even matter any more? I see it in /config and it doesnāt seem to hold anything of interest. I have a /addons directory thatās empty. My guess is that all the flat YAML configuration was migrated to the database, but thatās just a guess.
Home Assistant is definitely under rapid development and it gets better and better with each release. Yes, sometimes the official docs lag behind a little bit but for the most part they are accurate.
The configuration.yaml file is quite necessary, even if you personally find it uninteresting.
No, I didnāt āpersonallyā find it uninteresting. I found it personally fascinating, but I thought it might be technically uninteresting because it seems to just point to a bunch of empty files. This led me to conclude that the real configuration data (all that stuff I typed into the GUI) was elsewhere (where?) The ādocumentationā doesnāt say. My guess is database. But thatās just a guess.
A lot of the stuff youāre typing into the GUI ends up as JSON files in hidden storage folders.in the config directory. But at the end of the day everything (except lovelace) ends up being put together as one big configuration.yaml file. It is THE system file. Without it HA really has no idea where to find anything.
For simplicities sake, most people split up their configuration.yaml file into lots of other files to keep the system organized. That is what the !include directive is all about. You are including that code in your configuration.yaml file. The bigger and more customized your system gets, the more you will include in that file.
Thank you for confirming that the configuration.yaml is still a āthingā. I can see there must be at least two or three other places that configuration hides ā like where does all that detailed device library data for things like OpenZwave hide, I wonder. Some HA zwave docs suggest itās in the /addons directory, but that directory is empty for me, so it seems to be āancient historyā. But thatās just a guess.
Iāve been watching some YouTube tutorials and several of them start with āA lot has changed. My old tutorial is no longer valid so I decided to make a new tutorialā. Now that Iām getting a sense of the rapid flux of change, Iāll know better how to approach things.
I will say that itās amazing how big and active the HA community is. Iāve been involved in a lot of open source projects and this one has to be one of the most dynamic Iāve seen. Maybe thatās ultimately a good thing? But a core of stability is also a good thing.
The general āthingā of homeassistant hasnāt changed much, but things move around (like the info screen) and a lot of configuration is now done via the ui so the details of it end up in a hidden directory.
But at the end of it itās still a platform for taking a trigger and completing an action.
If youāve watched a video and thought āthat looks easyā, the chances are itās actually even easier now, but the video is pointing you to the wrong place, which makes it confusing (and therefore feels harder).
Try to treat videos as a āgeneral feel for what homeassistant can doā rather than an instruction manual
A big part of the āgeneral feelā for me is knowing where everything generally is. I donāt worry about the details of what exact config data is needed till I know basically where everything goes.
A couple of months ago I decided to swap my SD card because it was coming up on itās second birthday (Yes, Iām still on an RPi with an SD cardā¦ but my āBlueā is supposed to ship in March!) Anyway, I decided to rebuild my system from scratch (except my automations and scripts of course) just to try out the new onboarding process.
I was extremely impressed with how much easier it is now than it was a couple of years ago. Everything went without a hitch. I had my system completely rebuilt in a couple hours including my zwave network with 50ish devices. HA has definitely come a long way. Everyone has done a fantastic job.
Itās still pretty overwhelming for a beginner, I can testify. I wonder what Iāll be saying to people three years from now. I also wonder if HA will still exist. Iām old enough to remember X-10, so I have experience with Smart Home technology that never lives up to its initial promise.
In contrast, I have some always-on linux and BSD systems that ājust workā and havenāt been rebooted in years. So it IS possible to make things that are stable and reliable.
