Thanks Ken, I was have a similar issue with a fresh install on a Pi3. Got it fixed it in a similar way. And HA is now running on my Pi 3.
> cd
> rm hass_rpi_installer.sh
> rm -rf fabric-home-assistant
> sudo apt-get install build-essential libssl-dev libffi-dev python-dev
> sudo pip install cryptography
Then re-ran installer, ta-da.
I’m working on AiO v2. Regardless of the new version, I’ll have a look and get the issue sorted. Standby.
I’m okay now after manually installing fabric
I managed to get it installed with this thread thanks guys! However when i try connect to https://piadress:8123 i get connection refused, anyone else run into similar issues? i feel like my home assistant is not even running… does anyone know a command similiar to hass --open-ui but that applies to the AiO script? 
THANK YOU very much, for the last couple of days I was feeling like an idiot. I tried HASSBIAN and then I ran into all the z-wave issues and I was not able to make it work (for z-wave). Then I tried the all in one installer and the I ran into all the issues that you described, but thanks to your post I was able to make it run on my RPI-3 using the latest Raspbian version. What I did it was I installed the cryptography first and then I proceeded with the installation and to make it run I modified the MQTT inside the configuration.yaml.
Now I need to figure it out an easy way to rename all my z-wave devices, I am porting from version 0.28.2 running on a RPI-2 to version 0.34.4 on a RPI-3.
Thanks!
To modify the mqtt component, did you just delete the indentations or did you also change the broker and port? should the broker be your pi IP address?
Yes, I deleted the indentations and the IP address that I used was the address of my RPI. Or if you have any other MQTT broker point it to that one.
Just getting started with Home Assistant.
I’ve tried using the “Pixel” version of the OS with the same problems as mentioned above. Now writing the card with the “Jessie Lite” version and going to give it a shot.
Also, It seems SSH isn’t enabled by default on either the Pixel or Lite version. I always get connection refused.
Yes, thats the new default for SSH in the latest Raspbian release:
2016-11-25:
* SSH disabled by default; can be enabled by creating a file with name “ssh” in boot partition
It is possible to get Home Assistant running on Pixel. I used the info from @ken to get it working so thanks Ken 
I have literally just reinstalled Home Assistant on Pixel due to an issue with HADashboard.
Once the AIO installer has completed you will also need to remove a duplicate mqtt entry in the configuration.yaml and fix the indentation. This comment was posted by another user on the forum in another thread, but I cannot find it now, so thanks who ever you are
mqtt:
broker:
port:
username:
password:
I enabled SSH and WIFI in the GUI right before disabling it
@jbags81 Would it be possible to change the install to match the manual and hasbian image as far as install locations and user?
Man, that get’s my vote for sure. You would think that everything would be in the same location regardless of how you get it running.
I followed Ken’s instructions and came forward in the installation. But Home Assistant not start running. I have change the IP adress in configuration.yaml, reboot the Raspberry Pi still the same problem. I dont find any duplicate for MQTT in the file.
What do I miss?
This is the first time i try Home Assistant. Would appreciate step by step instruction
Have you got any errors in the homeassistant.log file found in the same location as your configuration.yaml?
Hi
I am getting the following errors from my log. Can someone please help?
16-12-15 20:11:08 homeassistant.loader: Unable to find component client_id
16-12-15 20:11:11 homeassistant.loader: Unable to find component password
16-12-15 20:11:11 homeassistant.loader: Unable to find component broker
16-12-15 20:11:11 homeassistant.loader: Unable to find component port
16-12-15 20:11:11 homeassistant.loader: Unable to find component username
Thanks.
Apologies the previous error got resolved as I had changed the broker address. However I get this error now with no luck:
16-12-15 20:23:22 homeassistant.components.mqtt: Unable to connect to the MQTT broker: Not authorised
For the moment just remove the mqtt entry all together, and see if you can have your system up and running. Then check if you have any mqtt broker available to use. Something like this:
mqtt:
broker: 192.168.2.80
port: 1883
client_id: home-assistant-1
username: pi
password: xyzwxx
Remember the indentation is one space underneath the m for the rest of the lines…
mqtt:
broker: 192.168.2.85
port: 1883
client_id: home-assistant-1
username: pi
password: xyzwww
I get this error
16-12-16 08:46:57 homeassistant.util.yaml: mapping values are not allowed here
in “/home/hass/.homeassistant/configuration.yaml”, line 46, column 9
I have changed the IP adress in the configuration.yaml to that the raspberry pi unit have, reboot. But still get the same problem.
Have you fixed the indentation for the mqtt line?
Are you able to post your config.yaml if your not sure?