mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-18 23:06:58 +00:00
🔨 Replaces all hardlinks with relative ones (#8207)
This commit is contained in:
Franck Nijhof
Joakim Sørensen
parent
3a43b537d9
commit
69a0bfd29a
@ -57,7 +57,7 @@ To use the Mosquitto as [broker](/docs/mqtt/broker/#run-your-own), go to the int
|
||||
|
||||
#### {% linkable_title Using Mosquitto with Hass.io %}
|
||||
|
||||
1. Install the [Mosquitto add-on](https://www.home-assistant.io/addons/mosquitto/) with the default configuration via 'Hass.io > ADD-ON STORE'. (Don't forget to start the add-on & verify that 'Start on boot' is enabled.)
|
||||
1. Install the [Mosquitto add-on](/addons/mosquitto/) with the default configuration via 'Hass.io > ADD-ON STORE'. (Don't forget to start the add-on & verify that 'Start on boot' is enabled.)
|
||||
|
||||
2. Create a new user for MQTT via the `Configuration > Users (manage users)`. (Note: This name cannot be "homeassistant" or "addon")
|
||||
|
||||
@ -71,7 +71,7 @@ To use the Mosquitto as [broker](/docs/mqtt/broker/#run-your-own), go to the int
|
||||
```
|
||||
|
||||
Note: .yaml modifications are not required.
|
||||
See [testing your setup](https://www.home-assistant.io/docs/mqtt/testing/) to verify the steps above.
|
||||
See [testing your setup](/docs/mqtt/testing/) to verify the steps above.
|
||||
|
||||
### {% linkable_title Disable listening on insecure (1883) ports %}
|
||||
|
||||
|
||||
@ -91,7 +91,7 @@ zones:
|
||||
required: true
|
||||
type: string
|
||||
type:
|
||||
description: "A type for the zone. Here you can find a list of [Device Classes](https://www.home-assistant.io/components/binary_sensor/#device-class)."
|
||||
description: "A type for the zone. Here you can find a list of [Device Classes](/components/binary_sensor/#device-class)."
|
||||
required: false
|
||||
default: opening
|
||||
type: string
|
||||
|
||||
@ -19,7 +19,7 @@ The platform does not directly interact with the buttons, *but communicates with
|
||||
|
||||
#### {% linkable_title Service setup %}
|
||||
|
||||
If you are using Hass.io, you can run the service locally by [installing](https://www.home-assistant.io/hassio/installing_third_party_addons/) the flicd add-on from [pschmitt's repository](https://github.com/pschmitt/hassio-addons). On a Hass.io installation that's not yet based on HassOS, you also need to install the [bluetooth add-on](/addons/bluetooth_bcm43xx/).
|
||||
If you are using Hass.io, you can run the service locally by [installing](/hassio/installing_third_party_addons/) the flicd add-on from [pschmitt's repository](https://github.com/pschmitt/hassio-addons). On a Hass.io installation that's not yet based on HassOS, you also need to install the [bluetooth add-on](/addons/bluetooth_bcm43xx/).
|
||||
|
||||
For instructions on how to install the service manually, visit the GitHub repository of the service for [Linux](https://github.com/50ButtonsEach/fliclib-linux-hci), [OS X](https://github.com/50ButtonsEach/flic-service-osx) or [Windows](https://github.com/50ButtonsEach/fliclib-windows).
|
||||
|
||||
|
||||
@ -31,5 +31,5 @@ Each Point exposes the following binary sensors:
|
||||
For installation instructions, see [the Point component](/components/point/).
|
||||
|
||||
<p class='note'>
|
||||
The events sent from the Point is also sent as a webhook back to Home Assistant with `event_type` as `point_webhook_received`, please consider the documentation for the [IFTT](https://www.home-assistant.io/components/ifttt/) component on how to write automations for webhooks.
|
||||
The events sent from the Point is also sent as a webhook back to Home Assistant with `event_type` as `point_webhook_received`, please consider the documentation for the [IFTT](/components/ifttt/) component on how to write automations for webhooks.
|
||||
</p>
|
||||
|
||||
@ -17,7 +17,7 @@ The `rainmachine` binary sensor platform allows you to view crucial sensor data
|
||||
within a [RainMachine smart Wi-Fi sprinkler controller](http://www.rainmachine.com/).
|
||||
|
||||
<p class='note'>
|
||||
You must have the [RainMachine component](https://www.home-assistant.io/components/rainmachine/)
|
||||
You must have the [RainMachine component](/components/rainmachine/)
|
||||
configured to use this platform. After configuring that component, binary
|
||||
sensors automatically appear.
|
||||
</p>
|
||||
|
||||
@ -96,6 +96,6 @@ automation:
|
||||
```
|
||||
|
||||
<p class='note'>
|
||||
Please remember that [as explained here](https://www.home-assistant.io/docs/configuration/devices/) you can only have a single `automation:` entry. Add the automation to your existing automations.
|
||||
Please remember that [as explained here](/docs/configuration/devices/) you can only have a single `automation:` entry. Add the automation to your existing automations.
|
||||
</p>
|
||||
|
||||
|
||||
@ -22,7 +22,7 @@ This component provides the following platforms:
|
||||
- Device tracker: The location of your car.
|
||||
- Lock: Control the lock of your car.
|
||||
- Sensors: Mileage, remaining range, remaining fuel, charging time remaining (electric cars), charging status (electric cars), remaining range electric (electric cars).
|
||||
- Services: Turn on air condition, sound the horn, flash the lights and update the state. More details can be found [here](https://www.home-assistant.io/components/bmw_connected_drive/#services).
|
||||
- Services: Turn on air condition, sound the horn, flash the lights and update the state. More details can be found [here](/components/bmw_connected_drive/#services).
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
|
||||
@ -17,7 +17,7 @@ The `ffmpeg` platform allows you to use any video feed as a camera in Home Assis
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
To enable your FFmpeg feed in your installation you must first configure the [ffmpeg component](https://www.home-assistant.io/components/ffmpeg/), then add the following to your `configuration.yaml` file:
|
||||
To enable your FFmpeg feed in your installation you must first configure the [ffmpeg component](/components/ffmpeg/), then add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
||||
@ -45,4 +45,4 @@ Devices will appear in the format `devicetracker.<home hub ip>_<device mac addre
|
||||
After running this component for a little while, you will likely see many devices appear. It's advisable to set the configuration to not discover new devices once the device you want to track have appeared (see [device tracker configuration][devicetrackerconfig] for details).
|
||||
|
||||
[googlehomeapi]: https://rithvikvibhu.github.io/GHLocalApi/
|
||||
[devicetrackerconfig]: https://www.home-assistant.io/components/device_tracker/#configuring-a-device_tracker-platform
|
||||
[devicetrackerconfig]: /components/device_tracker/#configuring-a-device_tracker-platform
|
||||
|
||||
@ -16,7 +16,7 @@ redirect_from: /components/apiai/
|
||||
|
||||
The `dialogflow` component is designed to be used with the [webhook](https://dialogflow.com/docs/fulfillment#webhook) integration of [Dialogflow](https://dialogflow.com/). When a conversation ends with a user, Dialogflow sends an action and parameters to the webhook.
|
||||
|
||||
To be able to receive messages from DialogFlow, your Home Assistant instance needs to be accessible from the web ([Hass.io instructions](/addons/duckdns/)) and you need to have the `base_url` configured for the HTTP component ([docs](https://www.home-assistant.io/components/http/#base_url)). Dialogflow will return fallback answers if your server does not answer or takes too long (more than 5 seconds).
|
||||
To be able to receive messages from DialogFlow, your Home Assistant instance needs to be accessible from the web ([Hass.io instructions](/addons/duckdns/)) and you need to have the `base_url` configured for the HTTP component ([docs](/components/http/#base_url)). Dialogflow will return fallback answers if your server does not answer or takes too long (more than 5 seconds).
|
||||
|
||||
Dialogflow could be [integrated](https://dialogflow.com/docs/integrations/) with many popular messaging, virtual assistant and IoT platforms.
|
||||
|
||||
|
||||
@ -17,7 +17,7 @@ featured: false
|
||||
The [Homematic](http://www.homematic.com/) component provides bi-directional communication with your CCU/Homegear. It uses a XML-RPC connection to set values on devices and subscribes to receive events the devices and the CCU emit.
|
||||
If you are using Homegear with paired [Intertechno](http://intertechno.at/) devices, uni-directional communication is possible as well.
|
||||
|
||||
Device support is available for most of the wired and wireless devices, as well as a lot of IP devices. If you have a setup with mixed protocols, you have to configure additional [interfaces](https://www.home-assistant.io/components/homematic#interfaces) with the appropriate ports. The default is using port 2001, which are wireless devices. Wired devices usually are available through port 2000 and IP devices through port 2010. The virtual thermostatgroups the CCU provides use port 9292 **and** require you to set the `path` setting to `/groups`. When using SSL on a CCU3, by default the same ports as usual with a prepended 4 are available. So 2001 becomes 42001, 2010 becomes 42010 etc..
|
||||
Device support is available for most of the wired and wireless devices, as well as a lot of IP devices. If you have a setup with mixed protocols, you have to configure additional [interfaces](/components/homematic#interfaces) with the appropriate ports. The default is using port 2001, which are wireless devices. Wired devices usually are available through port 2000 and IP devices through port 2010. The virtual thermostatgroups the CCU provides use port 9292 **and** require you to set the `path` setting to `/groups`. When using SSL on a CCU3, by default the same ports as usual with a prepended 4 are available. So 2001 becomes 42001, 2010 becomes 42010 etc..
|
||||
|
||||
If you want to see if a specific device you have is supported, head over to the [pyhomematic](https://github.com/danielperna84/pyhomematic/tree/master/pyhomematic/devicetypes) repository and browse through the source code. A dictionary with the device identifiers (e.g., HM-Sec-SC-2) can be found within the relevant modules near the bottom. If your device is not supported, feel free to contribute.
|
||||
|
||||
|
||||
@ -17,7 +17,7 @@ ha_iot_class: "Cloud Push"
|
||||
|
||||
## {% linkable_title Sending events from IFTTT to Home Assistant %}
|
||||
|
||||
To be able to receive events from IFTTT, your Home Assistant instance needs to be accessible from the web ([Hass.io instructions](/addons/duckdns/)) and you need to have the `base_url` configured for the HTTP component ([docs](https://www.home-assistant.io/components/http/#base_url)).
|
||||
To be able to receive events from IFTTT, your Home Assistant instance needs to be accessible from the web ([Hass.io instructions](/addons/duckdns/)) and you need to have the `base_url` configured for the HTTP component ([docs](/components/http/#base_url)).
|
||||
|
||||
To set it up, go to the integrations page in the configuration screen and find IFTTT. Click on configure. Follow the instructions on the screen to configure IFTTT.
|
||||
|
||||
|
||||
@ -77,7 +77,7 @@ source:
|
||||
|
||||
## {% linkable_title Automations %}
|
||||
|
||||
Use the `image_processing.detect_face` events to trigger automations, and breakout the `trigger.event.data` using a [data_template](https://www.home-assistant.io/docs/automation/templating/). The following example automation sends a notification when Ringo Star is recognized:
|
||||
Use the `image_processing.detect_face` events to trigger automations, and breakout the `trigger.event.data` using a [data_template](/docs/automation/templating/). The following example automation sends a notification when Ringo Star is recognized:
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
@ -139,7 +139,7 @@ You can use an automation to receive a notification when you train a face:
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
Any errors on teaching will be reported in the logs. If you enable [system_log](https://www.home-assistant.io/components/system_log/) events:
|
||||
Any errors on teaching will be reported in the logs. If you enable [system_log](/components/system_log/) events:
|
||||
|
||||
```yaml
|
||||
system_log:
|
||||
|
||||
@ -160,4 +160,4 @@ image_processing:
|
||||
|
||||
## {% linkable_title Optimising resources %}
|
||||
|
||||
[Image processing components](https://www.home-assistant.io/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.
|
||||
[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.
|
||||
|
||||
@ -181,7 +181,7 @@ In order for any two Insteon devices to talk with one another, they must be link
|
||||
If you are looking for more advanced options, you can use the [insteonplm_interactive] command line tool that is distributed with the [insteonplm] Python module. Please see the documentation on the [insteonplm] GitHub site. Alternatively, you can download [HouseLinc] which runs on any Windows PC, or you can use [Insteon Terminal] which is open source and runs on most platforms. SmartHome no longer supports HouseLinc, but it still works. Insteon Terminal is a very useful tool but please read the disclaimers carefully, they are important.
|
||||
|
||||
[understanding linking]: http://www.insteon.com/support-knowledgebase/2015/1/28/understanding-linking
|
||||
[Development Tools]: https://www.home-assistant.io/docs/tools/dev-tools/
|
||||
[Development Tools]: /docs/tools/dev-tools/
|
||||
[HouseLinc]: https://www.smarthome.com/houselinc.html
|
||||
[Insteon Terminal]: https://github.com/pfrommerd/insteon-terminal
|
||||
[insteonplm_interactive]: https://github.com/nugget/python-insteonplm#command-line-interface
|
||||
|
||||
@ -21,7 +21,7 @@ The component currently supports the following device types in Home Assistant:
|
||||
- [Binary Sensor](/components/binary_sensor.konnected/): Wired door and window sensors, motion detectors, glass-break detectors, leak sensors, smoke & CO detectors or any open/close switch.
|
||||
- [Switch](/components/switch.konnected/): Actuate a siren, strobe, buzzer or relay module.
|
||||
|
||||
This component requires the [`discovery`](https://www.home-assistant.io/components/discovery) component to be enabled.
|
||||
This component requires the [`discovery`](/components/discovery) component to be enabled.
|
||||
|
||||
### {% linkable_title Configuration %}
|
||||
|
||||
|
||||
@ -18,7 +18,7 @@ ha_release: 0.67
|
||||
|
||||
The `nanoleaf_aurora` platform allows you to control [Nanoleaf Aurora Light Panels](https://nanoleaf.me) from Home Assistant.
|
||||
|
||||
The preferred way to set up this platform is by enabling the [discovery component](https://www.home-assistant.io/components/discovery/). Make sure to press and hold the *ON* button for 5 seconds (the LED will start flashing) on your Nanoleaf Aurora Panel while Home Assistant is starting.
|
||||
The preferred way to set up this platform is by enabling the [discovery component](/components/discovery/). Make sure to press and hold the *ON* button for 5 seconds (the LED will start flashing) on your Nanoleaf Aurora Panel while Home Assistant is starting.
|
||||
|
||||
To configure the Aurora lights manually, add the following lines to your `configuration.yaml` file:
|
||||
|
||||
|
||||
@ -12,7 +12,7 @@ ha_category: Notifications
|
||||
ha_release: 0.38
|
||||
---
|
||||
|
||||
To be able to receive webhooks from Mailgun, your Home Assistant instance needs to be accessible from the web ([Hass.io instructions](/addons/duckdns/)) and you need to have the `base_url` configured for the HTTP component ([docs](https://www.home-assistant.io/components/http/#base_url)).
|
||||
To be able to receive webhooks from Mailgun, your Home Assistant instance needs to be accessible from the web ([Hass.io instructions](/addons/duckdns/)) and you need to have the `base_url` configured for the HTTP component ([docs](/components/http/#base_url)).
|
||||
|
||||
To set it up, go to the integrations page in the configuration screen and find Mailgun. Click on configure. Follow the instructions on the screen to configure Mailgun.
|
||||
|
||||
|
||||
@ -15,7 +15,7 @@ ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
|
||||
The `plex` platform allows you to connect to a [Plex Media Server](https://plex.tv). Once connected, [Plex Clients](https://www.plex.tv/apps-devices/) playing media from the connected Plex Media Server will show up as [Media Players](https://www.home-assistant.io/components/media_player/) in Home Assistant. It will allow you to control media playback and see the current playing item.
|
||||
The `plex` platform allows you to connect to a [Plex Media Server](https://plex.tv). Once connected, [Plex Clients](https://www.plex.tv/apps-devices/) playing media from the connected Plex Media Server will show up as [Media Players](/components/media_player/) in Home Assistant. It will allow you to control media playback and see the current playing item.
|
||||
|
||||
## {% linkable_title Setup %}
|
||||
|
||||
|
||||
@ -41,5 +41,5 @@ client_secret:
|
||||
|
||||
<p class='note'>
|
||||
The Point is just active occasionally so the sensors are only updated every hour or so.
|
||||
The events sent from the Point is sent as a webhook back to Home Assistant with `event_type` as `point_webhook_received`, please consider the documentation for the [IFTT](https://www.home-assistant.io/components/ifttt/) component on how to write automations for webhooks.
|
||||
The events sent from the Point is sent as a webhook back to Home Assistant with `event_type` as `point_webhook_received`, please consider the documentation for the [IFTT](/components/ifttt/) component on how to write automations for webhooks.
|
||||
</p>
|
||||
|
||||
@ -75,7 +75,7 @@ sensors:
|
||||
default: false
|
||||
type: string
|
||||
class:
|
||||
description: The [class](https://www.home-assistant.io/components/binary_sensor) or binary_sensor. Only applicable to binary_sensors.
|
||||
description: The [class](components/binary_sensor) or binary_sensor. Only applicable to binary_sensors.
|
||||
required: false
|
||||
default: door
|
||||
type: string
|
||||
|
||||
@ -20,7 +20,7 @@ The `mitemp_bt` sensor platform allows one to monitor room temperature and humid
|
||||
Depending on the operating system you're running, you have to configure the proper Bluetooth backend on your system:
|
||||
|
||||
- On [Hass.io](/hassio/installation/): `mitemp_bt` will work out of the box as long as the host supports Bluetooth (like the Raspberry Pi does).
|
||||
- On a [generic Docker installation](https://www.home-assistant.io/docs/installation/docker/): Works out of the box with `--net=host` and properly configured Bluetooth on the host.
|
||||
- On a [generic Docker installation](/docs/installation/docker/): Works out of the box with `--net=host` and properly configured Bluetooth on the host.
|
||||
- On other Linux systems:
|
||||
- Preferred solution: Install the `bluepy` and `btlewrap` library (via pip). When using a virtual environment, make sure to use install the library in the right one.
|
||||
- Fallback solution: Install `btlewrap` library (via pip) and `gatttool` via your package manager. Depending on the distribution, the package name might be: `bluez`, `bluetooth` or `bluez-deprecated`.
|
||||
|
||||
@ -17,7 +17,7 @@ The `rainmachine` sensor platform allows you to view crucial sensor data within
|
||||
a [RainMachine smart Wi-Fi sprinkler controller](http://www.rainmachine.com/).
|
||||
|
||||
<p class='note'>
|
||||
You must have the [RainMachine component](https://www.home-assistant.io/components/rainmachine/)
|
||||
You must have the [RainMachine component](/components/rainmachine/)
|
||||
configured to use this platform. After configuring that component, sensors
|
||||
automatically appear.
|
||||
</p>
|
||||
|
||||
@ -14,7 +14,7 @@ ha_release: 0.83
|
||||
---
|
||||
|
||||
<p class='note warning'>
|
||||
The API used for this sensor is shutting down soon, you should consider starting to use the [`entur_public_transport`](https://www.home-assistant.io/components/sensor.entur_public_transport/) sensor before that happen.
|
||||
The API used for this sensor is shutting down soon, you should consider starting to use the [`entur_public_transport`](/components/sensor.entur_public_transport/) sensor before that happen.
|
||||
To read the deprecation warning visit [ruter.no/labs](https://ruter.no/labs/),
|
||||
</p>
|
||||
|
||||
|
||||
@ -17,7 +17,7 @@ The `rainmachine` switch platform allows you to control programs and zones
|
||||
within a [RainMachine smart Wi-Fi sprinkler controller](http://www.rainmachine.com/).
|
||||
|
||||
<p class='note'>
|
||||
You must have the [RainMachine component](https://www.home-assistant.io/components/rainmachine/)
|
||||
You must have the [RainMachine component](/components/rainmachine/)
|
||||
configured to use this platform. After configuring that component, switches will
|
||||
automatically appear.
|
||||
</p>
|
||||
|
||||
@ -43,7 +43,7 @@ auth_token:
|
||||
|
||||
After configuring the base Twilio component, add and configure either or both of the [twilio SMS](/components/notify.twilio_sms/) and [twilio Phone](/components/notify.twilio_call) components to utilize the notification functionality.
|
||||
|
||||
To be able to receive events from Twilio, your Home Assistant instance needs to be accessible from the web ([Hass.io instructions](/addons/duckdns/)) and you need to have the `base_url` configured for the HTTP component ([docs](https://www.home-assistant.io/components/http/#base_url)).
|
||||
To be able to receive events from Twilio, your Home Assistant instance needs to be accessible from the web ([Hass.io instructions](/addons/duckdns/)) and you need to have the `base_url` configured for the HTTP component ([docs](/components/http/#base_url)).
|
||||
|
||||
To set it up, go to the integrations page in the configuration screen and find Twilio. Click on configure. Follow the instructions on the screen to configure Twilio.
|
||||
|
||||
|
||||
@ -65,7 +65,7 @@ TOTP is _time based_ so it relies on your Home Assistant clock being accurate. I
|
||||
|
||||
### {% linkable_title Notify multi-factor authentication module %}
|
||||
|
||||
The Notify MFA module uses the [notify component](https://www.home-assistant.io/components/notify/) to send you an [HMAC-based One-Time Password](https://en.wikipedia.org/wiki/HMAC-based_One-time_Password_algorithm). It is typically sent to your phone, but can be sent to any destination supported by a `notify` service. You use this password to log in.
|
||||
The Notify MFA module uses the [notify component](/components/notify/) to send you an [HMAC-based One-Time Password](https://en.wikipedia.org/wiki/HMAC-based_One-time_Password_algorithm). It is typically sent to your phone, but can be sent to any destination supported by a `notify` service. You use this password to log in.
|
||||
|
||||
#### {% linkable_title Setting up TOTP %}
|
||||
|
||||
|
||||
@ -38,7 +38,7 @@ If you run into trouble while configuring Home Assistant, have a look at the [co
|
||||
You will have to restart Home Assistant for most changes to `configuration.yaml` to take effect. You can load changes to [automations](/docs/automation/), [customize](/docs/configuration/customizing-devices/), [groups](/components/group/), and [scripts](/components/script/) without restarting if you're not using [packages](/docs/configuration/packages/).
|
||||
|
||||
<p class='note warning'>
|
||||
If you've made any changes, remember to [check your configuration](https://www.home-assistant.io/docs/configuration/troubleshooting/#problems-with-the-configuration) before trying to reload or restart.
|
||||
If you've made any changes, remember to [check your configuration](/docs/configuration/troubleshooting/#problems-with-the-configuration) before trying to reload or restart.
|
||||
</p>
|
||||
|
||||
## {% linkable_title Migrating to a new system %}
|
||||
|
||||
@ -55,4 +55,4 @@ For remote access for a component, for example, a device tracker, you have to en
|
||||
* A [self-signed certificate](/cookbook/tls_self_signed_certificate/) - be warned though, some services will refuse to work with self-signed certificates
|
||||
3. Optionally use a proxy like [NGINX](/docs/ecosystem/nginx/), [Apache](/cookbook/apache_configuration/), or another. These allow you to provide finer-grained access. You could use this to limit access to specific parts of the API (for example, only `/api/owntracks/`)
|
||||
4. Enable IP Filtering and configure a low [Login Attempts Threshold](/components/http/)
|
||||
5. If you use a proxy then install [fail2ban](https://www.fail2ban.org/wiki/index.php/Main_Page) to [monitor your proxy logs](https://www.home-assistant.io/cookbook/fail2ban/) (or Home Assistant logs) for failed authentication
|
||||
5. If you use a proxy then install [fail2ban](https://www.fail2ban.org/wiki/index.php/Main_Page) to [monitor your proxy logs](/cookbook/fail2ban/) (or Home Assistant logs) for failed authentication
|
||||
|
||||
@ -26,7 +26,7 @@ If you have incorrect entries in your configuration files you can use the [`chec
|
||||
|
||||
One of the most common problems with Home Assistant is an invalid `configuration.yaml` file.
|
||||
|
||||
- You can test your configuration using the command line with: `hass --script check_config`. On Hass.io you can use the [hassio command](https://www.home-assistant.io/hassio/commandline/#home-assistant): `hassio homeassistant check`.
|
||||
- You can test your configuration using the command line with: `hass --script check_config`. On Hass.io you can use the [hassio command](/hassio/commandline/#home-assistant): `hassio homeassistant check`.
|
||||
- You can verify your configuration's yaml structure using [this online YAML parser](http://yaml-online-parser.appspot.com/) or [YAML Lint](http://www.yamllint.com/).
|
||||
- To learn more about the quirks of YAML, read [YAML IDIOSYNCRASIES](https://docs.saltstack.com/en/latest/topics/troubleshooting/yaml_idiosyncrasies.html) by SaltStack (the examples there are specific to SaltStack, but do explain YAML issues well).
|
||||
|
||||
|
||||
@ -42,4 +42,4 @@ You can get more information on the [available services](/docs/z-wave/services/)
|
||||
|
||||
When you toggle a switch or control a light locally you may find that it takes some time for that to be reflected in Home Assistant. That's because Lutron had patents on the status updates using the *Hail* command class, the traditional way of allowing devices to tell the controller that something happened locally. The same result can be achieved through the *Association* command class, or *Central Scene* command class (though, *Central Scene* isn't [fully supported](https://github.com/OpenZWave/open-zwave/pull/1125) in OpenZWave).
|
||||
|
||||
If you search [the Z-Wave products database](http://products.z-wavealliance.org/) for your product and it lists one of those in the **Controlled** command classes (not the **Supported** command classes), then your device will be able to report state changes when they happen. If it doesn't then updates may either happen eventually, or you may need to (carefully) [enable polling](https://www.home-assistant.io/docs/z-wave/control-panel/#entities-of-this-node).
|
||||
If you search [the Z-Wave products database](http://products.z-wavealliance.org/) for your product and it lists one of those in the **Controlled** command classes (not the **Supported** command classes), then your device will be able to report state changes when they happen. If it doesn't then updates may either happen eventually, or you may need to (carefully) [enable polling](/docs/z-wave/control-panel/#entities-of-this-node).
|
||||
|
||||
@ -63,7 +63,7 @@ network_key:
|
||||
type: string
|
||||
default: None
|
||||
config_path:
|
||||
description: "The path to the Python OpenZWave configuration files. NOTE: there is also the [update_config service](https://www.home-assistant.io/docs/z-wave/services/) to perform updating the config within python-openzwave automatically."
|
||||
description: "The path to the Python OpenZWave configuration files. NOTE: there is also the [update_config service](/docs/z-wave/services/) to perform updating the config within python-openzwave automatically."
|
||||
required: false
|
||||
type: string
|
||||
default: the 'config' that is installed by python-openzwave
|
||||
|
||||
@ -12,7 +12,7 @@ footer: true
|
||||
|
||||
The Shopping List Card allows you to add, edit, check-off, and clear items from your shopping list.
|
||||
|
||||
Setup of the [Shopping List Intent](https://www.home-assistant.io/components/shopping_list/) is required
|
||||
Setup of the [Shopping List Intent](/components/shopping_list/) is required
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/lovelace_shopping_list_card.gif' alt='Screenshot of the shopping list card'>
|
||||
|
||||
@ -43,5 +43,5 @@ name:
|
||||
<p class="note">
|
||||
This card works only with platforms that define a `weather` entity.
|
||||
|
||||
E.g., it works with [Dark Sky](https://www.home-assistant.io/components/weather.darksky/) but not [Dark Sky Sensor](https://www.home-assistant.io/components/sensor.darksky/)
|
||||
E.g., it works with [Dark Sky](/components/weather.darksky/) but not [Dark Sky Sensor](/components/sensor.darksky/)
|
||||
</p>
|
||||
|
||||
@ -58,7 +58,7 @@ Once our new installation images with HassioOS are released, you have to reflash
|
||||
- Restore your snapshot.
|
||||
- Enjoy a new and improved Hass.io
|
||||
|
||||
[last July]: https://www.home-assistant.io/blog/2017/07/25/introducing-hassio/
|
||||
[last July]: /blog/2017/07/25/introducing-hassio/
|
||||
[the conclusion]: #what-hassio-users-should-do-to-prepare-for-these-updates
|
||||
[Buildroot]: https://buildroot.org/
|
||||
[RAUC]: https://www.rauc.io/
|
||||
|
||||
@ -11,7 +11,7 @@ categories: Release-Notes
|
||||
og_image: /images/blog/2018-07-0.73/lovelace-elements.png
|
||||
---
|
||||
|
||||
Today we're releasing Home Assistant 0.73. First, let's talk security. Home Assistant has a lot of power. It can control all devices in your house and know what you're up to. That's why securing it is very important. It's absolutely wrong to connect your instance unsecured to the internet and hope no one will find it. All ports on all computers are regularly scanned by bad actors. Please read [our guidelines thoroughly](https://www.home-assistant.io/docs/configuration/securing/) and follow them.
|
||||
Today we're releasing Home Assistant 0.73. First, let's talk security. Home Assistant has a lot of power. It can control all devices in your house and know what you're up to. That's why securing it is very important. It's absolutely wrong to connect your instance unsecured to the internet and hope no one will find it. All ports on all computers are regularly scanned by bad actors. Please read [our guidelines thoroughly](/docs/configuration/securing/) and follow them.
|
||||
|
||||
In the meanwhile, we're also working hard on the new authentication system. A preview version is included in this release, more info on [our developer blog](https://developers.home-assistant.io/blog/2018/07/02/trying-new-auth.html).
|
||||
|
||||
|
||||
@ -60,5 +60,5 @@ Feel free to jump into the project and help us to improve the documentation or o
|
||||
[Buildroot]: https://buildroot.org/
|
||||
[AppArmor]: https://gitlab.com/apparmor/apparmor/wikis/home/
|
||||
[USB stick]: https://github.com/home-assistant/hassos/blob/rel-1/Documentation/configuration.md#automatic
|
||||
[installation]: https://www.home-assistant.io/hassio/installation/
|
||||
[installation]: /hassio/installation/
|
||||
[Etcher]: https://etcher.io/
|
||||
|
||||
@ -37,8 +37,8 @@ There are many different ways to run Home Assistant. In this section please ment
|
||||
|
||||
Please add the link to the documention of the component/platform in question. E.g.,
|
||||
|
||||
- issue with the `random` sensor: [https://www.home-assistant.io/components/sensor.random/](/components/sensor.random/)
|
||||
- issue with the `hue` component: [https://www.home-assistant.io/components/hue/](/components/hue/)
|
||||
- issue with the `random` sensor: [/components/sensor.random/](/components/sensor.random/)
|
||||
- issue with the `hue` component: [/components/hue/](/components/hue/)
|
||||
|
||||
### {% linkable_title Description of problem %}
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user