From 6cee626337be487d9cad991147079ca7d73e61fa Mon Sep 17 00:00:00 2001 From: SukramJ Date: Mon, 13 Jan 2020 12:29:23 +0100 Subject: [PATCH 1/8] Add handling of missing devices to HomematicIP Cloud (#11725) * Add handling of missing devices to HomematicIP Cloud * fixes * Update source/_integrations/homematicip_cloud.markdown Co-Authored-By: Franck Nijhof * Update source/_integrations/homematicip_cloud.markdown Co-Authored-By: Franck Nijhof * Update source/_integrations/homematicip_cloud.markdown Co-Authored-By: Franck Nijhof * Update source/_integrations/homematicip_cloud.markdown Co-Authored-By: Franck Nijhof * Update source/_integrations/homematicip_cloud.markdown Co-Authored-By: Franck Nijhof * Update source/_integrations/homematicip_cloud.markdown Co-Authored-By: Franck Nijhof * Update source/_integrations/homematicip_cloud.markdown Co-Authored-By: Franck Nijhof * Update source/_integrations/homematicip_cloud.markdown Co-Authored-By: Franck Nijhof Co-authored-by: Franck Nijhof --- source/_integrations/homematicip_cloud.markdown | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/source/_integrations/homematicip_cloud.markdown b/source/_integrations/homematicip_cloud.markdown index d8fc91df9c3..088f7e35ccf 100644 --- a/source/_integrations/homematicip_cloud.markdown +++ b/source/_integrations/homematicip_cloud.markdown @@ -162,6 +162,18 @@ Within this delay the device registration should be completed in the App, otherw * Weather Sensor – plus (*HmIP-SWO-PL*) * Weather Sensor – pro (*HmIP-SWO-PR*) +## What to do, if a device is missing in Home Assistant + +In order for a device to be integrated into Home Assistant, it must first be implemented in the upstream library. A dump of your configuration is required for this, which is then attached to a new issue in the [upstream lib's](https://github.com/coreGreenberet/homematicip-rest-api) GitHub repository. + +1. Create a dump of your access point configuration in Home Assistant: + Developer Tools -> Services -> Select `homematicip_cloud.dump_hap_config` -> Execute. + The default dump is anonymized and is written to your configuration directory (`hmip_config_XXXX.json`). +2. Create a [new issue](https://github.com/coreGreenberet/homematicip-rest-api/issues/new) at this GitHub repository and attach the created dump file. + +Please be patient, wait for the implementation and a new release of the upstream library. +Afterward, this device can be implemented into Home Assistant. + ## Services - `homematicip_cloud.activate_eco_mode_with_duration`: Activate eco mode with duration. From 12f0edd8927fb37f9604ad11a8ff04ec85941e68 Mon Sep 17 00:00:00 2001 From: Dubh Ad Date: Mon, 13 Jan 2020 12:14:56 +0000 Subject: [PATCH 2/8] Removing the windows guide (#11709) * Removing the windows guide Reference to https://github.com/home-assistant/home-assistant.io/pull/11666 * Removed reference from the Python install guide Co-authored-by: Franck Nijhof --- source/_docs/installation/python.markdown | 2 +- source/_docs/installation/windows.markdown | 61 ---------------------- 2 files changed, 1 insertion(+), 62 deletions(-) delete mode 100644 source/_docs/installation/windows.markdown diff --git a/source/_docs/installation/python.markdown b/source/_docs/installation/python.markdown index ecb67056676..367cf4e6d0f 100644 --- a/source/_docs/installation/python.markdown +++ b/source/_docs/installation/python.markdown @@ -6,7 +6,7 @@ redirect_from: /getting-started/installation-python/
-If you're running a Linux-based platform, we strongly recommend you follow the instructions for a [virtual environment](/docs/installation/virtualenv/) instead. If you're running on Windows then [see here](/docs/installation/windows/#installing-in-a-python-virtual-environment) instead. +If you're running a Linux-based platform, we strongly recommend you follow the instructions for a [virtual environment](/docs/installation/virtualenv/) instead.
diff --git a/source/_docs/installation/windows.markdown b/source/_docs/installation/windows.markdown deleted file mode 100644 index 0d0095d63b7..00000000000 --- a/source/_docs/installation/windows.markdown +++ /dev/null @@ -1,61 +0,0 @@ ---- -title: "Installation on a Windows system" -description: "Instructions to install Home Assistant on a Microsoft Windows system." ---- - -To run Home Assistant on Microsoft Windows installation you need to install Python first. Download Python (the latest version of Python 3.6 is recommended) for [https://www.python.org/downloads/windows/](https://www.python.org/downloads/windows/) and follow the instructions of the installer. - -
-There may be alpha or beta releases of Python listed on that download page (marked by the letters `a` or `b` in the version number. Do not use these versions. -
- -If you use your machine for something other than Home Assistant, you should install it in a [Python virtual environment](#installing-in-a-python-virtual-environment). - -Start - -```bash -C:\...\> pip3 install homeassistant -C:\...\> py -m homeassistant --open-ui -``` - -For autostarting Home Assistant please refer to this [guide](https://community.home-assistant.io/t/autostart-on-windows/3504). - -Check this [video](https://www.youtube.com/watch?v=X27eVvuqwnY) for the installation on Windows 10. - -
-The Microsoft Windows platform is not a primary target to install Home Assistant. Also, not all tools and third-party modules will work. -
- -## Updating - -To update Home Assistant, stop it and then run: - -```bash -C:\...\> pip3 install --upgrade homeassistant -``` - -Then start Home Assistant. - -## Installing in a Python virtual environment - -Open `cmd.exe` and paste the following commands (one at the time): - -```bash -C:\...\> py -m venv homeassistant -C:\...\> cd homeassistant -C:\...\> Scripts\activate.bat -C:\...\> py -m pip install wheel setuptools pip -C:\...\> py -m pip install homeassistant -C:\...\> hass -``` - -## Upgrading in a Python virtual environment - -To update Home Assistant, stop it and then open `cmd.exe` and paste the following commands (one at the time): - -```bash -C:\...\> cd homeassistant -C:\...\> Scripts\activate.bat -C:\...\> py -m pip install --upgrade homeassistant -``` -Then start Home Assistant. From 46dfa1f959009b008b2f16fd3e84fd477e11c9ab Mon Sep 17 00:00:00 2001 From: heytcass Date: Mon, 13 Jan 2020 08:48:41 -0500 Subject: [PATCH 3/8] Clarify which name to put in devices (#11715) * Clarify which name to but in devices When setting up Automatic, I found it confusing which name to put in the `devices` section, and put the nickname in, which broke the integration. Added a note to clarify for future users. * Resolve @frenck suggestions. Yeah, I figured the tone was a bit too playful. Figured I'd give it a go though. Co-Authored-By: Franck Nijhof * Resolve @frenck suggestions. Co-Authored-By: Franck Nijhof Co-authored-by: Franck Nijhof --- source/_integrations/automatic.markdown | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/source/_integrations/automatic.markdown b/source/_integrations/automatic.markdown index 5aed9921cdf..16754fe63bd 100644 --- a/source/_integrations/automatic.markdown +++ b/source/_integrations/automatic.markdown @@ -53,6 +53,12 @@ devices: type: list {% endconfiguration %} +
+ +The device name must be the name given by Automatic automatically. This is typically the model year, make and model. This is *not* the nickname you have to give the vehicle in the `vehicles` section of the app's settings. + +
+ Home Assistant will also fire events when an update is received from Automatic. These can be used to trigger automations, as shown in the example below. A list of available event types can be found in the [Automatic Real-Time Events documentation](https://developer.automatic.com/api-reference/#real-time-events). ```yaml From a0e867766251b1a8448a329930c5bc8ceb8dcbb7 Mon Sep 17 00:00:00 2001 From: Iulian Onofrei <6d0847b9@opayq.com> Date: Mon, 13 Jan 2020 23:55:42 +0200 Subject: [PATCH 4/8] Fix typo in Google Assistant add-on page (#11734) --- source/_addons/google_assistant.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_addons/google_assistant.markdown b/source/_addons/google_assistant.markdown index 162c90fac3d..e159fcda86f 100644 --- a/source/_addons/google_assistant.markdown +++ b/source/_addons/google_assistant.markdown @@ -28,7 +28,7 @@ To enable access to the Google Assistant API, do the following: 1. Start the add-on. Check the log and click refresh till it says: "ENGINE Bus STARTED". 1. Now click "Open Web UI" and follow the authentication process. You will get an empty response after you have send your token. -That's it. You should no be able to use the Google Voice assistant. +That's it. You should now be able to use the Google Voice assistant. ### Add-on configuration From c8222b2ebf42abc50c8e989d99650ae7ea3d8e57 Mon Sep 17 00:00:00 2001 From: Rob Migchels Date: Tue, 14 Jan 2020 10:23:17 +0100 Subject: [PATCH 5/8] Update dsmr.markdown - fixed broken URL (#11736) Fixed the broken URL with official information about the P1 port. Updated it with a newer (5.0.2) version of the same document (PDF). --- source/_integrations/dsmr.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/dsmr.markdown b/source/_integrations/dsmr.markdown index a02484dad2d..a32c90faf68 100644 --- a/source/_integrations/dsmr.markdown +++ b/source/_integrations/dsmr.markdown @@ -12,7 +12,7 @@ A sensor platform for Dutch Smart Meters which comply to DSMR (Dutch Smart Meter - Currently support DSMR V2.2, V3, V4 and V5 through the [dsmr_parser](https://github.com/ndokter/dsmr_parser) module by Nigel Dokter. - For official information about DSMR refer to: [DSMR Document](https://www.netbeheernederland.nl/dossiers/slimme-meter-15) -- For official information about the P1 port refer to: +- For official information about the P1 port refer to: - For unofficial hardware connection examples refer to: [Domoticx](http://domoticx.com/p1-poort-slimme-meter-hardware/)

From 6b236cbc1258209cc5816554e6da37f0360572e5 Mon Sep 17 00:00:00 2001 From: Pascal Vizeli Date: Tue, 14 Jan 2020 12:40:07 +0100 Subject: [PATCH 6/8] Add Odroid N2 beta (#11737) --- source/hassio/installation.markdown | 2 ++ 1 file changed, 2 insertions(+) diff --git a/source/hassio/installation.markdown b/source/hassio/installation.markdown index d2dd6fc2438..019f7b7cac1 100644 --- a/source/hassio/installation.markdown +++ b/source/hassio/installation.markdown @@ -15,6 +15,7 @@ The following will take you through the steps required to install Hass.io. - [Raspberry Pi 4 Model B 64bit][pi4-64] - [Tinkerboard][tinker] - [Odroid-C2][odroid-c2] + - [Odroid-N2 (Beta)][odroid-n2] - [Odroid-XU4][odroid-xu4] - [Intel-Nuc][intel-nuc] @@ -216,6 +217,7 @@ A detailed guide about running Hass.io as a virtual machine is available in the [pi4-64]: https://github.com/home-assistant/hassos/releases/download/3.8/hassos_rpi4-64-3.8.img.gz [tinker]: https://github.com/home-assistant/hassos/releases/download/3.8/hassos_tinker-3.8.img.gz [odroid-c2]: https://github.com/home-assistant/hassos/releases/download/3.8/hassos_odroid-c2-3.8.img.gz +[odroid-n2]: https://github.com/home-assistant/hassos/releases/download/4.0/hassos_odroid-n2-4.0.img.gz [odroid-xu4]: https://github.com/home-assistant/hassos/releases/download/3.8/hassos_odroid-xu4-3.8.img.gz [intel-nuc]: https://github.com/home-assistant/hassos/releases/download/3.8/hassos_intel-nuc-3.8.img.gz [vmdk]: https://github.com/home-assistant/hassos/releases/download/3.8/hassos_ova-3.8.vmdk.gz From 359ee0730c8dc7563e0aba1db42c4b97e3109ec5 Mon Sep 17 00:00:00 2001 From: Dubh Ad Date: Tue, 14 Jan 2020 18:55:45 +0000 Subject: [PATCH 7/8] No longer loaded by default (#11741) `discovery:` isn't included in the default configuration any more... --- source/_integrations/discovery.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/discovery.markdown b/source/_integrations/discovery.markdown index e0d83cc0efb..b35c7211e54 100644 --- a/source/_integrations/discovery.markdown +++ b/source/_integrations/discovery.markdown @@ -47,7 +47,7 @@ Zeroconf discoverable integrations [Axis](/integrations/axis/)/[ESPHome](/integr -`discovery` is included in the default configuration. To load this component manually, add the following lines to your `configuration.yaml` file: +To load this integration, add the following lines to your `configuration.yaml` file: ```yaml # Example configuration.yaml entry From 2a60a44b5ec7422943bf161e958134559a03daf4 Mon Sep 17 00:00:00 2001 From: Franck Nijhof Date: Tue, 14 Jan 2020 20:47:49 +0100 Subject: [PATCH 8/8] Revert "Use self-hosted runner" This reverts commit 38afb52fbfbd776072f68b56e413816056f11ddc. --- .github/workflows/markdown.yml | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/.github/workflows/markdown.yml b/.github/workflows/markdown.yml index 3cb32f42203..1f74dac813e 100644 --- a/.github/workflows/markdown.yml +++ b/.github/workflows/markdown.yml @@ -4,8 +4,7 @@ on: [push, pull_request] jobs: remark: - #runs-on: ubuntu-latest - runs-on: self-hosted + runs-on: ubuntu-latest steps: - name: Checking out files from GitHub uses: actions/checkout@v1