Ok, so different levels of t/shooting then by the looks…
@brazil885 - you need to get a CLI up yes, certainly just for step1 (getting wideq to give you back a token, you need to type some stuff and get back other stuff - the token - to copy/paste into your config.yaml). I have a different setup to you (i dont use hassio) but some googling seems to show you can install some stuff to get access to your CLI. See --> Can't access hassio command line from hass.io installed on Ubuntu
@MrPotshot - no way, im actually a network engineer too! 
first thing that jumps out at me is your directory structure is wrong (if i understand your snip correctly), smartthinq and wideq need to be under custom_components i believe. At least they are for me.
Then after that, and a clean boot, mine just sprung to life - specifically i could see climate.XXXX (XXXX is what you name the device in your LG smartthinq app - for me its ‘air’) so i get the following in developer -> states:
what does your boot up look like? mine looks like this (i schedule a nightly reboot of hass at 1am) - pretty clean in the logs from a smartthinq point of view just one warning (and some other failure at 5am for some other reason - shitty LG API i guess), and then if i look for climate.air in the same log, i get the occasional warning its taking > 10 secs to poll the API (again, same reason!).
Hopefully this gives you enough of a comparison point to crack your problem.
Good luck both!