home-assistant / hassbian-scripts

Scripts used in the Hassbian image.

Hassbian-scripts

The documentation for the content in this repository can be found here:

https://home-assistant.github.io/hassbian-scripts/

hassbian-scripts's Issues

Installer Fails, Please run first boot installer on TMUX

This will allow the end user to hop on SSH and open the TMUX window. Even better, have it setup as a pi login script to open the tmux window if this is the first boot.

DuckDNS cert renew problem

I am running hassbian V 0.9.1 and the dehydrated certificate renew stoped to work.
Getting this error:
pi@hassbian:~ $ sudo su -s /bin/bash homeassistant
homeassistant@hassbian:/home/pi $ source /srv/homeassistant/bin/activate
(homeassistant) homeassistant@hassbian:/home/pi $ /home/homeassistant/dehydrated/dehydrated -c

INFO: Using main config file /home/homeassistant/dehydrated/config

/home/homeassistant/dehydrated/dehydrated: line 91: ./hook.sh: No such file or directory

Had to update manualy:
sudo su -s /bin/bash homeassistant
source /srv/homeassistant/bin/activate
cd /home/homeassistant/dehydrated
./dehydrated -c
exit

sudo hassbian-config install webterminal

This command returns:
"suite webterminal doesn't exist."

How to remove home assistant platform from homebridge

Hassbian-config version (hassbian-config -V):
0.9.1
Script/Suite:
homebridge
Description of problem:
How to uninstall?

Additional info:
I'd like to know how I can completely remove the home assistant platform from homebridge. It does not appear in my config but when I run it, it still loads it. I've deleted the homebridge user as well as it's home directory.

My config.json :
{ "bridge": { "name": "Homebridge", "username": "XX:XX:XX:XX:XX:XX", "port": 11111, "pin": "XXX-XX-XXX" }, "description": "This is an example configuration file to help you get set up with homebridge-rcswitch-gpiomem.", "accessories": [ { "accessory": "RCSwitch", "name": "Switch number one", "onCode": 1234567, "offCode": 2345678, "pin": 17, "protocol": 1, "pulseLength": 190, "bitLength": 24, "repeats": 10 } ] }

homebridge output :
`[2018-8-17 16:47:40] Loaded config.json with 1 accessories and 0 platforms.
[2018-8-17 16:47:40] ---
[2018-8-17 16:47:41] Loaded plugin: homebridge-homeassistant
[2018-8-17 16:47:42] Registering platform 'homebridge-homeassistant.HomeAssistant'
[2018-8-17 16:47:42] ---
[2018-8-17 16:47:42] Loading 1 accessories...
/usr/local/lib/node_modules/homebridge/lib/api.js:64
throw new Error("The requested accessory '" + name + "' was not registered by any plugin.");
^

Error: The requested accessory 'RCSwitch' was not registered by any plugin.
at API.accessory (/usr/local/lib/node_modules/homebridge/lib/api.js:64:13)
at Server._loadAccessories (/usr/local/lib/node_modules/homebridge/lib/server.js:285:42)
at Server.run (/usr/local/lib/node_modules/homebridge/lib/server.js:86:38)
at module.exports (/usr/local/lib/node_modules/homebridge/lib/cli.js:43:10)
at Object. (/usr/local/lib/node_modules/homebridge/bin/homebridge:17:22)
at Module._compile (module.js:569:30)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:503:32)
at tryModuleLoad (module.js:466:12)
at Function.Module._load (module.js:458:3)`

Add hassbian-config status

For integration into the frontend, we need a hassbian-config status command. The command will return (preferably in JSON) for each script the name, description and status (not_installed, installing, installed, est install time?).

Requires #11 to be merged

Use case:
So I am planning on adding a hassbian panel to the Home Assistant UI to trigger these scripts. I am thinking about the following implementation:

• whitelist the homeassistant user sudo rights to call hassbian-config
• hassbian component will call hassbian-config status and expose it as an API
• hassbian panel in UI will show status of the different scripts
• Future: see wifi settings etc etc

Migrated issues from pi-gen repo.

• Add Samba sharing the config folder
• [x Replace with pip support.] Pre-installed cython or open-zwave. Build script available but not pre-installed. Awaiting inclusion in base Os. Limited support is available today but problems with building OZWCP.
• Emulated hue

Permission needs to be set in the image for emulated_hue to function with Google Home and similar.
@bruhautomation contributed the following in home-assistant/core#4737 that can give the user a push in the right direction that want to implement it themselves or for someone willing to experiment with it and submit a pull request .
For people who are following this thread, after a little research the setcap command does work for the AiO method.
The magic sauce for people running HA in a venv via the AiO script is
sudo setcap 'cap_net_bind_service=+ep' /srv/hass/hass_venv/bin/python3
After running that, I was able to spin up the component no problem which both Google Home and the >Amazon Echo can see. Sick!

• Automate build of images.
• Identify the distribution correctly to the updater component

Our Analytics system (provided by the updater component) sends the OS name and version as part of the update check. Currently, it reports as either "Debian 8" or "Raspbian 8". It would be great to change it to say "Hassbian X.Y.Z" replacing X.Y.Z with whatever the version of Hassbian it is. I guess that also means we should start really start using semantic versioning for this...

The check for the OS name is done here and is powered by the platform.system() call. I'm hoping you can just change /etc/lsb_release but this will need a bit of testing.

• BLE beacon for HA. Fairly simple but disables any other use of the bluetooth chip.
  Wont be implemented as is today.

sudo hcitool -i hci0 cmd 0x08 0x0008 1f 02 01 06 03 03 aa fe 17 16 aa fe 10 00 03 68 6f 6d 65 2d 61 73 73 69 73 74 61 6e 74 2e 69 6f

Appdaemon is broken

Hassbian-config version (hassbian-config -V): 0.8.0
Script/Suite: AppDaemon

Description of problem:
AppDaemon does not start after installation.

Traceback/log (if applicable):

pi@hassbian:~ $ sudo service appdaemon@homeassistant status
● [email protected] - AppDaemon
   Loaded: loaded (/etc/systemd/system/[email protected]; enabled; vendor preset: enabled)
   Active: inactive (dead) since Fri 2018-03-23 09:11:01 UTC; 17s ago
  Process: 24493 ExecStart=/srv/appdaemon/bin/appdaemon -c /home/homeassistant/appdaemon/ (code=exited, status=0/SUCCESS)
 Main PID: 24493 (code=exited, status=0/SUCCESS)

Mar 23 09:10:56 hassbian systemd[1]: Started AppDaemon.
Mar 23 09:11:00 hassbian appdaemon[24493]: ERROR no 'appdaemon' section in /home/homeassistant/appdaemon/appdaemon.yaml

install ha failed

Make sure your running an up to date version of Hassbian before reporting a problem. If not make sure to specify what version and why so we can recreate the issue in question.

You should only file an issue if you found a bug. Feature and enhancement requests should go in #33 that's dedicated for this usage.

Hassbian-config version (hassbian-config -V):

Script/Suite:

Description of problem:
when i use sudo hassbian-config upgrade homeassistant=0.65.6 i got a suite homeassistant=0.65.6 doesn't exist. error
Expected:

Traceback/log (if applicable):

suite homeassistant=0.65.6 doesn't exist.

Additional info:

`hassbian-config state` is not working

On this PRi I have installed tradfri and Hue, both are showing as "Uninstalled"

Output:

pi@hassbian:~ $ sudo hassbian-config state
{ "suites": { "appdaemon": { "state": "Uninstalled", "description": "AppDaemon install script for Hassbian" } , "duckdns": { "state": "Uninstalled", "description": "Setup for Duck DNS auto renewal." } , "hue": { "state": "Uninstalled", "description": "Echo/Home/Mycroft Emulated Hue install script for Hassbian." } , "libcec": { "state": "Uninstalled", "description": "libcec install script for Hassbian" } , "mariadb": { "state": "Uninstalled", "description": "MariaDB install script for Hassbian" } , "mosquitto": { "state": "Uninstalled", "description": "Mosquitto Installer for Hassbian" } , "mssql": { "state": "Uninstalled", "description": "MS SQL install script for Hassbian" } , "mysql": { "state": "Uninstalled", "description": "MySQL install script for Hassbian" } , "postgresql": { "state": "Uninstalled", "description": "PostgreSQL install script for Hassbian" } , "razberry": { "state": "Uninstalled", "description": "Disables Bluetooth for the use of a RaZberry with Hassbian." } , "samba": { "state": "Uninstalled", "description": "Samba install script for Hassbian" } , "tradfri": { "state": "Uninstalled", "description": "Tradfri install script for Hassbian" } , "webterminal": { "state": "Uninstalled", "description": "Installs an websevice terminal." } } }

Hassbian Stretch

All issues are experienced on the 1.3 WIP.

Known problems

• sudo hassbian-config install mosquitto failed: Missing dependicies (libssl & libwebsockets)
  Workaround in place in the newest package of hassbian-config
• sudo hassbian-config install hue failed: Worng python version, should be 3.5 not 3.4
• sudo hassbian-config install libcec failed: Problems with python 3.5 & 3.6. Script should function when fixed in project.
• sudo hassbian-config install tellstick failed: libconfuse0 (>= 2.5) but it is not installable
• Unable to install package pyatv==0.3.4

Working/Tested

• Tradfri
• Samba
• Home-assistant

To be removed

• OpenZwave-pip. Baked in into Home Assistant.
• Tellstick. Packages has not been updated since 2014 and are missing dependencies in Debian Stretch.

To be added

• Upgrades to hassbian-config by @ludeeus in #42
• Added scripts to upgrade HA by @ludeeus in #42
• Added scripts to upgrade base OS by @ludeeus in #42
• Added scripts to upgrade hassbian-config by @ludeeus in #42
• Permissions for audio recommended by @ammaddon reference material here.

Homebridge script doesn't work for Pi Zero W

Hassbian-config version (hassbian-config -V): Latest v0.8

Script/Suite: homebridge

Description of problem:
Homebridge script doesn't work for Pi zero w with Armv6 since node 8+ could not be installed with default bash code: curl -sL https://deb.nodesource.com/setup_8.x | sudo -E bash -.

The script would give fake successful feedback after you fully run through whole scripts. If then you type node -v, system would fail you with v4.8.2. The log in the middle would show the warning: ## You appear to be running on ARMv6 hardware. Unfortunately this is not currently supported by the NodeSource Linux distributions. Please use the 'linux-armv6l' binary tarballs available directly from nodejs.org for Node.js v4 and later.

Expected:
Since Home Assistant support almost every version of Pi, then maybe we should adjust this script to fit it.

1. Add Pi model check at the first stage. (Like uname -a)
2. Add Pi Zero specific homebridge install script:

wget -O - https://raw.githubusercontent.com/sdesalas/node-pi-zero/master/install-node-v9.0.0.sh | bash
sudo apt-get install -y npm

3. Further adjustment since homebridge directory should differ from Pi with Armv7l

Some thoughts for the future.

First of all I would like to state that this is not an issue but my personal opinions and ideas.

Naming

I strongly belive that the package created with this repo should be called hassbian-config this is the name most users will think the name is, since all commands are hassbian-confing *some_comand*
For new install this should not be an issue, but for existing it will require manually removing the old package.

Versioning

Based on inspiration from https://semver.org/
I think that 'hassbian-scripts' should follow an MAJOR.MINOR.PATCH versioning scheme.

MAJOR version when you make incompatible API changes.
MINOR version when you add functionality in a backwards-compatible manner.
PATCH version when you make backwards-compatible bug fixes.

Examples:

1.x.x - MAJOR

Will include changes to core functionality, renaming (for instance to hassbian-config'), and other changes that will result in users having to take extra steps to custom scripts for hassbian-scripts or extra steps to update.

x.1.x - MINOR

Will include new functionality that wont break workflows, new scripts, or removal of scripts no longer applicable.

x.x.1 - PATCH

Will include stuff like minor corrections/additions to existing packages (scripts), typos and hotfixes.

Distribution

Lately I have been toying around with an distribution channel for hassbian-scripts that would streamline the install/update process.
The package itself is hosted on github, and installation/upgrade through apt install/upgrade.
I have an working demo/sample for this hosted here.
Updates to that repo is generated using this script.
That script also generate an changelog based on milestones used in home-assistant/hassbian-scripts.

Changelog*

For the changelog part of that workflow should work, there has to be an milestone matching that release, and PR's included (that should show up in an changelog) in that release needs to be tagged with matching milestone.
The change log, will include PR# (w/hyperlink), title of the PR, and the contributor(w/hyperlink)

Hassbian not working out of the box

Hi there. Just tried a clean install of HASSBIAN 1.1 (2017-02-03 build).

• Following given instructions, setup script goes somehow bad: no interface is reachable after 30+ mins of waiting.
  Other users with similar issues are suggesting a potential fix
  https://community.home-assistant.io/t/hassbian-not-working-out-of-the-box/11479/3

• Another problem is that with every sudo commands, I (we) get a
  sudo: unable to resolve host hassbian
  which happens when hostname is not in /etc/hosts (and it's not).

Would be nice if this can get fixed, as hassbian is - in my opinion - the more convenient way to start out with home assistant.

Thanks

Add script "update.sh" or "update-hassbian-scripts.sh"

Add a script to update to the last version of hassbian-scripts.
Running the commands ( from Home Assistant IO docs ) :

$ cd /home/pi/hassbian-scripts
$ git pull

Or some other appropriate combination of commands.
For a Home Assistent user like me. It is allways a pain to find all the right commands from the wiki.

Automatic shell linter for PR

https://stickler-ci.com/docs#bash
Can be activated on this repo to automatically check for common mistakes in shell scripts.
Before activating all existing scripts must be validated.

Scripts TODO

• libcec
• Samba, share config
• BLE eddystone beacon

hassbian-config is removed by `apt autoremove`

hassbian-config gets removed when running apt autoremove

Cloud9 Issue

Make sure your running an up to date version of Hassbian before reporting a problem. If not make sure to specify what version and why so we can recreate the issue in question.

You should only file an issue if you found a bug. Feature and enhancement requests should go in #33 that's dedicated for this usage.

Hassbian-config version (hassbian-config -V):
0.11.1
Script/Suite:
sudo hassbian-config install cloud9
Description of problem:
Service will not start after installing.
Expected:

Traceback/log (if applicable):

pi@hassbian:~ $ sudo systemctl status [email protected]
● [email protected] - Cloud9
Loaded: loaded (/etc/systemd/system/[email protected]; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2018-12-05 07:46:02 EST; 1min 7s ago
Process: 6032 ExecStart=/opt/c9sdk/server.js -l 0.0.0.0 -a : -w /home/homeassistant/c9workspace (code=exited, status=1/FAILURE)
Main PID: 6032 (code=exited, status=1/FAILURE)

Dec 05 07:46:02 hassbian server.js[6032]: at Module.require (internal/modules/cjs/loader.js:636:17)
Dec 05 07:46:02 hassbian server.js[6032]: at require (internal/modules/cjs/helpers.js:20:18)
Dec 05 07:46:02 hassbian server.js[6032]: at main (/opt/c9sdk/server.js:74:20)
Dec 05 07:46:02 hassbian server.js[6032]: at Object. (/opt/c9sdk/server.js:55:5)
Dec 05 07:46:02 hassbian server.js[6032]: at Module._compile (internal/modules/cjs/loader.js:688:30)
Dec 05 07:46:02 hassbian server.js[6032]: at Object.Module._extensions..js (internal/modules/cjs/loader.js:699:10)
Dec 05 07:46:02 hassbian server.js[6032]: at Module.load (internal/modules/cjs/loader.js:598:32)
Dec 05 07:46:02 hassbian systemd[1]: [email protected]: Main process exited, code=exited, status=1/FAILURE
Dec 05 07:46:02 hassbian systemd[1]: [email protected]: Unit entered failed state.
Dec 05 07:46:02 hassbian systemd[1]: [email protected]: Failed with result 'exit-code'.

Unable to get Beta version

When running hassbian-script 0.9.0 the script is unable to get the beta version of home assistant, it seems to be an issue with getting the current beta version from the json file

Errors updating hassbian-scripts from 0.9.1 to 0.11.0

Make sure your running an up to date version of Hassbian before reporting a problem. If not make sure to specify what version and why so we can recreate the issue in question.

You should only file an issue if you found a bug. Feature and enhancement requests should go in #33 that's dedicated for this usage.

Hassbian-config version (hassbian-config -V):

pi@hassbian:~ $ sudo hassbian-config -V
0.9.1

Script/Suite:

hassbian-script

Description of problem:

Attempting to upgrade hassbian-scripts package from 0.9.1 to 0.11.0 and receive an error.

Expected:

Expect to be able to run sudo hassbian-config upgrade hassbian-script and have it download and install the newest general release of the hassbian-script package. According to the releases page this should be 0.11.0.

Traceback/log (if applicable):

pi@hassbian:~ $ sudo hassbian-config upgrade hassbian-script
Hassbian-script upgrade script for Hassbian
Original concept by Ludeeus <https://github.com/ludeeus>

Changing to a temporary folder
Downloading latest release
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  2480  100  2480    0     0   9119      0 --:--:-- --:--:-- --:--:--  9151
Installing latest release

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Reading package lists...
E: Unsupported file /tmp/hassbian*.deb given on commandline
Cleanup
rm: cannot remove 'hassbian*.deb': No such file or directory

Upgrade is now done.

Additional info:

• RaspberryPi 3 Model B
• Home Assistant version 0.82.0
• My Home Assistant Configuration Files

Installation script not working.

Installing script not work with new Hassbian installation.

pi@hassbian:~ $ sudo hassbian-config install mosquitto Mosquitto Installer for Hassbian Copyright(c) 2016 Dale Higgs <https://github.com/dale3h> Modified by Landrash for use with Hassbian. Adding mosquitto user The system user mosquitto' already exists. Exiting.
Creating pid file
Creating data directory
Installing repository key
--2017-12-17 15:50:25-- http://repo.mosquitto.org/debian/mosquitto-repo.gpg.key
Resolving repo.mosquitto.org (repo.mosquitto.org)... 85.119.83.194, 2001:ba8:1f1:f271::2
Connecting to repo.mosquitto.org (repo.mosquitto.org)|85.119.83.194|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 3137 (3.1K) [application/octet-stream]
Saving to: ‘STDOUT’

•                                  100%[===========================================================================>]   3.06K  --.-KB/s    in 0s
  

2017-12-17 15:50:30 (76.8 MB/s) - written to stdout [3137/3137]

OK
Adding repository
--2017-12-17 15:50:30-- http://repo.mosquitto.org/debian/mosquitto-stretch.list
Resolving repo.mosquitto.org (repo.mosquitto.org)... 85.119.83.194, 2001:ba8:1f1:f271::2
Connecting to repo.mosquitto.org (repo.mosquitto.org)|85.119.83.194|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 50 [application/octet-stream]
Saving to: ‘mosquitto-stretch.list.3’

mosquitto-stretch.list.3 100%[===========================================================================>] 50 --.-KB/s in 0s

2017-12-17 15:50:35 (1.59 MB/s) - ‘mosquitto-stretch.list.3’ saved [50/50]

Installing mosquitto
Hit:1 http://repo.mosquitto.org/debian stretch InRelease
Hit:2 http://mirrordirector.raspbian.org/raspbian stretch InRelease
Hit:3 http://archive.raspberrypi.org/debian stretch InRelease
Reading package lists... Done
N: Ignoring file 'mosquitto-stretch.list.1' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension
N: Ignoring file 'mosquitto-stretch.list.3' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension
N: Ignoring file 'mosquitto-stretch.list.2' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
mosquitto : Depends: libssl1.0.0 (>= 1.0.1) but it is not installable
Depends: libwebsockets3 (>= 1.2) but it is not installable
mosquitto-clients : Depends: libmosquitto1 (= 1.4.12-0mosquitto1) but it is not going to be installed
N: Ignoring file 'mosquitto-stretch.list.1' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension
N: Ignoring file 'mosquitto-stretch.list.3' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension
N: Ignoring file 'mosquitto-stretch.list.2' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension
E: Unable to correct problems, you have held broken packages.
First try failed, adding dependencies and trying again.
This is an workaround and will be omited once it's fixed upstream.
Downloading dependencies
--2017-12-17 15:50:59-- http://ftp.se.debian.org/debian/pool/main/o/openssl/libssl1.0.0_1.0.1t-1+deb8u6_armhf.deb
Resolving ftp.se.debian.org (ftp.se.debian.org)... 194.71.11.173, 194.71.11.165, 2001:6b0:19::173, ...
Connecting to ftp.se.debian.org (ftp.se.debian.org)|194.71.11.173|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2017-12-17 15:51:04 ERROR 404: Not Found.

--2017-12-17 15:51:04-- http://ftp.se.debian.org/debian/pool/main/libw/libwebsockets/libwebsockets3_1.2.2-1_armhf.deb
Resolving ftp.se.debian.org (ftp.se.debian.org)... 194.71.11.173, 194.71.11.165, 2001:6b0:19::173, ...
Connecting to ftp.se.debian.org (ftp.se.debian.org)|194.71.11.173|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 38396 (37K) [application/x-debian-package]
Saving to: ‘libwebsockets3_1.2.2-1_armhf.deb’

libwebsockets3_1.2.2-1_armhf.deb 100%[===========================================================================>] 37.50K --.-KB/s in 0.02s

2017-12-17 15:51:09 (1.78 MB/s) - ‘libwebsockets3_1.2.2-1_armhf.deb’ saved [38396/38396]

Installing dependencies
dpkg: error: cannot access archive 'libssl1.0.0_1.0.1t-1+deb8u6_armhf.deb': No such file or directory
Selecting previously unselected package libwebsockets3:armhf.
(Reading database ... 41062 files and directories currently installed.)
Preparing to unpack libwebsockets3_1.2.2-1_armhf.deb ...
Unpacking libwebsockets3:armhf (1.2.2-1) ...
dpkg: dependency problems prevent configuration of libwebsockets3:armhf:
libwebsockets3:armhf depends on libssl1.0.0 (>= 1.0.0); however:
Package libssl1.0.0 is not installed.

dpkg: error processing package libwebsockets3:armhf (--install):
dependency problems - leaving unconfigured
Errors were encountered while processing:
libwebsockets3:armhf
Cleanup dependencies
rm: cannot remove 'libssl1.0.0_1.0.1t-1+deb8u6_armhf.deb': No such file or directory
Retrying installation of mosquitto
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
libwebsockets3 : Depends: libssl1.0.0 (>= 1.0.0) but it is not installable
mosquitto : Depends: libssl1.0.0 (>= 1.0.1) but it is not installable
mosquitto-clients : Depends: libmosquitto1 (= 1.4.12-0mosquitto1) but it is not going to be installed
N: Ignoring file 'mosquitto-stretch.list.1' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension
N: Ignoring file 'mosquitto-stretch.list.3' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension
N: Ignoring file 'mosquitto-stretch.list.2' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).
Writing default configuration
/opt/hassbian/suites/install_mosquitto.sh: line 72: cd: /etc/mosquitto: No such file or directory
mv: cannot stat 'mosquitto.conf': No such file or directory
cp: cannot create regular file '/etc/mosquitto/mosquitto.conf': No such file or directory
chown: cannot access 'mosquitto.conf': No such file or directory
Initializing password file

Please take a moment to setup your first MQTT user
If no choice is made a default account will be created`

Move user input to the top of every script.

Every user input should be at the start of scripts.

Upgrade Home Assistant - wrong

Hassbian-config version (hassbian-config -V):
0.11.1
Script/Suite:

Description of problem:
From update 0.86.3 when i use script to update HomeAssistant show me after uninstall old version that config is wrong and ask me revert ot no... I always use no and upgrade is ok and i have new version. But show error when use this script.

Expected:

Traceback/log (if applicable):

Additional info:

Razberry not turning off bluetooth correctly

Hassbian-config version (hassbian-config -V):
0.8.1
Script/Suite:
Razberry
Description of problem:
Does not seem to turn off bluetooth on raspberry pi 3

it should add "dtoverlay=pi3-miniuart-bt" to bottom of /boot/config.txt file (according to https://www.home-assistant.io/hassio/zwave/)
when i instead added it manually my razberry card started working

Expected:
properly add "dtoverlay=pi3-miniuart-bt" to bottom of /boot/config.txt file

Traceback/log (if applicable):

Additional info:

Install Failed On Raspberry Pi Zero w

Make sure your running an up to date version of Hassbian before reporting a problem. If not make sure to specify what version and why so we can recreate the issue in question.

You should only file an issue if you found a bug. Feature and enhancement requests should go in #33 that's dedicated for this usage.

**Hassbian-config version (hassbian-config -V):1.21

Script/Suite:

**Description of problem:/srv/homeassistant/bin/hass: No such file or directory

Expected:

Traceback/log (if applicable):

**Additional info:1) Flashed the hassbian 1.21
2) Ran sudo hassbian-config install homeassistant --force
3) Not working

Logs: sudo journalctl -f -u [email protected]
-- Logs begin at Sat 2017-04-29 17:59:46 SAST. --
Oct 13 15:06:48 hassbian systemd[1]: Starting Home Assistant for homeassistant...
Oct 13 15:06:48 hassbian systemd[1]: Started Home Assistant for homeassistant.
Oct 13 15:06:48 hassbian systemd[1403]: Failed at step EXEC spawning /srv/homeassistant/bin/hass: No such file or directory
Oct 13 15:06:48 hassbian systemd[1]: [email protected]: main process exited, code=exited, status=203/EXEC
Oct 13 15:06:48 hassbian systemd[1]: Unit [email protected] entered failed state.
Oct 13 15:18:56 hassbian systemd[1]: Starting Home Assistant for homeassistant...
Oct 13 15:18:56 hassbian systemd[1]: Started Home Assistant for homeassistant.
Oct 13 15:18:56 hassbian systemd[1474]: Failed at step EXEC spawning /srv/homeassistant/bin/hass: No such file or directory
Oct 13 15:18:56 hassbian systemd[1]: [email protected]: main process exited, code=exited, status=203/EXEC
Oct 13 15:18:56 hassbian systemd[1]: Unit [email protected] entered failed state.

sudo systemctl status [email protected]
● [email protected] - Home Assistant for homeassistant
Loaded: loaded (/etc/systemd/system/[email protected]; enabled)
Active: failed (Result: exit-code) since Sat 2018-10-13 15:18:56 SAST; 10min ago
Process: 1474 ExecStart=/srv/homeassistant/bin/hass (code=exited, status=203/EXEC)
Main PID: 1474 (code=exited, status=203/EXEC)

Oct 13 15:18:56 hassbian systemd[1]: Started Home Assistant for homeassistant.
Oct 13 15:18:56 hassbian systemd[1474]: Failed at step EXEC spawning /srv/ho...y
Oct 13 15:18:56 hassbian systemd[1]: [email protected]: ...EC
Oct 13 15:18:56 hassbian systemd[1]: Unit [email protected]...e.
Hint: Some lines were ellipsized, use -l to show in full.

Turn into hotspot when not connected to internet

It would be cool if we could have the Raspberry Pi turn itself into a hotspot when it is not connected to wifi and allow the user to configure it.

There is a tool available called resin-wifi-connect that does this. The people from Radiodan have been able to get it working on a Debian Jessie image and have detailed instructions on how to get it running: http://andrewnicolaou.co.uk/posts/2015/resin-wifi-connect-without-docker

It would be awesome if we could get this working too.

Upgrade script gives wrong discord channel?

As reported in Discord by eFlame, the upgrade script tells people:

If you have issues with this script, please say something in the #Hassbian channel on Discord

Except, there is no such channel, and the closest is the channel for Hassbian development, leading to general support questions being asked in the dev channel...

Add script "update-home-assistant.sh"

Add a script to update to the last version of Home Assistant.
Running the commands (from Home Assistant IO docs ) :

$ sudo systemctl stop [email protected]
$ sudo su -s /bin/bash homeassistant
$ source /srv/homeassistant/bin/activate
$ pip3 install --upgrade homeassistant
$ exit
$ sudo systemctl start [email protected]

Or some other appropriate combination of commands.
For a Home Assistent user like me. It is allways a pain to find which update procedure to use from the wiki.

New HASSBIAN install, hassbian-config install openzwave

Hello,

Just started a new installation with HASSBIAN 1.23. Ran into an issue that I wanted to make you aware of. Below are the steps I took during the install and the error from my hass.log.

1. Finish HASSBIAN installation
2. Set raspi-config options
3. Rebooted
4. Updated (update/upgrade)
5. Rebooted
6. Sudo hassbain-config install samba
7. Rebooted
8. Sudo hassbian-config install openzwave
9. Rebooted
10. Tried to access HA from browser, no luck, ran hass from putty, stalled trying to install OZWCP, rebooted
11. HASS launched after reboot with zwave config error
12. Error log is as follows.

2017-06-15 01:29:55 ERROR (MainThread) [homeassistant.setup] Error during setup of component zwave
Traceback (most recent call last):
File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/setup.py", line 190, in _async_setup_component
component.setup, hass, processed_config)
File "/usr/lib/python3.4/asyncio/futures.py", line 388, in iter
yield self # This tells Task to wait for completion.
File "/usr/lib/python3.4/asyncio/tasks.py", line 286, in _wakeup
value = future.result()
File "/usr/lib/python3.4/asyncio/futures.py", line 277, in result
raise self._exception
File "/usr/lib/python3.4/concurrent/futures/thread.py", line 54, in run
result = self.fn(*self.args, **self.kwargs)
File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/components/zwave/init.py", line 258, in setup
config_path=config[DOMAIN].get(CONF_CONFIG_PATH))
File "/srv/homeassistant/lib/python3.4/site-packages/pyozwweb-0.4.0.35-py3.4.egg/openzwave/option.py", line 82, in init
libopenzwave.PyOptions.init(self, config_path=config_path, user_path=user_path, cmd_line=cmd_line)
File "src-lib/libopenzwave/libopenzwave.pyx", line 669, in libopenzwave.PyOptions.init (openzwave-embed/open-zwave-master/python-openzwave/src-lib/libopenzwave/libopenzwave.cpp:10816)
libopenzwave.LibZWaveException: "LibOpenZwave Generic Exception : Can't autoconfigure path to config"

Frederick, normally I would contact you directly but seeing as how you are active with both HASSBIAN and these config files, I wanted to let you know asap. There are no other changes I made to the Pi or Hassbian install so there shouldn't have been any steps I missed.

jkvalence

sudo hassbian-config install cloud9 fails (compile error)

Hassbian-config version (hassbian-config -V):
0.11.1
Script/Suite:
sudo hassbian-config install cloud9

Description of problem:
Trying to install cloud9
Expected:
cloud9 installed

Traceback/log (if applicable):

:Compiling Libevent
test -d include/event2 || /bin/mkdir -p include/event2
/bin/sed -f ./make-event-config.sed < config.h > include/event2/event-config.hT
mv -f include/event2/event-config.hT include/event2/event-config.h
make  all-recursive
make[1]: Entering directory '/home/homeassistant/.c9/libevent-2.0.22-stable'
Making all in .
make[2]: Entering directory '/home/homeassistant/.c9/libevent-2.0.22-stable'
/bin/bash ./libtool --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I.  -I./compat -I./include -I./include    -g -O2 -Wall -fno-strict-aliasing -pthread -MT event.lo -MD -MP -MF .deps/event.Tpo -c -o event.lo event.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I./compat -I./include -I./include -g -O2 -Wall -fno-strict-aliasing -pthread -MT event.lo -MD -MP -MF .deps/event.Tpo -c event.c -o event.o
...
/bin/bash ./libtool --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I.  -I./compat -I./include -I./include    -g -O2 -Wall -fno-strict-aliasing -pthread -MT bufferevent_openssl.lo -MD -MP -MF .deps/bufferevent_openssl.Tpo -c -o bufferevent_openssl.lo bufferevent_openssl.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I./compat -I./include -I./include -g -O2 -Wall -fno-strict-aliasing -pthread -MT bufferevent_openssl.lo -MD -MP -MF .deps/bufferevent_openssl.Tpo -c bufferevent_openssl.c -o bufferevent_openssl.o
bufferevent_openssl.c: In function 'bio_bufferevent_new':
bufferevent_openssl.c:106:3: error: dereferencing pointer to incomplete type 'BIO {aka struct bio_st}'
  b->init = 0;
   ^~
bufferevent_openssl.c: At top level:
bufferevent_openssl.c:228:1: error: variable 'methods_bufferevent' has initializer but incomplete type
 static BIO_METHOD methods_bufferevent = {
 ^~~~~~
bufferevent_openssl.c:79:27: warning: excess elements in struct initializer
 #define BIO_TYPE_LIBEVENT 57
                           ^
bufferevent_openssl.c:229:2: note: in expansion of macro 'BIO_TYPE_LIBEVENT'
  BIO_TYPE_LIBEVENT, "bufferevent",
  ^~~~~~~~~~~~~~~~~
bufferevent_openssl.c:79:27: note: (near initialization for 'methods_bufferevent')
 #define BIO_TYPE_LIBEVENT 57
                           ^
bufferevent_openssl.c:229:2: note: in expansion of macro 'BIO_TYPE_LIBEVENT'
  BIO_TYPE_LIBEVENT, "bufferevent",
  ^~~~~~~~~~~~~~~~~
bufferevent_openssl.c:229:21: warning: excess elements in struct initializer
  BIO_TYPE_LIBEVENT, "bufferevent",
                     ^~~~~~~~~~~~~
bufferevent_openssl.c:229:21: note: (near initialization for 'methods_bufferevent')
bufferevent_openssl.c:230:2: warning: excess elements in struct initializer
  bio_bufferevent_write,
  ^~~~~~~~~~~~~~~~~~~~~
bufferevent_openssl.c:230:2: note: (near initialization for 'methods_bufferevent')
bufferevent_openssl.c:231:2: warning: excess elements in struct initializer
  bio_bufferevent_read,
  ^~~~~~~~~~~~~~~~~~~~
bufferevent_openssl.c:231:2: note: (near initialization for 'methods_bufferevent')
bufferevent_openssl.c:232:2: warning: excess elements in struct initializer
  bio_bufferevent_puts,
  ^~~~~~~~~~~~~~~~~~~~
bufferevent_openssl.c:232:2: note: (near initialization for 'methods_bufferevent')
bufferevent_openssl.c:233:2: warning: excess elements in struct initializer
  NULL /* bio_bufferevent_gets */,
  ^~~~
bufferevent_openssl.c:233:2: note: (near initialization for 'methods_bufferevent')
bufferevent_openssl.c:234:2: warning: excess elements in struct initializer
  bio_bufferevent_ctrl,
  ^~~~~~~~~~~~~~~~~~~~
bufferevent_openssl.c:234:2: note: (near initialization for 'methods_bufferevent')
bufferevent_openssl.c:235:2: warning: excess elements in struct initializer
  bio_bufferevent_new,
  ^~~~~~~~~~~~~~~~~~~
bufferevent_openssl.c:235:2: note: (near initialization for 'methods_bufferevent')
bufferevent_openssl.c:236:2: warning: excess elements in struct initializer
  bio_bufferevent_free,
  ^~~~~~~~~~~~~~~~~~~~
bufferevent_openssl.c:236:2: note: (near initialization for 'methods_bufferevent')
bufferevent_openssl.c:237:2: warning: excess elements in struct initializer
  NULL /* callback_ctrl */,
  ^~~~
bufferevent_openssl.c:237:2: note: (near initialization for 'methods_bufferevent')
bufferevent_openssl.c:228:19: error: storage size of 'methods_bufferevent' isn't known
 static BIO_METHOD methods_bufferevent = {
                   ^~~~~~~~~~~~~~~~~~~
Makefile:800: recipe for target 'bufferevent_openssl.lo' failed
make[2]: *** [bufferevent_openssl.lo] Error 1
make[2]: Leaving directory '/home/homeassistant/.c9/libevent-2.0.22-stable'
Makefile:864: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/homeassistant/.c9/libevent-2.0.22-stable'
Makefile:595: recipe for target 'all' failed
make: *** [all] Error 2

real	1m41.146s
user	1m18.442s
sys	0m13.193s
Creating workspace for Cloud9.
Create default config.
{"projecttree": {"@showhidden": false,"@hiddenFilePattern": ".*,.n*,*c9*,.b*,.p*,.w*,*.db"}}
Symlinking /home/homeassistant/.homeassistant to the workspace.
Copying Cloud9 service file...
cp: cannot stat '/opt/hassbian/suites/files/cloud9.service': No such file or directory
Enabling Cloud9 service...
Failed to enable unit: File [email protected]: No such file or directory
Starting Cloud9 service...
Failed to start [email protected]: Unit [email protected] not found.
Checking the installation...

Additional info:
Any ideas whats wrong?

Incorrect upgrade instructions for 0.7.0 - Need to specify 'hassbian-script-dev'

The upgrade instructions are incorrect for upgrading to hassbian-script version 0.7.0. The instructions seen here indicate to run the following command:

sudo hassbian-config upgrade hassbian-script

However, since this release is tagged as pre-release you'd need to execute

sudo hassbian-config upgrade hassbian-script-dev

Thanks!

Install Python package hassbian

To detect that we're running hassbian, please install hassbian into the image: pip3 install hassbian==0.1

Make sure you pin the version so that we know which version shipped with which Hassbian image and we can notify the user as such if they need to upgrade.

Is it possible to have a hassbian appdaemon script for python 3.5 or 3.6?

Make sure your running an up to date version of Hassbian before reporting a problem. If not make sure to specify what version and why so we can recreate the issue in question.

You should only file an issue if you found a bug. Feature and enhancement requests should go in #33 that's dedicated for this usage.

Hassbian-config version (hassbian-config -V):
0.81
Script/Suite:
appdaemon
Description of problem:
Installs appdaemon using python 3.4
Expected:
python 3.5 or later (as per Home assistant current version 0.66.1)

Traceback/log (if applicable):

Additional info:

Mosquitto - Illegal instruction

Hi,

I wanted to know if you got the same behavior on your installation of mosquitto. I got definitely an issue with this...

pi@hassbian:~ $ mosquitto
Illegal instruction
pi@hassbian:~ $ sudo mosquitto
Illegal instruction
pi@hassbian:~ $ sudo -i
root@hassbian:~# mosquitto
Illegal instruction

root@hassbian:~# uname -a
Linux hassbian 4.9.41+ #1023 Tue Aug 8 15:47:12 BST 2017 armv6l GNU/Linux

Sorry if you have already covered it... 

Webterminal Hassbian Script Over HTTPS

Webterminal Script for Hassbian is great but it does not work over HTTPS
The script uses shellinabox and that has support for ssl ... anyone ??

AppDaemon install error

Hassbian-config version (hassbian-config -V):
0.9.1

Script/Suite:
AppDaemon

Description of problem:
Error on install AppDaemon suite.

Traceback/log (if applicable):

AppDaemon install script for Hassbian.
Copyright(c) 2017 Fredrik Lindqvist <https://github.com/Landrash>.

Stopping AppDaemon service...
Failed to stop [email protected]: Unit [email protected] not loaded.
Changing to the homeassistant user...
Changing to AppDaemon venv...
/bin/bash: line 3: /srv/appdaemon/bin/activate: No such file or directory
Installing latest version of AppDaemon...
Collecting wheel
  Using cached https://files.pythonhosted.org/packages/81/30/e935244ca6165187ae8be876b6316ae201b71485538ffac1d718843025a9/wheel-0.31.1-py2.py3-none-any.whl
Installing collected packages: wheel
Successfully installed wheel-0.31.1
Collecting appdaemon
  Downloading https://files.pythonhosted.org/packages/ec/3c/fb5c9dd92f12d1ff82322de4f9eeab99a32d3ecb6d94e9ccb7823025708d/appdaemon-3.0.1-py3-none-any.whl (5.9MB)
Collecting aiohttp==2.3.10 (from appdaemon)
  Downloading https://www.piwheels.org/simple/aiohttp/aiohttp-2.3.10-cp35-cp35m-linux_armv7l.whl (622kB)
Collecting voluptuous (from appdaemon)
  Using cached https://files.pythonhosted.org/packages/f5/09/a0e20a0bd743131e237128bad3a4f83b283f70c032b7e7c0f06baf7f6862/voluptuous-0.11.1-py2.py3-none-any.whl
Collecting feedparser (from appdaemon)
  Downloading https://www.piwheels.org/simple/feedparser/feedparser-5.2.1-py3-none-any.whl (44kB)
Collecting websocket-client (from appdaemon)
  Downloading https://files.pythonhosted.org/packages/8a/a1/72ef9aa26cfe1a75cee09fc1957e4723add9de098c15719416a1ee89386b/websocket_client-0.48.0-py2.py3-none-any.whl (198kB)
Collecting requests>=2.6.0 (from appdaemon)
  Using cached https://files.pythonhosted.org/packages/65/47/7e02164a2a3db50ed6d8a6ab1d6d60b69c4c3fdf57a284257925dfc12bda/requests-2.19.1-py2.py3-none-any.whl
Collecting iso8601 (from appdaemon)
  Downloading https://files.pythonhosted.org/packages/ef/57/7162609dab394d38bbc7077b7ba0a6f10fb09d8b7701ea56fa1edc0c4345/iso8601-0.1.12-py2.py3-none-any.whl
Collecting pyyaml (from appdaemon)
  HTTP error 404 while getting https://www.piwheels.org/simple/pyyaml/PyYAML-4.1-cp35-cp35m-linux_armv7l.whl#sha256=a5b125a24244830d574ccfd8fab861198d2ffe491b73179ffd75abf78caee6ff (from https://www.piwheels.org/simple/pyyaml/)
  Could not install requirement pyyaml from https://www.piwheels.org/simple/pyyaml/PyYAML-4.1-cp35-cp35m-linux_armv7l.whl#sha256=a5b125a24244830d574ccfd8fab861198d2ffe491b73179ffd75abf78caee6ff (from appdaemon) because of error 404 Client Error: Not Found for url: https://www.piwheels.org/simple/pyyaml/PyYAML-4.1-cp35-cp35m-linux_armv7l.whl
Could not install requirement pyyaml from https://www.piwheels.org/simple/pyyaml/PyYAML-4.1-cp35-cp35m-linux_armv7l.whl#sha256=a5b125a24244830d574ccfd8fab861198d2ffe491b73179ffd75abf78caee6ff (from appdaemon) because of HTTP error 404 Client Error: Not Found for url: https://www.piwheels.org/simple/pyyaml/PyYAML-4.1-cp35-cp35m-linux_armv7l.whl for URL https://www.piwheels.org/simple/pyyaml/PyYAML-4.1-cp35-cp35m-linux_armv7l.whl#sha256=a5b125a24244830d574ccfd8fab861198d2ffe491b73179ffd75abf78caee6ff (from https://www.piwheels.org/simple/pyyaml/)
Deactivating virtualenv...
/bin/bash: line 11: deactivate: command not found
Starting AppDaemon service...
Failed to start [email protected]: Unit [email protected] not found.
Checking the installation...

Upgrade done..

To continue have a look at http://appdaemon.readthedocs.io/en/latest/

Additional info:
First problem i see is that script can't set venv

Changing to AppDaemon venv...
/bin/bash: line 3: /srv/appdaemon/bin/activate: No such file or directory

Second problem is, that script can't install pyyaml:

Collecting pyyaml (from appdaemon)
  HTTP error 404 while getting https://www.piwheels.org/simple/pyyaml/PyYAML-4.1-cp35-cp35m-linux_armv7l.whl#sha256=a5b125a24244830d574ccfd8fab861198d2ffe491b73179ffd75abf78caee6ff (from https://www.piwheels.org/simple/pyyaml/)
  Could not install requirement pyyaml from https://www.piwheels.org/simple/pyyaml/PyYAML-4.1-cp35-cp35m-linux_armv7l.whl#sha256=a5b125a24244830d574ccfd8fab861198d2ffe491b73179ffd75abf78caee6ff (from appdaemon) because of error 404 Client Error: Not Found for url: https://www.piwheels.org/simple/pyyaml/PyYAML-4.1-cp35-cp35m-linux_armv7l.whl
Could not install requirement pyyaml from https://www.piwheels.org/simple/pyyaml/PyYAML-4.1-cp35-cp35m-linux_armv7l.whl#sha256=a5b125a24244830d574ccfd8fab861198d2ffe491b73179ffd75abf78caee6ff (from appdaemon) because of HTTP error 404 Client Error: Not Found for url: https://www.piwheels.org/simple/pyyaml/PyYAML-4.1-cp35-cp35m-linux_armv7l.whl for URL https://www.piwheels.org/simple/pyyaml/PyYAML-4.1-cp35-cp35m-linux_armv7l.whl#sha256=a5b125a24244830d574ccfd8fab861198d2ffe491b73179ffd75abf78caee6ff (from https://www.piwheels.org/simple/pyyaml/)

Symlinks openzwave not working

The symlinks are only for ozw_config, but ozwcp and homeassistant still uses folder config. I executed the below statements and it worked for me. I also had to execute the chown with a sudo, cause I got an exit denied.

echo "Linking ozwcp config directory"
cd /srv/homeassistant/src/open-zwave-control-panel
ln -sd /srv/homeassistant/lib/python3./site-packages/python_openzwave/ozw_config
ln -sd /srv/homeassistant/lib/python3./site-packages/python_openzwave/ozw_config config
sudo chown -R homeassistant:homeassistant /srv/homeassistant/src

echo "Linking Home Assistant OpenZWave config directory"
cd /home/homeassistant/.homeassistant
sudo -u homeassistant ln -sd /srv/homeassistant/lib/python3./site-packages/python_openzwave/ozw_config
sudo chown -R homeassistant:homeassistant /home/homeassistant/.homeassistant
sudo ln -sd /srv/homeassistant/lib/python3./site-packages/python_openzwave/ozw_config config
sudo chown -R homeassistant:homeassistant /srv/homeassistant/src

Installation fails without sources repo enabled

Installation on Hassbian install of ~6 months old.

/etc/apt/sources.list did not have the sources bit uncommented.

deb http://mirrordirector.raspbian.org/raspbian/ jessie main contrib non-free rpi
# Uncomment line below then 'apt-get update' to enable 'apt-get source'
#deb-src http://archive.raspbian.org/raspbian/ jessie main contrib non-free rpi

Had to uncomment it to allow installation.

deb http://mirrordirector.raspbian.org/raspbian/ jessie main contrib non-free rpi
# Uncomment line below then 'apt-get update' to enable 'apt-get source'
deb-src http://archive.raspbian.org/raspbian/ jessie main contrib non-free rpi

Maybe should add to install guide?

sudo: unable to resolve host hassbian

I got the error "sudo: unable to resolve host hassbian" every time I issued a sudo command after installation. I believe this was because the install failed to update /etc/hosts with the hostname it assigned

Script of OpenZwave reinstalls again !!

Hi

Downloaded the latest Hassbian image on HA website, burn on sd card then installed on my PI, then installed Mosquitto server and then Zwave-pip. Once done, I add in my configuration.yaml declaration of ZWave with just the USB port it's plugged in !
I then restart HA and it triggers again the installation of ZWave-pip and then HA complains Zwave is not working and need to be fixed !
Did the whole process two times and still the same :(

Vincèn

hassbian-script 0.10.0 now with double entries

I updated to 0.10 And now have i have double entries.

Getting the RC version?

Make sure your running an up to date version of Hassbian before reporting a problem. If not make sure to specify what version and why so we can recreate the issue in question.

You should only file an issue if you found a bug. Feature and enhancement requests should go in #33 that's dedicated for this usage.

Hassbian-config version (hassbian-config -V):

Script/Suite:

Description of problem:

Expected:

Traceback/log (if applicable):

Additional info:
Is there any way to include the rc branch?

Cloud9 - workspace directory is (possibly) incorrect

When installing Cloud9 using the scripts the default workspace directory is /home/homeassistant
Since ./.homeassistant directory is hidden (starts with a period) it doesn't show in searches made with Ctrl+E in C9

Install script for Hombridge

Hi,

It would be very nice if Hassbian could be preconfigured with Hombridge suport!

//Tim

can't find install tellstick command

Hi,

Reading this guidehttps://home-assistant.io/docs/installation/hassbian/customization/

Tells me that there should be a command like "hassbian-config install tellstick", is it in development/removed?

Thanks in advance!

error installing libcec using hassbian-config

Starting with 2017-05-09-Hassbian.img on a Raspberry Pi 3, I logged in, did the following:

sudo apt-get update 
sudo apt-get upgrade 
reboot

Logged back in and proceeded to try and install libcec using hassbian-config. Errors ensued.

Any suggestions to resolve this problem?

pi@hassbian:/home/homeassistant/.homeassistant $ hassbian-config install libcec
/usr/local/bin/hassbian-config: line 47: /srv/homeassistant/hassbian/suite-states.lock: Permission denied
flock: 300: Bad file descriptor
pi@hassbian:/home/homeassistant/.homeassistant $ sudo !!
sudo hassbian-config install libcec
libcec install script for Hassbian
Copyright(c) 2017 Fredrik Lindqvist <https://github.im/Landrash>
Running apt-get preparation
Hit http://archive.raspberrypi.org jessie InRelease
Hit http://mirrordirector.raspbian.org jessie InRelease
Hit http://mirrordirector.raspbian.org jessie/main armhf Packages
Hit http://archive.raspberrypi.org jessie/main armhf Packages
Hit http://mirrordirector.raspbian.org jessie/contrib armhf Packages                            
Hit http://mirrordirector.raspbian.org jessie/non-free armhf Packages                           
Hit http://archive.raspberrypi.org jessie/ui armhf Packages               
Hit http://mirrordirector.raspbian.org jessie/rpi armhf Packages
Ign http://archive.raspberrypi.org jessie/main Translation-en_GB                                 
Ign http://archive.raspberrypi.org jessie/main Translation-en                                       
Ign http://mirrordirector.raspbian.org jessie/contrib Translation-en_GB           
Ign http://mirrordirector.raspbian.org jessie/contrib Translation-en              
Ign http://archive.raspberrypi.org jessie/ui Translation-en_GB                    
Ign http://mirrordirector.raspbian.org jessie/main Translation-en_GB
Ign http://mirrordirector.raspbian.org jessie/main Translation-en                 
Ign http://archive.raspberrypi.org jessie/ui Translation-en                       
Ign http://mirrordirector.raspbian.org jessie/non-free Translation-en_GB
Ign http://mirrordirector.raspbian.org jessie/non-free Translation-en
Ign http://mirrordirector.raspbian.org jessie/rpi Translation-en_GB
Ign http://mirrordirector.raspbian.org jessie/rpi Translation-en
Reading package lists... Done
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following extra packages will be installed:
  cmake-data libarchive13 libjsoncpp0 liblzo2-2 libpthread-stubs0-dev libpython-dev libpython2.7-dev libx11-dev libx11-doc libxau-dev libxcb1-dev libxdmcp-dev
  libxext-dev libxrandr2 libxrender-dev libxrender1 python2.7-dev swig2.0 x11proto-core-dev x11proto-input-dev x11proto-kb-dev x11proto-randr-dev
  x11proto-render-dev x11proto-xext-dev xorg-sgml-doctools xtrans-dev
Suggested packages:
  codeblocks eclipse ninja-build lrzip libxcb-doc libxext-doc swig-doc swig-examples swig2.0-examples swig2.0-doc
The following NEW packages will be installed:
  cmake cmake-data libarchive13 libjsoncpp0 liblzo2-2 libpthread-stubs0-dev libpython-dev libpython2.7-dev libudev-dev libx11-dev libx11-doc libxau-dev
  libxcb1-dev libxdmcp-dev libxext-dev libxrandr-dev libxrandr2 libxrender-dev libxrender1 python-dev python2.7-dev swig swig2.0 x11proto-core-dev
  x11proto-input-dev x11proto-kb-dev x11proto-randr-dev x11proto-render-dev x11proto-xext-dev xorg-sgml-doctools xtrans-dev
0 upgraded, 31 newly installed, 0 to remove and 0 not upgraded.
Need to get 28.2 MB of archives.
After this operation, 67.9 MB of additional disk space will be used.
Get:1 http://archive.raspberrypi.org/debian/ jessie/main cmake-data all 3.6.2-2~bpo8+1 [1,168 kB]
Get:2 http://mirrordirector.raspbian.org/raspbian/ jessie/main liblzo2-2 armhf 2.08-1.2 [47.6 kB]
Get:3 http://mirrordirector.raspbian.org/raspbian/ jessie/main libarchive13 armhf 3.1.2-11+deb8u3 [231 kB]
Get:4 http://mirrordirector.raspbian.org/raspbian/ jessie/main libjsoncpp0 armhf 0.6.0~rc2-3.1 [61.1 kB]
Get:5 http://mirrordirector.raspbian.org/raspbian/ jessie/main libpython2.7-dev armhf 2.7.9-2+deb8u1 [17.9 MB]
Get:6 http://archive.raspberrypi.org/debian/ jessie/main cmake armhf 3.6.2-2~bpo8+1 [2,379 kB]     
Get:7 http://mirrordirector.raspbian.org/raspbian/ jessie/main python-dev armhf 2.7.9-1 [1,188 B]
Get:8 http://archive.raspberrypi.org/debian/ jessie/main x11proto-core-dev all 7.0.31-1 [728 kB]                                                                
Get:9 http://archive.raspberrypi.org/debian/ jessie/main xtrans-dev all 1.3.5-1 [100 kB]                                                                        
Get:10 http://archive.raspberrypi.org/debian/ jessie/main x11proto-randr-dev all 1.5.0-1 [49.7 kB]                                                              
Get:11 http://mirrordirector.raspbian.org/raspbian/ jessie/main libxrender1 armhf 1:0.9.8-1 [30.4 kB]                                                           
Get:12 http://mirrordirector.raspbian.org/raspbian/ jessie/main libxrandr2 armhf 2:1.4.2-1 [31.7 kB]                                                            
Get:13 http://mirrordirector.raspbian.org/raspbian/ jessie/main libpthread-stubs0-dev armhf 0.3-4 [4,042 B]                                                     
Get:14 http://mirrordirector.raspbian.org/raspbian/ jessie/main libpython-dev armhf 2.7.9-1 [19.6 kB]                                                           
Get:15 http://mirrordirector.raspbian.org/raspbian/ jessie/main libudev-dev armhf 215-17+deb8u7 [23.2 kB]                                                       
Get:16 http://mirrordirector.raspbian.org/raspbian/ jessie/main xorg-sgml-doctools all 1:1.11-1 [21.9 kB]                                                       
Get:17 http://mirrordirector.raspbian.org/raspbian/ jessie/main libxau-dev armhf 1:1.0.8-1 [23.0 kB]                                                            
Get:18 http://mirrordirector.raspbian.org/raspbian/ jessie/main libxdmcp-dev armhf 1:1.1.1-1 [40.8 kB]                                                          
Get:19 http://mirrordirector.raspbian.org/raspbian/ jessie/main x11proto-input-dev all 2.3.1-1 [157 kB]                                                         
Get:20 http://mirrordirector.raspbian.org/raspbian/ jessie/main x11proto-kb-dev all 1.0.6-2 [269 kB]                                                            
Get:21 http://mirrordirector.raspbian.org/raspbian/ jessie/main libxcb1-dev armhf 1.10-3 [78.1 kB]                                                              
Get:22 http://mirrordirector.raspbian.org/raspbian/ jessie/main libx11-dev armhf 2:1.6.2-3 [726 kB]                                                             
Get:23 http://mirrordirector.raspbian.org/raspbian/ jessie/main libx11-doc all 2:1.6.2-3 [2,026 kB]                                                             
Get:24 http://mirrordirector.raspbian.org/raspbian/ jessie/main x11proto-xext-dev all 7.3.0-1 [212 kB]                                                          
Get:25 http://mirrordirector.raspbian.org/raspbian/ jessie/main libxext-dev armhf 2:1.3.3-1 [102 kB]                                                            
Get:26 http://mirrordirector.raspbian.org/raspbian/ jessie/main x11proto-render-dev all 2:0.11.1-2 [20.8 kB]                                                    
Get:27 http://mirrordirector.raspbian.org/raspbian/ jessie/main libxrender-dev armhf 1:0.9.8-1 [38.8 kB]                                                        
Get:28 http://mirrordirector.raspbian.org/raspbian/ jessie/main libxrandr-dev armhf 2:1.4.2-1 [39.3 kB]                                                         
Get:29 http://mirrordirector.raspbian.org/raspbian/ jessie/main python2.7-dev armhf 2.7.9-2+deb8u1 [287 kB]                                                     
Get:30 http://mirrordirector.raspbian.org/raspbian/ jessie/main swig2.0 armhf 2.0.12-1 [1,071 kB]                                                               
Get:31 http://mirrordirector.raspbian.org/raspbian/ jessie/main swig armhf 2.0.12-1 [285 kB]                                                                    
Fetched 28.2 MB in 1min 3s (441 kB/s)                                                                                                                           
Extracting templates from packages: 100%
Selecting previously unselected package cmake-data.
(Reading database ... 34439 files and directories currently installed.)
Preparing to unpack .../cmake-data_3.6.2-2~bpo8+1_all.deb ...
Unpacking cmake-data (3.6.2-2~bpo8+1) ...
Selecting previously unselected package liblzo2-2:armhf.
Preparing to unpack .../liblzo2-2_2.08-1.2_armhf.deb ...
Unpacking liblzo2-2:armhf (2.08-1.2) ...
Selecting previously unselected package libarchive13:armhf.
Preparing to unpack .../libarchive13_3.1.2-11+deb8u3_armhf.deb ...
Unpacking libarchive13:armhf (3.1.2-11+deb8u3) ...
Selecting previously unselected package libjsoncpp0.
Preparing to unpack .../libjsoncpp0_0.6.0~rc2-3.1_armhf.deb ...
Unpacking libjsoncpp0 (0.6.0~rc2-3.1) ...
Selecting previously unselected package cmake.
Preparing to unpack .../cmake_3.6.2-2~bpo8+1_armhf.deb ...
Unpacking cmake (3.6.2-2~bpo8+1) ...
Selecting previously unselected package libpython2.7-dev:armhf.
Preparing to unpack .../libpython2.7-dev_2.7.9-2+deb8u1_armhf.deb ...
Unpacking libpython2.7-dev:armhf (2.7.9-2+deb8u1) ...
Selecting previously unselected package libxrender1:armhf.
Preparing to unpack .../libxrender1_1%3a0.9.8-1_armhf.deb ...
Unpacking libxrender1:armhf (1:0.9.8-1) ...
Selecting previously unselected package libxrandr2:armhf.
Preparing to unpack .../libxrandr2_2%3a1.4.2-1_armhf.deb ...
Unpacking libxrandr2:armhf (2:1.4.2-1) ...
Selecting previously unselected package libpthread-stubs0-dev:armhf.
Preparing to unpack .../libpthread-stubs0-dev_0.3-4_armhf.deb ...
Unpacking libpthread-stubs0-dev:armhf (0.3-4) ...
Selecting previously unselected package libpython-dev:armhf.
Preparing to unpack .../libpython-dev_2.7.9-1_armhf.deb ...
Unpacking libpython-dev:armhf (2.7.9-1) ...
Selecting previously unselected package libudev-dev:armhf.
Preparing to unpack .../libudev-dev_215-17+deb8u7_armhf.deb ...
Unpacking libudev-dev:armhf (215-17+deb8u7) ...
Selecting previously unselected package xorg-sgml-doctools.
Preparing to unpack .../xorg-sgml-doctools_1%3a1.11-1_all.deb ...
Unpacking xorg-sgml-doctools (1:1.11-1) ...
Selecting previously unselected package x11proto-core-dev.
Preparing to unpack .../x11proto-core-dev_7.0.31-1_all.deb ...
Unpacking x11proto-core-dev (7.0.31-1) ...
Selecting previously unselected package libxau-dev:armhf.
Preparing to unpack .../libxau-dev_1%3a1.0.8-1_armhf.deb ...
Unpacking libxau-dev:armhf (1:1.0.8-1) ...
Selecting previously unselected package libxdmcp-dev:armhf.
Preparing to unpack .../libxdmcp-dev_1%3a1.1.1-1_armhf.deb ...
Unpacking libxdmcp-dev:armhf (1:1.1.1-1) ...
Selecting previously unselected package x11proto-input-dev.
Preparing to unpack .../x11proto-input-dev_2.3.1-1_all.deb ...
Unpacking x11proto-input-dev (2.3.1-1) ...
Selecting previously unselected package x11proto-kb-dev.
Preparing to unpack .../x11proto-kb-dev_1.0.6-2_all.deb ...
Unpacking x11proto-kb-dev (1.0.6-2) ...
Selecting previously unselected package xtrans-dev.
Preparing to unpack .../xtrans-dev_1.3.5-1_all.deb ...
Unpacking xtrans-dev (1.3.5-1) ...
Selecting previously unselected package libxcb1-dev:armhf.
Preparing to unpack .../libxcb1-dev_1.10-3_armhf.deb ...
Unpacking libxcb1-dev:armhf (1.10-3) ...
Selecting previously unselected package libx11-dev:armhf.
Preparing to unpack .../libx11-dev_2%3a1.6.2-3_armhf.deb ...
Unpacking libx11-dev:armhf (2:1.6.2-3) ...
Selecting previously unselected package libx11-doc.
Preparing to unpack .../libx11-doc_2%3a1.6.2-3_all.deb ...
Unpacking libx11-doc (2:1.6.2-3) ...
Selecting previously unselected package x11proto-xext-dev.
Preparing to unpack .../x11proto-xext-dev_7.3.0-1_all.deb ...
Unpacking x11proto-xext-dev (7.3.0-1) ...
Selecting previously unselected package libxext-dev:armhf.
Preparing to unpack .../libxext-dev_2%3a1.3.3-1_armhf.deb ...
Unpacking libxext-dev:armhf (2:1.3.3-1) ...
Selecting previously unselected package x11proto-randr-dev.
Preparing to unpack .../x11proto-randr-dev_1.5.0-1_all.deb ...
Unpacking x11proto-randr-dev (1.5.0-1) ...
Selecting previously unselected package x11proto-render-dev.
Preparing to unpack .../x11proto-render-dev_2%3a0.11.1-2_all.deb ...
Unpacking x11proto-render-dev (2:0.11.1-2) ...
Selecting previously unselected package libxrender-dev:armhf.
Preparing to unpack .../libxrender-dev_1%3a0.9.8-1_armhf.deb ...
Unpacking libxrender-dev:armhf (1:0.9.8-1) ...
Selecting previously unselected package libxrandr-dev:armhf.
Preparing to unpack .../libxrandr-dev_2%3a1.4.2-1_armhf.deb ...
Unpacking libxrandr-dev:armhf (2:1.4.2-1) ...
Selecting previously unselected package python2.7-dev.
Preparing to unpack .../python2.7-dev_2.7.9-2+deb8u1_armhf.deb ...
Unpacking python2.7-dev (2.7.9-2+deb8u1) ...
Selecting previously unselected package python-dev.
Preparing to unpack .../python-dev_2.7.9-1_armhf.deb ...
Unpacking python-dev (2.7.9-1) ...
Selecting previously unselected package swig2.0.
Preparing to unpack .../swig2.0_2.0.12-1_armhf.deb ...
Unpacking swig2.0 (2.0.12-1) ...
Selecting previously unselected package swig.
Preparing to unpack .../swig_2.0.12-1_armhf.deb ...
Unpacking swig (2.0.12-1) ...
Processing triggers for man-db (2.7.5-1~bpo8+1) ...
Setting up cmake-data (3.6.2-2~bpo8+1) ...
Setting up liblzo2-2:armhf (2.08-1.2) ...
Setting up libarchive13:armhf (3.1.2-11+deb8u3) ...
Setting up libjsoncpp0 (0.6.0~rc2-3.1) ...
Setting up cmake (3.6.2-2~bpo8+1) ...
Setting up libpython2.7-dev:armhf (2.7.9-2+deb8u1) ...
Setting up libxrender1:armhf (1:0.9.8-1) ...
Setting up libxrandr2:armhf (2:1.4.2-1) ...
Setting up libpthread-stubs0-dev:armhf (0.3-4) ...
Setting up libpython-dev:armhf (2.7.9-1) ...
Setting up libudev-dev:armhf (215-17+deb8u7) ...
Setting up xorg-sgml-doctools (1:1.11-1) ...
Setting up x11proto-core-dev (7.0.31-1) ...
Setting up libxau-dev:armhf (1:1.0.8-1) ...
Setting up libxdmcp-dev:armhf (1:1.1.1-1) ...
Setting up x11proto-input-dev (2.3.1-1) ...
Setting up x11proto-kb-dev (1.0.6-2) ...
Setting up xtrans-dev (1.3.5-1) ...
Setting up libxcb1-dev:armhf (1.10-3) ...
Setting up libx11-dev:armhf (2:1.6.2-3) ...
Setting up libx11-doc (2:1.6.2-3) ...
Setting up x11proto-xext-dev (7.3.0-1) ...
Setting up libxext-dev:armhf (2:1.3.3-1) ...
Setting up x11proto-randr-dev (1.5.0-1) ...
Setting up x11proto-render-dev (2:0.11.1-2) ...
Setting up libxrender-dev:armhf (1:0.9.8-1) ...
Setting up libxrandr-dev:armhf (2:1.4.2-1) ...
Setting up python2.7-dev (2.7.9-2+deb8u1) ...
Setting up python-dev (2.7.9-1) ...
Setting up swig2.0 (2.0.12-1) ...
Setting up swig (2.0.12-1) ...
Processing triggers for libc-bin (2.19-18+deb8u10) ...
Changing to homeassistant user
Creating source directory
Cloning Pulse-Eight platform
Cloning into 'platform'...
remote: Counting objects: 517, done.
remote: Compressing objects: 100% (2/2), done.
remote: Total 517 (delta 0), reused 1 (delta 0), pack-reused 515
Receiving objects: 100% (517/517), 176.54 KiB | 0 bytes/s, done.
Resolving deltas: 100% (294/294), done.
Checking connectivity... done.
Building Pulse-Eight platform
-- The C compiler identification is GNU 4.9.2
-- The CXX compiler identification is GNU 4.9.2
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - not found
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE  
-- Looking for __atomic_fetch_add_4 in atomic
-- Looking for __atomic_fetch_add_4 in atomic - found
-- Performing Test HAS_BUILTIN_SYNC_ADD_AND_FETCH
-- Performing Test HAS_BUILTIN_SYNC_ADD_AND_FETCH - Success
-- Performing Test HAS_BUILTIN_SYNC_SUB_AND_FETCH
-- Performing Test HAS_BUILTIN_SYNC_SUB_AND_FETCH - Success
-- Performing Test HAS_BUILTIN_SYNC_VAL_COMPARE_AND_SWAP
-- Performing Test HAS_BUILTIN_SYNC_VAL_COMPARE_AND_SWAP - Success
-- Configuring done
-- Generating done
-- Build files have been written to: /srv/homeassistant/src/platform/build
Scanning dependencies of target p8-platform
[ 50%] Building CXX object CMakeFiles/p8-platform.dir/src/util/StringUtils.cpp.o
[100%] Linking CXX static library libp8-platform.a
[100%] Built target p8-platform
Installing Pulse-Eight platform
[100%] Built target p8-platform
Install the project...
-- Install configuration: ""
-- Installing: /usr/local/lib/libp8-platform.a
-- Installing: /usr/local/include/p8-platform/os.h
-- Installing: /usr/local/include/p8-platform/posix/os-socket.h
-- Installing: /usr/local/include/p8-platform/posix/os-threads.h
-- Installing: /usr/local/include/p8-platform/posix/os-types.h
-- Installing: /usr/local/include/p8-platform/sockets/cdevsocket.h
-- Installing: /usr/local/include/p8-platform/sockets/socket.h
-- Installing: /usr/local/include/p8-platform/sockets/tcp.h
-- Installing: /usr/local/include/p8-platform/threads/atomics.h
-- Installing: /usr/local/include/p8-platform/threads/mutex.h
-- Installing: /usr/local/include/p8-platform/threads/threads.h
-- Installing: /usr/local/include/p8-platform/util/atomic.h
-- Installing: /usr/local/include/p8-platform/util/buffer.h
-- Installing: /usr/local/include/p8-platform/util/StringUtils.h
-- Installing: /usr/local/include/p8-platform/util/StdString.h
-- Installing: /usr/local/include/p8-platform/util/timeutils.h
-- Installing: /usr/local/include/p8-platform/util/util.h
-- Installing: /usr/local/lib/pkgconfig/p8-platform.pc
-- Installing: /usr/local/lib/p8-platform/p8-platform-config.cmake
Changing back to homeassistant user
Cloning Pulse-Eight libcec
Cloning into 'libcec'...
remote: Counting objects: 14813, done.
remote: Compressing objects: 100% (49/49), done.
remote: Total 14813 (delta 29), reused 39 (delta 15), pack-reused 14749
Receiving objects: 100% (14813/14813), 5.15 MiB | 209.00 KiB/s, done.
Resolving deltas: 100% (11238/11238), done.
Checking connectivity... done.
Building Pulse-Eight platform
-- The C compiler identification is GNU 4.9.2
-- The CXX compiler identification is GNU 4.9.2
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Performing Test SUPPORTS_CXX11
-- Performing Test SUPPORTS_CXX11 - Success
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - not found
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE  
-- Looking for initscr in curses
-- Looking for initscr in curses - not found
-- Looking for dlopen in dl
-- Looking for dlopen in dl - found
-- Looking for clock_gettime in rt
-- Looking for clock_gettime in rt - found
-- Found PythonLibs: /usr/lib/arm-linux-gnueabihf/libpython3.4m.so (found version "3.4.2") 
-- git found: libcec-4.0.2+30-8adc786
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.28") 
-- Looking for include file sys/file.h
-- Looking for include file sys/file.h - found
-- Looking for flock
-- Looking for flock - found
-- Checking for module 'udev'
--   Found udev, version 215
-- Looking for 3 include files X11/Xlib.h, ..., X11/extensions/Xrandr.h
-- Looking for 3 include files X11/Xlib.h, ..., X11/extensions/Xrandr.h - found
-- Looking for XRRGetScreenResources in Xrandr
-- Looking for XRRGetScreenResources in Xrandr - found
-- Looking for bcm_host_init in bcm_host
-- Looking for bcm_host_init in bcm_host - found
-- Looking for include files tda998x_ioctl.h, comps/tmdlHdmiCEC/inc/tmdlHdmiCEC_Types.h
-- Looking for include files tda998x_ioctl.h, comps/tmdlHdmiCEC/inc/tmdlHdmiCEC_Types.h - not found
-- Found SWIG: /usr/bin/swig2.0 (found version "2.0.12") 
CMake Error at src/libcec/cmake/CheckPlatformSupport.cmake:193 (if):
  if given arguments:

    "3" "GREATER" "2" "AND" "3" "GREATER_EQUAL" "7"

  Unknown arguments specified
Call Stack (most recent call first):
  src/libcec/CMakeLists.txt:133 (include)


-- Configuring incomplete, errors occurred!
See also "/srv/homeassistant/src/libcec/build/CMakeFiles/CMakeOutput.log".
See also "/srv/homeassistant/src/libcec/build/CMakeFiles/CMakeError.log".
make: *** No targets specified and no makefile found.  Stop.
Installing Pulse-Eight libcec
make: *** No rule to make target 'install'.  Stop.
Linking libcec to venv site packages

Installation done.

If you have issues with this script, please contact @Landrash on gitter.im

To continue have a look at https://home-assistant.io/components/hdmi_cec/
It's recomended that you restart your Pi before continuing with testing libcec.

Turn hassbian-scripts into available tool

It would be cool if instead of some scripts in a repo that we clone, if we had a command line tool available: hassbian-config.

We could install it as part of our image installation script and base our further installation on it.

$ hassbian-config samba
$ hassbian-config z-wave

We can take inspiration from the Radiodan people who have done an excellent job with their provision command to install different things on a RPi: https://github.com/radiodan/provision

Fixed with #11 .

hassbian-config and home assistant disappeared

Trying to run dasher. (its not workig btw^^)
somehow hassbian-config and home assistant disappeared.
but could run home assistand manual.
also systemctl [email protected] went missing

pi@hassbian:~ $ hassbian-config -V
-bash: hassbian-config: command not found

ways i took
2018-02-09-Hassbian.img
raspy-config
-filesystem & changing time zone
https://github.com/home-assistant/hassbian-scripts/blob/dev/docs/samba.md
https://github.com/danielperna84/hass-configurator#installation
https://github.com/maddox/dasher#raspberry-pi

Incorrect permissionson /srv/homeassistant

Make sure your running an up to date version of Hassbian before reporting a problem. If not make sure to specify what version and why so we can recreate the issue in question.

You should only file an issue if you found a bug. Feature and enhancement requests should go in #33 that's dedicated for this usage.

Hassbian-config version (hassbian-config -V):
image_2018-10-27-Hassbian
Script/Suite:
homeassistant
Description of problem:
According to this thread https://community.home-assistant.io/t/home-assistant-service-not-starting-on-new-hassbian-install/77869
and this thread
https://community.home-assistant.io/t/services-home-assistant-homeassistant-failed/78681

A number of new installers are experiencing incorrect permissions on /srv/homeassistant

Expected:

Traceback/log (if applicable):

Additional info:

Hassbian Wishlist

Wish list for functionality that we want to add to Hassbian. Pull requests welcome.

Install scripts

• Refactor database scripts for client and server parts.
• Node-RED
• Wireguard VPN
• HomeBridge. Implemented in #79
• Let's Encrypt. Registration and renewal. Implemented in #81
• MySQL. Replaced with MariaDB. Implemented in #53
• AppDaemon. Implemented in #52

Other functionality

• Iptables. Only listen to specified ports. Add exceptions with install scripts for use with Iptables.
• IPV6 support. Adapt scripts to display ipv6 address if available. Currently not implementable due to upstream problems with only running image with ipv6.
• MOTD. Using update-motd. #201
• Hotspot if no network functionality is detected. See #8 for details.
• Aliases for commonly used functions, Implemented in #107
• Service control functionality for homeassistant user.
• Power profile for wlan0 to off. Not implemented since package can be used with different hardware where this is not applicable.

Additions to base image

• Add zip package
• Backup and restore
• Load config on first boot

Extended functionality of scripts

• Add functionality for building Z-wave for older pies with limited amount of memory. Deprecated since package isn't built from source anymore.
• Add compatibility for scripts that doesn't work with Raspberry Pi zero.