OSMC doesn't seem to utilize wifi details from installer

It seems that the SSID & Key entered mid-way through the installer prompts is not being utilized within OSMC.
I’ve rerun the installer several times, being very attentive to spelling and case.

On first boot however, I start through the first-run prompts for language and license agreement, then I’m suddenly redirected to the networking setup dialog with an information bar at the top explaining that OSMC was unable to connect to the network.

I can see my SSID listed, select it, provide my Key and I’m golden.

My question is… why isn’t this getting picked up from the installer? (Linux installer)

I don’t know what the current state of this is, but there were problems with the setting up of wireless networking - this is being sorted out as quickly as possible.
Derek

The settings from the installer will most likely be getting picked up, but it will be failing to connect. A system journal taken immediately after first boot would show what the cause of the problem was (as there is reasonably good logging in the script) but that would require a fresh install for you, so no point if you are set up and working now.

The preseeding script (/usr/bin/preseed) is a bit crude and dates back to a time before the Networking GUI in MyOSMC was written, so for a while it was the only way to configure networking during the development process other than the command line tool connmanctl.

But it is now largely redundant - the only real use it has is if you have no remote control, no CEC remote support on your TV, and no USB keyboard available during first boot, and you need to connect to wifi or configure Static IP settings on Ethernet. Then it is useful to pre-configure the networking settings.

But in every other case it is just as easy to use the My OSMC networking GUI to do the job.

The preseeding script has a couple of known limitations:

  1. Hidden wifi networks are not supported. (They are through the GUI) This may get fixed at some point if time allows.

  2. It only tries once to connect. If for any reason it fails it gives up and doesn’t try again.

So it is quite possible that it sometimes fails to connect, where the GUI would succeed.

I’m not sure whether there are plans to do more work on improving the preseeding system or whether it will actually get ripped out, at the moment it is a vestige of a time before the Networking GUI was written, and is a fairly low priority for us to work on.