-
hello_panel:
- who: 'You'
+ panel_custom:
+ - name: hello_world
+ sidebar_title: Hello World
+ sidebar_icon: mdi:hand-pointing-right
+ url_path: hello_world
+ webcomponent_path: <config dir>/panels/hello.html
diff --git a/developers/rest_api/index.html b/developers/rest_api/index.html
index 700dc3b4f0..ad36386add 100644
--- a/developers/rest_api/index.html
+++ b/developers/rest_api/index.html
@@ -181,7 +181,7 @@ You can append
?password=YOUR_PASSWORD to any url to log in automat
"latitude":
44.1234,
"location_name":
"Home",
"longitude":
5.5678,
-
"temperature_unit":
"\u00b0C",
+
"unit_system":
"metric",
"time_zone":
"Europe/Zurich",
"version":
"0.8.0.dev0"
}
diff --git a/getting-started/basic/index.html b/getting-started/basic/index.html
index 5dcb26809f..7502e580f5 100644
--- a/getting-started/basic/index.html
+++ b/getting-started/basic/index.html
@@ -102,8 +102,8 @@
elevation:
430
-
-
temperature_unit:
C
+
+
unit_system:
metric
diff --git a/getting-started/z-wave-controllers/index.html b/getting-started/z-wave-controllers/index.html
index c2224b58b3..96f8e094a7 100644
--- a/getting-started/z-wave-controllers/index.html
+++ b/getting-started/z-wave-controllers/index.html
@@ -125,6 +125,12 @@ Upon first run, the z-wave component will take time to initialize entities and e
|
|
+
+ | ZWave.me UZB1 |
+ ✓ |
+ |
+ |
+
diff --git a/getting-started/z-wave-device-specific/index.html b/getting-started/z-wave-device-specific/index.html
index e9e84686a0..2886032b2c 100644
--- a/getting-started/z-wave-device-specific/index.html
+++ b/getting-started/z-wave-device-specific/index.html
@@ -101,44 +101,6 @@ The option is commented out by default in
options.xml and is a defa
It is best to pair these devices in Open Zwave Control Panel or other Zwave tool that can show you logs while pairing. Test the device before you save the configuration.
Make sure you copy the newly saved
zwcfg_[home_id].xmlinto your HomeAssistant config directory.
-
Event basic_level for automation
-
HomeAssistant will trigger a event when command_class_basic changes value on a node.
-This can be virtually anything, so tests have to be made to determine what value equals what.
-You can use this for automations.
-
-
Example:
-
-
-
- alias: Minimote Button Pressed
- trigger:
- platform: event
- event_type: zwave.node_event
- event_data:
- object_id: aeon_labs_minimote_1
- basic_level: 255
-
-
-
-
-
Event scene_id for automation
-
HomeAssistant will trigger a event when a scene is activated by a node in the zwave network.
-This can be a press of a button, so tests have to be made to determine what scene_id equals what.
-You can use this for automations.
-
-
Example:
-
-
-
- alias: Minimote Button 1 Pressed
- trigger:
- platform: event
- event_type: zwave.scene_activated
- event_data:
- object_id: aeon_labs_minimote_1
- scene_id: 1
-
-
-
-
Aeon Minimote
Here’s a handy configuration for the Aeon Labs Minimote that defines all possible button presses. Put it into automation.yaml.
diff --git a/getting-started/z-wave/index.html b/getting-started/z-wave/index.html
index ed7e4b0d06..efdce69434 100644
--- a/getting-started/z-wave/index.html
+++ b/getting-started/z-wave/index.html
@@ -190,7 +190,77 @@ Depending on what’s plugged into your USB ports, the name found above may chan
Events
-
Some devices can also trigger scene activation events, which can be used in automation scripts (for example the press of a button on a wall switch):
+
zwave.network_complete
+HomeAssistant will trigger a event when the zwave network is complete. Meaning all of the nodes on the network have been queried. This can take quite som time, depending on wakeup intervals on the battery powered devices on the network.
+
+
+
- alias: ZWave network is complete
+ trigger:
+ platform: event
+ event_type: zwave.network_complete
+
+
+
+
+
zwave.network_ready
+HomeAssistant will trigger a event when the zwave network is ready for use. Between zwave.network_start and zwave.network_ready HomeAssistant will feel sluggish when trying to send commands to zwave nodes. This is because the controller is requesting information from all of the nodes on the network. When this is triggered all awake nodes have been queried and sleeping nodes will be queried when they awake.
+
+
+
- alias: ZWave network is ready
+ trigger:
+ platform: event
+ event_type: zwave.network_ready
+
+
+
+
+
zwave.network_start
+HomeAssistant will trigger a event when the zwave network is set up to be started.
+
+
+
- alias: ZWave network is starting
+ trigger:
+ platform: event
+ event_type: zwave.network_start
+
+
+
+
+
zwave.network_stop
+HomeAssistant will trigger a event when the zwave network stopping.
+
+
+
- alias: ZWave network is stopping
+ trigger:
+ platform: event
+ event_type: zwave.network_start
+
+
+
+
+
zwave.node_event
+HomeAssistant will trigger a event when command_class_basic changes value on a node.
+This can be virtually anything, so tests have to be made to determine what value equals what.
+You can use this for automations.
+
+
Example:
+
+
+
- alias: Minimote Button Pressed
+ trigger:
+ platform: event
+ event_type: zwave.node_event
+ event_data:
+ object_id: aeon_labs_minimote_1
+ basic_level: 255
+
+
+
+
+
The object_id and basic_level of all triggered events can be seen in the console output.
+
+
zwave.scene_activated
+Some devices can also trigger scene activation events, which can be used in automation scripts (for example the press of a button on a wall switch):
@@ -200,13 +270,13 @@ Depending on what’s plugged into your USB ports, the name found above may chan
platform: event
event_type: zwave.scene_activated
event_data:
- entity_id: zwaveme_zme_wallcs_secure_wall_controller_8
+ object_id: zwaveme_zme_wallcs_secure_wall_controller_8
scene_id: 11
-
The entity_id and scene_id of all triggered events can be seen in the console output.
+
The object_id and scene_id of all triggered events can be seen in the console output.
Services
@@ -225,13 +295,21 @@ Depending on what’s plugged into your USB ports, the name found above may chan
Put the zwave controller in inclusion mode. Allows one to add a new device to the zwave network. |
- | remove_node |
- Put the zwave controller in exclusion mode. Allows one to remove a device from the zwave network. |
+ add_node_secure |
+ Put the zwave controller in secure inclusion mode. Allows one to add a new device with secure communications to the zwave network. |
+
+
+ | cancel_command |
+ Cancels a running zwave command. If you have started a add_node or remove_node command, and decides you are not going to do it, then this must be used to stop the inclusion/exclusion command. |
| heal_network |
Tells the controller to “heal” the network. Bascially asks the nodes to tell the controller all of their neighbors so the controller can refigure out optimal routing. |
+
+ | remove_node |
+ Put the zwave controller in exclusion mode. Allows one to remove a device from the zwave network. |
+
| soft_reset |
Tells the controller to do a “soft reset”. This is not supposed to lose any data, but different controllers can behave differently to a “soft reset” command. |
diff --git a/images/supported_brands/fastdotcom.png b/images/supported_brands/fastdotcom.png
new file mode 100644
index 0000000000..537ce9180c
Binary files /dev/null and b/images/supported_brands/fastdotcom.png differ
diff --git a/images/supported_brands/ffmpeg.png b/images/supported_brands/ffmpeg.png
new file mode 100644
index 0000000000..a7f78f5b51
Binary files /dev/null and b/images/supported_brands/ffmpeg.png differ
diff --git a/images/supported_brands/foursquare.png b/images/supported_brands/foursquare.png
new file mode 100644
index 0000000000..492431843b
Binary files /dev/null and b/images/supported_brands/foursquare.png differ
diff --git a/images/supported_brands/gpsd.png b/images/supported_brands/gpsd.png
new file mode 100644
index 0000000000..83ca308013
Binary files /dev/null and b/images/supported_brands/gpsd.png differ
diff --git a/images/supported_brands/ohmconnect.png b/images/supported_brands/ohmconnect.png
new file mode 100644
index 0000000000..e3aaf1b38b
Binary files /dev/null and b/images/supported_brands/ohmconnect.png differ
diff --git a/images/supported_brands/pilight.png b/images/supported_brands/pilight.png
new file mode 100644
index 0000000000..a95bf31001
Binary files /dev/null and b/images/supported_brands/pilight.png differ
diff --git a/index.html b/index.html
index e1a6d486d2..b7785b32c5 100644
--- a/index.html
+++ b/index.html
@@ -115,11 +115,11 @@ Home Assistant is an open-source home automation platform running on Python 3. T
-
Current Version: 0.25.2
- Released:
August 2, 2016
+
Current Version: 0.26
+ Released:
August 13, 2016
diff --git a/sitemap.xml b/sitemap.xml
index 34ad5fa05e..9e40d41db5 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -1,5 +1,9 @@
+
+ https://home-assistant.io/blog/2016/08/13/foursquare-fast-com-ffmpeg-gpsd/
+ 2016-08-13T19:00:00+00:00
+
https://home-assistant.io/blog/2016/08/07/optimizing-the-home-assistant-mobile-web-app/
2016-08-07T19:36:00+00:00
@@ -815,6 +819,9 @@
https://home-assistant.io/components/switch.command_line/
+
+ https://home-assistant.io/components/switch.pilight/
+
https://home-assistant.io/components/switch.edimax/
@@ -878,6 +885,12 @@
https://home-assistant.io/components/mqtt/
+
+ https://home-assistant.io/components/pilight/
+
+
+ https://home-assistant.io/components/panel_custom/
+
https://home-assistant.io/components/media_player.squeezebox/
@@ -1676,6 +1689,9 @@
https://home-assistant.io/components/switch.tplink/
+
+ https://home-assistant.io/components/sensor.gpsd/
+
https://home-assistant.io/components/media_player.directv/
@@ -1688,6 +1704,24 @@
https://home-assistant.io/components/media_player.mpchc/
+
+ https://home-assistant.io/components/sensor.ohmconnect/
+
+
+ https://home-assistant.io/components/foursquare/
+
+
+ https://home-assistant.io/components/light.mqtt_json/
+
+
+ https://home-assistant.io/components/sensor.fastdotcom/
+
+
+ https://home-assistant.io/components/sensor.serial_pm/
+
+
+ https://home-assistant.io/components/camera.ffmpeg/
+
https://home-assistant.io/cookbook/automation_for_rainy_days/
@@ -2042,64 +2076,67 @@
https://home-assistant.io/blog/2016/08/07/optimizing-the-home-assistant-mobile-web-app/
+
+ https://home-assistant.io/blog/2016/08/13/foursquare-fast-com-ffmpeg-gpsd/
+
https://home-assistant.io/demo/frontend.html
- 2016-08-13T15:58:28+00:00
+ 2016-08-13T19:21:34+00:00
https://home-assistant.io/demo/index.html
- 2016-08-13T15:58:28+00:00
+ 2016-08-13T19:21:34+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-event.html
- 2016-08-13T15:58:28+00:00
+ 2016-08-13T19:21:34+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-info.html
- 2016-08-13T15:58:28+00:00
+ 2016-08-13T19:21:34+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-service.html
- 2016-08-13T15:58:28+00:00
+ 2016-08-13T19:21:34+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-state.html
- 2016-08-13T15:58:28+00:00
+ 2016-08-13T19:21:34+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-template.html
- 2016-08-13T15:58:28+00:00
+ 2016-08-13T19:21:34+00:00
https://home-assistant.io/demo/panels/ha-panel-history.html
- 2016-08-13T15:58:28+00:00
+ 2016-08-13T19:21:34+00:00
https://home-assistant.io/demo/panels/ha-panel-iframe.html
- 2016-08-13T15:58:28+00:00
+ 2016-08-13T19:21:34+00:00
https://home-assistant.io/demo/panels/ha-panel-logbook.html
- 2016-08-13T15:58:28+00:00
+ 2016-08-13T19:21:34+00:00
https://home-assistant.io/demo/panels/ha-panel-map.html
- 2016-08-13T15:58:28+00:00
+ 2016-08-13T19:21:34+00:00
https://home-assistant.io/googlef4f3693c209fe788.html
- 2016-08-13T15:58:28+00:00
+ 2016-08-13T19:21:34+00:00
https://home-assistant.io/static/fonts/roboto/DESCRIPTION.en_us.html
- 2016-08-13T15:58:28+00:00
+ 2016-08-13T19:21:34+00:00
https://home-assistant.io/static/fonts/robotomono/DESCRIPTION.en_us.html
- 2016-08-13T15:58:28+00:00
+ 2016-08-13T19:21:34+00:00
https://home-assistant.io/static/mdi-demo.html
- 2016-08-13T15:58:28+00:00
+ 2016-08-13T19:21:34+00:00
diff --git a/topics/platform_options/index.html b/topics/platform_options/index.html
index 2fc5867429..0ed719a93a 100644
--- a/topics/platform_options/index.html
+++ b/topics/platform_options/index.html
@@ -142,7 +142,9 @@
+
+
-
diff --git a/topics/secrets/index.html b/topics/secrets/index.html
index 40d7a5e782..f0753bd252 100644
--- a/topics/secrets/index.html
+++ b/topics/secrets/index.html
@@ -124,17 +124,17 @@
- Python Keyring
+ Storing passwords in a keyring managed by your OS
-Using Keyring is an alternative way to secrets.yaml but requires that keyring is installed (incl. its command-line tools). This can be done with:
+Using Keyring is an alternative way to secrets.yaml. They can be managed from the command line via the keyring script.
-
$ pip3 install keyring
+ $ hass --script keyring --help
-
Replace your password or API key with !secret and an identifier in configuration.yaml file.
+
To store a password in keyring, replace your password or API key with !secret and an identifier in configuration.yaml file.
http:
@@ -143,28 +143,10 @@
-
Create an entry in your keyring. The service (SERVICE) is homeassistant and the identifier is the USERNAME in the keyring context.
+
Create an entry in your keyring.
-
$ keyring set homeassistant http_password
-Password for 'http_password' in 'homeassistant':
-Please set a password for your new keyring:
-Please confirm the password:
-
-
-
-
-
If the command-line tool keyring is not available, launch python3 and do the process manually.
-
-
-
>>> import keyring
->>> keyring.set_password("homeassistant", "http_password", "12345")
-Please set a password for your new keyring:
-Please confirm the password:
->>> keyring.get_password("homeassistant", "http_password")
-'12345'
->>> keyring.get_keyring()
-<EncryptedKeyring at /home/your_user/.local/share/python_keyring/crypted_pass.cfg>
+ $ hass --script keyring set http_password
@@ -174,7 +156,7 @@ Please confirm the password:
$ hass
Config directory: /home/fab/.homeassistant
-Please enter password for encrypted keyring:
+Please enter password for encrypted keyring:
@@ -184,7 +166,6 @@ Please enter password for encrypted keyring:
-
diff --git a/topics/splitting_configuration/index.html b/topics/splitting_configuration/index.html
index e4f67074c7..f42eeccdb0 100644
--- a/topics/splitting_configuration/index.html
+++ b/topics/splitting_configuration/index.html
@@ -108,8 +108,8 @@
latitude:
37
longitude:
-121
-
-
temperature_unit:
F
+
+
unit_system:
imperial
time_zone:
America/Los_Angeles
customize:
!include customize.yaml
diff --git a/topics/templating/index.html b/topics/templating/index.html
index 76649c1e0a..a04c09ca7f 100644
--- a/topics/templating/index.html
+++ b/topics/templating/index.html
@@ -102,12 +102,12 @@
Building templates
-
Templating in Home Assistant is powered by the Jinja2 templating engine. This means that we are using their syntax and make some custom Home Assistant variables available to templates during rendering. We will not go over the basics of the syntax, as Jinja2 does a lot better job at this in their Jinja2 documentation.
+
Templating in Home Assistant is powered by the Jinja2 templating engine. This means that we are using their syntax and make some custom Home Assistant variables available to templates during rendering. We will not go over the basics of the syntax, as Jinja2 does a lot better job at this in their Jinja2 documentation.
The frontend has a template editor developer tool to help develop and debug templates.
@@ -131,6 +131,14 @@ The frontend has a template editor developer tool to help develop and debug temp
+
Jinja2 supports a width variety of operations:
+
+
+
Home Assistant template extensions
Home Assistant adds extensions to allow templates to access all of the current states:
@@ -149,7 +157,6 @@ The frontend has a template editor developer tool to help develop and debug temp
closest() will find the closest entity.
relative_time(timestamp) will format the date time as relative time vs now (ie 7 seconds)
float will format the output as float.
-
Filter multiply(x) will convert the input to a number and multiply it with x.
Filter round(x) will convert the input to a number and round it to x decimals.
Filter timestamp_local will convert an UNIX timestamp to local time/data.
Filter timestamp_utc will convert an UNIX timestamp to UTC time/data.
@@ -199,7 +206,9 @@ The frontend has a template editor developer tool to help develop and debug temp
Paulus is at {{ states('device_tracker.paulus')) }}.
{% endif %}
-{{ states.sensor.temperature | multiply(10) | round(2) }}
+{{ states.sensor.temperature | float + 1 }}
+
+{{ states.sensor.temperature | float * 10 | round(2) }}
{% if states('sensor.temperature') | float > 20 %}
It is warm!
@@ -300,9 +309,9 @@ Closest to an entity: {{ closest(states.zone.school, 'group.children') }}
# Format output
{{ "%+.1f" | value_json }}
-# Calculations
-{{ value_json | multiply(1024) }}
-{{ value_json.used | multiply(0.0001) | round(0) }}
+# Math
+{{ value_json | float * 1024 }}
+{{ float(value_json) * (2**10) }}
# Timestamps
{{ value_json.tst | timestamp_local }}
+ 
-Picture of the final setup (+ 2 LED for decoration)
-
-Home Assistant will keep track of historical values and allow you to integrate it into automation.
-
The big new addition in this release is the support for the MQTT protocol by 
+
+ 
+
+ 
+