mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-19 15:26:59 +00:00
Merge branch 'current' into next
This commit is contained in:
Paulus Schoutsen
commit
d1efccfb25
2
Rakefile
2
Rakefile
@ -92,7 +92,7 @@ task :preview, :listen do |t, args|
|
||||
raise "### You haven't set anything up yet. First run `rake install` to set up an Octopress theme." unless File.directory?(source_dir)
|
||||
puts "Starting to watch source with Jekyll and Compass. Starting Rack on port #{server_port}"
|
||||
system "compass compile --css-dir #{source_dir}/stylesheets" unless File.exist?("#{source_dir}/stylesheets/screen.css")
|
||||
jekyllPid = Process.spawn({"OCTOPRESS_ENV"=>"preview"}, "jekyll build --watch --incremental")
|
||||
jekyllPid = Process.spawn({"OCTOPRESS_ENV"=>"preview"}, "jekyll build -t --watch --incremental")
|
||||
compassPid = Process.spawn("compass watch")
|
||||
rackupPid = Process.spawn("rackup --port #{server_port} --host #{listen_addr}")
|
||||
|
||||
|
||||
@ -139,8 +139,8 @@ social:
|
||||
# Home Assistant release details
|
||||
current_major_version: 0
|
||||
current_minor_version: 89
|
||||
current_patch_version: 0
|
||||
date_released: 2019-03-06
|
||||
current_patch_version: 2
|
||||
date_released: 2019-03-12
|
||||
|
||||
# Either # or the anchor link to latest release notes in the blog post.
|
||||
# Must be prefixed with a # and have double quotes around it.
|
||||
|
||||
@ -70,6 +70,63 @@ module Jekyll
|
||||
def canonical_url(input)
|
||||
full_url(input).sub(/index\.\w+$/i, '')
|
||||
end
|
||||
|
||||
# Sort an array of semvers
|
||||
def group_components_by_release(input)
|
||||
input.group_by { |v|
|
||||
raise ArgumentError, "ha_release must be set in #{v.basename}" if v["ha_release"].nil?
|
||||
release_str = v["ha_release"].to_s
|
||||
if release_str == "pre 0.7"
|
||||
release_str = "0.7"
|
||||
end
|
||||
release_str
|
||||
}.map{ |v|
|
||||
version = v[0]
|
||||
|
||||
begin
|
||||
gem_ver = Gem::Version.new(version).to_s
|
||||
rescue
|
||||
raise ArgumentError, "Error when parsing ha_release #{version} in #{v.path}."
|
||||
end
|
||||
|
||||
{ "label" => version, "new_components_count" => v[1].count, "sort_key" => gem_ver }
|
||||
}.sort_by { |v| v["sort_key"] }.reverse.group_by { |v|
|
||||
version = v["label"]
|
||||
|
||||
split_ver = version.split('.')
|
||||
major = split_ver[0]
|
||||
minor = split_ver[1]
|
||||
|
||||
if minor.length == 1
|
||||
"#{major}.X"
|
||||
else
|
||||
"#{major}.#{minor[0]}X"
|
||||
end
|
||||
}.map { |v|
|
||||
sort_key = v[1][-1]["sort_key"]
|
||||
if v[0] == "0.X"
|
||||
sort_key = "0.01" # Ensure 0.X is always sorted at bottom.
|
||||
end
|
||||
|
||||
total_new_components = 0
|
||||
|
||||
v[1].each do |vers|
|
||||
total_new_components += vers["new_components_count"]
|
||||
end
|
||||
|
||||
{ "label" => v[0], "versions" => v[1], "new_components_count" => total_new_components, "sort_key" => sort_key }
|
||||
}.sort_by { |v| v["sort_key"] }.reverse
|
||||
end
|
||||
|
||||
# Get version N behind current
|
||||
# input is output of group_components_by_release
|
||||
def version_behind(input, n)
|
||||
input.each do |group|
|
||||
if group["versions"].length > n
|
||||
return group["versions"][n]
|
||||
end
|
||||
end
|
||||
end
|
||||
end
|
||||
end
|
||||
|
||||
|
||||
@ -50,12 +50,12 @@
|
||||
margin: 12px 0;
|
||||
}
|
||||
|
||||
.added_in_current_version {
|
||||
margin-top: 12px;
|
||||
.version_select {
|
||||
margin: 12px 0 12px 0;
|
||||
}
|
||||
|
||||
.added_two_versions_ago {
|
||||
margin-bottom: 12px;
|
||||
.version_select > select {
|
||||
width: 100%;
|
||||
}
|
||||
|
||||
.btn {
|
||||
|
||||
@ -69,3 +69,15 @@ You'll need to forward the port you listed in your configuration (8123 in the ex
|
||||
Ensure that you allocate the Home Assistant system a fixed IP on your network before you configure port forwarding. You can do this either on the computer itself (see the [install guide](/hassio/installation/) or via a static lease on your router.
|
||||
|
||||
Restart Home Assistant for the configured changes to take effect. When you access the Home Assistant frontend you will now need to use `https`, even when accessing local instances, for example at `https://192.168.0.1:8123`.
|
||||
|
||||
## {% linkable_title Generate Let's Encrypt certificate for Duck DNS sub sub domains %}
|
||||
|
||||
To generate certificates for nr.my-domain.duckdns.org update the domain JSON settings to:
|
||||
|
||||
```json
|
||||
{
|
||||
...
|
||||
"domains": ["my-domain.duckdns.org","*.my-domain.duckdns.org"],
|
||||
...
|
||||
}
|
||||
```
|
||||
|
||||
@ -7,7 +7,6 @@ sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
featured: false
|
||||
---
|
||||
|
||||
<p class='note'>
|
||||
|
||||
@ -7,7 +7,6 @@ sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
featured: false
|
||||
---
|
||||
|
||||
Setting up the [Tellstick](http://telldus.com) service and tools contained in the [telldus-core](http://developer.telldus.com/) package and adding configuration to enable Tellstick and Tellstick Duo to work on your Hass.io.
|
||||
|
||||
@ -19,7 +19,7 @@ ha_category:
|
||||
- Sensor
|
||||
- Switch
|
||||
ha_release: 0.52
|
||||
ha_iot_class: "Cloud Push"
|
||||
ha_iot_class: Cloud Push
|
||||
redirect_from:
|
||||
- /components/alarm_control_panel.abode/
|
||||
- /components/binary_sensor.abode/
|
||||
|
||||
@ -15,7 +15,7 @@ ha_category:
|
||||
- Sensor
|
||||
- Switch
|
||||
ha_release: "0.60"
|
||||
ha_iot_class: "Local Push"
|
||||
ha_iot_class: Local Push
|
||||
redirect_from:
|
||||
- /components/binary_sensor.ads/
|
||||
- /components/light.ads/
|
||||
|
||||
@ -8,6 +8,7 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
redirect_from: /components/air_pollutants/
|
||||
ha_release: 0.85
|
||||
---
|
||||
|
||||
The `air_quality` gather information about the air quality and pollution details.
|
||||
|
||||
@ -9,7 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: nilu_logo.png
|
||||
ha_category: Health
|
||||
ha_iot_class: "Cloud Polling"
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_release: 0.87
|
||||
---
|
||||
|
||||
|
||||
@ -10,7 +10,7 @@ footer: true
|
||||
logo: opensensemap.png
|
||||
ha_category: Health
|
||||
ha_release: 0.85
|
||||
ha_iot_class: "Cloud Polling"
|
||||
ha_iot_class: Cloud Polling
|
||||
redirect_from: /components/air_pollutants.opensensemap/
|
||||
---
|
||||
|
||||
|
||||
@ -7,6 +7,7 @@ sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
ha_release: 0.7.3
|
||||
---
|
||||
|
||||
Home Assistant can give you an interface with is similar to a classic alarm system. There are several panels supported:
|
||||
|
||||
@ -10,7 +10,7 @@ footer: true
|
||||
logo: mqtt.png
|
||||
ha_category: Alarm
|
||||
ha_release: 0.7.4
|
||||
ha_iot_class: depends
|
||||
ha_iot_class: Configurable
|
||||
---
|
||||
|
||||
The `mqtt` alarm panel platform enables the possibility to control MQTT capable alarm panels. The Alarm icon will change state after receiving a new state from `state_topic`. If these messages are published with *RETAIN* flag, the MQTT alarm panel will receive an instant state update after subscription and will start with the correct state. Otherwise, the initial state will be `unknown`.
|
||||
|
||||
@ -13,7 +13,7 @@ ha_category:
|
||||
- Binary Sensor
|
||||
- Sensor
|
||||
ha_release: 0.43
|
||||
ha_iot_class: "Local Push"
|
||||
ha_iot_class: Local Push
|
||||
redirect_from:
|
||||
- /components/alarm_control_panel.alarmdecoder/
|
||||
- /components/binary_sensor.alarmdecoder/
|
||||
|
||||
@ -10,7 +10,7 @@ footer: true
|
||||
logo: amazon-echo.png
|
||||
ha_category: Voice
|
||||
featured: true
|
||||
ha_release: '0.10'
|
||||
ha_release: "0.10"
|
||||
---
|
||||
|
||||
## {% linkable_title Automatic setup via Home Assistant Cloud %}
|
||||
|
||||
@ -7,8 +7,8 @@ sidebar: true
|
||||
comments: false
|
||||
logo: ambient_weather.png
|
||||
ha_category: Weather
|
||||
ha_release: "0.85"
|
||||
ha_iot_class: "Cloud Push"
|
||||
ha_release: 0.85
|
||||
ha_iot_class: Cloud Push
|
||||
redirect_from:
|
||||
- /components/sensor.ambient_station/
|
||||
---
|
||||
|
||||
@ -13,7 +13,7 @@ ha_category:
|
||||
- Camera
|
||||
- Sensor
|
||||
- Switch
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_iot_class: Local Polling
|
||||
ha_release: 0.49
|
||||
redirect_from:
|
||||
- /components/camera.amcrest/
|
||||
|
||||
@ -15,7 +15,7 @@ ha_category:
|
||||
- Sensor
|
||||
- Switch
|
||||
ha_release: "0.40"
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_iot_class: Local Polling
|
||||
redirect_from:
|
||||
- /components/binary_sensor.android_ip_webcam/
|
||||
- /components/camera.android_ip_webcam/
|
||||
|
||||
@ -13,7 +13,7 @@ ha_category:
|
||||
- Binary Sensor
|
||||
- Sensor
|
||||
ha_release: 0.13
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_iot_class: Local Polling
|
||||
redirect_from:
|
||||
- /components/binary_sensor.apcupsd/
|
||||
- /components/sensor.apcupsd/
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: home-assistant.png
|
||||
ha_category: "Other"
|
||||
ha_qa_scale: internal
|
||||
ha_release: 0.7
|
||||
---
|
||||
|
||||
The `api` component exposes a RESTful API and allows one to interact with a Home Assistant instance that is running headless. This component depends on the [`http` component](/components/http/).
|
||||
|
||||
@ -12,7 +12,7 @@ ha_category:
|
||||
- Multimedia
|
||||
- Media Player
|
||||
- Remote
|
||||
ha_iot_class: "Local Push"
|
||||
ha_iot_class: Local Push
|
||||
ha_release: 0.49
|
||||
redirect_from:
|
||||
- /components/media_player.apple_tv/
|
||||
|
||||
@ -13,7 +13,7 @@ ha_category:
|
||||
- Sensor
|
||||
- Switch
|
||||
ha_release: "0.80"
|
||||
ha_iot_class: "Local Push"
|
||||
ha_iot_class: Local Push
|
||||
redirect_from:
|
||||
- /components/sensor.aqualogic/
|
||||
- /components/switch.aqualogic/
|
||||
|
||||
@ -11,7 +11,7 @@ logo: arduino.png
|
||||
ha_category: DIY
|
||||
featured: true
|
||||
ha_release: pre 0.7
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_iot_class: Local Polling
|
||||
---
|
||||
|
||||
The [Arduino](https://www.arduino.cc/) device family are microcontroller boards that are often based on the ATmega328 chip. They come with digital input/output pins (some can be used as PWM outputs), analog inputs, and a USB connection.
|
||||
|
||||
@ -14,7 +14,7 @@ ha_category:
|
||||
- Camera
|
||||
- Sensor
|
||||
ha_release: 0.46
|
||||
ha_iot_class: "Cloud Polling"
|
||||
ha_iot_class: Cloud Polling
|
||||
redirect_from:
|
||||
- /components/alarm_control_panel.arlo/
|
||||
- /components/camera.arlo/
|
||||
|
||||
@ -9,7 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: asterisk.png
|
||||
ha_category: Mailbox
|
||||
ha_iot_class: "Local Push"
|
||||
ha_iot_class: Local Push
|
||||
ha_release: 0.51
|
||||
redirect_from:
|
||||
- /components/mailbox.asterisk_mbox/
|
||||
|
||||
@ -13,7 +13,7 @@ ha_category:
|
||||
- Presence Detection
|
||||
- Sensor
|
||||
ha_release: 0.83
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_iot_class: Local Polling
|
||||
redirect_from:
|
||||
- /components/device_tracker.asuswrt/
|
||||
- /components/sensor.asuswrt/
|
||||
|
||||
@ -13,8 +13,8 @@ ha_category:
|
||||
- Binary Sensor
|
||||
- Camera
|
||||
- Lock
|
||||
ha_release: "0.64"
|
||||
ha_iot_class: "Cloud Polling"
|
||||
ha_release: 0.64
|
||||
ha_iot_class: Cloud Polling
|
||||
redirect_from:
|
||||
- /components/binary_sensor.august/
|
||||
- /components/camera.august/
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: home-assistant.png
|
||||
ha_category: Automation
|
||||
ha_qa_scale: internal
|
||||
ha_release: 0.7
|
||||
---
|
||||
|
||||
Please see the [docs section](/docs/automation/) for in-depth
|
||||
@ -24,14 +25,14 @@ Starting with 0.28 your automation rules can be controlled with the frontend.
|
||||
This allows one to reload the automation without restarting Home Assistant
|
||||
itself. If you don't want to see the automation rule in your frontend use
|
||||
`hide_entity: true` to hide it.
|
||||
You can also use `initial_state: 'off'` so that the automation
|
||||
You can also use `initial_state: 'false'` so that the automation
|
||||
is not automatically turned on after a Home Assistant reboot.
|
||||
|
||||
```yaml
|
||||
automation:
|
||||
- alias: Door alarm
|
||||
hide_entity: true
|
||||
initial_state: 'off'
|
||||
initial_state: 'true'
|
||||
trigger:
|
||||
- platform: state
|
||||
...
|
||||
|
||||
@ -11,8 +11,8 @@ logo: axis.png
|
||||
ha_category:
|
||||
- Camera
|
||||
- Binary Sensor
|
||||
ha_release: "0.45"
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_release: 0.45
|
||||
ha_iot_class: Local Polling
|
||||
redirect_from:
|
||||
- /components/binary_sensor.axis/
|
||||
- /components/camera.axis/
|
||||
|
||||
@ -13,7 +13,7 @@ ha_category:
|
||||
- Binary Sensor
|
||||
- Switch
|
||||
ha_release: 0.36
|
||||
ha_iot_class: "Local Push"
|
||||
ha_iot_class: Local Push
|
||||
redirect_from:
|
||||
- /components/binary_sensor.bbb_gpio/
|
||||
- /components/switch.bbb_gpio/
|
||||
|
||||
@ -9,7 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: arest.png
|
||||
ha_category: DIY
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_iot_class: Local Polling
|
||||
ha_release: 0.9
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: home-assistant.png
|
||||
ha_category: Utility
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_iot_class: Local Polling
|
||||
ha_release: 0.53
|
||||
ha_qa_scale: internal
|
||||
---
|
||||
|
||||
@ -10,7 +10,7 @@ footer: true
|
||||
logo: command_line.png
|
||||
ha_category: Utility
|
||||
ha_release: 0.12
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_iot_class: Local Polling
|
||||
---
|
||||
|
||||
The `command_line` binary sensor platform issues specific commands to get data.
|
||||
|
||||
@ -9,7 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: flic.png
|
||||
ha_category: Binary Sensor
|
||||
ha_iot_class: "Local Push"
|
||||
ha_iot_class: Local Push
|
||||
ha_release: 0.35
|
||||
---
|
||||
|
||||
|
||||
@ -10,7 +10,7 @@ footer: true
|
||||
logo: hikvision.png
|
||||
ha_category: Binary Sensor
|
||||
ha_release: 0.35
|
||||
ha_iot_class: "Local Push"
|
||||
ha_iot_class: Local Push
|
||||
---
|
||||
|
||||
The Hikvision Binary Sensor is a platform that parses the event stream of a
|
||||
|
||||
@ -10,7 +10,7 @@ footer: true
|
||||
logo: ihc.png
|
||||
ha_category: Binary Sensor
|
||||
ha_release: 0.62
|
||||
ha_iot_class: "Local Push"
|
||||
ha_iot_class: Local Push
|
||||
---
|
||||
|
||||
Before you can use the IHC Binary Sensor platform,
|
||||
|
||||
@ -10,7 +10,7 @@ footer: true
|
||||
logo: knx.png
|
||||
ha_category: Binary Sensor
|
||||
ha_release: 0.24
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_iot_class: Local Polling
|
||||
---
|
||||
|
||||
The `knx` sensor platform allows you to monitor [KNX](http://www.knx.org) binary sensors.
|
||||
|
||||
@ -7,6 +7,7 @@ sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
ha_release: 0.9
|
||||
---
|
||||
|
||||
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.
|
||||
|
||||
@ -10,7 +10,7 @@ footer: true
|
||||
logo: modbus.png
|
||||
ha_category: Binary Sensor
|
||||
ha_release: 0.28
|
||||
ha_iot_class: "Local Push"
|
||||
ha_iot_class: Local Push
|
||||
---
|
||||
|
||||
The `modbus` binary sensor allows you to gather data from [Modbus](http://www.modbus.org/) coils.
|
||||
|
||||
@ -10,7 +10,7 @@ footer: true
|
||||
logo: mqtt.png
|
||||
ha_category: Binary Sensor
|
||||
ha_release: 0.9
|
||||
ha_iot_class: "depends"
|
||||
ha_iot_class: Configurable
|
||||
---
|
||||
|
||||
The `mqtt` binary sensor platform uses an MQTT message payload to set the binary sensor to one of two states: `on` or `off`.
|
||||
|
||||
@ -12,7 +12,7 @@ ha_category:
|
||||
- DIY
|
||||
- Binary Sensor
|
||||
ha_release: 0.14
|
||||
ha_iot_class: "Local Push"
|
||||
ha_iot_class: Local Push
|
||||
---
|
||||
|
||||
Integrates MySensors binary sensors into Home Assistant. See the [main component] for configuration instructions.
|
||||
|
||||
@ -9,7 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: mystrom.png
|
||||
ha_category: Binary Sensor
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_iot_class: Local Polling
|
||||
ha_release: 0.45
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: networx.png
|
||||
ha_category: Binary Sensor
|
||||
ha_iot_class: "Local Push"
|
||||
ha_iot_class: Local Push
|
||||
ha_release: 0.14
|
||||
---
|
||||
|
||||
|
||||
@ -9,8 +9,8 @@ sharing: true
|
||||
footer: true
|
||||
logo: raincloud.jpg
|
||||
ha_category: Irrigation
|
||||
ha_release: "0.55"
|
||||
ha_iot_class: "Cloud Polling"
|
||||
ha_release: 0.55
|
||||
ha_iot_class: Cloud Polling
|
||||
---
|
||||
|
||||
To get your [Melnor RainCloud](https://wifiaquatimer.com) binary sensors working within Home Assistant, please follow the instructions for the general [Raincloud component](/components/raincloud).
|
||||
|
||||
@ -9,7 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: home-assistant.png
|
||||
ha_category: Utility
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_iot_class: Local Polling
|
||||
ha_release: 0.57
|
||||
ha_qa_scale: internal
|
||||
---
|
||||
|
||||
@ -10,7 +10,7 @@ footer: true
|
||||
logo: restful.png
|
||||
ha_category: Binary Sensor
|
||||
ha_release: "0.10"
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_iot_class: Local Polling
|
||||
---
|
||||
|
||||
The `rest` binary sensor platform is consuming a given endpoint which is exposed
|
||||
|
||||
@ -9,8 +9,8 @@ sharing: true
|
||||
footer: true
|
||||
logo: rflink.png
|
||||
ha_category: Binary Sensor
|
||||
ha_iot_class: "Local Push"
|
||||
ha_release: "0.81"
|
||||
ha_iot_class: Local Push
|
||||
ha_release: 0.81
|
||||
---
|
||||
|
||||
The `rflink` component supports devices that use [RFLink gateway firmware](http://www.nemcon.nl/blog2/), for example the [Nodo RFLink Gateway](https://www.nodo-shop.nl/nl/21-rflink-gateway). RFLink gateway is an Arduino firmware that allows two-way communication with a multitude of RF wireless devices using cheap hardware (Arduino + transceiver).
|
||||
|
||||
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: rfxtrx.png
|
||||
ha_category: Binary Sensor
|
||||
ha_release: 0.48
|
||||
---
|
||||
|
||||
The `rfxtrx` platform support binary sensors that
|
||||
|
||||
@ -10,7 +10,7 @@ footer: true
|
||||
logo: raspberry-pi.png
|
||||
ha_category: DIY
|
||||
ha_release: 0.45
|
||||
ha_iot_class: "Local Push"
|
||||
ha_iot_class: Local Push
|
||||
---
|
||||
|
||||
The `rpi_pfio` binary sensor platform allows you to read sensor values of the [PiFace Digital I/O](http://www.piface.org.uk/products/piface_digital/) .
|
||||
|
||||
@ -9,9 +9,8 @@ sharing: true
|
||||
footer: true
|
||||
logo: tapsaff.png
|
||||
ha_category: Weather
|
||||
featured: false
|
||||
ha_release: 0.47
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_iot_class: Local Polling
|
||||
---
|
||||
|
||||
The `tapsaff` binary sensor provides the 'Taps Aff' status for a given location within the UK using [Taps Aff](http://www.taps-aff.co.uk).
|
||||
|
||||
@ -9,7 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
ha_category: Binary Sensor
|
||||
ha_release: 0.12
|
||||
ha_iot_class: "Local Push"
|
||||
ha_iot_class: Local Push
|
||||
logo: home-assistant.png
|
||||
ha_qa_scale: internal
|
||||
---
|
||||
|
||||
@ -9,7 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: home-assistant.png
|
||||
ha_category: Utility
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_iot_class: Local Polling
|
||||
ha_release: 0.34
|
||||
ha_qa_scale: internal
|
||||
---
|
||||
|
||||
@ -9,7 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
ha_category: Binary Sensor
|
||||
ha_release: 0.89
|
||||
ha_iot_class: "Local Push"
|
||||
ha_iot_class: Local Push
|
||||
logo: home-assistant.png
|
||||
ha_qa_scale: internal
|
||||
---
|
||||
@ -32,6 +32,11 @@ binary_sensor:
|
||||
after: sunrise
|
||||
after_offset: '-02:00'
|
||||
before: '07:00'
|
||||
|
||||
- platform: tod
|
||||
name: Late Morning
|
||||
after: '10:00'
|
||||
before: '12:00'
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
|
||||
@ -10,7 +10,7 @@ footer: true
|
||||
ha_category: Utility
|
||||
logo: home-assistant.png
|
||||
ha_release: 0.28
|
||||
ha_iot_class: "Local Push"
|
||||
ha_iot_class: Local Push
|
||||
ha_qa_scale: internal
|
||||
---
|
||||
|
||||
|
||||
@ -9,8 +9,8 @@ sharing: true
|
||||
footer: true
|
||||
logo: uptimerobot.png
|
||||
ha_category: System Monitor
|
||||
ha_release: "0.72"
|
||||
ha_iot_class: "Cloud Polling"
|
||||
ha_release: 0.72
|
||||
ha_iot_class: Cloud Polling
|
||||
---
|
||||
|
||||
The `uptimerobot` binary sensor platform allows you get the status for all of your monitors from your account on [Uptime Robot.]( https://uptimerobot.com).
|
||||
|
||||
@ -9,7 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: home-assistant.png
|
||||
ha_category: Utility
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_iot_class: Local Polling
|
||||
ha_release: 0.41
|
||||
ha_qa_scale: internal
|
||||
---
|
||||
|
||||
@ -10,7 +10,7 @@ footer: true
|
||||
logo: xiaomi.png
|
||||
ha_category: Binary Sensor
|
||||
ha_release: "0.50"
|
||||
ha_iot_class: "Local Push"
|
||||
ha_iot_class: Local Push
|
||||
---
|
||||
|
||||
The `xiaomi aqara` binary sensor platform allows you to get data from your [Xiaomi](http://www.mi.com/en/) binary sensors.
|
||||
|
||||
@ -10,7 +10,7 @@ footer: true
|
||||
logo: zigbee.png
|
||||
ha_category: Binary Sensor
|
||||
ha_release: 0.12
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_iot_class: Local Polling
|
||||
---
|
||||
|
||||
A `zigbee` binary sensor in this context is a device connected to one of the digital input pins on a [Zigbee](http://www.zigbee.org/) module. The states reported by such a device are limited to `on` or `off`. By default, a binary sensor is considered `on` when the Zigbee device's digital input pin is held 'high' and considered `off` when it is held `low`. This behavior can be inverted by setting the `on_state` configuration variable to `low`.
|
||||
|
||||
@ -15,8 +15,8 @@ ha_category:
|
||||
- Camera
|
||||
- Sensor
|
||||
ha_release: "0.40"
|
||||
ha_iot_class: "Cloud Polling"
|
||||
redirect_form:
|
||||
ha_iot_class: Cloud Polling
|
||||
redirect_from:
|
||||
- /components/alarm_control_panel.blink/
|
||||
- /components/binary_sensor.blink/
|
||||
- /components/camera.blink/
|
||||
|
||||
@ -14,7 +14,7 @@ ha_category:
|
||||
- Camera
|
||||
- Sensor
|
||||
ha_release: 0.14
|
||||
ha_iot_class: "Cloud Polling"
|
||||
ha_iot_class: Cloud Polling
|
||||
redirect_from:
|
||||
- /components/binary_sensor.bloomsky/
|
||||
---
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: home-assistant.png
|
||||
ha_category: Utility
|
||||
ha_qa_scale: internal
|
||||
ha_release: pre 0.7
|
||||
---
|
||||
|
||||
The `browser` component provides a service to open URLs in the default browser on the host machine.
|
||||
|
||||
@ -8,7 +8,7 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
ha_category: Calendar
|
||||
ha_iot_class: "Cloud Polling"
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_release: "0.60"
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: google_calendar.png
|
||||
ha_category: Calendar
|
||||
ha_iot_class: "Cloud Polling"
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_release: 0.33
|
||||
---
|
||||
|
||||
|
||||
@ -7,6 +7,7 @@ sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
ha_release: 0.33
|
||||
---
|
||||
|
||||
The calendar component allows you to integrate your calendars into Home Assistant.
|
||||
|
||||
@ -9,7 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: todoist.png
|
||||
ha_category: Calendar
|
||||
ha_iot_class: "Cloud Polling"
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_release: 0.54
|
||||
---
|
||||
|
||||
|
||||
@ -10,7 +10,7 @@ footer: true
|
||||
ha_category: Camera
|
||||
logo: camcorder.png
|
||||
ha_release: "0.40"
|
||||
ha_iot_class: "depends"
|
||||
ha_iot_class: Configurable
|
||||
---
|
||||
|
||||
<p class='note'>
|
||||
|
||||
@ -10,7 +10,7 @@ footer: true
|
||||
logo: familyhub.png
|
||||
ha_category: Camera
|
||||
ha_release: "0.70"
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_iot_class: Local Polling
|
||||
---
|
||||
|
||||
The `familyhub` platform allows you to get images of the inside of your [Samsung Family Hub refrigerator](https://www.samsung.com/us/explore/family-hub-refrigerator/connected-hub/) in Home Assistant.
|
||||
|
||||
@ -10,7 +10,7 @@ footer: true
|
||||
logo: ffmpeg.png
|
||||
ha_category: Camera
|
||||
ha_release: 0.26
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_iot_class: Local Polling
|
||||
---
|
||||
|
||||
The `ffmpeg` platform allows you to use any video feed as a camera in Home Assistant via [FFmpeg](http://www.ffmpeg.org/). This video source must support multiple simultaneous reads, because for every concurrent Home Assistant user, a connection will be made to the source every 10 seconds. Normally this should not be a problem.
|
||||
|
||||
@ -9,7 +9,8 @@ sharing: true
|
||||
footer: true
|
||||
logo: foscam.png
|
||||
ha_category: Camera
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_iot_class: Local Polling
|
||||
ha_release: 0.7.3
|
||||
---
|
||||
|
||||
The `foscam` platform allows you to watch the live stream of your [Foscam](http://www.foscam.com/) IP camera in Home Assistant.
|
||||
|
||||
@ -10,7 +10,7 @@ footer: true
|
||||
ha_category: Camera
|
||||
logo: home-assistant.png
|
||||
ha_release: pre 0.7
|
||||
ha_iot_class: "depends"
|
||||
ha_iot_class: Configurable
|
||||
---
|
||||
|
||||
The `generic` camera platform allows you to integrate any IP camera or other URL into Home Assistant. Templates can be used to generate the URLs on the fly.
|
||||
|
||||
@ -9,7 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: file.png
|
||||
ha_category: Camera
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_iot_class: Local Polling
|
||||
ha_release: 0.22
|
||||
---
|
||||
|
||||
|
||||
@ -10,7 +10,7 @@ footer: true
|
||||
logo: logi_circle.png
|
||||
ha_category: Camera
|
||||
ha_release: 0.79
|
||||
ha_iot_class: "Cloud Polling"
|
||||
ha_iot_class: Cloud Polling
|
||||
---
|
||||
|
||||
The `logi_circle` camera platform allows you to watch the still frames of your [Logi Circle](https://circle.logi.com/) camera's live stream in Home Assistant.
|
||||
|
||||
@ -7,6 +7,7 @@ sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
ha_release: 0.7
|
||||
---
|
||||
|
||||
The camera component allows you to use IP cameras with Home Assistant. With a little additional work you could use [USB cameras](/blog/2016/06/23/usb-webcams-and-home-assistant/) as well.
|
||||
|
||||
@ -10,7 +10,7 @@ footer: true
|
||||
logo: home-assistant.png
|
||||
ha_category: Camera
|
||||
ha_release: pre 0.7
|
||||
ha_iot_class: "depends"
|
||||
ha_iot_class: Configurable
|
||||
---
|
||||
|
||||
The `mjpeg` camera platform allows you to integrate IP cameras which are capable
|
||||
|
||||
@ -10,7 +10,7 @@ footer: true
|
||||
logo: mqtt.png
|
||||
ha_category: Camera
|
||||
ha_release: 0.43
|
||||
ha_iot_class: depends
|
||||
ha_iot_class: Configurable
|
||||
---
|
||||
|
||||
The `mqtt` camera platform allows you to integrate the content of an image file sent through MQTT into Home Assistant as a camera. Every time a message under the `topic` in the configuration is received, the image displayed in Home Assistant will also be updated.
|
||||
|
||||
@ -10,7 +10,7 @@ footer: true
|
||||
logo: netatmo.png
|
||||
ha_category: Camera
|
||||
ha_release: 0.22
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_iot_class: Local Polling
|
||||
---
|
||||
|
||||
The `netatmo` camera platform is consuming the information provided by a [Netatmo](https://www.netatmo.com) camera. This component allows you to view the current photo created by the Camera.
|
||||
|
||||
@ -9,7 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: camcorder.png
|
||||
ha_category: Camera
|
||||
ha_iot_class: "Local Push"
|
||||
ha_iot_class: Local Push
|
||||
ha_release: 0.74
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: raspberry-pi.png
|
||||
ha_category: DIY
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_iot_class: Local Polling
|
||||
ha_release: 0.17
|
||||
---
|
||||
|
||||
|
||||
@ -10,7 +10,7 @@ footer: true
|
||||
logo: synology.png
|
||||
ha_category: Camera
|
||||
ha_release: 0.31
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_iot_class: Local Polling
|
||||
---
|
||||
|
||||
The `synology` camera platform allows you to watch the live streams of your [Synology](https://www.synology.com/) Surveillance Station based IP cameras in Home Assistant.
|
||||
|
||||
@ -10,7 +10,7 @@ footer: true
|
||||
logo: ubiquiti.png
|
||||
ha_category: Camera
|
||||
ha_release: 0.13
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_iot_class: Local Polling
|
||||
---
|
||||
|
||||
The `uvc` camera platform allows you to integrate [UniFi Video Camera (UVC)](https://www.ubnt.com/products/#unifivideo) into Home Assistant.
|
||||
|
||||
@ -9,7 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: xeoma.png
|
||||
ha_category: Camera
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_iot_class: Local Polling
|
||||
ha_release: 0.62
|
||||
---
|
||||
|
||||
|
||||
@ -10,7 +10,7 @@ footer: true
|
||||
logo: xiaomi.png
|
||||
ha_category: Camera
|
||||
ha_release: 0.72
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_iot_class: Local Polling
|
||||
---
|
||||
|
||||
The `Xiaomi` camera platform allows you to utilize Xiaomi Cameras within Home Assistant.
|
||||
|
||||
@ -10,7 +10,7 @@ footer: true
|
||||
logo: yi.png
|
||||
ha_category: Camera
|
||||
ha_release: 0.56
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_iot_class: Local Polling
|
||||
---
|
||||
|
||||
The `yi` camera platform allows you to utilize [Yi Home Cameras](https://www.yitechnology.com/) within Home Assistant. Specifically, this platform supports the line of Yi Home Cameras that are based on the Hi3518e Chipset. This includes:
|
||||
|
||||
@ -13,7 +13,7 @@ ha_category:
|
||||
- Camera
|
||||
- Sensor
|
||||
ha_release: "0.60"
|
||||
ha_iot_class: "Cloud Polling"
|
||||
ha_iot_class: Cloud Polling
|
||||
redirect_from:
|
||||
- /components/alarm_control_panel.canary/
|
||||
- /components/camera.canary/
|
||||
|
||||
@ -11,7 +11,7 @@ logo: google_cast.png
|
||||
ha_category: Media Player
|
||||
featured: true
|
||||
ha_release: pre 0.7
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_iot_class: Local Polling
|
||||
redirect_from: /components/media_player.cast/
|
||||
---
|
||||
|
||||
|
||||
@ -10,7 +10,7 @@ footer: true
|
||||
logo: coolautomation.png
|
||||
ha_category: Climate
|
||||
ha_release: 0.88
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_iot_class: Local Polling
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -10,7 +10,7 @@ footer: true
|
||||
logo: ephcontrolsember.png
|
||||
ha_category: Climate
|
||||
ha_release: 0.57
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_iot_class: Local Polling
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -9,7 +9,8 @@ sharing: true
|
||||
footer: true
|
||||
logo: eq3.gif
|
||||
ha_category: Climate
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_iot_class: Local Polling
|
||||
ha_release: 0.18
|
||||
---
|
||||
|
||||
The `eq3btsmart` climate platform allows you to integrate EQ3 Bluetooth Smart Thermostats.
|
||||
|
||||
@ -10,7 +10,7 @@ footer: true
|
||||
logo: honeywell.png
|
||||
ha_category: Climate
|
||||
ha_release: 0.80
|
||||
ha_iot_class: "Cloud Polling"
|
||||
ha_iot_class: Cloud Polling
|
||||
---
|
||||
|
||||
The `evohome` climate platform integrates your _non-US_ [Honeywell Total Connect Comfort (TCC)](https://international.mytotalconnectcomfort.com/Account/Login) system into Home Assistant. It has been tested with the Honeywell evohome multi-zone CH/DHW system, but other systems may also work.
|
||||
|
||||
@ -10,7 +10,7 @@ footer: true
|
||||
logo: flexit.png
|
||||
ha_category: Climate
|
||||
ha_release: 0.47
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_iot_class: Local Polling
|
||||
---
|
||||
|
||||
Integrates [Flexit](https://www.flexit.no/en/) Air Conditioning unit into Home Assistant.
|
||||
|
||||
@ -10,7 +10,7 @@ footer: true
|
||||
logo: home-assistant.png
|
||||
ha_category: Climate
|
||||
ha_release: pre 0.7
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_iot_class: Local Polling
|
||||
---
|
||||
|
||||
The `generic_thermostat` climate platform is a thermostat implemented in Home Assistant. It uses a sensor and a switch connected to a heater or air conditioning under the hood. When in heater mode, if the measured temperature is cooler than the target temperature, the heater will be turned on and turned off when the required temperature is reached. When in air conditioning mode, if the measured temperature is hotter than the target temperature, the air conditioning will be turned on and turned off when required temperature is reached. One Generic Thermostat entity can only control one switch. If you need to activate two switches, one for a heater and one for an air conditioner, you will need two Generic Thermostat entities.
|
||||
|
||||
@ -10,7 +10,7 @@ footer: true
|
||||
logo: heatmiser.png
|
||||
ha_category: Climate
|
||||
ha_release: "0.10"
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_iot_class: Local Polling
|
||||
---
|
||||
|
||||
The `heatmiser` climate platform let you control [Heatmiser DT/DT-E/PRT/PRT-E](https://www.heatmisershop.co.uk/thermostats) thermostats from Heatmiser. The module itself is currently setup to work over a RS232 -> RS485 converter, therefore it connects over IP.
|
||||
|
||||
@ -10,7 +10,7 @@ footer: true
|
||||
logo: honeywell.png
|
||||
ha_category: Climate
|
||||
ha_release: pre 0.7
|
||||
ha_iot_class: "Cloud Polling"
|
||||
ha_iot_class: Cloud Polling
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -10,7 +10,7 @@ footer: true
|
||||
logo: knx.png
|
||||
ha_category: Climate
|
||||
ha_release: 0.25
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_iot_class: Local Polling
|
||||
---
|
||||
|
||||
The `knx` climate platform is used as in interface with KNX thermostats.
|
||||
|
||||
@ -7,6 +7,7 @@ sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
ha_release: 0.19
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -10,7 +10,7 @@ footer: true
|
||||
logo: mill.png
|
||||
ha_category: Climate
|
||||
ha_release: 0.81
|
||||
ha_iot_class: "Cloud Polling"
|
||||
ha_iot_class: Cloud Polling
|
||||
---
|
||||
|
||||
Integrates Mill heater into Home Assistant.
|
||||
|
||||
@ -10,7 +10,7 @@ footer: true
|
||||
logo: modbus.png
|
||||
ha_category: Climate
|
||||
ha_release: 0.68
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_iot_class: Local Polling
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -10,7 +10,7 @@ footer: true
|
||||
logo: mqtt.png
|
||||
ha_category: Climate
|
||||
ha_release: 0.55
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_iot_class: Local Polling
|
||||
---
|
||||
|
||||
The `mqtt` climate platform lets you control your MQTT enabled HVAC devices.
|
||||
|
||||
@ -12,7 +12,7 @@ ha_category:
|
||||
- DIY
|
||||
- Climate
|
||||
ha_release: 0.29
|
||||
ha_iot_class: "Local Push"
|
||||
ha_iot_class: Local Push
|
||||
---
|
||||
|
||||
Integrates MySensors HVAC into Home Assistant. See the [main component] for configuration instructions.
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
x
Reference in New Issue
Block a user