Merge branch 'current' into next

_config.yml

@@ -100,9 +100,9 @@ social:
 
 # Home Assistant release details
 current_major_version: 0
-current_minor_version: 100
+current_minor_version: 101
-current_patch_version: 3
+current_patch_version: 0
-date_released: 2019-10-21
+date_released: 2019-10-30
 
 # Either # or the anchor link to latest release notes in the blog post.
 # Must be prefixed with a # and have double quotes around it.

source/_docs/installation.markdown

@@ -45,6 +45,12 @@ NUC i7/i9 | Pure power, you should not have *any* performance issues
 
 These install options are fully supported by Home Assistant's documentation. For example, if a integration requires that you install something to make it work on one of these methods then the integration page will document the steps required.
 
+<div class='note'>
+
+The only installation methods that allow you to use Hass.io Add-ons are the Hass.io image and manual installer. All other methods only install the base Home Assistant packages, however the software from the add-ons may still usually be installed manually like any other program.
+
+</div>
+
 **Method**|**You have**|**Recommended for**
 :-----|:-----|:-----
 [Hass.io](/hassio/installation/)|Raspberry Pi<br>VM|Anybody

source/_docs/installation/freenas.markdown

@@ -173,6 +173,77 @@ USB Z-wave sticks may give `dmesg` warnings similar to "data interface 1, has no
 
 </div>
 
+# Adding support for Z-wave stick
+
+The following two packages need to be installed in the jail
+
+```bash
+pkg install gmake
+pkg install libudev-devd
+```
+
+Then you can install the zwave package
+```bash
+pip3 install homeassistant-pyozw==0.1.4
+```
+
+Stop the hass Jail
+```bash
+sudo iocage stop hass
+```
+
+Edit the devfs rules on the Freenas Host
+```bash
+vi /etc/devfs.rules
+```
+
+Add the following lines 
+```bash
+[devfsrules_jail_allow_usb=7]  
+add path 'cu\*' mode 0660 group 8123 unhide 
+```
+
+Reload devfs
+```bash
+sudo service devfs restart
+```
+
+Edit the ruleset used by the jail in the Freenas GUI by going to Jails -> hass -> Edit ->  Jail Properties ->  devfs_ruleset
+Set it to 7
+
+Start the hass jail
+```bash
+sudo iocage start hass
+```
+
+Connect to the hass jail and verify that you see the modem devices
+```bash
+sudo iocage console hass
+```
+
+```bash
+ls /dev/cu*
+```
+This should ouput the following 
+```bash
+/dev/cuau0      /dev/cuaU0
+```
+
+Add the zwave config to your `configuration.yaml` and restart HA
+```bash
+vi /home/homeassistant/.homeassistant/configuration.yaml
+```
+```yaml
+zwave:
+  usb_path: /dev/cuaU0
+  polling_interval: 10000
+```
+
+```bash
+service homeassistant restart
+```
+
+
 # Updating
 Before updating, read the changelog to see what has changed and how it affects your Home Assistant instance. Enter the jail using `iocage exec <jailname>`. Stop the Home Assistant service:
 

source/_docs/security.markdown

@@ -27,7 +27,7 @@ Home Assistant is following the [Mozilla's Operations Security team recommendati
 
 The SSH connection for [debugging](https://developers.home-assistant.io/docs/en/hassio_debugging.html) on port 22222 is not enabled by default and can only be used with keys.
 
-Is SSH used with the [SSH server add-on](/addons/ssh/) then the user is responsible for the configuration and security. 
+If SSH is used with the [SSH server add-on](/addons/ssh/) then the user is responsible for the configuration and security. 
 
 ## Source code
 

source/_faq/release.markdown

@@ -7,7 +7,6 @@ ha_category: Common
 The current release cycle is three weeks. This allows for two weeks of development time and 1 week of beta testing and fixing. Releases usually occur on a Wednesday. There is no fixed time of day when the release will happen because that depends on the person who is finishing the release, it could therefore be Tuesday or Thursday depending on your timezone when its available for you. If there was no announcement made in the previous release notes or on another communication channel then the release will happen.
 
 Beta's are normally released on the 2nd Wednesday after the last major release. Please subscribe to the Beta Channel on the [Home Assistant Discord server](https://discord.gg/RMC8WkX) for help running beta versions.
-When a beta release is in progress the the release notes for it can be found here [Beta Release Notes](https://rc.home-assistant.io/latest-release-notes/).
+When a beta release is in progress, the release notes for it can be found under [Beta Release Notes](https://rc.home-assistant.io/latest-release-notes/).
 
 The release schedule is published in the upcoming events calender on the [Home Assistant Developers](https://developers.home-assistant.io/) website.
-  

source/_includes/asides/component_navigation.html

@@ -9,7 +9,7 @@
   </div>
 
   {%- assign file_parts = page.url | split: '/' | last | split: '.' -%}
-  {%- assign imp_name = file_parts | first -%}
+  {%- assign imp_name = file_parts | last -%}
   {%- assign imp_url = imp_name | prepend: '/components/' | append: '/' -%}
 
   <div class="section">

source/_integrations/bmw_connected_drive.markdown

@@ -16,7 +16,7 @@ The `bmw_connected_drive` integration lets you retrieve data of your BMW vehicle
 
 The `bmw_connected_drive` integration also works with (recent) Mini vehicles. You need to have a working Mini Connected account, and a Mini Connected enabled vehicle for this to work.
 
-For compatibility with your BMW vehicle check the [bimmer_connected page](https://github.com/m1n3rva/bimmer_connected) on github.
+For compatibility with your BMW vehicle check the [bimmer_connected page](https://github.com/bimmerconnected/bimmer_connected) on GitHub.
 
 This integration provides the following platforms:
 

source/_integrations/broadlink.markdown

@@ -36,7 +36,7 @@ host:
   required: true
   type: string
 mac:
-  description: Device mac address.
+  description: "Device MAC address. Use the following format: `AA:BB:CC:DD:EE:FF`."
   required: true
   type: string
 name:
@@ -139,7 +139,7 @@ host:
   required: true
   type: string
 mac:
-  description: Device MAC address.
+  description: "Device MAC address. Use the following format: `AA:BB:CC:DD:EE:FF`."
   required: true
   type: string
 timeout:

source/_integrations/calendar.google.markdown

@@ -178,7 +178,7 @@ You can use the service `google.add_event` to create a new calendar event in a c
 
 | Service data attribute | Optional | Description | Example |
 | ---------------------- | -------- | ----------- | --------|
-| `calendar_id` | no | The id of the calendar you want. |	Your email
+| `calendar_id` | no | The id of the calendar you want. | *****@group.calendar.google.com
 | `summary` | no | Acts as the title of the event. | Bowling
 | `description` | yes | The description of the event. | Birthday bowling
 | `start_date_time` | yes | The date and time the event should start. | 2019-03-10 20:00:00

source/_integrations/cloudflare.markdown

@@ -7,7 +7,7 @@ ha_category:
 ha_release: 0.74
 ---
 
-With the `cloudflare` integration can you keep your Cloudflare records up to date.
+With the `cloudflare` integration you can keep your Cloudflare records up to date.
 
 The integration will run every hour, but can also be started manually by using the service `cloudflare.update_records` under services.
 

source/_integrations/doods.markdown

@@ -176,7 +176,7 @@ image_processing:
       - truck
 ```
 
-## Optimising resources
+## Optimizing resources
 
 [Image processing components](/components/image_processing/) process the image from a camera at a fixed period given by the `scan_interval`. This leads to excessive processing if the image on the camera hasn't changed, as the default `scan_interval` is 10 seconds. You can override this by adding to your config `scan_interval: 10000` (setting the interval to 10,000 seconds), and then call the `image_processing.scan` service when you actually want to perform processing.
 

source/_integrations/fritz.markdown

@@ -13,7 +13,7 @@ The `fritz` platform offers presence detection by looking at connected devices t
 ## Setup
 
 <div class='note warning'>
-If not running Hass.io it might be necessary to install additional packages: <code>sudo apt-get install python3-lxml libxslt-dev libxml2-dev zlib1g-dev</code>
+If not running Home Assistant via Hass.io or Docker it might be necessary to install additional packages: <code>sudo apt-get install python3-lxml libxslt-dev libxml2-dev zlib1g-dev</code>
 If you installed Home Assistant in a virtualenv, run the following commands inside it: <code>pip3 install lxml</code>; be patient this will take a while.</div>
 
 ## Configuration

source/_integrations/fritzbox_netmonitor.markdown

@@ -11,7 +11,7 @@ ha_iot_class: Local Polling
 The `fritzbox_netmonitor` sensor monitors the network statistics exposed by [AVM Fritz!Box](https://avm.de/produkte/fritzbox/) routers.
 
 <div class='note warning'>
-It might be necessary to install additional packages: <code>sudo apt-get install libxslt-dev libxml2-dev python3-lxml</code>
+If not running Home Assistant via Hass.io or Docker it might be necessary to install additional packages: <code>sudo apt-get install libxslt-dev libxml2-dev python3-lxml</code>
 If you are working with the All-in-One installation, you may also need to execute also within your virtual environment the command <code>pip3 install lxml</code>; be patient this will take a while.
 </div>
 

source/_integrations/here_travel_time.markdown

@@ -15,7 +15,7 @@ The `here_travel_time` sensor provides travel time from the [HERE Routing API](h
 
 You need to register for an API key (REST & XYZ HUB API/CLI) by following the instructions [here](https://developer.here.com/documentation/routing/topics/introduction.html?create=Freemium-Basic&keepState=true&step=account).
 
-HERE offers a Freemium Plan which includes 250.000 free Transactions per month. For the Routing API, one transaction equals one request with one starting point (no multi stop). More information can be found [here](https://developer.here.com/faqs#payment-subscription)
+HERE offers a Freemium Plan which includes 250,000 free Transactions per month. For the Routing API, one transaction equals one request with one starting point (no multi stop). More information can be found [here](https://developer.here.com/faqs#payment-subscription)
 
 By default HERE will deactivate your account if you exceed the free Transaction limit for the month. You can add payment details to reenable your account as described [here](https://developer.here.com/faqs)
 

source/_integrations/http.markdown

@@ -218,7 +218,7 @@ In this section you'll find some real-life examples of how to use this sensor, b
 
 #### Using Python request module
 
-As already shown on the [API](/developers/rest_api/) page, it's very simple to use Python and the [Requests](https://requests.kennethreitz.org//en/latest/) module for the interaction with Home Assistant.
+As already shown on the [API](/developers/rest_api/) page, it's very simple to use Python and the [Requests](https://requests.kennethreitz.org/en/latest/) module for the interaction with Home Assistant.
 
 ```python
 response = requests.post(

source/_integrations/input_datetime.markdown

@@ -107,7 +107,7 @@ automation (note that you will need a
 automation:
   trigger:
     platform: template
-    value_template: "{{ states('sensor.time') == (state_attr('input_datetime.bedroom_alarm_clock_time', 'timestamp') | int | timestamp_custom('%H:%M', False)) }}"
+    value_template: "{{ states('sensor.time') == (state_attr('input_datetime.bedroom_alarm_clock_time', 'timestamp') | int | timestamp_custom('%H:%M', True)) }}"
   action:
     service: light.turn_on
     entity_id: light.bedroom

source/_integrations/logger.markdown

@@ -53,8 +53,16 @@ logger:
 
     # log level for the `aiohttp` Python package
     aiohttp: error
+
+    # log level for both 'glances_api' and 'glances' integration
+    homeassistant.components.glances: fatal
+    glances_api: fatal
 ```
 
+The log entries are in the form  
+*timestamp* *log-level* *thread* [**namespace**] *message*  
+where **namespace** is the *<component_namespace>* currently logging. 
+
 {% configuration %}
   default:
     description: Default log level. See [log_level](#log-levels).
@@ -71,6 +79,9 @@ logger:
         type: string
 {% endconfiguration %}
 
+In the example, do note the difference between 'glances_api' and 'homeassistant.components.glances' namespaces, 
+both of which are at root. They are logged by different APIs.
+
 ### Log Levels
 
 Possible log severity levels, listed in order from most severe to least severe, are:

source/_integrations/moon.markdown

@@ -9,7 +9,7 @@ ha_release: 0.38
 ha_qa_scale: internal
 ---
 
-The `moon` integration is tracking the moon phases.
+The `moon` integration tracks the phases of the moon.
 
 ## Configuration
 

source/_integrations/panasonic_viera.markdown

@@ -14,6 +14,7 @@ Currently known supported models:
 
 - TC-P65VT30
 - TX-32AS520E
+- TX-32DSX609
 - TX-49DX650B
 - TX-50DX700B
 - TX-55CX700E
@@ -32,6 +33,8 @@ If your model is not on the list then give it a test, if everything works correc
 
 Some Panasonic Viera TVs allow Home Assistant to turn them on, if you specify the MAC address with `mac:`.
 
+Note that your TV has to reside in the same network as your home assistant instance for this platform to work.
+
 To add a TV to your installation, add the following to your `configuration.yaml` file:
 
 ```yaml

source/_integrations/pocketcasts.markdown

@@ -1,6 +1,6 @@
 ---
-title: PocketCasts
+title: Pocket Casts
-description: "Instructions on how to set up PocketCasts sensors within Home Assistant."
+description: "Instructions on how to set up Pocket Casts sensors within Home Assistant."
 logo: pocketcasts.png
 ha_category:
   - Multimedia
@@ -8,10 +8,16 @@ ha_release: 0.39
 ha_iot_class: Cloud Polling
 ---
 
-The `pocketcasts` sensor platform lets one monitor the podcasts at [Pocket Casts](https://play.pocketcasts.com/).
+The `pocketcasts` sensor platform lets you monitor how many unplayed episodes you have of your favorite podcasts at [Pocket Casts](https://play.pocketcasts.com/).
 
 ## Configuration
 
+<div class='note warning'>
+  
+  This integration requires a [Pocket Casts + Plus](https://www.pocketcasts.com/plus/) subscription to work!
+  
+</div>
+
 To enable this sensor, add the following lines to your `configuration.yaml`:
 
 ```yaml

source/_integrations/pushetta.markdown

@@ -53,6 +53,6 @@ curl -X POST \
   http://api.pushetta.com/api/pushes/home-assistant/
 ```
 
-For further details, please check the [API](http://pushetta.com/pushetta-api/).
+For further details, please check the [API](http://www.pushetta.com/pushetta-api/).
 
 To use notifications, please see the [getting started with automation page](/getting-started/automation/).

source/_integrations/recorder.markdown

@@ -200,7 +200,7 @@ homeassistant@homeassistant:~$ source /srv/homeassistant/bin/activate
 (homeassistant) homeassistant@homeassistant:~$ pip3 install mysqlclient
 ```
 
-For MariaDB you may have to install a few dependencies. If you're using MariaDB version 10.2, `libmariadbclient-dev` was renamed to `libmariadb-dev`. If you're using MariaDB 10.3, the package `libmariadb-dev-compat` must also be installed. Please install the correct packages based on your MariaDB version.
+For MariaDB you may have to install a few dependencies. If you're using MariaDB version 10.2, `libmariadbclient-dev` was renamed to `libmariadb-dev`. If you're using MariaDB 10.3, the package `libmariadb-dev-compat` must also be installed. For MariaDB v10.0.34 only `libmariadb-dev-compat` is needed. Please install the correct packages based on your MariaDB version.
 
 On the Python side we use the `mysqlclient`:
 

source/_integrations/rejseplanen.markdown

@@ -72,8 +72,11 @@ departure_type:
 
 ## Direction
 
-If you use the `direction` filter it's important to put correct destination or else the sensor will not work at all.
+If you use the `direction` filter it's important to put correct final destination(s) or else the sensor will not work at all.
-The direction has to be the destination(s) for the transport type(s) for the departure stop destination, and NOT the stop where you want to get off. Check [https://rejseplanen.dk/](https://rejseplanen.dk/), make a search and use the destinations from there in your configuration. Make sure you use the exact name as the destination(s).
+The `direction` has to be the final destination(s) for the `Departure type` - ***NOT the stop where you want to get off***. 
+
+- Check [https://rejseplanen.dk/](https://rejseplanen.dk/)
+- Make a search and use **all variations** for the final destination(s) for the needed `Departure type` in your configuration under `direction`. Make sure you use the exact name for final destination(s).
 
 A working example on how to use this sensor with direction:
 
@@ -98,7 +101,7 @@ sensor:
       - 'København H'
 ```
 
-It fails because the destination from the departure is NOT København H, but 'CPH Lufthavn', 'Helsingør St.' and others.
+It fails because the final destination for the train from the departure station is NOT 'københavn H', but 'CPH Lufthavn' and 'Helsingør St.'.
 
 ## Examples
 

source/_integrations/smartthings.markdown

@@ -108,8 +108,8 @@ The integration will trigger an event when a device with the [button](https://sm
 | Attribute                 | Description
 |---------------------------|------------------------------------------------------------------|
 `component_id`              | Describes which integration of the device triggered the event. `main` represents the parent device. For devices with child-devices, this attribute identifies the child that raised the event.
-`device_id`                 | The unique id of the device in SmartThings. This can be located in the HASS device registry or in the [SmartThings Groovy IDE](https://developers.smartthings.com/).
+`device_id`                 | The unique id of the device in SmartThings. This can be located in the HASS device registry or in the [SmartThings Developer Workspace](https://smartthings.developer.samsung.com/workspace/).
-`location_id`               | The unique id of the location the device is part of. This can be found in the config entry registry or in the [SmartThings Groovy IDE](https://developers.smartthings.com/).
+`location_id`               | The unique id of the location the device is part of. This can be found in the config entry registry or in the [SmartThings Developer Workspace](https://smartthings.developer.samsung.com/workspace/).
 `value`                     | Describes the action taken on the button. See the [button](https://smartthings.developer.samsung.com/develop/api-ref/capabilities.html#Button) capability reference for a list of possible values (not all are supported by every device).
 `name`                      | The name given to the device in SmartThings.
 

source/_integrations/vacuum.mqtt.markdown

@@ -8,9 +8,9 @@ ha_release: 0.54
 ---
 
 The `mqtt` vacuum integration allows you to control your MQTT-enabled vacuum.
-There are 2 possible message schemas - `legacy` and `state`.
+There are two possible message schemas - `legacy` and `state`.
-New installation should use `state` schema as `legacy` is deprecated and might be removed someday in the future.
+New installations should use the `state` schema as `legacy` is deprecated and might be removed someday in the future.
-`state` schema is preferred because the vacuum will then be represented as a `StateVacuumDevice` which is preferred parent vacuum entity.
+The `state` schema is preferred because the vacuum will then be represented as a `StateVacuumDevice` which is the preferred parent vacuum entity.
 
 This documentation has 3 sections. Config for `legacy` vacuum with examples, config for `state` vacuum with examples and shared section with examples which are the same for both schemas.
 
@@ -523,7 +523,7 @@ MQTT topic: `vacuum/send_command`
 
 This integration is supported by the cloud-free Xiaomi Vacuum Webinterface [Valetudo](https://github.com/Hypfer/Valetudo).
 
-### Retrofitting a non-wifi vacuums
+### Retrofitting non-wifi vacuums
 
 - Retrofitting your old Roomba with an ESP8266. [This repo](https://github.com/johnboiles/esp-roomba-mqtt) provides MQTT client firmware.
-- In you own a non-wifi Neato, you can refer to [this repo](https://github.com/jeroenterheerdt/neato-serial) that uses a Raspberry Pi to retrofit an old Neato.
+- If you own a non-wifi Neato, you can refer to [this repo](https://github.com/jeroenterheerdt/neato-serial) that uses a Raspberry Pi to retrofit an old Neato.

source/_integrations/weather.darksky.markdown

@@ -54,7 +54,7 @@ name:
   description: Name to use in the frontend.
   required: false
   type: string
-  default: Open Sky
+  default: Dark Sky
 mode:
   description: "The forecast type. Can be `hourly` or `daily`."
   required: false

source/_integrations/wink.markdown

@@ -52,7 +52,9 @@ Wink requests three pieces of information from the user when they sign up for a
 2. `Website:` The external address of your Home Assistant instance. If not externally accessible you can use your email address.
 3. `Redirect URI:` This should be `http://192.168.1.5:8123/auth/wink/callback` replacing the IP with the internal IP of your Home Assistant box.
 
-No settings are required in the `configuration.yaml` other than `wink:` this is because you will be guided through setup via the configurator on the frontend.
+No settings are required in the `configuration.yaml` other than `wink:`. 
+
+After adding `wink:` to your `configuration.yaml` and restarting Home Assistant you will see a persistent notification on the frontend with a `CONFIGURE` button that will guide you through the setup via the frontend configurator.
 
 <div class='note'>
 When using the configurator make sure the initial setup is performed on the same local network as the Home Assistant server, if not from the same box Home Assistant is running on. This will allow for authentication redirects to happen correctly.

source/_posts/2019-10-25-rip-hassbian.markdown

@@ -0,0 +1,44 @@
+---
+layout: post
+title: "R.I.P Hassbian"
+description: "The end of Hassbian"
+date: 2019-10-26 06:00:00
+date_formatted: "October 26, 2019"
+author: Fredrik Lindqvist
+author_twitter: Landrash
+comments: true
+categories: community
+---
+
+It's time for what was once the simplest way to install Home Assistant to retire.
+
+## R.I.P Hassbian
+
+Some of you will probably wonder why Hassbian is being retired and I'll try to give a proper motivation. 
+First of is the age-old factor of **time**. I as the lead developer of Hassbian haven't been able to give it the time and attention it requires, and there have been few others that have pushed the project further. The one exception being [@ludeeus] who's done most of the heavy lifting when the image was retooled to use a proper apt package and repository.
+Second is that it's no longer the best option for most to use as an installation method. Hass.io has surpassed Hassbian in almost all ways I can imagine.
+
+## Next Step for Hassbian
+Since Hassbian has been around for quite a while, there are quite a few users that don't want Hassbian to go away. To make this as easy as possible for those users, here's the plan.
+
+ - The repositories [pi-gen] and [hassbian-scripts] hosting the Hassbian projects files will be moved to a new organization. 
+ - A last release will be done by me mid Q4 2019. This image will be hosted under the [pi-gen] repository. 
+ - The [pi-gen] repository will be reworked to work with a standard [raspbian] image with minor modifications for anyone wanting to create their own "Hassbian like" image. This has always been possible, but the current repository is a bit out of date with the current layout of the Raspbian image. 
+ - The [hassbian-scripts] package will get a final release and will continue to be hosted on Gitlab. Some minor changes will be made to reflect the changes to the project.
+
+## Next step for Hassbian users
+The Hassbian image has always aimed to be the same as a manual Raspbian Lite installation with some packages added.
+There won't really be any big changes for all of the users of Hassbian and for documentation, please refer to the [Manual installation on a Raspberry PI] method.
+
+## Alternatives
+If you want to continue using something similar, have a look at the [manual installation on a Raspberry Pi] since it is the base Hassbian was created from.
+For everyone else, I would wholeheartedly recommend Hass.io since it is what I personally use now (It's what I had hoped Hassbian could have been but better).
+
+## Last but not least
+Last but not least, thank you to all of those who contributed, in any way, to the Hassbian project and image.
+
+[@ludeeus]: https://github.com/ludeeus
+[pi-gen]: https://github.com/Hassbian/pi-gen
+[hassbian-scripts]: https://github.com/Hassbian/hassbian-scripts
+[Manual installation on a Raspberry Pi]: /docs/installation/raspberry-pi/
+[raspbian]: https://www.raspberrypi.org/downloads/raspbian/

source/hassio/index.markdown

@@ -25,7 +25,7 @@ The advantages of using Hass.io:
 
 ### Upgrading
 
-Hass.io users can update Home Assistant via the 'Hass.io' page in the UI. However, please note that a Home Assistant updates take time to roll into the Hass.io builds. Therefore, there is often a slight delay between the availability of a Home Assistant update and the update being available in Hass.io, so be patient. When a Hass.io update is available, it will be shown as a notification in the ‘Hass.io' page in the web interface.
+Hass.io users can update Home Assistant via the 'Hass.io' panel in the UI. However, please note that Home Assistant updates take some time to roll into the Hass.io builds. Therefore, there is often a slight delay (a day or two) between the availability of a Home Assistant update and the update being available in Hass.io, so be patient. When a Hass.io update is available, it will be shown as a notification in the ‘Hass.io' panel in the web interface.
 
 <p class='img'>
 <img src='/images/hassio/screenshots/dashboard.png'>

source/hassio/installation.markdown

@@ -147,10 +147,17 @@ You also need to have Docker-CE installed. There are well-documented procedures
 
 To prepare your machine for the Hass.io installation, run the following commands:
 
+For Ubuntu:
+
+```bash
+add-apt-repository universe
+```
+
+Debian/Ubuntu:
+
 ```bash
 sudo -i
 apt-get install software-properties-common
-add-apt-repository universe
 apt-get update
 apt-get install -y apparmor-utils apt-transport-https avahi-daemon ca-certificates curl dbus jq network-manager socat
 curl -fsSL get.docker.com | sh