mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-23 09:17:06 +00:00
Merge remote-tracking branch 'origin/current' into next
This commit is contained in:
Paulus Schoutsen
commit
dfa36c5eb5
@ -18,7 +18,8 @@ Set up [Mosquitto](https://mosquitto.org/) as MQTT broker.
|
||||
"ssl": false,
|
||||
"anonymous": true,
|
||||
"logins": [
|
||||
{"username": "testuser", "password": "mypw"}
|
||||
{"username": "testuser", "password": "mypw"},
|
||||
{"username": "testuser2", "password": "mypw2"}
|
||||
],
|
||||
"customize": {
|
||||
"active": false,
|
||||
@ -74,5 +75,24 @@ protocol mqtt
|
||||
4. Restart MQTT
|
||||
|
||||
<p class='note warning'>
|
||||
It's recommened that you only open your firewall to the SSL/TLS port (8883) and only use the insecure port (1883) for local devices. Also, disable `anonymous:` and set `logins:`.
|
||||
It's recommended that you only open your firewall to the SSL/TLS port (8883) and only use the insecure port (1883) for local devices. Also, disable `anonymous:` and set `logins:`.
|
||||
</p>
|
||||
|
||||
### {% linkable_title Access Control Lists (ACLs) %}
|
||||
|
||||
It is possible to restrict access to topics based upon the user logged in to Mosquitto. In this scenario it is recommended to create individual users for each of your clients and create an appropriate ACL.
|
||||
|
||||
See the following links for more information:
|
||||
|
||||
* [Mosquitto topic restrictions](http://www.steves-internet-guide.com/topic-restriction-mosquitto-configuration/)
|
||||
* [Mosquitto.conf man page](https://mosquitto.org/man/mosquitto-conf-5.html)
|
||||
|
||||
Add the following configuration to enable ACLs:
|
||||
|
||||
1. Set `customize` flag to `true` in your configuration.
|
||||
2. Create a file in `/share/mosquitto` named `acl.conf` with the following contents:
|
||||
|
||||
```text
|
||||
acl_file /share/mosquitto/accesscontrollist
|
||||
```
|
||||
3. Create a file in `/share/mosquitto` named `accesscontrollist` and add contents according to your requirements.
|
||||
|
||||
@ -38,7 +38,7 @@ alarm_control_panel:
|
||||
```
|
||||
|
||||
<p class='note warning'>
|
||||
It is strongly discouraged to use this platform when you don't use encryption; otherwise, your API password will be send unprotected through the IFTTT Webhooks. It is adviced to [setup encryption using Let's Encrypt](https://home-assistant.io/blog/2017/09/27/effortless-encryption-with-lets-encrypt-and-duckdns/).
|
||||
It is strongly discouraged to use this platform when you don't use encryption; otherwise, your API password will be send unprotected through the IFTTT Webhooks. It is advised to [setup encryption using Let's Encrypt](https://home-assistant.io/blog/2017/09/27/effortless-encryption-with-lets-encrypt-and-duckdns/).
|
||||
</p>
|
||||
|
||||
{% linkable_title Required IFTTT applets %}
|
||||
@ -86,7 +86,7 @@ For this system to operate correctly, the following IFTTT applets have to be set
|
||||
type: string
|
||||
default: alarm_disarm
|
||||
optimistic:
|
||||
description: Specify if the state will be updated by a ifttt_push_alarm_state call (false) or can be set immediately (true).
|
||||
description: Specify if the state will be updated by an ifttt_push_alarm_state call (false) or can be set immediately (true).
|
||||
required: false
|
||||
type: boolean
|
||||
default: false
|
||||
|
||||
@ -8,7 +8,7 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: modbus.png
|
||||
ha_category: Thermostat
|
||||
ha_category: Climate
|
||||
ha_release: 0.68
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
@ -34,12 +34,14 @@ Home Assistant can discover and automatically configure [zeroconf](https://en.wi
|
||||
* [Plex media server](/components/media_player.plex/)
|
||||
* [Roku media player](/components/media_player.roku/)
|
||||
* [SABnzbd downloader](/components/sensor.sabnzbd/)
|
||||
* [Samsung SyncThru Printer](/components/sensor.syncthru/)
|
||||
* [Samsung TVs](/components/media_player.samsungtv/)
|
||||
* [Sonos speakers](/components/media_player.sonos/)
|
||||
* [Telldus Live](/components/tellduslive/)
|
||||
* [Wink](/components/wink/)
|
||||
* [Yamaha media player](/components/media_player.yamaha/)
|
||||
* [Yeelight Sunflower bulb](/components/light.yeelightsunflower/)
|
||||
* [Xiaomi Gateway (Aqara)](/components/xiaomi_aqara/)
|
||||
|
||||
It will be able to add Google Chromecasts and Belkin WeMo switches automatically, for Philips Hue it will require some configuration from the user.
|
||||
|
||||
@ -80,13 +82,15 @@ Valid values for ignore are:
|
||||
* `plex_mediaserver`: Plex media server
|
||||
* `roku`: Roku media player
|
||||
* `sabnzbd`: SABnzbd downloader
|
||||
* `samsung_printer`: Samsung SyncThru Printer
|
||||
* `samsung_tv`: Samsung TVs
|
||||
* `sonos`: Sonos speakers
|
||||
* `songpal` : Songpal
|
||||
* `tellduslive`: Telldus Live
|
||||
* `tellstick`: Telldus Live
|
||||
* `wink`: Wink Hub
|
||||
* `yamaha`: Yamaha media player
|
||||
* `yeelight`: Yeelight Sunflower bulb
|
||||
* `xiaomi_gw`: Xiaomi Aqara gateway
|
||||
|
||||
- **enable** (*Optional*): A list of platforms not enabled by default that `discovery` should discover.
|
||||
|
||||
|
||||
@ -20,89 +20,78 @@ To connect your device, add the following to your `configuration.yaml` file:
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
doorbird:
|
||||
host: DOORBIRD_IP_OR_HOSTNAME
|
||||
username: YOUR_USERNAME
|
||||
password: YOUR_PASSWORD
|
||||
hass_url_override: HASS_IP
|
||||
devices:
|
||||
- host: DOORBIRD_IP_OR_HOSTNAME
|
||||
username: YOUR_USERNAME
|
||||
password: YOUR_PASSWORD
|
||||
hass_url_override: HASS_URL
|
||||
name: Front Door
|
||||
- host: DOORBIRD_IP_OR_HOSTNAME
|
||||
username: YOUR_USERNAME
|
||||
password: YOUR_PASSWORD
|
||||
name: Driveway Gate
|
||||
monitored_conditions:
|
||||
- doorbell
|
||||
- motion
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
{% configuration %}
|
||||
devices:
|
||||
description: List of doorbird devices.
|
||||
required: true
|
||||
type: list
|
||||
keys:
|
||||
host:
|
||||
description: The LAN IP address or hostname of your device. You can find this by going to the [DoorBird Online check](http://www.doorbird.com/checkonline) and entering the information from the paper that was included in the box.
|
||||
required: true
|
||||
type: string
|
||||
username:
|
||||
description: The username of a non-administrator user account on the device.
|
||||
required: true
|
||||
type: string
|
||||
password:
|
||||
description: The password for the user specified.
|
||||
required: true
|
||||
type: string
|
||||
name:
|
||||
description: Custom name for this device.
|
||||
required: false
|
||||
type: string
|
||||
hass_url_override:
|
||||
description: If your DoorBird cannot connect to the machine running Home Assistant because you are using dynamic DNS or some other HTTP configuration (such as HTTPS), specify the LAN IP of the machine here to force a LAN connection.
|
||||
required: false
|
||||
type: string
|
||||
monitored_conditions:
|
||||
description: Monitor motion and/or doorbell events for this device.
|
||||
required: false
|
||||
type: string
|
||||
keys:
|
||||
doorbell:
|
||||
description: Monitor doorbell events
|
||||
motion:
|
||||
description: Monitor motion events (Motion monitoring must be enabled on the doorstation via DoorBird app)
|
||||
|
||||
- **host** (*Required*): The LAN IP address or hostname of your device. You can find this by going to the [DoorBird Online check](http://www.doorbird.com/checkonline) and entering the information from the paper that was included in the box.
|
||||
- **username** (*Required*): The username of a non-administrator user account on the device.
|
||||
- **password** (*Required*): The password for the user specified.
|
||||
- **doorbell_events** (*Optional*): Setting this to `true` this will register a callback URL with the device so that events can be published to the event bus when the doorbell rings.
|
||||
- **hass_url_override** (*Optional*): If your DoorBird cannot connect to the machine running Home Assistant because you are using dynamic DNS or some other HTTP configuration (such as HTTPS), specify the LAN IP of the machine here to force a LAN connection.
|
||||
{% endconfiguration %}
|
||||
|
||||
The configuration above is also used by the following components:
|
||||
- [Camera](../camera.doorbird) - View live and historical event based images
|
||||
- [Switch](../switch.doorbird) - Enable control of relays and camera night vision
|
||||
|
||||
## {% linkable_title Motion and Doorbell Events %}
|
||||
|
||||
Home Assistant will fire an event any time a `monitored_condition` happens on a doorstation. Event names are created using the format `doorbird_{station}_{event}` (Examples: `doorbird_side_entry_button`, `doorbird_side_entry_motion`). You can verify the assigned event names in the Home Assistant log file.
|
||||
|
||||
<p class="note warning">
|
||||
Enabling `doorbell_events` will delete all other registered push notification services with the device every time Home Assistant starts. This will not affect notifications delivered by the DoorBird mobile app.
|
||||
Enabling any monitored condition will delete all registered notification services on the doorstation every time Home Assistant starts. This will not affect notifications delivered by the DoorBird mobile app.
|
||||
</p>
|
||||
|
||||
### Doorbell Sound Examples
|
||||
|
||||
You can create an automation that triggers on event `doorbird_doorbell` to play a doorbell sound when the Doorbird button is pressed. This should work with any media player.
|
||||
|
||||
#### Example using SONOS
|
||||
|
||||
[`SONOS`](http://www.sonos.com) players have features allowing for "snapshotting" the current state of some or all players so those state(s) can be "restored" at a later time. This feature is perfect for implementing a doorbell sound (from Doorbird or any other Doorbell setup for that matter). The [`media_player.sonos`](/components/media_player.sonos/) platform includes the [`SONOS_SNAPSHOT`](/components/media_player.sonos/#service-sonos_snapshot) and [`SONOS_RESTORE`](/components/media_player.sonos/#service-sonos_restore) features. The result of not using these features is any currently playing songs or media will not continue playing after the doorbell sound has played and you will be left with the doorbell sound queued as the last played song. This setup allows for seamless ringing of the doorbell and all SONOS devices continuing nicely on as if nothing had happened.
|
||||
|
||||
The example script below takes a snapshot of three SONOS players that are not currently grouped together, joins the three players in a group (so the sound plays at the same time on all players), plays the doorbell MP3 sound, unjoins the players from the group and finally restores the players to their original state. When the players are grouped they are controlled by refering to the `master`.
|
||||
|
||||
Automation file:
|
||||
|
||||
### {% linkable_title Automation Example %}
|
||||
```yaml
|
||||
- alias: Doorbird ring
|
||||
- alias: Doorbird Ring
|
||||
trigger:
|
||||
platform: event
|
||||
event_type: doorbird_doorbell
|
||||
event_type: doorbird_side_entry_button
|
||||
action:
|
||||
service: script.turn_on
|
||||
entity_id: script.doorbell
|
||||
```
|
||||
|
||||
Script file:
|
||||
|
||||
```yaml
|
||||
doorbell:
|
||||
alias: Ring Doorbell
|
||||
sequence:
|
||||
- service: media_player.sonos_snapshot
|
||||
data:
|
||||
entity_id:
|
||||
- media_player.kitchen
|
||||
- media_player.master_bedroom
|
||||
- media_player.study
|
||||
- service: media_player.sonos_join
|
||||
data:
|
||||
master: media_player.study
|
||||
entity_id:
|
||||
- media_player.kitchen
|
||||
- media_player.master_bedroom
|
||||
- media_player.study
|
||||
- service: media_player.play_media
|
||||
data:
|
||||
entity_id: media_player.study # the group master
|
||||
media_content_id: http://10.1.1.10/sounds/doorbell.mp3 # this is on a NAS but could be HASS local
|
||||
media_content_type: music
|
||||
- service: media_player.volume_set
|
||||
data:
|
||||
entity_id: # can still control the volume of grouped players indivdually
|
||||
- media_player.study
|
||||
- media_player.kitchen
|
||||
- media_player.master_bedrom
|
||||
volume_level: 0.50
|
||||
- delay:
|
||||
seconds: 4 # wait while the sound plays
|
||||
- service: media_player.sonos_unjoin
|
||||
data:
|
||||
entity_id:
|
||||
- media_player.kitchen
|
||||
- media_player.master_bedroom
|
||||
- media_player.study
|
||||
- service: media_player.sonos_restore
|
||||
data:
|
||||
entity_id:
|
||||
- media_player.kitchen
|
||||
- media_player.master_bedroom
|
||||
- media_player.study
|
||||
```
|
||||
service: light.turn_on
|
||||
entity_id: light.side_entry_porch
|
||||
```
|
||||
@ -94,7 +94,7 @@ fan:
|
||||
required: false
|
||||
type: action
|
||||
set_oscillating:
|
||||
description: Defines an action to run when the fan is given a osc state command.
|
||||
description: Defines an action to run when the fan is given an osc state command.
|
||||
required: false
|
||||
type: action
|
||||
set_direction:
|
||||
|
||||
@ -72,7 +72,7 @@ This component is tested to work with the following models. If you have a differ
|
||||
|
||||
### {% linkable_title Service `light.yeelight_set_mode` %}
|
||||
|
||||
Set a operation mode.
|
||||
Set an operation mode.
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
|---------------------------|----------|---------------------------------------------------------------------------------------------|
|
||||
|
||||
@ -39,7 +39,7 @@ password:
|
||||
required: true
|
||||
type: string
|
||||
homeserver:
|
||||
description: "The full URL for your homeserver. If you use the defauls matrix.org homeserver, this is 'https://matrix.org'."
|
||||
description: "The full URL for your homeserver. If you use the default matrix.org homeserver, this is 'https://matrix.org'."
|
||||
required: true
|
||||
type: string
|
||||
verify_ssl:
|
||||
|
||||
@ -73,6 +73,7 @@ Currently tested but not working models:
|
||||
- J5500 - State is always "on" and unable to control (but port 8001 *is* open)
|
||||
- JU7000 - Unable to see state and unable to control (but port 8001 *is* open)
|
||||
- JU7500 - Unable to see state and unable to control
|
||||
- JS8005 - State tracking working but unable to control (but port 8001 *is* open)
|
||||
- JS9000 - State is always "on" and unable to control (but port 8001 *is* open)
|
||||
- JS9500 - State is always "on" and unable to control (but port 8001 *is* open)
|
||||
- MU6300 - Port set to 8001, `pip3 install websocket-client` must be executed, turning on works, status not working reliably, turning off is not permanent (it comes back on)
|
||||
|
||||
@ -29,7 +29,7 @@ username:
|
||||
required: true
|
||||
type: string
|
||||
password:
|
||||
description: v
|
||||
description: Password for the Neato account.
|
||||
required: true
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
@ -91,7 +91,7 @@ To add a notification sound, icon, cycles, or priority override, it has to be do
|
||||
|
||||
### {% linkable_title Only notify specific device %}
|
||||
|
||||
If you have more than one La Metric device, you can specify which will recieve the message by adding `target:` to the service data:
|
||||
If you have more than one La Metric device, you can specify which will receive the message by adding `target:` to the service data:
|
||||
|
||||
```yaml
|
||||
action:
|
||||
|
||||
@ -18,7 +18,7 @@ This component can expose regular REST commands as services. Services can be cal
|
||||
[script]: /components/script/
|
||||
[automation]: /getting-started/automation/
|
||||
|
||||
To enable this switch, add the following lines to your `configuration.yaml` file:
|
||||
To use this component, add the following lines to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
@ -39,4 +39,5 @@ Configuration variables:
|
||||
- **timeout** (*Optional*): Timeout for requests. Defaults to 10 seconds.
|
||||
- **content_type** (*Optional*): Content type for the request.
|
||||
|
||||
The commands can be dynamic, using templates to insert values of other entities. Service call support variables for template stuff.
|
||||
The commands can be dynamic, using templates to insert values of other entities.
|
||||
Service call support variables for template stuff.
|
||||
|
||||
@ -50,3 +50,7 @@ Configuration variables:
|
||||
- **manual** (*Optional*): True or False to turn manual mode on or off. Manual mode will disable scheduled speedtests.
|
||||
|
||||
There is also a service named `sensor.update_fastdotcom` that you can use to run a fast.com speedtest on demand. You can turn on manual mode to disable the scheduled speedtests.
|
||||
|
||||
## Note
|
||||
|
||||
- When running on Raspberry Pi, just note that the maximum speed is limited by its 100 Mbit/s LAN adapter.
|
||||
|
||||
@ -21,7 +21,7 @@ You need to find a valid GTFS data set, which you can usually find just by searc
|
||||
Here are some examples:
|
||||
|
||||
- [Bay Area Rapid Transit (BART)](http://www.bart.gov/schedules/developers/gtfs) - The light rail system for the San Francisco Bay Area.
|
||||
- [Metropolitan Transit Authority of New York City (MTA)](http://www.bart.gov/schedules/developers/gtfs) - Provides separate data feeds for subway, bus, LIRR and Metro-North of the greater New York City metropolitan region.
|
||||
- [Metropolitan Transit Authority of New York City (MTA)](http://web.mta.info/developers/) - Provides separate data feeds for subway, bus, LIRR and Metro-North of the greater New York City metropolitan region.
|
||||
- [GBRail.info](http://www.gbrail.info/) - Provides data feeds for most if not all rail companies in Britain.
|
||||
- [Official Timetable Switzerland](http://www.fahrplanfelder.ch/en/timetable-data.html) - The official timetable data for Switzerland.
|
||||
- [Public Transport Victoria (Australia)](https://www.data.vic.gov.au/data/dataset/ptv-timetable-and-geographic-information-2015-gtfs) - Official PTV GTFS dataset.
|
||||
|
||||
@ -70,10 +70,10 @@ sensor:
|
||||
- **median** (*Optional*): Sometimes the sensor measurements show spikes. Using this parameter, the poller will report the median of the last 3 (you can also use larger values) measurements. This filters out single spikes. Median: 5 will also filter double spikes. If you never have problems with spikes, `median: 1` will work fine.
|
||||
- **timeout** (*Optional*): Define the timeout value in seconds when polling (defaults to 10 if not defined)
|
||||
- **retries** (*Optional*): Define the number of retries when polling (defaults to 2 if not defined)
|
||||
- **cache_value** (*Optional*): Define cache expiration value in seconds (defaults to 1200 if not defined)
|
||||
- **cache_value** (*Optional*): Define cache expiration value in seconds (defaults to 300 if not defined)
|
||||
- **adapter** (*Optional*): Define the Bluetooth adapter to use (defaults to hci0). Run `hciconfig` to get a list of available adapters.
|
||||
|
||||
Note that by default the sensor is only polled once every 5 minutes. This means with the `median: 3` setting will take as least 15 minutes before the sensor will report a value after a Home Assistant restart. Even though the hardware is able to provide new values every second, room temperaturs don't change that quickly.
|
||||
Note that by default the sensor is only polled once every 5 minutes. This means with the `median: 3` setting will take as least 15 minutes before the sensor will report a value after a Home Assistant restart. Even though the hardware is able to provide new values every second, room temperatures don't change that quickly.
|
||||
Reducing polling intervals will have a negative effect on the battery life.
|
||||
|
||||
A full configuration example could look like the one below:
|
||||
|
||||
@ -16,10 +16,34 @@ ha_iot_class: "Local Polling"
|
||||
|
||||
The `netdata` sensor platform allows you to display information collected by [Netdata](http://my-netdata.io/).
|
||||
|
||||
## {% linkable_title Setup %}
|
||||
|
||||
Getting the details to configure the sensors is a bit tricky as Netdata uses different name for the `element:` value that is required. To get the value for the `data_group:` use Netdata's web interface. `1.` marks the name for the `data_group:`. `2.` are the names for the element to show in Home Assistant. The name that is shown can be different than the name under which the metrics are available.
|
||||
|
||||
<p class='img'>
|
||||
<img src='{{site_root}}/images/components/netdata/details.png' />
|
||||
</p>
|
||||
|
||||
To check if the `element:` name matches the name in the Netdata frontend, use `curl` with the IP address of your Netdata instance, its port and the `data_group`:
|
||||
|
||||
```bash
|
||||
$ curl -X GET "http://[Netdata_Instance]:19999/api/v1/data?chart=[data_group]&points=2&options=jsonwrap"
|
||||
{
|
||||
"api": 1,
|
||||
"id": "system.ipv4",
|
||||
"name": "system.ipv4",
|
||||
[...]
|
||||
"dimension_names": ["received", "sent"],
|
||||
"dimension_ids": ["InOctets", "OutOctets"],
|
||||
[...]
|
||||
```
|
||||
|
||||
- `dimension_names`: Names shown in the frontend.
|
||||
- `dimension_ids`: Names to use for `element`.
|
||||
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
|
||||
|
||||
To add this platform to your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
|
||||
@ -115,8 +115,8 @@ site_ids:
|
||||
description: A list of siteIds if using multiple Snips instances. Used to make sure feedback is toggled on or off for all sites.
|
||||
required: false
|
||||
type: str
|
||||
probability_threshhold:
|
||||
description: Threshhold for intent probability. Range is from 0.00 to 1.00, 1 being highest match. Intents under this level are discarded.
|
||||
probability_threshold:
|
||||
description: Threshold for intent probability. Range is from 0.00 to 1.00, 1 being highest match. Intents under this level are discarded.
|
||||
require: false
|
||||
type: float
|
||||
{% endconfiguration %}
|
||||
|
||||
@ -30,6 +30,14 @@ switch:
|
||||
- open_door
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **switches** (*Required*): A list of switches to include. Possible entries are `light_on` for control of the IR array and `open_door` for control of an electronic door strike or alarm.
|
||||
{% configuration %}
|
||||
switches:
|
||||
description: A list of switches to include. Possible entries are `light_on` for control of the IR array and `open_door` for control of an electronic door strike or alarm.
|
||||
required: false
|
||||
type: list
|
||||
keys:
|
||||
light_on:
|
||||
description: Enable the IR light for 3 minutes.
|
||||
open_door:
|
||||
description: Activate DoorBird door relay
|
||||
{% endconfiguration %}
|
||||
|
||||
@ -15,7 +15,7 @@ Home Assistant currently supports free web services and such which require a reg
|
||||
|
||||
## {% linkable_title Condition mapping %}
|
||||
|
||||
The `weather` platform only knows the below listed conditions. The reason for this is that for these conditions is an icon from [Material Design Icons](https://materialdesignicons.com/) available and mapped in the [frontend](https://github.com/home-assistant/home-assistant-polymer/blob/master/src/cards/ha-weather-card.html#L77).
|
||||
The `weather` platform only knows the below listed conditions. The reason for this is that for these conditions is an icon from [Material Design Icons](https://materialdesignicons.com/) available and mapped in the [frontend](https://github.com/home-assistant/home-assistant-polymer/blob/master/src/cards/ha-weather-card.js#L170).
|
||||
|
||||
- 'cloudy'
|
||||
- 'fog'
|
||||
|
||||
@ -134,7 +134,7 @@ automation:
|
||||
trigger:
|
||||
platform: numeric_state
|
||||
entity_id: sun.sun
|
||||
value_template: "{{ state.attributes.elevation }"
|
||||
value_template: "{{ state.attributes.elevation }}"
|
||||
# Can be a positive or negative number
|
||||
below: -4.0
|
||||
action:
|
||||
|
||||
@ -33,7 +33,7 @@ Here is where you [include and exclude](/docs/z-wave/adding/) Z-Wave devices fro
|
||||
## {% linkable_title Z-Wave Node Management %}
|
||||
|
||||
<p class='note warning'>
|
||||
Since 0.63 and the new experimental [entity registry](/docs/configuration/entity-registry/) **Rename Node** no longer changes the entity id for anything other than the `zwave.` entity for the node (it does change the default *friendly_name* attribute for all the entities). See [this issue](https://github.com/home-assistant/home-assistant/issues/12430).
|
||||
Since 0.63 and the new experimental [entity registry](/docs/configuration/entity-registry/) **Rename Node** no longer changes the entity id for anything other than the `zwave.` entity for the node (it does change the default *friendly_name* attribute for all the entities). If you would like to update the entity id after renaming a z-wave device, you need to manually edit the [entity_registry.yaml](/docs/configuration/entity-registry/) file. See [this issue](https://github.com/home-assistant/home-assistant/issues/12430).
|
||||
</p>
|
||||
|
||||
* **Refresh Node** refreshes the information on the node and its entities. If used on a battery powered device, the device will first need to wake for this to work.
|
||||
|
||||
@ -15,7 +15,7 @@ The [ESP8266](https://www.espressif.com/en/products/hardware/esp8266ex/overview)
|
||||
|
||||
Setting up these microcontrollers for some basic functionality has also gotten really easy over the years with popular projects like ESPEasy or Sonoff-Tasmota: You just download their firmware and flash it onto your chip. But if you’ve ever tried to go a bit beyond the basic set of functions of those frameworks and tried to do some customization, you will have probably noticed that it’s not that easy. Often times you’ll end up having to download some Arduino code project from the internet and customizing it to your needs.
|
||||
|
||||
This is where esphomlib comes in: The [esphomelib suite](https://esphomelib.com/esphomeyaml/index.html) is a set of tools that are designed with the goal of achieving the best possible user experience. esphomelib a) allows for lots of customization without touching *a single line* of code and b) has complete Home Assistant integration. Inside the esphomelib ecosystem, you essentially just have to write a simple YAML configuration file. The rest like compiling, flashing, uploading etc. will then be taken care of automatically.
|
||||
This is where esphomelib comes in: The [esphomelib suite](https://esphomelib.com/esphomeyaml/index.html) is a set of tools that are designed with the goal of achieving the best possible user experience. esphomelib a) allows for lots of customization without touching *a single line* of code and b) has complete Home Assistant integration. Inside the esphomelib ecosystem, you essentially just have to write a simple YAML configuration file. The rest like compiling, flashing, uploading etc. will then be taken care of automatically.
|
||||
|
||||
<!--more-->
|
||||
|
||||
|
||||
@ -13,7 +13,7 @@ og_image: /images/blog/2018-06-0.71/components.png
|
||||
|
||||
<a href='/components/#version/0.71'><img src='/images/blog/2018-06-0.71/components.png' style='border: 0;box-shadow: none;'></a>
|
||||
|
||||
0.71 has arrived. My favorite feature in this release is the conversion of the Nest component from cloud poll to cloud push. Sure, it's still through the cloud but changes are now made available in Home Assistnat as soon as they happen. Thanks [@awarecan]!
|
||||
0.71 has arrived. My favorite feature in this release is the conversion of the Nest component from cloud poll to cloud push. Sure, it's still through the cloud but changes are now made available in Home Assistant as soon as they happen. Thanks [@awarecan]!
|
||||
|
||||
We've continued the frontend tweaks after the major overhaul in the last release. We've had some issues with the Hass.io panel on both Firefox and Safari. They have been addressed and all browsers should hopefully work again.
|
||||
|
||||
|
||||
@ -32,8 +32,8 @@ Please remember to ensure you're using an [appropriate power supply](https://www
|
||||
There is an easy workaround, just uncompress the image first.
|
||||
|
||||
```bash
|
||||
bunzip2 -c resinos-hassio-1.1-raspberrypi3.img.bz2 > image.img
|
||||
```
|
||||
$ bunzip2 -c resinos-hassio-1.3-raspberrypi3.img.bz2 > image.img
|
||||
```
|
||||
</p>
|
||||
|
||||
- Optional - Setup the WiFi or static IP: On the SD-card, edit the `system-connections/resin-sample` file and follow the [ResinOS howto][resinos-network].
|
||||
@ -54,10 +54,25 @@ If you copy over your existing Home Assistant configuration, make sure to enable
|
||||
|
||||
## {% linkable_title Alternative: install on generic Linux server %}
|
||||
|
||||
For advanced users, it is also possible to try Hass.io on your [Linux server or inside a virtual machine][linux]. To do so, run the following command as root:
|
||||
For advanced users, it is also possible to try Hass.io on your [Linux server or inside a virtual machine][linux].
|
||||
|
||||
This is the list of packages you need to have available on your system that will run Hass.io if you are using Debian/Ubuntu:
|
||||
|
||||
- apparmor-utils
|
||||
- apt-transport-https
|
||||
- avahi-daemon
|
||||
- ca-certificates
|
||||
- curl
|
||||
- dbus
|
||||
- jq
|
||||
- network-manager
|
||||
- socat
|
||||
- software-properties-common
|
||||
|
||||
To perform the Hass.io installation, run the following command as root:
|
||||
|
||||
```bash
|
||||
curl -sL https://raw.githubusercontent.com/home-assistant/hassio-build/master/install/hassio_install | bash -s
|
||||
$ curl -sL https://raw.githubusercontent.com/home-assistant/hassio-build/master/install/hassio_install | bash -s
|
||||
```
|
||||
|
||||
<p class='note'>
|
||||
|
||||
BIN
source/images/components/netdata/details.png
Normal file
BIN
source/images/components/netdata/details.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 35 KiB |
Loading…
x
Reference in New Issue
Block a user