The eq3btsmart climate platform allows you to integrate EQ3 Bluetooth Smart Thermostats.
The only functionality is to set the temperature, there doesn’t seem to be any way to query the temperature sensor or battery level (read more).
+The current functionality allows setting the temperature as well as controlling the supported modes with help of python-eq3bt library. +As the device doesn’t contain a temperature sensor (read more), +we report target temperature also as current one.
-Setup is a bit more cumbersome than for most other thermostats. It has to be paired first:
+Before configuring Home Assistant you should check that connectivity with the thermostat is working, which can can be done with the eq3cli tool:
-bluetoothctl
-scan on
-<Wait for the thermostat to be found, which looks like this: [NEW] Device 00:11:22:33:44:55 CC-RT-BLE>
-scan off
-<Set the thermostat to pairing mode.>
-pair <MAC>
-trust <MAC>
-disconnect <MAC>
-exit
+eq3cli --mac 00:11:22:33:44:55
+
+[00:1A:22:XX:XX:XX] Target 17.0 (mode: auto dst, away: no)
+Locked: False
+Batter low: False
+Window open: False
+Boost: False
+Current target temp: 21.0
+Current mode: auto dst
+Valve: 0
-Then check with gatttool if the connection works as expected:
-
-gatttool -b 00:11:22:33:44:55 -I
-[00:11:22:33:44:55][LE]> connect
-Attempting to connect to 00:11:22:33:44:55
-Connection successful
-[00:11:22:33:44:55][LE]> char-write-req 0x0411 03
-Characteristic value was written successfully
-Notification handle = 0x0421 value: 02 01 09 14 04 2d
-[00:11:22:33:44:55][LE]> disconnect
-[00:11:22:33:44:55][LE]> exit
-
-
-
-Important: For gatttool or homeassistant to work, the thermostat needs to be disconnected from bluetoothd, so I found it best to modify the hass-daemon startscript by adding:
-
-/usr/bin/bt-device -d CC-RT-BLE
-
-
-
-to the start function of /etc/init.d/hass-daemon.
+Configuration
# Example configuration.yaml entry
climate:
diff --git a/components/device_tracker.swisscom/index.html b/components/device_tracker.swisscom/index.html
index 844b5e3907..8588ce6b5c 100644
--- a/components/device_tracker.swisscom/index.html
+++ b/components/device_tracker.swisscom/index.html
@@ -90,7 +90,7 @@
- The swisscom platform offers presence detection by looking at connected devices to an Internet-Box router from Swisscom, which is the main Internet provider in Switzerland.
+ The swisscom platform offers presence detection by looking at connected devices to an Internet-Box router from Swisscom which is an Internet provider in Switzerland.
There are three models of Internet-Box (light, standard and plus). The platform has only been tested on the Internet-Box plus but the others should work as well because they have the same web interface.
@@ -100,11 +100,16 @@ There are three models of Internet-Box (light, standard and plus). The platform
# Example configuration.yaml entry
device_tracker:
- platform: swisscom
- host: "192.168.1.1" # only required if not 192.168.1.1
+ - platform: swisscom
+Configuration variables:
+
+
+ - host (Optional): The IP address of your router. Set it if you are not using
192.168.1.1.
+
+
See the device tracker component page for instructions how to configure the people to be tracked.
diff --git a/components/device_tracker.upc_connect/index.html b/components/device_tracker.upc_connect/index.html
index bc7c3c467d..931155ebc6 100644
--- a/components/device_tracker.upc_connect/index.html
+++ b/components/device_tracker.upc_connect/index.html
@@ -90,18 +90,24 @@
- The upc_connect platform offers presence detection by looking at connected devices to an ConnectBox router from Liberty Global, which is a Internet provider in Switzerland, Austria.
+ The upc_connect platform offers presence detection by looking at connected devices to a Connect Box from Liberty Global (also known as UPC Cablecom in Switzerland) which is a Internet provider in Switzerland and Austria.
-To use an Internet-Box router in your installation, add the following to your configuration.yaml file:
+To use a Connect Box in your installation, add the following to your configuration.yaml file:
# Example configuration.yaml entry
device_tracker:
- platform: upc_connect
- password: '123456'
- host: "192.168.0.1" # only required if not 192.168.0.1
+ - platform: upc_connect
+ password: YOUR_PASSWORD
+Configuration variables:
+
+
+ - password (Required): The password for your Connect Box.
+ - host (Optional): The IP address of your router. Set it if you are not using
192.168.0.1.
+
+
See the device tracker component page for instructions how to configure the people to be tracked.
diff --git a/components/media_player.vlc/index.html b/components/media_player.vlc/index.html
index 03576923c9..6321473a05 100644
--- a/components/media_player.vlc/index.html
+++ b/components/media_player.vlc/index.html
@@ -123,6 +123,14 @@
+ Additional configuration on macOS
+
+On macOS phython-vlc won’t find the VLC plugin directory unless you add this to the user’s .bash_profile that is running Home Assistant:
+
+export VLC_PLUGIN_PATH=$VLC_PLUGIN_PATH:/Applications/VLC.app/Contents/MacOS/plugins
+
+
+
diff --git a/developers/releasing/index.html b/developers/releasing/index.html
index 7fa6bbe1e8..a376954188 100644
--- a/developers/releasing/index.html
+++ b/developers/releasing/index.html
@@ -114,6 +114,10 @@
Merge pull request (blog post, updated frontpage, and all new documentation) to current.
+ Docker Hub
+
+Create a new tag at https://hub.docker.com for the release.
+
Python Package Index
Checkout the master branch and run script/release to publish the new release on Python Package Index.
diff --git a/sitemap.xml b/sitemap.xml
index cc2cf0dff4..f066f3dc50 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -2615,62 +2615,62 @@
https://home-assistant.io/demo/frontend.html
-2017-01-17T19:54:39+00:00
+2017-01-18T07:41:02+00:00
https://home-assistant.io/demo/index.html
-2017-01-17T19:54:39+00:00
+2017-01-18T07:41:02+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-event.html
-2017-01-17T19:54:39+00:00
+2017-01-18T07:41:02+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-info.html
-2017-01-17T19:54:39+00:00
+2017-01-18T07:41:02+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-service.html
-2017-01-17T19:54:39+00:00
+2017-01-18T07:41:02+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-state.html
-2017-01-17T19:54:39+00:00
+2017-01-18T07:41:02+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-template.html
-2017-01-17T19:54:39+00:00
+2017-01-18T07:41:02+00:00
https://home-assistant.io/demo/panels/ha-panel-history.html
-2017-01-17T19:54:39+00:00
+2017-01-18T07:41:02+00:00
https://home-assistant.io/demo/panels/ha-panel-iframe.html
-2017-01-17T19:54:39+00:00
+2017-01-18T07:41:02+00:00
https://home-assistant.io/demo/panels/ha-panel-logbook.html
-2017-01-17T19:54:39+00:00
+2017-01-18T07:41:02+00:00
https://home-assistant.io/demo/panels/ha-panel-map.html
-2017-01-17T19:54:39+00:00
+2017-01-18T07:41:02+00:00
https://home-assistant.io/googlef4f3693c209fe788.html
-2017-01-17T19:54:39+00:00
+2017-01-18T07:41:02+00:00
https://home-assistant.io/static/fonts/roboto/DESCRIPTION.en_us.html
-2017-01-17T19:54:39+00:00
+2017-01-18T07:41:02+00:00
https://home-assistant.io/static/fonts/robotomono/DESCRIPTION.en_us.html
-2017-01-17T19:54:39+00:00
+2017-01-18T07:41:02+00:00
https://home-assistant.io/static/mdi-demo.html
-2017-01-17T19:54:39+00:00
+2017-01-18T07:41:02+00:00