Noob head question - Error - "Integration not found : introduction"

Oh dear. This isnt going well now after initial joy of setting up my new Pi 3b+ with HASSIO today. Complete noob here working through initial set-up. Was going through the “getting started” section where it instructs how to make a “small change” to the configuration.yaml file (to change name, lat, long, units and time zone). Did that. Saved it. Tried to then update but the system now says the config is not valid. I get the following error:

Configuration invalidCHECK CONFIG
Integration not found: introduction

Cant find anything on Google or in the forum here to explain what might have happened. What is the Introduction integration?!?!

Please assist this complete noob head :disappointed_relieved:

The introduction component has been removed from version 0.92
you need to remove it from your configuration.yaml file

  • Introduction - The introduction integration has been removed. It used to be part of the initially created configuration but no longer served a purpose. (@balloob - #22944) (introduction docs)
1 Like

Well, what an adventure this is going to be. Just as I’ve read, HA not for the faint of heart or prime noob.

So I uninstalled the Configurator add-on and re-installed it (seemed logical thing to try prior to seeing your message - thanks for your kind help - although I have to say, why the heck didnt someone remove the Introduction integration if its not needed anymore? Sigh). After reinstalling, now I find the “Open web UI” option no longer exists, and the Configurator option on the left hand menu of the main page now reports an error “Unable to open ingress connection”. Fun fun fun.

I’m almost ready to go back to Hubitat and throw my shiny new Pi 3B+ in the bin after this evening’s shambles :grimacing::grimacing::grimacing:

0.92 was only released a few hours ago, maybe the documentation still being updated

Yes HA can seem a bit daunting and it is, but stick with it. its a good piece of software

Thanks so much. Yeah, i’m joking about giving up. The fun is in the chase that’s for sure. I will get there. Time to go for dinner now and hope its all fixed automagically for me somehow when I get back. Yeah right! lol

if only just started, and i mean if nothing has really been setup. maybe start again, remembering to not include introduction

And welcome to HA

1 Like

Just remove the line introduction: from your configuration.yaml file.

1 Like

Thanks guys.Unfortunately now the web editor function is missing as above and I think it’s all screwed. Maybe have to rebuild again.

You mean Configurator?

What version of Home Assistant?

EDIT: I just realized you must be on 0.92.0. There us supposed to be an option in the Configurator setup to display in the side menu.
Otherwise there should be an option to open in the Web UI.

The above assumes you are running Hassio.

Yes, latest version 0.92. The option to “Open Web UI” to edit the config file is now missing since I uninstalled the configurator and then reinstalled it. And the Configurator option in the menu on the left now returns an error “Unable to open ingress connection” so it’s really got its knickers in a twist. Not sure what to do now from here.

I avoid the “.0” releases. This time I will either wait for the “.2” patched version, or one week.

How did you install Hassio on your Pi? It may be possible to downgrade to 0.91.4

Smart and wise plan. But having literally only started today I didn’t realise the latest version would be a veritable crock of the proverbial. Interesting first day on (the clearly not very well noob tested) HA :slight_smile:

My personal preference is to put NOOBS Lite on your card (after erasing with SD Formatter), Install Raspbian Lite, & then Hassio. I do not have a lot of faith in the stripped down HassOs. If you need more instruction, I can help. It can be a little tricky.

1 Like

Much appreciated, great community assistance here! It’s late now so giving up for the day. Will get back to it tomorrow and at the weekend probably. Cheers!

1 Like

Rebuilt the Pi (I’d only just started so figured it was quickest route). No error now from the missing Introduction, so I’m assuming they fixed the configuration file. However, in the Configurator Add-On, I’m still missing the “Open Web UI” option. Weird…

“Well, what an adventure this is going to be. Just as I’ve read, HA not for the faint of heart or prime noob.”

Amen to that. I spent half a day yesterday trying to figure out why after weeks of working, suddenly the 8123 port was blocked but (thankfully) the 3218 port was not. Through the latter, I commented out almost everything in my barely-modified previously-functional configuration.yaml and got it up and running again, upgrading to the latest versions.

Now I find this thread, b/c of the same error you are getting. I comment out the “introduction:” from the yaml, and now there is no accessing 8123, and the 3218 port is closed.

I got started on hassio because Smartthings and Vera are painfully inadequate, unreliable, and buggy, and waiting 3-6 months to spend $500 every time I want a professional Control4 or Lutron change was ridiculous. Now with hassio, I’m discovering that I had no idea what buggy was.

Home automation is clearly more hope than results. I’m starting to think that the best anyone with a full-time job can reasonably achieve, is whatever Google Home or Alexa will allow, or to be satisfied with never changing a $10,000-20,000 professional installation.

1 Like

I just installed Node Red in a vain attempt to get back at least some of the flow functionality Stringify provided. It installed fine. Had the same open to open the Web UI. Clicked on it and saw a momentary error come up (502 : bad gateway). now the Open Web UI option has also dissappeared from this add-on. So it seems I have an issue which is preventing these Web UI’s from opening. Strange because the Configurator Web UI was working fine yesterday for me until I uninstalled it and reinstalled it to try to fix the error I was getting due to the Introduction statement in the configuration.yaml file.

Sigh. Complexity upon complexity.

Not sure what to do now because even a rebuld of the Pi hasnt fixed this issue. Now i"m wondering if its a firewall issue, althought why that would have changed from yesterday on my PC I dont know.