The official Mosquitto MQTT broker is still based on version 1.4.12.
There has been some releases addressing mostly security vulnerabilities (up to 1.4.15).
Also a 1.5 features release which "brings a host of changes to the broker, including performance improvements and [...] numerous bug fixes".

I have a weird issue with Dnsmasq "Options" text field in the front end (Chrome latest version).
Whatever I try to fill in, when I click save, it doesn't save the values. It reports no error, but when I leave the tab and go back in my entry is replaced by the default one.
Syntax is correct, so it's not a typo, and save button it not grayed out.

this are the logs , in case there may be a lead. , it was workin perfect before update to hassOs , and also i updated samba to latest version .

mbd version 4.7.6 started.
Copyright Andrew Tridgell and the Samba Team 1992-2017
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
added interface wlan0 ip=192.168.0.61 bcast=192.168.0.255 netmask=255.255.255.0
making subnet name:192.168.0.61 Broadcast address:192.168.0.255 Subnet mask:255.255.255.0
making subnet name:UNICAST_SUBNET Broadcast address:0.0.0.0 Subnet mask:0.0.0.0
making subnet name:REMOTE_BROADCAST_SUBNET Broadcast address:0.0.0.0 Subnet mask:0.0.0.0
load_lmhosts_file: Can't open lmhosts file /etc/samba/lmhosts. Error was No such file or directory
STATUS=daemon 'nmbd' finished starting up and ready to serve connections
smbd version 4.7.6 started.
Copyright Andrew Tridgell and the Samba Team 1992-2017
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
Processing section "[config]"
Processing section "[addons]"
Processing section "[ssl]"
Processing section "[share]"
Processing section "[backup]"
added interface wlan0 ip=192.168.0.61 bcast=192.168.0.255 netmask=255.255.255.0
INFO: Profiling support unavailable in this build.
No builtin backend found, trying to load plugin
tdb(/var/lib/samba/registry.tdb): tdb_open_ex: could not open file /var/lib/samba/registry.tdb: No such file or directory
tdb(/var/lib/samba/account_policy.tdb): tdb_open_ex: could not open file /var/lib/samba/account_policy.tdb: No such file or directory
account_policy_get: tdb_fetch_uint32_t failed for type 1 (min password length), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 2 (password history), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 3 (user must logon to change password), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 4 (maximum password age), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 5 (minimum password age), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 6 (lockout duration), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 7 (reset count minutes), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 8 (bad lockout attempt), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 9 (disconnect time), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 10 (refuse machine password change), returning 0
tdbsam_open: Converting version 0.0 database to version 4.0.
tdbsam_convert_backup: updated /var/lib/samba/private/passdb.tdb file.
tdb(/var/lib/samba/winbindd_idmap.tdb): tdb_open_ex: could not open file /var/lib/samba/winbindd_idmap.tdb: No such file or directory
STATUS=daemon 'smbd' finished starting up and ready to serve connections
waiting for connections

I'm running hassio on a new RPi 3 B+ and I've installed the 'bluetooth_bcm43xx' add-on (restarted host machine) and added the 2 required lines to my config file:

device_tracker:
  - platform: bluetooth_tracker

When I look at the log for the add-on I see the following error:

starting version 3.2.4
bcm43xx_init
Failed to write reset command
Can't initialize device: No error information

and in my hass log I see:

018-06-21 20:06:31 ERROR (MainThread) [homeassistant.components.device_tracker] Error setting up platform bluetooth_tracker
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/bluetooth/bluez.py", line 31, in discover_devices
    lookup_class=lookup_class, device_id=device_id)
_bluetooth.error: (110, 'Operation timed out')

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/homeassistant/components/device_tracker/__init__.py", line 183, in async_setup_platform
    disc_info)
  File "/usr/lib/python3.6/concurrent/futures/thread.py", line 56, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/lib/python3.6/site-packages/homeassistant/components/device_tracker/bluetooth_tracker.py", line 72, in setup_scanner
    for dev in discover_devices():
  File "/usr/lib/python3.6/site-packages/homeassistant/components/device_tracker/bluetooth_tracker.py", line 50, in discover_devices
    lookup_class=False)
  File "/usr/lib/python3.6/site-packages/bluetooth/bluez.py", line 34, in discover_devices
    raise BluetoothError ("error communicating with local "
bluetooth.btcommon.BluetoothError: error communicating with local bluetooth adapter

Is this likely due to different hardware chip for BL/BLE radio or have I made some basic mistake in my setup?

I would like to request the personal wake word feature for hass.io.
I don't know if it's possible with the current state of hass.io, but it would be a nice addition.

A possible solutions could be to create and train the wake word on another computer, and upload the files to the share folder.

After update to 3.0 of the snips addon, I get the following errors:

2018-05-11 00:23:22,311 INFO exited: snips-asr (exit status 1; not expected)
ERROR:snips_tts: Could not start MQTT client
 -> caused by: Connection refused (os error 111)
2018-05-11 00:23:22,358 INFO spawned: 'snips-asr' with pid 75
2018-05-11 00:23:22,368 INFO exited: snips-tts (exit status 1; not expected)
ERROR:snips_dialogue: Could not start MQTT client
 -> caused by: Connection refused (os error 111)
2018-05-11 00:23:22,370 INFO exited: snips-dialogue (exit status 1; not expected)
ERROR:snips_audio_server: Could not start MQTT client
 -> caused by: Connection refused (os error 111)
2018-05-11 00:23:22,408 INFO exited: snips-audio-server (exit status 1; not expected)
ERROR:snips_nlu: Could not start MQTT client
 -> caused by: Connection refused (os error 111)
2018-05-11 00:23:22,461 INFO exited: snips-nlu (exit status 1; not expected)
ERROR:snips_asr: Could not start MQTT client
 -> caused by: Connection refused (os error 111)
2018-05-11 00:23:23,455 INFO success: snips-asr entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-05-11 00:23:23,463 INFO spawned: 'snips-hotword' with pid 76
2018-05-11 00:23:23,466 INFO exited: snips-asr (exit status 1; not expected)
ERROR:snips_hotword: Could not start MQTT client
 -> caused by: Connection refused (os error 111)
2018-05-11 00:23:23,827 INFO spawned: 'snips-asr' with pid 77
2018-05-11 00:23:23,830 INFO exited: snips-hotword (exit status 1; not expected)
2018-05-11 00:23:24,834 INFO success: snips-asr entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
ERROR:snips_asr: Could not start MQTT client
 -> caused by: Connection refused (os error 111)
2018-05-11 00:23:24,848 INFO exited: snips-asr (exit status 1; not expected)
2018-05-11 00:23:25,855 INFO spawned: 'snips-tts' with pid 78
2018-05-11 00:23:25,865 INFO spawned: 'snips-dialogue' with pid 79
2018-05-11 00:23:25,873 INFO spawned: 'snips-asr' with pid 80
2018-05-11 00:23:25,881 INFO spawned: 'snips-nlu' with pid 81
2018-05-11 00:23:25,890 INFO spawned: 'snips-audio-server' with pid 82
ERROR:snips_audio_server: Could not start MQTT client
 -> caused by: Connection refused (os error 111)
ERROR:snips_dialogue: Could not start MQTT client
 -> caused by: Connection refused (os error 111)
2018-05-11 00:23:25,957 INFO exited: snips-dialogue (exit status 1; not expected)
ERROR:snips_tts: Could not start MQTT client
 -> caused by: Connection refused (os error 111)
2018-05-11 00:23:25,961 INFO gave up: snips-dialogue entered FATAL state, too many start retries too quickly
2018-05-11 00:23:25,963 INFO exited: snips-tts (exit status 1; not expected)
2018-05-11 00:23:25,966 INFO gave up: snips-tts entered FATAL state, too many start retries too quickly
2018-05-11 00:23:25,968 INFO exited: snips-audio-server (exit status 1; not expected)
ERROR:snips_nlu: Could not start MQTT client
 -> caused by: Connection refused (os error 111)
2018-05-11 00:23:26,060 INFO gave up: snips-audio-server entered FATAL state, too many start retries too quickly
2018-05-11 00:23:26,074 INFO exited: snips-nlu (exit status 1; not expected)
ERROR:snips_asr: Could not start MQTT client
 -> caused by: Connection refused (os error 111)
2018-05-11 00:23:27,002 INFO success: snips-asr entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-05-11 00:23:27,003 INFO gave up: snips-nlu entered FATAL state, too many start retries too quickly
2018-05-11 00:23:27,010 INFO spawned: 'snips-hotword' with pid 83
2018-05-11 00:23:27,013 INFO exited: snips-asr (exit status 1; not expected)
ERROR:snips_hotword: Could not start MQTT client
 -> caused by: Connection refused (os error 111)
2018-05-11 00:23:27,397 INFO spawned: 'snips-asr' with pid 84
2018-05-11 00:23:27,400 INFO exited: snips-hotword (exit status 1; not expected)
2018-05-11 00:23:28,404 INFO success: snips-asr entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-05-11 00:23:28,404 INFO gave up: snips-hotword entered FATAL state, too many start retries too quickly
ERROR:snips_asr: Could not start MQTT client
 -> caused by: Connection refused (os error 111)
2018-05-11 00:23:28,432 INFO exited: snips-asr (exit status 1; not expected)
2018-05-11 00:23:29,439 INFO spawned: 'snips-asr' with pid 85
2018-05-11 00:23:30,442 INFO success: snips-asr entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
ERROR:snips_asr: Could not start MQTT client
 -> caused by: Connection refused (os error 111)
2018-05-11 00:23:30,513 INFO exited: snips-asr (exit status 1; not expected)
2018-05-11 00:23:31,520 INFO spawned: 'snips-asr' with pid 86
ERROR:snips_asr: Could not start MQTT client
 -> caused by: Connection refused (os error 111)

Snips Config:

{
  "mqtt_bridge": {
    "active": true,
    "host": "core-mosquitto",
    "port": 1883,
    "user": "***",
    "password": "***"
  },
  "assistant": "assistant_proj_***",
  "language": "de",
  "custom_tts": {
    "active": false,
    "platform": "amazon_polly"
  }
}

(sensitive data replaced with ***)

Mosquitto addon log:

starting version 3.2.2
1525994129: mosquitto version 1.4.12 (build date 2017-06-01 13:03:48+0000) starting
1525994129: Config loaded from /etc/mosquitto.conf.
1525994129: Opening ipv4 listen socket on port 1883.
1525994129: Opening ipv6 listen socket on port 1883.
1525994129: Opening ipv4 listen socket on port 8883.
1525994129: Opening ipv6 listen socket on port 8883.
1525994129: Warning: Mosquitto should not be run as root/administrator.
1525994131: New connection from 172.30.32.1 on port 1883.
1525994132: Socket error on client <unknown>, disconnecting.
1525994132: New connection from 172.30.32.1 on port 1883.
1525994132: New client connected from 172.30.32.1 as ***
1525994154: Client core-snips.main-mqtt disconnected.
1525994154: New client connected from 172.30.33.3 as core-snips.main-mqtt (c0, k60, ***).

Mosquitto config:

{
  "plain": true,
  "ssl": true,
  "anonymous": true,
  "logins": [
    {
      "username": "***",
      "password": "***"
    }
  ],
  "customize": {
    "active": false,
    "folder": "mosquitto"
  },
  "certfile": "fullchain.pem",
  "keyfile": "privkey.pem"
}

@tschmidty69

hello, I just updated the google assistant addon on hassio, and to my surprise I find this:Traceback (most recent call last):
File "/hassio_gassistant.py", line 30, in
with Assistant(credentials) as assistant:
TypeError: init() missing 1 required positional argument: 'device_model_id'

I removed everything and installed again but it gives me this error

Traceback (most recent call last):
File "/hassio_oauth.py", line 6, in
import cherrypy
File "/usr/local/lib/python3.5/dist-packages/cherrypy/init.py", line 73, in
from ._cptools import default_toolbox as tools, Tool
File "/usr/local/lib/python3.5/dist-packages/cherrypy/_cptools.py", line 33, in
from cherrypy.lib import auth_basic, auth_digest
File "/usr/local/lib/python3.5/dist-packages/cherrypy/lib/auth_digest.py", line 26, in
from six.moves.urllib.parse import unquote_to_bytes
ImportError: cannot import name 'unquote_to_bytes'

I've setup a custom server (with the us of "servers": "nginx_proxy/*.conf"). I'd like for this server to have a cert. Right now it comes up but the lock is greyed out in a browser.

To make the Samba add-on more secure by default, we should limit which IP addresses can access it. This should be limited to just local ones by default.

We can achieve this by setting the hosts allow property in smb.conf. We can then make it configurable for users via the options.

I had trouble renewing my cert with 3 SAN.

The hooks.sh loops 3 times through "deploy_challenge" for all domains butt different tokens. Therefore the 3rd call sets 2 wrong TXT records and 1 correct.
I exchanged $DOMAINS with $2 in deploy_challenge and clean_challenge to get it working again.

I am not sure which tool or API changed because it had been working on 12th of April the last time.
I think it is related to https://github.com/lukas2511/dehydrated/releases/tag/v0.6.0

Challenge validation loop has been modified to loop over authorization identifiers instead of altnames (ACMEv2 + wildcard support)

@narongk commented on Jul 1, 2018, 2:40 PM UTC:

[FATAL:audio_input_stream.cc(47)] Input device could not be opened: default

This issue was moved by frenck from home-assistant/home-assistant.github.io#5643.

Home Assistant release (hass --version):
Hassio 0.64.1

Python release (python3 --version):
N/A for Hassio

Component/platform:
Mosquitto broker installed from Hassio add-ons

Description of problem:
MQTT server doesn't start when the start button is clicked on this page:
http://hassio.local:8123/hassio/addon/core_mosquitto

Does not start with the system either.

This worked with <0.64.1 . No configuration changes prior.
Expected:

MQTT server running

Problem-relevant configuration.yaml entries and steps to reproduce:

1. Try and start Mosquitto server from the web interface by clicking start
2. It appears to start but reloading the page shows that the MQTT server is not actually running.

Restarts and uninstalling the addon and reinstalling do not help.

Traceback (if applicable):

2018-02-28 23:15:14 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/aiohttp/web_protocol.py", line 416, in start
    resp = yield from self._request_handler(request)
  File "/usr/lib/python3.6/site-packages/aiohttp/web.py", line 325, in _handle
    resp = yield from handler(request)
  File "/usr/lib/python3.6/site-packages/aiohttp/web_middlewares.py", line 93, in impl
    return (yield from handler(request))
  File "/usr/lib/python3.6/site-packages/homeassistant/components/http/static.py", line 70, in staticresource_middleware
    return (yield from handler(request))
  File "/usr/lib/python3.6/site-packages/homeassistant/components/http/real_ip.py", line 28, in real_ip_middleware
    return (yield from handler(request))
  File "/usr/lib/python3.6/site-packages/homeassistant/components/http/ban.py", line 70, in ban_middleware
    return (yield from handler(request))
  File "/usr/lib/python3.6/site-packages/homeassistant/components/http/auth.py", line 53, in auth_middleware
    return (yield from handler(request))
  File "/usr/lib/python3.6/site-packages/homeassistant/components/http/__init__.py", line 409, in handle
    result = yield from result
  File "/usr/lib/python3.6/site-packages/homeassistant/components/hassio/http.py", line 66, in _handle
    return _create_response_log(client, data)
  File "/usr/lib/python3.6/site-packages/homeassistant/components/hassio/http.py", line 120, in _create_response_log
    log = re.sub(r"\x1b(\[.*?[@-~]|\].*?(\x07|\x1b\\))", "", data.decode())
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position 138: invalid start byte

Additional info:

From yersterday night Samba do not works
I use HA 0.64 and HASSIO 0.94 and my config is:

{
"workgroup": "WORKGROUP",
"name": "hassio",
"guest": true,
"map": {
"config": true,
"addons": true,
"ssl": false,
"share": true,
"backup": true
},
"username": "admin",
"password": "admin",
"interface": "eth0"
}

Hassio system log is:

18-02-25 21:10:37 INFO (SyncWorker_18) [hassio.docker.interface] Stop homeassistant/armhf-addon-samba docker application
18-02-25 21:10:38 INFO (SyncWorker_18) [hassio.docker.interface] Clean homeassistant/armhf-addon-samba docker application
18-02-25 21:10:45 INFO (SyncWorker_3) [hassio.docker.addon] Start docker addon homeassistant/armhf-addon-samba with version 3.0
18-02-25 21:12:52 INFO (SyncWorker_19) [hassio.docker.interface] Stop homeassistant/armhf-addon-samba docker application
18-02-25 21:12:53 INFO (SyncWorker_19) [hassio.docker.interface] Clean homeassistant/armhf-addon-samba docker application
18-02-25 21:12:54 INFO (SyncWorker_7) [hassio.docker.addon] Start docker addon homeassistant/armhf-addon-samba with version 3.0
18-02-25 21:13:17 INFO (SyncWorker_9) [hassio.docker.interface] Stop homeassistant/armhf-addon-samba docker application
18-02-25 21:13:18 INFO (SyncWorker_9) [hassio.docker.interface] Clean homeassistant/armhf-addon-samba docker application
18-02-25 21:13:19 INFO (SyncWorker_8) [hassio.docker.addon] Start docker addon homeassistant/armhf-addon-samba with version 3.0

Samba show me this log…

starting version 3.2.4
nmbd version 4.7.3 started.
Copyright Andrew Tridgell and the Samba Team 1992-2017
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
added interface eth0 ip=192.168.1.2 bcast=192.168.1.255 netmask=255.255.255.0
making subnet name:192.168.1.2 Broadcast address:192.168.1.255 Subnet mask:255.255.255.0
making subnet name:UNICAST_SUBNET Broadcast address:0.0.0.0 Subnet mask:0.0.0.0
making subnet name:REMOTE_BROADCAST_SUBNET Broadcast address:0.0.0.0 Subnet mask:0.0.0.0
load_lmhosts_file: Can’t open lmhosts file /etc/samba/lmhosts. Error was No such file or directory
STATUS=daemon ‘nmbd’ finished starting up and ready to serve connections
smbd version 4.7.3 started.
Copyright Andrew Tridgell and the Samba Team 1992-2017
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
Processing section "[config]"
Processing section "[addons]"
Processing section "[share]"
Processing section "[backup]"
added interface eth0 ip=192.168.1.2 bcast=192.168.1.255 netmask=255.255.255.0
INFO: Profiling support unavailable in this build.
No builtin backend found, trying to load plugin
tdb(/var/lib/samba/registry.tdb): tdb_open_ex: could not open file /var/lib/samba/registry.tdb: No such file or directory
tdb(/var/lib/samba/account_policy.tdb): tdb_open_ex: could not open file /var/lib/samba/account_policy.tdb: No such file or directory
account_policy_get: tdb_fetch_uint32_t failed for type 1 (min password length), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 2 (password history), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 3 (user must logon to change password), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 4 (maximum password age), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 5 (minimum password age), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 6 (lockout duration), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 7 (reset count minutes), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 8 (bad lockout attempt), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 9 (disconnect time), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 10 (refuse machine password change), returning 0
tdbsam_open: Converting version 0.0 database to version 4.0.
tdbsam_convert_backup: updated /var/lib/samba/private/passdb.tdb file.
tdb(/var/lib/samba/winbindd_idmap.tdb): tdb_open_ex: could not open file /var/lib/samba/winbindd_idmap.tdb: No such file or directory
STATUS=daemon ‘smbd’ finished starting up and ready to serve connections
waiting for connections
check_for_master_browser_fail: Forcing election on workgroup WORKGROUP subnet 192.168.1.2
send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 192.168.1.2
send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 192.168.1.2
send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 192.168.1.2
send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 192.168.1.2
send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 192.168.1.2
run_elections: >>> Won election for workgroup WORKGROUP on subnet 192.168.1.2 <<<
become_local_master_browser: Starting to become a master browser for workgroup WORKGROUP on subnet 192.168.1.2

Samba name server HASSIO is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.2

What's happening?

Snips.ai now produces models with version 0.12.0. Any attempt to use these with the current build of the snips addon results in model mismatch error and fails to run. I did a local docker build of the snips addon using 0.52.7 and can confirm that it works as expected. Obviously the bundled assistant.zip would need to be updated as well...

Been trying to set Configurator up behind an Nginx proxy and need to modify the HASS_API value.
This can't be set via the addon config, is this something that can be changed?

How do I clear the MosquittoDB? I have quite a few messages retained in there from devices that no longer exist. These are cluttering up my dashboard.

I have already tried:

• sending null length messages. i.e. mosquitto_pub -h 10.50.50.77 -r -n -t '/espurna/FurnacePump/energy -u <username> -P <password>
• Restarting mosquitto
• uninstalling and reinstalling mosquitto
• restarting hassio

I am at a loss since there is no /var/lib/mosquitto/mosquitto.db to simply delete

I am left with a bunch of these:

@pvizeli FYI, there is an updated copy of the default SNIPS assistant here: https://github.com/tschmidty69/hassio-snips/releases/download/0.1-pre1/assistant.zip

The latest version needs to use this as the default

I would like to configure mosquitto as bridge,
actually I can do that adding my configuration via the samba addon as stated in the configuration.

If the other mosquitto instance is running with ssl I am unable to connect to it because in the configuration file must be present the bridge_cafile configuration option.
Inspecting the addon I cannot find the /ssl/certs/ca-certificates.crt needed for this configuration.

My first attempt was

ln -s /etc/ssl/certs /resin-data/ssl/

in the hassio root but this is not optimal because it requires access to the underlying os.

Am I missing something about the ssl connection?
There is other routes?

I never tryed to work with the hassio addons, if it can be an interesting advance in the configuration I can try to help if someone can point me in the right direction.

Thank you
Andrea

The addon claims my cert is up to date, expiring in 3 months. When attempting to access the ddns domain, the resulting cert claims it expired yesterday. There is no way to update the cert because the addon think's it's up to date. I had to create a new ddns domain to get around this issue. New domain works fine after a new cert was created.

Released 13th June and now produces 0.15.0 models which won't work with the current addon.

@jasimancas commented on Jun 28, 2018, 3:34 PM UTC:

I have installed the addon Bluetooth BCM43xx, but the devices dont report.

Raspberry PI3B

The log of the add-on:

bcm43xx_init
Flash firmware /lib/firmware/brcm/BCM43430A1.hcd
Set BDADDR UART: b8:27:eb:60:46:d0
Set Controller UART speed to 921600 bit/s
Device setup complete

I have https://www.home-assistant.io/components/sensor.mitemp_bt/ and https://www.home-assistant.io/components/sensor.miflora/

This issue was moved by pvizeli from home-assistant/hassos#52.

When using "long" dns server name from for example duckdns nginx won't start and prints an error message:

nginx: [emerg] could not build server_names_hash, you should increase server_names_hash_bucket_size: 32

Setting server_names_hash_bucket_size 32; in the http part of nginx.conf should fix the issue.

Setting domain to *.duckdns.org works in the meantime.

{ "domain": "*.duckdns.org", "certfile": "fullchain.pem", "keyfile": "privkey.pem" }

• sesame (Optional): Secret token to dynamically allow access from the IP the request originates from. Open your bookmark https://hassio.yourdomain.com:8123/somesecretnobodycanguess while allowed_networks is set to [] and boom! Open Sesame! You can use the Network status menu to revoke IP addresses for which access has been granted.

From a security point of view is this a pretty high risk. The token can be anything, as far as I can tell, which make it vulnerable for enumerations and simple guessing. The token is part of the request and will be visible in logs. It looks also like that we are facing a similar issue as with #14345 here.

When I try to clone my Hassio configuration from a GitHub repo (ssh cloned) i got these errors:

starting version 3.2.4
Check SSH connection
Host key verification failed.
Valid SSH connection for [email protected]
git repository exists, start pulling
Host key verification failed.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
[Error] Git pull failed

Debugging I've seen that the exit code of the check-ssh-key internal check is a bit buggy in this case because reports that there is a Valid SSH connection even if no ssh key is already installed, it does not proceed adding the given key and the following commands fail.
I tried to solve it with PR #241
Hope it will help!

@JAAlperin commented on Jun 19, 2018, 5:25 PM UTC:

{
"lets_encrypt": {
"accept_terms": true,
"certfile": "fullchain.pem",
"keyfile": "privkey.pem"
},
"token": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
"domains": [
"xxx.duckdns.org",
"*.xxx.duckdns.org"
],
"seconds": 1800
}

results in this:

OKOKOKOK + Responding to challenge for xxx.duckdns.org authorization...

• Cleaning challenge tokens...
  OKOKOKOK + Challenge validation has failed :(
  ERROR: Challenge is invalid! (returned: invalid) (result: {
  "type": "dns-01",
  "status": "invalid",
  "error": {
  "type": "urn:ietf:params:acme:error:unauthorized",
  "detail": "Incorrect TXT record "gYvyuKSEz-Sa58khnK9KUc0MUu3C5WDf_7qRDwlDAcM" found at _acme-challenge.xxx.duckdns.org",
  "status": 403
  },
  "url": "https://acme-v02.api.letsencrypt.org/acme/challenge/szX3vuPHMvfMYF-heQcbgmGA4sYZzSVXMMLbjhDm3_Q/5197664255",
  "token": "MxeILOKZ8GYrxuHkWPQYTu3_ZXjbexpDp_miok76grY"
  })

If I understand the many internet posts regarding this issue, it has to do with HOOK_CHAIN=yes, the tokens in the single TXT record, and has been fixed already in certbot via a changed script.

This issue was moved by frenck from home-assistant/home-assistant.io/issues/5574.

Hi, in my logs I am seeing this error:

starting version 3.2.4
/run.sh: line 8: jq: command not found

Let's Encrypt has worked before on this machine.

I'm trying to make some changes to the nginx configuration that has to be stored in the /share/ directory. Unfortuntely, the UI seems to be hiding this even though it exists.

See this image of what the UI shows: https://i.imgur.com/gsDzn4O.png

SSHing in and ls'ing the root:

ls -lh /
drwxr-xr-x    2 root     root        4.0K Jul 18  2017 addons
drwxr-xr-x    2 root     root        4.0K May 28 01:57 backup
drwxr-xr-x    2 root     root        4.0K May  2 13:21 bin
drwxr-xr-x    7 root     root        4.0K Jul  4 11:43 config
drwxr-xr-x    3 root     root        4.0K Jan  8 23:04 data
drwxr-xr-x    5 root     root         340 Jun 12 21:32 dev
drwxr-xr-x   29 root     root        4.0K Jun 12 21:33 etc
drwxr-xr-x    2 root     root        4.0K Nov 30  2017 home
drwxr-xr-x    8 root     root        4.0K May  2 13:20 lib
drwxr-xr-x    5 root     root        4.0K Nov 30  2017 media
drwxr-xr-x    2 root     root        4.0K Nov 30  2017 mnt
dr-xr-xr-x  184 root     root           0 Jun 12 21:32 proc
drwx------    2 root     root        4.0K Jun 12 21:33 root
drwxr-xr-x    2 root     root        4.0K Jun 12 21:33 run
-rwxr-xr-x    1 root     root        1.6K Jun 12 05:39 run.sh
drwxr-xr-x    2 root     root        4.0K May  2 13:20 sbin
drwxr-xr-x    4 root     root        4.0K Jun  3 21:05 share
drwxr-xr-x    2 root     root        4.0K Nov 30  2017 srv
drwxr-xr-x    2 root     root        4.0K Jun  2 19:57 ssl
dr-xr-xr-x   12 root     root           0 Jun 12 21:32 sys
drwxrwxrwt    2 root     root        4.0K Jul  4 11:42 tmp
drwxr-xr-x   21 root     root        4.0K Jun  1 10:28 usr
drwxr-xr-x   12 root     root        4.0K Jun  1 10:28 var

Hello!
I’ve tried reimaging my SD card multiple times with the lastest hassio release. Still no luck though, the only repository that displays is the Community Hassio Addons(https://github.com/hassio-addons/repository). Everytime I try to add this repository to my addon store I get this error:
18-05-12 15:44:22 ERROR (MainThread) [hassio.addons] Can't load from repository https://github.com/home-assistant/hassio-addons
18-05-12 15:44:22 INFO (MainThread) [hassio.addons] Load addons: 14 all - 0 new - 0 remove.
Please help, I want to use letsencrypt on my setup. Thanks, Will.

Can someone update snips add-on. I'm working on getting snips to work via voice. I'm almost there, but snips is now compiling with version 13 and is causing snips to fail on hassio.

Thanks,

rschoolm

I am not able to update certificate because addon won't start. This is in syslog

18-04-14 07:53:03 INFO (SyncWorker_10) [hassio.docker.interface] Clean homeassistant/armhf-addon-letsencrypt docker application
18-04-14 07:53:04 ERROR (SyncWorker_10) [hassio.docker] Can't start addon_core_letsencrypt: 500 Server Error: Internal Server Error ("driver failed programming external connectivity on endpoint addon_core_letsencrypt (f02325c6e24d436c91fd3535941f0f8d032cc9bdd81b26f972cc60a85ffe724d): Bind for 0.0.0.0:80 failed: port is already allocated")

Adding something like this before location / in nginx.conf would provide a useful extension point with which one could add additional proxied locations:

include /ssl/nginx_proxy/%%DOMAIN%%*.conf;
(The * is important, it prevents failures if the file doesn't exist.)

I tried to add it myself, but am having problems getting local addon build to refresh (e.g. no matter what changes I make to run.sh, e.g. add some echos/logging, they don't show up in the addon's logs).

Hello! I have an add-on suggestion.

Similar to the DuckDNS add-on, it would be great to update custom DNS domains on some service such as Cloudflare, Google Domains, etc.

ddclient supports a big list of supported services (DuckDNS included).

Usage example: I have my own personal domain my-domain.com and want to create one sub-domain for my rpi installation at home and another one for work. So I can create home.my-domain.com and work.my-domain.com. Assuming that I'm already using Cloudflare for my main domain, I can update the sub-domain with ddclient directly into Cloudflare.

Possible related PR: #277

i try to install samba,but i don't work. i check the system log : samba can't install. what should i do to fix the problem. thanks.

[hassio.docker.interface] Can't install homeassistant/armhf-addon-samba:3.0 -> 404 Client Error: Not Found ("no such image: homeassistant/armhf-addon-samba:3.0: No such image: homeassistant/armhf-addon-samba:3.0").

I am using duckdns with let's encrypt and the nginx addon. This week I had a problem that the in use certificate was outdated because I did not restart the nginx addon since a long time and it did not pick up the up to date certificate that was ready.

In an issue was mentioned that the SSH daemon for the debugging is using obsolete settings.

• Disable weak MAC algorithms
• Disable weak ciphers and modes

I would like to suggest that the SSH Add-on is set to more strict settings in regard of algorithms, ciphers and allowed modes.

Trying to get a certificate with the let's encryt addon, I get this log:

starting version 3.2.4
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator standalone, Installer None
An unexpected error occurred:
ConnectionError: HTTPSConnectionPool(host='acme-v01.api.letsencrypt.org', port=443): Max retries exceeded with url: /directory (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7fe0f6191590>: Failed to establish a new connection: [Errno -3] Try again',))
Please see the logfiles in /var/log/letsencrypt for more details.

It is like if the addon can't connect to acme-v01.api.letsencrypt.org
Port 80 is forwarded to docker host.
Hassio can connect to the internet with no issue.

I think that we should limit the official repository to only the addons that are really useful for a broad audience and related to making Home Assistant more useful. A bunch of these add-ons are cool to run on your server (DNS, DHCP, Nginx proxy), but are just not Home Automation specific enough.

Here are the add-ons that I would suggest to move out of the official add-on repo:

• cec_scan. Too niche of an add-on
• custom_deps. Too dangerous to be in default repo. This is one of those add-ons that people first get a use case, than want to find the add-on.
• dhcp_server. Very small use case. Also has danger of people breaking their network.
• dnsmasq. I think pretty niche use case
• letsencrypt. People can achieve this using DuckDNS + Let's Encrypt. By having a standalone add-on, it becomes confusing.
• nginx_proxy. Not home automation specific
• rpc_shutdown`. Too niche use case.

Having too many add-ons means that the user is getting overwhelmed and will be unable to find the add-ons that it probably needs. (not seeing the forrest through the trees)

I am running Google Assistant SDK 2.1 on a Ubuntu server and I can not select all my audio outputs/inputs.

It is not picking up my built-in mic port but will pick up the mic on a USB sound card and it will only pick up some built-in audio output but not the USB output, so I cant get sound to work with it. All the hardware shows up under show hardware.

input:
	HDA Intel PCH Rear Mic
	Power Button
	Sleep Button
	HDA Intel PCH Line
	GeneralPlus USB Audio Device
	HDA Intel PCH Line Out Front
	HDA Intel PCH Line Out CLFE
	HDA Intel PCH HDMI/DP,pcm=3
	HDA Intel PCH HDMI/DP,pcm=7
	Video Bus
	HDA Intel PCH Line Out Surround
	Logitech Optical USB Mouse
	Dell Dell USB Keyboard
	HDA Intel PCH HDMI/DP,pcm=8

audio:
	0:
		name: HDA-Intel - HDA Intel PCH
		type: PCH
		devices:
			0: hardware dependent
			1: digital audio playback
			2: hardware dependent
			3: digital audio playback
			7: digital audio playback
			8: digital audio playback
	1:
		name: USB-Audio - USB Audio Device
		type: Device
		devices:
			0: digital audio capture

It used to work fine when I had to give the card and sub device in the config.

I've added the repository link. However, unable to add repository. Following is the log.

<>18-04-22 02:41:01 INFO (MainThread) [hassio.addons.git] Clone addon https://github.com/home-assistant/hassio-addons repository
18-04-22 02:41:55 WARNING (MainThread) [hassio.addons.data] Can't read /data/addons/core/nginx_proxy/config.json
18-04-22 02:41:55 WARNING (MainThread) [hassio.addons.data] Can't read /data/addons/core/samba/config.json
18-04-22 02:41:55 WARNING (MainThread) [hassio.addons.data] Can't read /data/addons/core/configurator/config.json
18-04-22 02:41:55 WARNING (MainThread) [hassio.addons.data] Can't read /data/addons/core/google_assistant/config.json
18-04-22 02:41:55 WARNING (MainThread) [hassio.addons.data] Can't read /data/addons/core/cec_scan/config.json
18-04-22 02:41:55 WARNING (MainThread) [hassio.addons.data] Can't read /data/addons/core/rpc_shutdown/config.json
18-04-22 02:41:55 WARNING (MainThread) [hassio.addons.data] Can't read /data/addons/core/ssh/config.json
18-04-22 02:41:55 WARNING (MainThread) [hassio.addons.data] Can't read /data/addons/core/bluetooth_bcm43xx/config.json
18-04-22 02:41:55 WARNING (MainThread) [hassio.addons.data] Can't read /data/addons/core/git_pull/config.json
18-04-22 02:41:55 WARNING (MainThread) [hassio.addons.data] Can't read /data/addons/core/letsencrypt/config.json
18-04-22 02:41:55 WARNING (MainThread) [hassio.addons.data] Can't read /data/addons/core/mosquitto/config.json
18-04-22 02:41:55 WARNING (MainThread) [hassio.addons.data] Can't read /data/addons/core/dhcp_server/config.json
18-04-22 02:41:55 WARNING (MainThread) [hassio.addons.data] Can't read /data/addons/core/dnsmasq/config.json
18-04-22 02:41:55 WARNING (MainThread) [hassio.addons.data] Can't read /data/addons/core/snips/config.json
18-04-22 02:41:55 WARNING (MainThread) [hassio.addons.data] Can't read /data/addons/core/homematic/config.json
18-04-22 02:41:55 WARNING (MainThread) [hassio.addons.data] Can't read /data/addons/core/check_config/config.json
18-04-22 02:41:55 WARNING (MainThread) [hassio.addons.data] Can't read /data/addons/core/tellstick/config.json
18-04-22 02:41:55 WARNING (MainThread) [hassio.addons.data] Can't read /data/addons/core/mariadb/config.json
18-04-22 02:41:55 WARNING (MainThread) [hassio.addons.data] Can't read /data/addons/core/duckdns/config.json
18-04-22 02:41:55 WARNING (MainThread) [hassio.addons.data] Can't read repository information from /data/addons/git/e724ce20/repository.json
18-04-22 02:41:55 INFO (MainThread) [hassio.addons] Load addons: 14 all - 0 new - 0 remove<>

@jasimancas commented on Jun 28, 2018, 3:34 PM UTC:

I have installed the addon Bluetooth BCM43xx, but the devices dont report.

Raspberry PI3B

The log of the add-on:

bcm43xx_init
Flash firmware /lib/firmware/brcm/BCM43430A1.hcd
Set BDADDR UART: b8:27:eb:60:46:d0
Set Controller UART speed to 921600 bit/s
Device setup complete

I have https://www.home-assistant.io/components/sensor.mitemp_bt/ and https://www.home-assistant.io/components/sensor.miflora/

This issue was moved by pvizeli from home-assistant/hassos#52.

Hello! Thanks for the great addons available here.

I'm having an issue setting up the Google Assistant SDK add-on. After configuring every option and everything on Cloud Platform Console, it properly opens the OAuth2 Web UI.

Following the steps, after getting a token and submitting the page, it gives an 500 error on the page with a python traceback showing that it failed to establish a connection to the Google server.

I searched online how to solve this issue, however I was not able to fix it directly. On the main machine I'm able to solve the host, so doesn't look any problems with the DNS server I'm using.

Server: Ubuntu 18.04 LTS (Lubuntu on Acer netbook) with Docker
Installed via generic server script

Traceback (most recent call last):
  File "/usr/local/lib/python3.5/dist-packages/cherrypy/_cprequest.py", line 631, in respond
    self._do_respond(path_info)
  File "/usr/local/lib/python3.5/dist-packages/cherrypy/_cprequest.py", line 690, in _do_respond
    response.body = self.handler()
  File "/usr/local/lib/python3.5/dist-packages/cherrypy/lib/encoding.py", line 221, in __call__
    self.body = self.oldhandler(*args, **kwargs)
  File "/usr/local/lib/python3.5/dist-packages/cherrypy/_cpdispatch.py", line 60, in __call__
    return self.callable(*self.args, **self.kwargs)
  File "/hassio_oauth.py", line 46, in token
    self.oauth2.fetch_token(self.user_data['token_uri'], client_secret=self.user_data['client_secret'], code=token)
  File "/usr/local/lib/python3.5/dist-packages/requests_oauthlib/oauth2_session.py", line 221, in fetch_token
    verify=verify, proxies=proxies)
  File "/usr/local/lib/python3.5/dist-packages/requests/sessions.py", line 555, in post
    return self.request('POST', url, data=data, json=json, **kwargs)
  File "/usr/local/lib/python3.5/dist-packages/requests_oauthlib/oauth2_session.py", line 360, in request
    headers=headers, data=data, **kwargs)
  File "/usr/local/lib/python3.5/dist-packages/requests/sessions.py", line 508, in request
    resp = self.send(prep, **send_kwargs)
  File "/usr/local/lib/python3.5/dist-packages/requests/sessions.py", line 618, in send
    r = adapter.send(request, **kwargs)
  File "/usr/local/lib/python3.5/dist-packages/requests/adapters.py", line 508, in send
    raise ConnectionError(e, request=request)
requests.exceptions.ConnectionError: HTTPSConnectionPool(host='accounts.google.com', port=443): Max retries exceeded with url: /o/oauth2/token (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7f2a987c8d30>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution',))
192.168.1.198 - - [17/Jun/2018:14:18:13] "GET /token?token=<token> HTTP/1.1" 500 5187 "http://192.168.1.129:9324/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_5) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/11.1.1 Safari/605.1.15"
[17/Jun/2018:14:23:26] HTTP 
Request Headers:
  UPGRADE-INSECURE-REQUESTS: 1
  ACCEPT: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
  CONNECTION: keep-alive
  REFERER: http://192.168.1.129:9324/
  HOST: 192.168.1.129:9324
  DNT: 1
  ACCEPT-LANGUAGE: pt-br
  USER-AGENT: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_5) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/11.1.1 Safari/605.1.15
  Remote-Addr: 192.168.1.198
  ACCEPT-ENCODING: gzip, deflate
[17/Jun/2018:14:23:26] HTTP 
Traceback (most recent call last):
  File "/usr/local/lib/python3.5/dist-packages/urllib3/connection.py", line 141, in _new_conn
    (self.host, self.port), self.timeout, **extra_kw)
  File "/usr/local/lib/python3.5/dist-packages/urllib3/util/connection.py", line 60, in create_connection
    for res in socket.getaddrinfo(host, port, family, socket.SOCK_STREAM):
  File "/usr/lib/python3.5/socket.py", line 733, in getaddrinfo
    for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
socket.gaierror: [Errno -3] Temporary failure in name resolution

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.5/dist-packages/urllib3/connectionpool.py", line 601, in urlopen
    chunked=chunked)
  File "/usr/local/lib/python3.5/dist-packages/urllib3/connectionpool.py", line 346, in _make_request
    self._validate_conn(conn)
  File "/usr/local/lib/python3.5/dist-packages/urllib3/connectionpool.py", line 850, in _validate_conn
    conn.connect()
  File "/usr/local/lib/python3.5/dist-packages/urllib3/connection.py", line 284, in connect
    conn = self._new_conn()
  File "/usr/local/lib/python3.5/dist-packages/urllib3/connection.py", line 150, in _new_conn
    self, "Failed to establish a new connection: %s" % e)
urllib3.exceptions.NewConnectionError: <urllib3.connection.VerifiedHTTPSConnection object at 0x7f2a98bcb160>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.5/dist-packages/requests/adapters.py", line 440, in send
    timeout=timeout
  File "/usr/local/lib/python3.5/dist-packages/urllib3/connectionpool.py", line 639, in urlopen
    _stacktrace=sys.exc_info()[2])
  File "/usr/local/lib/python3.5/dist-packages/urllib3/util/retry.py", line 388, in increment
    raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='accounts.google.com', port=443): Max retries exceeded with url: /o/oauth2/token (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7f2a98bcb160>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution',))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.5/dist-packages/cherrypy/_cprequest.py", line 631, in respond
    self._do_respond(path_info)
  File "/usr/local/lib/python3.5/dist-packages/cherrypy/_cprequest.py", line 690, in _do_respond
    response.body = self.handler()
  File "/usr/local/lib/python3.5/dist-packages/cherrypy/lib/encoding.py", line 221, in __call__
    self.body = self.oldhandler(*args, **kwargs)
  File "/usr/local/lib/python3.5/dist-packages/cherrypy/_cpdispatch.py", line 60, in __call__
    return self.callable(*self.args, **self.kwargs)
  File "/hassio_oauth.py", line 46, in token
    self.oauth2.fetch_token(self.user_data['token_uri'], client_secret=self.user_data['client_secret'], code=token)
  File "/usr/local/lib/python3.5/dist-packages/requests_oauthlib/oauth2_session.py", line 221, in fetch_token
    verify=verify, proxies=proxies)
  File "/usr/local/lib/python3.5/dist-packages/requests/sessions.py", line 555, in post
    return self.request('POST', url, data=data, json=json, **kwargs)
  File "/usr/local/lib/python3.5/dist-packages/requests_oauthlib/oauth2_session.py", line 360, in request
    headers=headers, data=data, **kwargs)
  File "/usr/local/lib/python3.5/dist-packages/requests/sessions.py", line 508, in request
    resp = self.send(prep, **send_kwargs)
  File "/usr/local/lib/python3.5/dist-packages/requests/sessions.py", line 618, in send
    r = adapter.send(request, **kwargs)
  File "/usr/local/lib/python3.5/dist-packages/requests/adapters.py", line 508, in send
    raise ConnectionError(e, request=request)
requests.exceptions.ConnectionError: HTTPSConnectionPool(host='accounts.google.com', port=443): Max retries exceeded with url: /o/oauth2/token (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7f2a98bcb160>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution',))
192.168.1.198 - - [17/Jun/2018:14:23:26] "GET /token?token=<token> HTTP/1.1" 500 5187 "http://192.168.1.129:9324/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_5) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/11.1.1 Safari/605.1.15"

It appears that the Let's Encrypt addon cannot verify when the port is anything other than 80. This isn't practical since port 80 is often used by other services. The configured port needs to be added to the url. Is there a way to provide this value as part of the environment so it can be added in the run.sh script?

I want to git-push my config from hassio to external repo. Therefor I would like to able to configure public and private key for user root.

I would like to propose a security policy for official add-ons:

All add-ons that can be user protected should:

• Be protected with a default subnet mask limiting connections to local networks
• If they can write config, should not have a guest mode at all and should not start without a username/password defined.

What do you think?

Hassio Addons should use domain in ssl path

Currently

/ssl/fullchain.pem
/ssl/privkey.pem

Recommended

/ssl/mydomain.duckdns.org/fullchain.pem
/ssl/mydomain.duckdns.org/privkey.pem

The reason for the above is to allow multiple vhosts on the same Hassio. If you run grafana, home assistant a configurator and some other http server you can't generate properly multiple vhosts using nginx.

An example is bestlibre nginx that works with certbot based on aliases, but that can't be made to work properly with official addons.

https://github.com/home-assistant/hassio-addons/blob/d2d1d8aa010d9a28a0e9adda7bcde5b3e07c0914/google_assistant/hassio_gassistant.py#L30

hey....
could somebody help me
I'm trying to get the Google assistant working
but it asks for a device_model_id
Info] Install/Update service client_secrets file
Traceback (most recent call last):
File "/hassio_gassistant.py", line 30, in
with Assistant(credentials) as assistant:
TypeError: init() missing 1 required positional argument: 'device_model_id'
i figured that it is the model id that i get when registering a device (seems logical)(edited)
https://developers.google.com/assistant/sdk/guides/service/python/embed/run-sample
here in the docs
it passes a extra argument to it
--device-model-id my-model--device-model-id(edited)
i think

run assistant
    with Assistant(credentials) as assistant:
        for event in assistant.start():
            process_event(event)

Here there should be a extra parameter to start the Assistant

run assistant
    with Assistant(credentials, deviceID) as assistant:
        for event in assistant.start():
            process_event(event) 

something like this
could somebody help me do that.... i'm not that experienced with Python... and i don't have much time to learn it

This is from discord

Home Assistant release (hass --version):
0.65.5

Python release (python3 --version):
The one supplied with Hassio.

Component/platform:
DuckDNS version 1.2

Description of problem:
DuckDNS Addon fails to recognize that cert for my domain is expiring in less than 30 days, hence it is not refreshing it.

This is log from DuckDNS on restart:
starting version 3.2.4

INFO: Using main config file /data/workdir/config
Account already registered!
Sun Mar 25 21:33:35 CEST 2018: OK
NOCHANGE # INFO: Using main config file /data/workdir/config Unknown hook this_hookscript_is_broken__dehydrated_is_working_fine__please_ignore_unknown_hooks_in_your_script Processing <domain>.duckdns.org Unknown hook this_hookscript_is_broken__dehydrated_is_working_fine__please_ignore_unknown_hooks_in_your_script + Checking domain name(s) of existing cert... unchanged. + Checking expire date of existing cert... + Valid till Jun 22 17:50:27 2018 GMT (Longer than 30 days). Skipping renew! 

Config of DuckDNS:

{
"lets_encrypt": {
"accept_terms": true,
"certfile": "fullchain.pem",
"keyfile": "privkey.pem"
},
"token": ,
"domains": [
  <domain>.duckdns.org"
],
"seconds": 60
}

The SSL sensor correctly reports 29 days till expiry:

sensor.ssl_certificate_expiry | 29 | unit_of_measurement: days friendly_name: Dostęp SSL icon: mdi:certificate
-- | -- | --

Chrome (correctly) says that the cert for the UI (opened on the domain specified in the duckdns page) is valid till 2018-04-23.

Expected:
DuckDNS should referesh the cert since there are less than 30 days till expiry.

Hello, I am not sure if I have the right thread for this, but I figure that I have to start somewhere so here goes. I have been trying to setup the DUck DNS addon for a couple of weeks now and have the remote access working fine except it is not https. When I check the logs for the DuckDNS platform, I see this message
ERROR: Problem connecting to server (get for https://acme-v02.api.letsencrypt.org/directory; curl returned with 6)
I have tried uninstalling and reinstalling the addon several times now to no avail. Any help would be much appreciated.

@pvizeli, thanks a bunch for working on this, having the assistant embedded on my CN62 would be ideal!
I've tried to get it to work over the past few days, and have probably hit every issue you've been fixing :)
Is the documentation being updated along with the code changes? Given all the issues I've had, my distinct feeling is that this isn't yet stable; should this perhaps be in the beta channel of hassio instead?

@robmarkcole commented on Feb 2, 2018, 7:25 AM UTC:

I'm experiencing that the config file I can edit with the Configurator is different from that I can edit via the Samba share. The file shown by Configurator is up to date whilst that shown by Samba is the default. Hassio 0.61

This issue was moved by @pvizeli from home-assistant/supervisor/issues/344.