mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-09 18:36:51 +00:00
Merge branch 'current' into next
This commit is contained in:
Franck Nijhof
commit
f88a51495e
@ -54,14 +54,6 @@ $ha__primary_color: #03a9f4;
|
||||
max-width: 1000px;
|
||||
margin: auto;
|
||||
|
||||
.sub-title {
|
||||
font-weight: bold;
|
||||
font-size: 42px;
|
||||
line-height: 49px;
|
||||
margin: 32px;
|
||||
text-align: center;
|
||||
}
|
||||
|
||||
.missing-piece {
|
||||
z-index: 2;
|
||||
position: relative;
|
||||
|
||||
@ -1,5 +1,6 @@
|
||||
.feature-cards {
|
||||
display: grid;
|
||||
letter-spacing: normal;
|
||||
grid-template-columns: repeat(2, 1fr);
|
||||
gap: 32px;
|
||||
margin: auto;
|
||||
@ -43,6 +44,15 @@
|
||||
}
|
||||
}
|
||||
|
||||
.sub-title {
|
||||
letter-spacing: normal;
|
||||
font-weight: bold;
|
||||
font-size: 42px;
|
||||
line-height: 49px;
|
||||
margin: 32px;
|
||||
text-align: center;
|
||||
}
|
||||
|
||||
@media only screen and (max-width: $palm-end) {
|
||||
.feature-cards {
|
||||
width: 95%;
|
||||
|
||||
@ -1,3 +1,4 @@
|
||||
{% assign percentage = 100.0 | times: site.data.analytics_data.integrations[page.ha_domain] | divided_by: site.data.analytics_data.reports_integrations | round: 1 %}
|
||||
<section class="aside-module grid__item one-whole lap-one-half">
|
||||
|
||||
<div class='brand-logo-container section'>
|
||||
@ -20,8 +21,13 @@
|
||||
|
||||
<div class='section'>
|
||||
The {{ page.name | default: page.title }} integration was introduced in Home Assistant {{ page.ha_release | default: "unknown" }},
|
||||
and it's used by <a title="Open analytics.home-assistant.io" href="https://analytics.home-assistant.io" target="_blank" rel="noopener">
|
||||
{{ 100.0 | times: site.data.analytics_data.integrations[page.ha_domain] | divided_by: site.data.analytics_data.reports_integrations | round: 1 | remove: ".0" }}%</a> of the active installations.
|
||||
and it's used by <a title="Open analytics.home-assistant.io" href="https://analytics.home-assistant.io/#integrations" target="_blank" rel="noopener">
|
||||
|
||||
{% if percentage < 1 %}
|
||||
{{ site.data.analytics_data.integrations[page.ha_domain] }}</a> active installations.
|
||||
{% else %}
|
||||
{{ percentage | remove: ".0" }}%</a> of the active installations.
|
||||
{% endif %}
|
||||
|
||||
{%- if page.ha_iot_class %}
|
||||
Its IoT class is <a href='/blog/2016/02/12/classifying-the-internet-of-things/#classifiers'>{{ page.ha_iot_class }}</a>
|
||||
|
||||
@ -49,7 +49,7 @@
|
||||
<ul>
|
||||
<li>Run AdGuard, a DNS-based ad blocker</li>
|
||||
<li>Run third party automation engines like NodeRed</li>
|
||||
<li>Turn Home Assistant Blue into a Spotify Connect target</li>
|
||||
<li>Turn Home Assistant into a Spotify Connect target</li>
|
||||
</ul>
|
||||
<a class="button" href="/addons">EXPLORE ADD-ONS</a>
|
||||
</div>
|
||||
|
||||
@ -1,51 +0,0 @@
|
||||
<h2 class="title">Observe</h2>
|
||||
<hr>
|
||||
<p>Home Assistant will track the state of all the devices in your home, so you don't have to.</p>
|
||||
<div class="supported-brands clearfix">
|
||||
<a href="/integrations/ecobee/">
|
||||
<img alt="Ecobee" src="https://brands.home-assistant.io/ecobee/logo.png"/>
|
||||
</a>
|
||||
<a href="/integrations/hue/">
|
||||
<img alt="Philips Hue" src="https://brands.home-assistant.io/hue/logo.png"/>
|
||||
</a>
|
||||
<a href="/integrations/cast/">
|
||||
<img alt="Google Cast" src="https://brands.home-assistant.io/cast/logo.png"/>
|
||||
</a>
|
||||
<a href="/integrations/google_assistant/">
|
||||
<img alt="Google Assistant" src="https://brands.home-assistant.io/google_assistant/logo.png"/>
|
||||
</a>
|
||||
<a href="/integrations/mqtt/">
|
||||
<img alt="MQTT" src="https://brands.home-assistant.io/mqtt/logo.png"/>
|
||||
</a>
|
||||
<a href="/integrations/wemo/">
|
||||
<img alt="Belkin WeMo" src="https://brands.home-assistant.io/wemo/logo.png"/>
|
||||
</a>
|
||||
<a href="/integrations/shelly/">
|
||||
<img alt="Shelly" src="https://brands.home-assistant.io/shelly/logo.png"/>
|
||||
</a>
|
||||
<a href="/integrations/kodi/">
|
||||
<img alt="Kodi" src="https://brands.home-assistant.io/kodi/logo.png"/>
|
||||
</a>
|
||||
<a href="/integrations/plex/">
|
||||
<img alt="Plex" src="https://brands.home-assistant.io/plex/logo.png"/>
|
||||
</a>
|
||||
<a href="/integrations/tradfri/">
|
||||
<img alt="IKEA Tradfri" src="https://brands.home-assistant.io/tradfri/logo.png"/>
|
||||
</a>
|
||||
<a href="/integrations/vera/">
|
||||
<img alt="Vera" src="https://brands.home-assistant.io/vera/logo.png"/>
|
||||
</a>
|
||||
<a href="/integrations/sonos/">
|
||||
<img alt="Sonos" src="https://brands.home-assistant.io/sonos/logo.png"/>
|
||||
</a>
|
||||
<a href="/integrations/zha/">
|
||||
<img alt="Zigbee Home Automation" src="https://brands.home-assistant.io/zha/logo.png"/>
|
||||
</a>
|
||||
<a href="/integrations/zwave_js/">
|
||||
<img alt="Z-Wave JS" src="https://brands.home-assistant.io/zwave_js/logo.png"/>
|
||||
</a>
|
||||
</div>
|
||||
|
||||
<p class="pull-right">
|
||||
<a href="/integrations/">Browse all »</a>
|
||||
</p>
|
||||
@ -1,6 +0,0 @@
|
||||
<h2 class="title">Control</h2>
|
||||
<hr>
|
||||
<p>Control all your devices from a single, mobile-friendly, interface.</p>
|
||||
<p>
|
||||
Home Assistant allows you to control all your devices without storing any of your data in the cloud. We like to keep your privacy private.
|
||||
</p>
|
||||
@ -1,12 +0,0 @@
|
||||
<h2 class="title">Automate</h2>
|
||||
<hr>
|
||||
<p>Set up advanced rules to control devices and bring your home alive.</p>
|
||||
<p>Do you want to …</p>
|
||||
<ul>
|
||||
<li>have the lights turn on when the sun sets and you are home?</li>
|
||||
<li>have the lights turn on when anyone comes home and it is dark?</li>
|
||||
<li>dim the lights when you start watching a movie on your Chromecast?</li>
|
||||
<li>receive a message when the lights turn on while you are not at home?</li>
|
||||
</ul>
|
||||
<p><a href='/getting-started/automation/'>We've got you covered.</a></p>
|
||||
<p><a href='/examples/'>View examples by the community.</a></p>
|
||||
@ -6,5 +6,5 @@ Open source home automation that puts local control and privacy first. Powered b
|
||||
<p class='hero-buttons'>
|
||||
<a href='/getting-started/'>Get started</a>
|
||||
<a href='https://demo.home-assistant.io' target='_blank'>View demo</a>
|
||||
<a rel="me" href='https://github.com/home-assistant/home-assistant'>Browse code on GitHub</a>
|
||||
<a href='/integrations/'>Browse 1000+ integrations</a>
|
||||
</p>
|
||||
|
||||
@ -8,11 +8,40 @@ ha_quality_scale: internal
|
||||
ha_domain: binary_sensor
|
||||
---
|
||||
|
||||
Binary sensors gather information about the state of devices which have a "digital" return value (either 1 or 0). These can be switches, contacts, pins, etc. These sensors only have two states: **0/off/low/closed/false** and **1/on/high/open/true**. Knowing that there are only two states allows Home Assistant to represent these sensors in a better way in the frontend according to their functionality.
|
||||
Binary sensors are similar to other [sensors](/integrations/sensor) in that they
|
||||
monitor the states and conditions of different entities. Where binary sensors
|
||||
differ is they can only return one of two mutually exclusive values.
|
||||
For example, a binary sensor for a window may report a value
|
||||
of `open` or `closed`, a switch `on` or `off`, a condition `true` or `false`.
|
||||
|
||||
This *either/or* constraint is what makes these sensors binary. They are digital
|
||||
in nature, whereas analog sensors, like temperature and weight sensors,
|
||||
return a range of values.
|
||||
|
||||
Some binary sensors are created automatically when you add a device integration.
|
||||
For example, adding the [ecobee integration](/integrations/ecobee/) will create
|
||||
a binary sensor to detect room occupancy. Other binary sensors can be created
|
||||
manually using the [template integration](/integrations/template/)
|
||||
or using an [input boolean helper](/integrations/input_boolean),
|
||||
|
||||
### Device Class
|
||||
|
||||
The way these sensors are displayed in the frontend can be modified in the [customize section](/getting-started/customizing-devices/). The following device classes are supported for binary sensors:
|
||||
Knowing a sensor is binary impacts how the sensor's current state may be
|
||||
represented in Home Assistant's UI (see [Lovelace](/lovelace/)). Opposing states
|
||||
may be given different icons, colors, and value labels to highlight a particular
|
||||
state over the other. This is set by the binary sensor's device class.
|
||||
|
||||
Here are a few examples of this representation in the UI:
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/screenshots/binary_sensor_classes_icons.png' />
|
||||
Example of various device classes icons in `on` and `off` state. The on image
|
||||
in this example has `state_color: true` specified in the Entities card
|
||||
configuration to receive the icon coloring.
|
||||
</p>
|
||||
|
||||
The full list of supported binary sensor device classes is below
|
||||
*(note: these may also be modified in the [customizing section](/docs/configuration/customizing-devices)).*
|
||||
|
||||
- **None**: Generic on/off. This is the default and doesn't need to be set.
|
||||
- **battery**: `on` means low, `off` means normal
|
||||
@ -40,9 +69,4 @@ The way these sensors are displayed in the frontend can be modified in the [cust
|
||||
- **vibration**: `on` means vibration detected, `off` means no vibration (clear)
|
||||
- **window**: `on` means open, `off` means closed
|
||||
|
||||
For analog sensors please check the [integration overview](/integrations/sensor).
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/screenshots/binary_sensor_classes_icons.png' />
|
||||
Example of various device classes icons in `on` and `off` state. The on image in this example has `state_color: true` specified in the Entities card configuration to receive the icon coloring.
|
||||
</p>
|
||||
For comparison, here are the [device classes](https://www.home-assistant.io/integrations/sensor#device-class) for analog sensors.
|
||||
|
||||
@ -30,6 +30,15 @@ Supported devices (see Requirements section below):
|
||||
- Shades
|
||||
- Fireplaces
|
||||
|
||||
## Tested Bond Devices
|
||||
|
||||
The following devices have been tested with Home Assistant and confirmed to be working:
|
||||
|
||||
- Bond Bridge v1 (snowbird)
|
||||
- Bond Bridge v2 (zermatt)
|
||||
- Bond Bridge Pro (zermatt-pro)
|
||||
- Smart By Bond Fans (breck)
|
||||
|
||||
## Prerequisites
|
||||
|
||||
To use Bond controlled devices in your installation, add your Bond hub host and access token from the integrations page. Instructions for how to obtain an access token can be found on the [Bond Local API](http://docs-local.appbond.com/#section/Getting-Started/Get-Device-Information) documentation, which includes a section for how to obtain the [IP address of the device](http://docs-local.appbond.com/#section/Getting-Started/Finding-the-Bond-IP) which you will need to obtain the access token.
|
||||
|
||||
@ -31,7 +31,7 @@ Besides the weather platform, there is currently support for the following addit
|
||||
|
||||
## Camera
|
||||
|
||||
The `buienradar` camera platform uses [buienradar.nl](https://buienradar.nl/) as a source for the last rain radar map. The overview image of the whole of the Netherlands is loaded and shown as a camera in Home Assistant. The Netherlands is the default country and can be changed to Belgium (see [Setting options](#setting-options)).
|
||||
The `buienradar` camera platform uses [buienradar.nl](https://buienradar.nl/) as a source for the last rain radar map. The overview image of the whole of the Netherlands is loaded and shown as a camera in Home Assistant. The Netherlands is the default country and can be changed to Belgium (see [Options](#options)).
|
||||
|
||||
Internally this component uses the radar map image as [documented](https://www.buienradar.nl/overbuienradar/gratis-weerdata) on buienradar.nl.
|
||||
The downloaded image is cached to prevent Home Assistant from making a new request to buienradar.nl multiple times a minute when Home Assistant checks for new stills from the camera.
|
||||
|
||||
@ -19,6 +19,10 @@ ha_platforms:
|
||||
- switch
|
||||
---
|
||||
|
||||
<p class='note warning'>
|
||||
Daikin has removed their local API in newer products. They offer a cloud API accessible only under NDA, which is incompatible with open source.
|
||||
</p>
|
||||
|
||||
The `daikin` integration integrates Daikin air conditioning systems into Home Assistant.
|
||||
|
||||
There is currently support for the following device types within Home Assistant:
|
||||
|
||||
@ -64,8 +64,8 @@ keyboard_remote:
|
||||
- device_descriptor: '/dev/input/by-id/bluetooth-keyboard'
|
||||
type: "key_down"
|
||||
emulate_key_hold: true
|
||||
emulate_key_hold_delay: 250
|
||||
emulate_key_hold_repeat: 33
|
||||
emulate_key_hold_delay: 0.25
|
||||
emulate_key_hold_repeat: 0.033
|
||||
- device_descriptor: '/dev/input/event0'
|
||||
type:
|
||||
- 'key_up'
|
||||
|
||||
@ -1255,7 +1255,7 @@ state_address:
|
||||
required: true
|
||||
type: [string, list]
|
||||
type:
|
||||
description: A type from the value types table below must be defined. The DPT of the group address should match the expected KNX DPT to be parsed correctly.
|
||||
description: A type from the [value types table](/integrations/knx/#value-types) below must be defined. The DPT of the group address should match the expected KNX DPT to be parsed correctly.
|
||||
required: true
|
||||
type: [string, integer]
|
||||
name:
|
||||
|
||||
@ -82,6 +82,12 @@ commands:
|
||||
default: empty
|
||||
{% endconfiguration %}
|
||||
|
||||
<div class="note">
|
||||
|
||||
In order to prevent infinite loops when reacting to commands, you have to use a separate account for the Matrix integration.
|
||||
|
||||
</div>
|
||||
|
||||
### Event Data
|
||||
|
||||
If a command is triggered, a `matrix_command` event is fired. The event contains the name of the command in the `name` field.
|
||||
@ -190,3 +196,17 @@ action:
|
||||
images:
|
||||
- /path/to/picture.jpg
|
||||
```
|
||||
|
||||
<div class='note'>
|
||||
|
||||
If you need to include a file from an external folder in your notifications, you will have to [list the source folder as allowed](/docs/configuration/basic/).
|
||||
|
||||
```yaml
|
||||
configuration.yaml
|
||||
...
|
||||
homeassistant:
|
||||
allowlist_external_dirs:
|
||||
- /tmp
|
||||
```
|
||||
|
||||
</div>
|
||||
|
||||
@ -62,7 +62,7 @@ transparency:
|
||||
default: 25%
|
||||
type: string
|
||||
timeout:
|
||||
description: The timeout in seconds.
|
||||
description: The timeout in seconds for trying to send the notification to the device.
|
||||
required: false
|
||||
default: 5
|
||||
type: integer
|
||||
|
||||
@ -112,7 +112,7 @@ Some of the known valid key values are:
|
||||
- `down`
|
||||
- `left`
|
||||
- `right`
|
||||
- `select`
|
||||
- `enter`
|
||||
- `home`
|
||||
- `back`
|
||||
- `power`
|
||||
|
||||
@ -37,7 +37,7 @@ You have two options to choose from: webhook and `auth_token.` The webhook is on
|
||||
|
||||
### Auth Token
|
||||
|
||||
To be able to query the API an `auth_token` is required which can be obtained by following [these](https://plaato.zendesk.com/hc/en-us/articles/360003234717-Auth-token) instructions.
|
||||
To be able to query the API an `auth_token` is required which can be obtained by following [these](https://intercom.help/plaato/en/articles/5004720-auth_token) instructions.
|
||||
|
||||
### Webhook (Airlock only)
|
||||
|
||||
|
||||
@ -16,7 +16,7 @@ This integration adds an image processing entity where the state of the entity i
|
||||
|
||||
If `save_file_folder` is configured, on each new detection of a person, an annotated image with the name `sighthound_{camera_name}_latest.jpg` is saved in the configured folder if it doesn't already exist, and overwritten if it does exist. The saved image shows the bounding box around detected people and can be displayed on the Home Assistant front end using a [Local File](/integrations/local_file/) camera, and used in notifications. If `save_timestamped_file` is configured as `true`, then the annotated image is saved with a file name that includes the time of detection.
|
||||
|
||||
**Note** that by default the component will not automatically scan images, but requires you to call the `image_processing.scan` service, e.g., using an automation triggered by motion.
|
||||
**Note** that by default the component will not automatically scan images, but requires you to call the `image_processing.scan` service, e.g., using an automation triggered by motion.
|
||||
|
||||
## Configuration
|
||||
|
||||
@ -63,3 +63,45 @@ source:
|
||||
required: false
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
To verify the integration, check if a new entity is appeared as `image_processing.sighthound_my_cam`
|
||||
|
||||
## Process an Image
|
||||
|
||||
When you want to process an image, you have to call `image_processing.scan` service and listen to the `sighthound.person_detected` and/or `sighthound.vehicle_detected` events.
|
||||
|
||||
An example using two automations:
|
||||
|
||||
- The first automation is triggered, when a motion is detected. It calls the `image_processing.scan` service to send the camera image to the sighthound server for processing.
|
||||
|
||||
- The second automation is triggered by a `sighthound.vehicle_detected` event. It sends a notification to a phone.
|
||||
|
||||
```yaml
|
||||
# Example automations.yaml entry
|
||||
- id: "SOME_UNIQUE_ID"
|
||||
alias: "Entrance Motion Image Processing"
|
||||
description: "Send a camera image to sighthound, when motion is detected at the entrance"
|
||||
trigger:
|
||||
- type: motion
|
||||
platform: device
|
||||
device_id: YOUR_DEVICE_ID
|
||||
entity_id: binary_sensor.my_motion_sensor
|
||||
domain: binary_sensor
|
||||
action:
|
||||
- service: image_processing.scan
|
||||
target:
|
||||
entity_id: image_processing.sighthound_my_cam
|
||||
mode: single
|
||||
|
||||
- id: "ANOTHER_UNIQUE_ID"
|
||||
alias: "Arriving Vehicle Notification"
|
||||
description: "Send a notification to a phone, when a vehicle is detected at the entrance"
|
||||
trigger:
|
||||
- platform: event
|
||||
event_type: sighthound.vehicle_detected
|
||||
action:
|
||||
- service: notify.mobile_app_my_iphone
|
||||
data:
|
||||
message: "Somebody has just arrived by car."
|
||||
mode: single
|
||||
```
|
||||
|
||||
@ -29,7 +29,7 @@ This integration allows you to control [Tasmota](https://tasmota.github.io/docs/
|
||||
|
||||
- MQTT broker and the [MQTT integration](/integrations/mqtt/) set up in Home Assistant.
|
||||
- Tasmota devices' MQTT setting configured to communicate with the MQTT broker.
|
||||
- Tasmota devices flashed with version 9.2, or later.
|
||||
- Tasmota devices flashed with version 9.2, or later (`tasmota-lite.bin` does not support this integration).
|
||||
- Tasmota devices configured for native discovery (`SetOption19 0`)
|
||||
- Although the Tasmota integration supports custom fulltopic it is strongly suggested to leave fulltopic at its default, Tasmota does not prevent setting an invalid or non-unique fulltopic, for example a fulltopic without the %prefix% or %topic% tokens.
|
||||
|
||||
|
||||
@ -60,7 +60,7 @@ Plugs are type `switch` when autodiscovery has been disabled.
|
||||
|
||||
### Bulbs
|
||||
|
||||
Other bulbs may also work, but with limited color temperatures. If you find a bulb isn't reaching the full-color temperature boundaries, submit a bug report.
|
||||
Other bulbs may also work, but with limited color temperatures. If you find a bulb isn't reaching the full-color temperature boundaries, submit a bug report. Bulbs do generally report some energy consumption information, see the entity state attributes to find out what information is available.
|
||||
|
||||
- LB100
|
||||
- LB110
|
||||
@ -150,6 +150,7 @@ Devices that are confirmed to support Consumption Reading;
|
||||
1. HS110
|
||||
2. HS300
|
||||
3. KP115
|
||||
4. Bulbs (device-specific, only current power consumption is commonly available)
|
||||
|
||||
In order to get the power consumption readings from a TP-Link HS110 device, you'll have to create a [template sensor](/integrations/template/).
|
||||
In the example below, change all of the `my_tp_switch`'s to match your device's entity ID (without the domain). For example, if your entity is `switch.whale_heater` then replace `my_tp_switch` with `whale_heater`:
|
||||
|
||||
@ -123,7 +123,6 @@ geo_location:
|
||||
Assuming you configure this service using `feed_type: past_week_all_earthquakes`, you can create a corresponding map card in the Lovelace UI with the following card:
|
||||
```yaml
|
||||
type: map
|
||||
name: Earthquakes
|
||||
geo_location_sources:
|
||||
- usgs_earthquakes_feed
|
||||
entities:
|
||||
|
||||
@ -79,9 +79,10 @@ Some other Zigbee coordinator hardware may not support a firmware that is capabl
|
||||
- Bitron Video/Smabit BV AV2010/10 USB-Stick with Silicon Labs Ember 3587
|
||||
- Telegesis ETRX357USB/ETRX357USB-LR/ETRX357USB-LRS+8M (Note! These first have to be [flashed with other EmberZNet firmware](https://github.com/walthowd/husbzb-firmware))
|
||||
- Texas Instruments based radios (via the [zigpy-znp](https://github.com/zigpy/zigpy-znp) library for zigpy)
|
||||
- [CC2652P/CC2652R/CC2652RB USB stick or dev board hardware flashed with Z-Stack 3.x.x coordinator firmware](https://www.zigbee2mqtt.io/information/supported_adapters)
|
||||
- [CC1352P/CC1352R USB stick or dev board hardware flashed with Z-Stack 3.x.x coordinator firmware](https://www.zigbee2mqtt.io/information/supported_adapters)
|
||||
- [CC2538 USB stick or dev board hardware flashed with Z-Stack 3.x.x coordinator firmware](https://www.zigbee2mqtt.io/information/supported_adapters)
|
||||
- [CC2652P/CC2652R/CC2652RB USB stick, module, or dev board hardware flashed with Z-Stack coordinator firmware](https://www.zigbee2mqtt.io/information/supported_adapters)
|
||||
- [CC1352P/CC1352R USB stick, module, or dev board hardware flashed with Z-Stack coordinator firmware](https://www.zigbee2mqtt.io/information/supported_adapters)
|
||||
- [CC2538 USB stick, module, or dev board hardware flashed with Z-Stack coordinator firmware](https://www.zigbee2mqtt.io/information/supported_adapters)
|
||||
- [CC2530/CC2531 USB stick, module, or dev board hardware flashed with Z-Stack coordinator firmware](https://www.zigbee2mqtt.io/information/supported_adapters)
|
||||
- Digi XBee Zigbee based radios (via the [zigpy-xbee](https://github.com/zigpy/zigpy-xbee) library for zigpy)
|
||||
- [Digi XBee Series 3 (xbee3-24)](https://www.digi.com/products/embedded-systems/digi-xbee/rf-modules/2-4-ghz-rf-modules/xbee3-zigbee-3) and [Digi XBee Series S2C](https://www.digi.com/products/embedded-systems/digi-xbee/rf-modules/2-4-ghz-rf-modules/xbee-zigbee) modules
|
||||
- Note! While not a must, [it is recommend to upgrade XBee Series 3 and S2C to newest firmware using XCTU](https://www.digi.com/resources/documentation/Digidocs/90002002/Default.htm#Tasks/t_load_zb_firmware.htm)
|
||||
@ -124,7 +125,7 @@ a new pop-up asking for a radio type. In the pop-up:
|
||||
| ------------- | ------------- |
|
||||
| `ezsp` | Silicon Labs EmberZNet protocol (e.g., Elelabs, HUSBZB-1, Telegesis) |
|
||||
| `deconz` | dresden elektronik deCONZ protocol (e.g., ConBee I/II, RaspBee I/II) |
|
||||
| `znp` | Texas Instruments (e.g., CC2531, CC26x2, CC13x2, zzh!, Slaesh's coordinator) |
|
||||
| `znp` | Texas Instruments (e.g., CC253x, CC26x2, CC13x2) |
|
||||
| `ti_cc` | Texas Instruments (legacy) |
|
||||
| `zigate` | ZiGate Serial protocol (e.g., ZiGate USB-TTL, PiZiGate, ZiGate WiFi) |
|
||||
| `xbee` | Digi XBee ZB Coordinator Firmware protocol (e.g., Digi XBee Series 2, 2C, 3) |
|
||||
|
||||
@ -127,7 +127,7 @@ card:
|
||||
Entity filter combined with glance card.
|
||||
</p>
|
||||
|
||||
You can also specify multiple `state_filter` conditions, in which case the entity will be displayed if it matches any condition. This example will display everyone who isn't at home or at work.
|
||||
You can also specify multiple `state_filter` conditions, in which case the entity will be displayed if it matches any condition. This example will display everyone who is at home or at work.
|
||||
|
||||
```yaml
|
||||
type: entity-filter
|
||||
@ -136,13 +136,13 @@ entities:
|
||||
- device_tracker.demo_anne_therese
|
||||
- device_tracker.demo_home_boy
|
||||
state_filter:
|
||||
- operator: "!="
|
||||
- operator: "=="
|
||||
value: home
|
||||
- operator: "!="
|
||||
- operator: "=="
|
||||
value: work
|
||||
card:
|
||||
type: glance
|
||||
title: Who's Running Errands
|
||||
title: Who's at work or home
|
||||
```
|
||||
|
||||
Specify filter for a single entity.
|
||||
|
||||
@ -29,7 +29,7 @@ entities:
|
||||
type: list
|
||||
hours_to_show:
|
||||
required: false
|
||||
description: Hours to show. Minimum is 1 hour, maximum of 80 hours.
|
||||
description: Hours to show in graph. Minimum is 1 hour. Big values can result in delayed rendering, especially if the selected entities have a lot of state changes.
|
||||
type: integer
|
||||
default: 24
|
||||
refresh_interval:
|
||||
|
||||
@ -111,7 +111,7 @@ For example:
|
||||
```yaml
|
||||
type: markdown
|
||||
content: |
|
||||
<ha-icon icon="mdi:home-assistant"></ha-icon>
|
||||
<ha-icon icon="mdi:home-assistant" />
|
||||
```
|
||||
|
||||
{% endraw %}
|
||||
|
||||
112
source/_posts/2021-06-25-community-highlights.markdown
Normal file
112
source/_posts/2021-06-25-community-highlights.markdown
Normal file
@ -0,0 +1,112 @@
|
||||
---
|
||||
title: "Community Highlights: 27th edition"
|
||||
description: "Know when a device is no longer connected to your network with a blueprint, lock your cards with a card and get started with statistics in Home Assistant."
|
||||
date: 2021-06-25 00:00:00
|
||||
date_formatted: "June 25, 2021"
|
||||
author: Klaas Schoute
|
||||
author_twitter: klaasnicolaas
|
||||
categories: Community
|
||||
og_image: /images/blog/2021-06-25-community-highlights/social.png
|
||||
---
|
||||
|
||||
The 27th edition of the Home Assistant Community Highlights! Some interesting
|
||||
things popped up around our community, which we thought was worth sharing.
|
||||
|
||||
But first I have one more announcement. My internship is (almost) over and I'm
|
||||
happy to say that I passed and completed it with a good grade. That also means that
|
||||
this community highlight is the last one from me as an intern, time will tell
|
||||
when the next one will appear.
|
||||
|
||||
Do you want to share something for the next edition?
|
||||
Information on [how to share](#got-a-tip-for-the-next-edition).
|
||||
|
||||
./Klaas <br>
|
||||
*Intern on Home Assistant Energy*
|
||||
|
||||
## Blueprint of the week
|
||||
------
|
||||
|
||||
{% my blueprint_import badge blueprint_url="https://gist.github.com/bfranke1973/4a0835efffc81759d02f44842265ea96" %}
|
||||
|
||||
This week's blueprint is that of [bfranke1973](https://community.home-assistant.io/u/bfranke1973),
|
||||
who has created a blueprint with which you can receive a notification when
|
||||
a device loses connection with the network. Try it out! Read more about it
|
||||
on the [community forum][week_blueprint] or install this automation in your
|
||||
instance with a click on the My button!
|
||||
|
||||
## Love Lock Card
|
||||
------
|
||||
|
||||
<div style="margin:0 auto; text-align:center">
|
||||
<a href="https://github.com/CyrisXD/love-lock-card" target="_blank">
|
||||
<img
|
||||
src='/images/blog/2021-06-25-community-highlights/lock.gif'
|
||||
alt="Preview of the love lock card"
|
||||
style='border: 0;box-shadow: none;width:100%;margin-bottom:15px;'
|
||||
/>
|
||||
</a>
|
||||
</div>
|
||||
|
||||
Do you ever accidentally turn on a light or switch? Then try the
|
||||
[love lock card](https://github.com/CyrisXD/love-lock-card) made by
|
||||
[CyrisXD](https://github.com/CyrisXD). With this, you can create a card
|
||||
that is locked and you can unlock it with, for example, a pin code or a
|
||||
simple click on the card.
|
||||
|
||||
<a href="https://github.com/CyrisXD/love-lock-card"><img style="border: 0;" src="https://gh-card.dev/repos/CyrisXD/love-lock-card.svg"></a>
|
||||
|
||||
## Lovelace Dashboard
|
||||
------
|
||||
|
||||
This week again we have a new Lovelace dashboard for the necessary portion
|
||||
of inspiration 😄 This time the one from [swake88](https://www.reddit.com/user/swake88/)
|
||||
who is improving his [dashboard](https://www.reddit.com/r/homeassistant/comments/o2za2z/slowly_redesigning_my_ha_dashboards_for_mobile/)
|
||||
for use on a mobile device. If you want to know more about it, check out
|
||||
the comment part on Reddit.
|
||||
|
||||
<div style="margin:0 auto; text-align:center; margin-bottom:15px">
|
||||
<iframe id="reddit-embed" src="https://www.redditmedia.com/r/homeassistant/comments/o2za2z/slowly_redesigning_my_ha_dashboards_for_mobile/?ref_source=embed&ref=share&embed=true" sandbox="allow-scripts allow-same-origin allow-popups" style="border: none;" height="639" width="640" scrolling="no"></iframe>
|
||||
</div>
|
||||
|
||||
Would you also like your dashboard to be in the community highlight? Drop it
|
||||
on [Reddit][reddit] and maybe I'll pick it out for the next edition.
|
||||
|
||||
## Statistic Tools
|
||||
------
|
||||
|
||||
<div style="margin:0 auto; text-align:center; margin-bottom:15px">
|
||||
<iframe id="reddit-embed" src="https://www.redditmedia.com/r/homeassistant/comments/o6co3v/mini_graph_card_that_displays_a_dynamic_color/?ref_source=embed&ref=share&embed=true" sandbox="allow-scripts allow-same-origin allow-popups" style="border: none;" height="426" width="640" scrolling="no"></iframe>
|
||||
</div>
|
||||
|
||||
Home Assistant has a number of tools for working with statistics, but the
|
||||
question is how can you best approach this. [Carlos](https://www.reddit.com/user/cgomesu/)
|
||||
has written a very good [guide](https://cgomesu.com/blog/smarter-hass/) on
|
||||
how to get started and how to make cards that use this data.
|
||||
|
||||
## Got a tip for the next edition?
|
||||
------
|
||||
|
||||
Have you seen (or made) something awesome, interesting, unique, amazing,
|
||||
inspirational, unusual or funny, using Home Assistant?
|
||||
|
||||
[Click here to send us your Community Highlight suggestion](/suggest-community-highlight).
|
||||
|
||||
Also, don't forget to share your creations with us via Social Media:
|
||||
|
||||
- Tweet it! Be sure to mention [@home_assistant][twitter]
|
||||
- Share it on our [Facebook group][facebook-group]
|
||||
- Post it to our [subreddit][reddit]
|
||||
- Tag [@homeasssistant][instagram] on Instagram
|
||||
- Or via chat, drop us a line in the [#lounge at Discord][chat]
|
||||
|
||||
See you next edition!
|
||||
|
||||
[chat]: https://www.home-assistant.io/join-chat
|
||||
[facebook-group]: https://www.facebook.com/groups/HomeAssistant
|
||||
[instagram]: https://www.instagram.com/homeassistant
|
||||
[reddit]: https://www.reddit.com/r/homeassistant
|
||||
[twitter]: https://www.twitter.com/home_assistant
|
||||
[blueprints]: https://community.home-assistant.io/c/blueprints-exchange
|
||||
[community]: https://community.home-assistant.io
|
||||
[esphome]: https://esphome.io
|
||||
[week_blueprint]: https://community.home-assistant.io/t/send-notification-if-and-when-a-network-device-loses-connectivity/317323
|
||||
BIN
source/images/blog/2021-06-25-community-highlights/lock.gif
Normal file
BIN
source/images/blog/2021-06-25-community-highlights/lock.gif
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 312 KiB |
BIN
source/images/blog/2021-06-25-community-highlights/social.png
Normal file
BIN
source/images/blog/2021-06-25-community-highlights/social.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 160 KiB |
@ -167,47 +167,8 @@ description:
|
||||
</a>
|
||||
</div>
|
||||
|
||||
<div class="grid__item one-third lap-one-whole palm-one-whole usp">
|
||||
<div class="grid">
|
||||
<div class="grid__item one-whole lap-one-third">
|
||||
<span class="icon">
|
||||
<i class="icon-eye-open"></i>
|
||||
</span>
|
||||
</div>
|
||||
|
||||
<div class="grid__item one-whole lap-two-thirds">
|
||||
{% include custom/grid_item_left.html %}
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="grid__item one-third lap-one-whole palm-one-whole usp">
|
||||
<div class="grid">
|
||||
<div class="grid__item one-whole lap-one-third">
|
||||
<span class="icon">
|
||||
<i class="icon-mobile-phone"></i>
|
||||
</span>
|
||||
</div>
|
||||
|
||||
<div class="grid__item one-whole lap-two-thirds">
|
||||
{% include custom/grid_item_middle.html %}
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="grid__item one-third lap-one-whole palm-one-whole usp">
|
||||
<div class="grid">
|
||||
<div class="grid__item one-whole lap-one-third">
|
||||
<span class="icon">
|
||||
<i class="icon-cogs"></i>
|
||||
</span>
|
||||
</div>
|
||||
|
||||
<div class="grid__item one-whole lap-two-thirds">
|
||||
{% include custom/grid_item_right.html %}
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<div class="sub-title">Features</div>
|
||||
{% include custom/features.html %}
|
||||
|
||||
<div class="seen-press grid__item one-half lap-one-half palm-one-whole">
|
||||
<div class="material-card">
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user