mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-19 07:17:14 +00:00
Merge branch 'current' into next
This commit is contained in:
Franck Nijhof
commit
d2e4397766
38
CODEOWNERS
38
CODEOWNERS
@ -27,7 +27,6 @@ source/_integrations/alert.markdown @home-assistant/core
|
||||
source/_integrations/alexa.markdown @home-assistant/cloud @ochlocracy
|
||||
source/_integrations/alexa.smart_home.markdown @home-assistant/cloud @ochlocracy
|
||||
source/_integrations/almond.markdown @gcampax @balloob
|
||||
source/_integrations/alpha_vantage.markdown @fabaff
|
||||
source/_integrations/ambee.markdown @frenck
|
||||
source/_integrations/amberelectric.markdown @madpilot
|
||||
source/_integrations/ambiclimate.markdown @danielhiversen
|
||||
@ -41,7 +40,6 @@ source/_integrations/apple_tv.markdown @postlund
|
||||
source/_integrations/apprise.markdown @caronc
|
||||
source/_integrations/aprs.markdown @PhilRW
|
||||
source/_integrations/arcam_fmj.markdown @elupus
|
||||
source/_integrations/arest.markdown @fabaff
|
||||
source/_integrations/arris_tg2492lg.markdown @vanbalken
|
||||
source/_integrations/aseko_pool_live.markdown @milanmeu
|
||||
source/_integrations/asuswrt.markdown @kennedyshead @ollo69
|
||||
@ -64,7 +62,6 @@ source/_integrations/backup.markdown @home-assistant/core
|
||||
source/_integrations/balboa.markdown @garbled1
|
||||
source/_integrations/beewi_smartclim.markdown @alemuro
|
||||
source/_integrations/binary_sensor.markdown @home-assistant/core
|
||||
source/_integrations/bitcoin.markdown @fabaff
|
||||
source/_integrations/bizkaibus.markdown @UgaitzEtxebarria
|
||||
source/_integrations/blebox.markdown @bbx-a @bbx-jp
|
||||
source/_integrations/blink.markdown @fronzbot
|
||||
@ -136,7 +133,6 @@ source/_integrations/dsmr.markdown @Robbie1221 @frenck
|
||||
source/_integrations/dsmr_reader.markdown @depl0y
|
||||
source/_integrations/dunehd.markdown @bieniu
|
||||
source/_integrations/dwd_weather_warnings.markdown @runningman84 @stephan192 @Hummel95
|
||||
source/_integrations/dweet.markdown @fabaff
|
||||
source/_integrations/dynalite.markdown @ziv1234
|
||||
source/_integrations/ecobee.markdown @marthoc
|
||||
source/_integrations/econet.markdown @vangorra @w1ll1am23
|
||||
@ -183,7 +179,6 @@ source/_integrations/fjaraskupan.markdown @elupus
|
||||
source/_integrations/flick_electric.markdown @ZephireNZ
|
||||
source/_integrations/flipr.markdown @cnico
|
||||
source/_integrations/flo.markdown @dmulcahey
|
||||
source/_integrations/flock.markdown @fabaff
|
||||
source/_integrations/flume.markdown @ChrisMandich @bdraco
|
||||
source/_integrations/flunearyou.markdown @bachya
|
||||
source/_integrations/flux_led.markdown @icemanch @bdraco
|
||||
@ -195,6 +190,7 @@ source/_integrations/freebox.markdown @hacf-fr @Quentame
|
||||
source/_integrations/freedompro.markdown @stefano055415
|
||||
source/_integrations/fritz.markdown @mammuth @AaronDavidSchneider @chemelli74 @mib1185
|
||||
source/_integrations/fritzbox.markdown @mib1185 @flabbamann
|
||||
source/_integrations/fritzbox_callmonitor.markdown @cdce8p
|
||||
source/_integrations/fronius.markdown @nielstron @farmio
|
||||
source/_integrations/frontend.markdown @home-assistant/frontend
|
||||
source/_integrations/garages_amsterdam.markdown @klaasnicolaas
|
||||
@ -209,8 +205,7 @@ source/_integrations/geonetnz_quakes.markdown @exxamalte
|
||||
source/_integrations/geonetnz_volcano.markdown @exxamalte
|
||||
source/_integrations/gios.markdown @bieniu
|
||||
source/_integrations/github.markdown @timmo001 @ludeeus
|
||||
source/_integrations/gitter.markdown @fabaff
|
||||
source/_integrations/glances.markdown @fabaff @engrbm87
|
||||
source/_integrations/glances.markdown @engrbm87
|
||||
source/_integrations/goalzero.markdown @tkdrob
|
||||
source/_integrations/gogogate2.markdown @vangorra @bdraco
|
||||
source/_integrations/goodwe.markdown @mletenay @starkillerOG
|
||||
@ -261,7 +256,7 @@ source/_integrations/ign_sismologia.markdown @exxamalte
|
||||
source/_integrations/image.markdown @home-assistant/core
|
||||
source/_integrations/image_processing.markdown @home-assistant/core
|
||||
source/_integrations/incomfort.markdown @zxdavb
|
||||
source/_integrations/influxdb.markdown @fabaff @mdegat01
|
||||
source/_integrations/influxdb.markdown @mdegat01
|
||||
source/_integrations/input_boolean.markdown @home-assistant/core
|
||||
source/_integrations/input_button.markdown @home-assistant/core
|
||||
source/_integrations/input_datetime.markdown @home-assistant/core
|
||||
@ -303,6 +298,7 @@ source/_integrations/launch_library.markdown @ludeeus @DurgNomis-drol
|
||||
source/_integrations/lcn.markdown @alengwenus
|
||||
source/_integrations/lg_netcast.markdown @Drafteed
|
||||
source/_integrations/life360.markdown @pnbruckner
|
||||
source/_integrations/lifx.markdown @Djelibeybi
|
||||
source/_integrations/light.markdown @home-assistant/core
|
||||
source/_integrations/linux_battery.markdown @fabaff
|
||||
source/_integrations/litejet.markdown @joncar
|
||||
@ -322,6 +318,7 @@ source/_integrations/lyric.markdown @timmo001
|
||||
source/_integrations/mastodon.markdown @fabaff
|
||||
source/_integrations/matrix.markdown @tinloaf
|
||||
source/_integrations/mazda.markdown @bdr99
|
||||
source/_integrations/meater.markdown @Sotolotl @emontnemery
|
||||
source/_integrations/media_player.markdown @home-assistant/core
|
||||
source/_integrations/media_source.markdown @hunterjm
|
||||
source/_integrations/mediaroom.markdown @dgomes
|
||||
@ -348,7 +345,6 @@ source/_integrations/monoprice.markdown @etsinko @OnFreund
|
||||
source/_integrations/moon.markdown @fabaff @frenck
|
||||
source/_integrations/motion_blinds.markdown @starkillerOG
|
||||
source/_integrations/motioneye.markdown @dermotduffy
|
||||
source/_integrations/mpd.markdown @fabaff
|
||||
source/_integrations/mqtt.markdown @emontnemery
|
||||
source/_integrations/msteams.markdown @peroyvind
|
||||
source/_integrations/mullvad.markdown @meichthys
|
||||
@ -376,7 +372,6 @@ source/_integrations/nilu.markdown @hfurubotten
|
||||
source/_integrations/nina.markdown @DeerMaximum
|
||||
source/_integrations/nissan_leaf.markdown @filcole
|
||||
source/_integrations/nmbs.markdown @thibmaek
|
||||
source/_integrations/no_ip.markdown @fabaff
|
||||
source/_integrations/noaa_tides.markdown @jdelaney72
|
||||
source/_integrations/notify.markdown @home-assistant/core
|
||||
source/_integrations/notify_events.markdown @matrozov @papajojo
|
||||
@ -416,7 +411,7 @@ source/_integrations/panel_iframe.markdown @home-assistant/frontend
|
||||
source/_integrations/peco.markdown @IceBotYT
|
||||
source/_integrations/persistent_notification.markdown @home-assistant/core
|
||||
source/_integrations/philips_js.markdown @elupus
|
||||
source/_integrations/pi_hole.markdown @fabaff @johnluetke @shenxn
|
||||
source/_integrations/pi_hole.markdown @johnluetke @shenxn
|
||||
source/_integrations/picnic.markdown @corneyl
|
||||
source/_integrations/pilight.markdown @trekky12
|
||||
source/_integrations/plaato.markdown @JohNan
|
||||
@ -434,10 +429,11 @@ source/_integrations/proxmoxve.markdown @jhollowe @Corbeno
|
||||
source/_integrations/ps4.markdown @ktnrg45
|
||||
source/_integrations/pure_energie.markdown @klaasnicolaas
|
||||
source/_integrations/push.markdown @dgomes
|
||||
source/_integrations/pvoutput.markdown @fabaff @frenck
|
||||
source/_integrations/pvoutput.markdown @frenck
|
||||
source/_integrations/pvpc_hourly_pricing.markdown @azogue
|
||||
source/_integrations/qbittorrent.markdown @geoffreylagaisse
|
||||
source/_integrations/qld_bushfire.markdown @exxamalte
|
||||
source/_integrations/qnap_qsw.markdown @Noltari
|
||||
source/_integrations/quantum_gateway.markdown @cisasteelersfan
|
||||
source/_integrations/qvr_pro.markdown @oblogic7
|
||||
source/_integrations/qwikswitch.markdown @kellerza
|
||||
@ -470,6 +466,7 @@ source/_integrations/rpi_power.markdown @shenxn @swetoast
|
||||
source/_integrations/rss_feed_template.markdown @home-assistant/core
|
||||
source/_integrations/rtsp_to_webrtc.markdown @allenporter
|
||||
source/_integrations/ruckus_unleashed.markdown @gabe565
|
||||
source/_integrations/sabnzbd.markdown @shaiu
|
||||
source/_integrations/safe_mode.markdown @home-assistant/core
|
||||
source/_integrations/saj.markdown @fredericvl
|
||||
source/_integrations/samsungtv.markdown @chemelli74 @epenet
|
||||
@ -486,6 +483,7 @@ source/_integrations/senseme.markdown @mikelawrence @bdraco
|
||||
source/_integrations/sensibo.markdown @andrey-git @gjohansson-ST
|
||||
source/_integrations/sensor.markdown @home-assistant/core
|
||||
source/_integrations/sentry.markdown @dcramer @frenck
|
||||
source/_integrations/senz.markdown @milanmeu
|
||||
source/_integrations/serial.markdown @fabaff
|
||||
source/_integrations/seven_segments.markdown @fabaff
|
||||
source/_integrations/sharkiq.markdown @JeffResc @funkybunch @AritroSaha10
|
||||
@ -504,6 +502,7 @@ source/_integrations/sky_hub.markdown @rogerselwyn
|
||||
source/_integrations/slack.markdown @bachya
|
||||
source/_integrations/sleepiq.markdown @mfugate1 @kbickar
|
||||
source/_integrations/slide.markdown @ualex73
|
||||
source/_integrations/slimproto.markdown @marcelveldt
|
||||
source/_integrations/sma.markdown @kellerza @rklomp
|
||||
source/_integrations/smappee.markdown @bsmappee
|
||||
source/_integrations/smart_meter_texas.markdown @grahamwetzler
|
||||
@ -512,7 +511,6 @@ source/_integrations/smarttub.markdown @mdz
|
||||
source/_integrations/smarty.markdown @z0mbieprocess
|
||||
source/_integrations/smhi.markdown @gjohansson-ST
|
||||
source/_integrations/sms.markdown @ocalvo
|
||||
source/_integrations/smtp.markdown @fabaff
|
||||
source/_integrations/solaredge.markdown @frenck
|
||||
source/_integrations/solaredge_local.markdown @drobtravels @scheric
|
||||
source/_integrations/solarlog.markdown @Ernst79
|
||||
@ -527,11 +525,12 @@ source/_integrations/speedtestdotnet.markdown @rohankapoorcom @engrbm87
|
||||
source/_integrations/spider.markdown @peternijssen
|
||||
source/_integrations/splunk.markdown @Bre77
|
||||
source/_integrations/spotify.markdown @frenck
|
||||
source/_integrations/sql.markdown @dgomes
|
||||
source/_integrations/sql.markdown @dgomes @gjohansson-ST
|
||||
source/_integrations/squeezebox.markdown @rajlaud
|
||||
source/_integrations/srp_energy.markdown @briglx
|
||||
source/_integrations/starline.markdown @anonym-tsk
|
||||
source/_integrations/statistics.markdown @fabaff @ThomDietrich
|
||||
source/_integrations/steam_online.markdown @tkdrob
|
||||
source/_integrations/steamist.markdown @bdraco
|
||||
source/_integrations/stiebel_eltron.markdown @fucm
|
||||
source/_integrations/stookalert.markdown @fwestenberg @frenck
|
||||
@ -553,7 +552,6 @@ source/_integrations/syncthing.markdown @zhulik
|
||||
source/_integrations/syncthru.markdown @nielstron
|
||||
source/_integrations/synology_dsm.markdown @hacf-fr @Quentame @mib1185
|
||||
source/_integrations/synology_srm.markdown @aerialls
|
||||
source/_integrations/syslog.markdown @fabaff
|
||||
source/_integrations/system_bridge.markdown @timmo001
|
||||
source/_integrations/tado.markdown @michaelarnauts @north3221
|
||||
source/_integrations/tag.markdown @balloob @dmulcahey
|
||||
@ -561,7 +559,7 @@ source/_integrations/tailscale.markdown @frenck
|
||||
source/_integrations/tankerkoenig.markdown @guillempages @mib1185
|
||||
source/_integrations/tapsaff.markdown @bazwilliams
|
||||
source/_integrations/tasmota.markdown @emontnemery
|
||||
source/_integrations/tautulli.markdown @ludeeus
|
||||
source/_integrations/tautulli.markdown @ludeeus @tkdrob
|
||||
source/_integrations/tellduslive.markdown @fredrike
|
||||
source/_integrations/template.markdown @PhracturedBlue @tetienne @home-assistant/core
|
||||
source/_integrations/tesla_wall_connector.markdown @einarhauks
|
||||
@ -576,14 +574,15 @@ source/_integrations/todoist.markdown @boralyl
|
||||
source/_integrations/tolo.markdown @MatthiasLohr
|
||||
source/_integrations/tomorrowio.markdown @raman325
|
||||
source/_integrations/totalconnect.markdown @austinmroczek
|
||||
source/_integrations/tplink.markdown @rytilahti @thegardenmonkey
|
||||
source/_integrations/tplink.markdown @rytilahti @thegardenmonkey @bdraco
|
||||
source/_integrations/traccar.markdown @ludeeus
|
||||
source/_integrations/tractive.markdown @Danielhiversen @zhulik @bieniu
|
||||
source/_integrations/trafikverket_ferry.markdown @gjohansson-ST
|
||||
source/_integrations/trafikverket_train.markdown @endor-force @gjohansson-ST
|
||||
source/_integrations/trafikverket_weatherstation.markdown @endor-force @gjohansson-ST
|
||||
source/_integrations/transmission.markdown @engrbm87 @JPHutchins
|
||||
source/_integrations/tts.markdown @pvizeli
|
||||
source/_integrations/tuya.markdown @Tuya @zlinoliver @METISU @frenck
|
||||
source/_integrations/tuya.markdown @Tuya @zlinoliver @frenck
|
||||
source/_integrations/twentemilieu.markdown @frenck
|
||||
source/_integrations/twinkly.markdown @dr1rrb @Robbie1221
|
||||
source/_integrations/unifi.markdown @Kane610
|
||||
@ -593,7 +592,6 @@ source/_integrations/upb.markdown @gwww
|
||||
source/_integrations/upc_connect.markdown @pvizeli @fabaff
|
||||
source/_integrations/upcloud.markdown @scop
|
||||
source/_integrations/update.markdown @home-assistant/core
|
||||
source/_integrations/updater.markdown @home-assistant/core
|
||||
source/_integrations/upnp.markdown @StevenLooman @ehendrix23
|
||||
source/_integrations/uptime.markdown @frenck
|
||||
source/_integrations/uptimerobot.markdown @ludeeus @chemelli74
|
||||
@ -608,7 +606,7 @@ source/_integrations/venstar.markdown @garbled1
|
||||
source/_integrations/vera.markdown @pavoni
|
||||
source/_integrations/verisure.markdown @frenck
|
||||
source/_integrations/versasense.markdown @flamm3blemuff1n
|
||||
source/_integrations/version.markdown @fabaff @ludeeus
|
||||
source/_integrations/version.markdown @ludeeus
|
||||
source/_integrations/vesync.markdown @markperdue @webdjoe @thegardenmonkey
|
||||
source/_integrations/vicare.markdown @oischinger
|
||||
source/_integrations/vilfo.markdown @ManneW
|
||||
|
||||
2
Gemfile
2
Gemfile
@ -20,7 +20,7 @@ group :jekyll_plugins do
|
||||
end
|
||||
|
||||
gem 'sinatra', '2.2.0'
|
||||
gem 'nokogiri', '1.13.4'
|
||||
gem 'nokogiri', '1.13.6'
|
||||
|
||||
# Windows and JRuby does not include zoneinfo files, so bundle the tzinfo-data gem
|
||||
# and associated library
|
||||
|
||||
@ -70,10 +70,10 @@ GEM
|
||||
multi_json (1.15.0)
|
||||
mustermann (1.1.1)
|
||||
ruby2_keywords (~> 0.0.1)
|
||||
nokogiri (1.13.4)
|
||||
nokogiri (1.13.6)
|
||||
mini_portile2 (~> 2.8.0)
|
||||
racc (~> 1.4)
|
||||
nokogiri (1.13.4-x64-mingw32)
|
||||
nokogiri (1.13.6-x64-mingw32)
|
||||
racc (~> 1.4)
|
||||
pathutil (0.16.2)
|
||||
forwardable-extended (~> 2.6)
|
||||
@ -123,7 +123,7 @@ DEPENDENCIES
|
||||
jekyll-paginate (= 1.1.0)
|
||||
jekyll-sitemap (= 1.4.0)
|
||||
jekyll-toc (= 0.17.1)
|
||||
nokogiri (= 1.13.4)
|
||||
nokogiri (= 1.13.6)
|
||||
rake (= 13.0.6)
|
||||
sass-globbing (= 1.1.5)
|
||||
sassc (= 2.1.0)
|
||||
|
||||
@ -106,9 +106,9 @@ social:
|
||||
|
||||
# Home Assistant release details
|
||||
current_major_version: 2022
|
||||
current_minor_version: 4
|
||||
current_patch_version: 7
|
||||
date_released: 2022-04-24
|
||||
current_minor_version: 5
|
||||
current_patch_version: 3
|
||||
date_released: 2022-05-08
|
||||
|
||||
# Either # or the anchor link to latest release notes in the blog post.
|
||||
# Must be prefixed with a # and have double quotes around it.
|
||||
|
||||
16
package-lock.json
generated
16
package-lock.json
generated
@ -16,7 +16,7 @@
|
||||
"remark-stringify": "^10.0.2",
|
||||
"textlint": "^12.1.1",
|
||||
"textlint-rule-common-misspellings": "^1.0.1",
|
||||
"textlint-rule-terminology": "^2.1.5"
|
||||
"textlint-rule-terminology": "^3.0.0"
|
||||
}
|
||||
},
|
||||
"node_modules/@azu/format-text": {
|
||||
@ -5251,9 +5251,9 @@
|
||||
}
|
||||
},
|
||||
"node_modules/textlint-rule-terminology": {
|
||||
"version": "2.1.5",
|
||||
"resolved": "https://registry.npmjs.org/textlint-rule-terminology/-/textlint-rule-terminology-2.1.5.tgz",
|
||||
"integrity": "sha512-VW+ea4ByLPddSUqoFkVVJF8zWnO8kqKwvC681wGFAjI4CYz9WhjEQH1ikhoEHXnd5AFXNArcjyoa8hoihrXy0w==",
|
||||
"version": "3.0.0",
|
||||
"resolved": "https://registry.npmjs.org/textlint-rule-terminology/-/textlint-rule-terminology-3.0.0.tgz",
|
||||
"integrity": "sha512-ySHbdLcA9Mdbbbc/Wkts3f8CVvY2Nsy3r21NH4bK785jhdpZozG771WDR7d7L5nNnFBeH7MmS0IcscfMpxMyvQ==",
|
||||
"dev": true,
|
||||
"dependencies": {
|
||||
"lodash": "^4.17.15",
|
||||
@ -5261,7 +5261,7 @@
|
||||
"textlint-rule-helper": "^2.1.1"
|
||||
},
|
||||
"engines": {
|
||||
"node": ">=8.9"
|
||||
"node": ">=14"
|
||||
}
|
||||
},
|
||||
"node_modules/textlint-rule-terminology/node_modules/@textlint/ast-node-types": {
|
||||
@ -9831,9 +9831,9 @@
|
||||
}
|
||||
},
|
||||
"textlint-rule-terminology": {
|
||||
"version": "2.1.5",
|
||||
"resolved": "https://registry.npmjs.org/textlint-rule-terminology/-/textlint-rule-terminology-2.1.5.tgz",
|
||||
"integrity": "sha512-VW+ea4ByLPddSUqoFkVVJF8zWnO8kqKwvC681wGFAjI4CYz9WhjEQH1ikhoEHXnd5AFXNArcjyoa8hoihrXy0w==",
|
||||
"version": "3.0.0",
|
||||
"resolved": "https://registry.npmjs.org/textlint-rule-terminology/-/textlint-rule-terminology-3.0.0.tgz",
|
||||
"integrity": "sha512-ySHbdLcA9Mdbbbc/Wkts3f8CVvY2Nsy3r21NH4bK785jhdpZozG771WDR7d7L5nNnFBeH7MmS0IcscfMpxMyvQ==",
|
||||
"dev": true,
|
||||
"requires": {
|
||||
"lodash": "^4.17.15",
|
||||
|
||||
@ -12,7 +12,7 @@
|
||||
"remark-stringify": "^10.0.2",
|
||||
"textlint": "^12.1.1",
|
||||
"textlint-rule-common-misspellings": "^1.0.1",
|
||||
"textlint-rule-terminology": "^2.1.5"
|
||||
"textlint-rule-terminology": "^3.0.0"
|
||||
},
|
||||
"resolutions": {
|
||||
"minimist": ">=1.2.5"
|
||||
|
||||
@ -85,6 +85,7 @@ module Jekyll
|
||||
|
||||
# Default title used for in-line text
|
||||
DEFAULT_TITLES = {
|
||||
"automations" => "Automations & Scenes",
|
||||
"blueprint_import" => "Import Blueprint",
|
||||
"cloud" => "Home Assistant Cloud",
|
||||
"config_energy" => "Energy Configuration",
|
||||
@ -92,7 +93,7 @@ module Jekyll
|
||||
"config_mqtt" => "MQTT Configuration",
|
||||
"config_zha" => "ZHA Configuration",
|
||||
"config_zwave_js" => "Z-Wave JS Configuration",
|
||||
"config" => "Configuration",
|
||||
"config" => "Settings",
|
||||
"developer_events" => "Events",
|
||||
"developer_services" => "Services",
|
||||
"developer_states" => "States",
|
||||
|
||||
@ -103,7 +103,7 @@ content: |
|
||||
|
||||
## Icons
|
||||
|
||||
You can also use [materialdesignicons.com](https://materialdesignicons.com/) icons in the `content` of the card.
|
||||
You can use [materialdesignicons.com](https://materialdesignicons.com/) icons in the `content` of the card.
|
||||
|
||||
For example:
|
||||
|
||||
@ -116,3 +116,25 @@ content: |
|
||||
```
|
||||
|
||||
{% endraw %}
|
||||
|
||||
|
||||
## ha-alert
|
||||
|
||||
You can also use our [\`ha-alert\`](https://design.home-assistant.io/#components/ha-alert) component in the Markdown card.
|
||||
|
||||
Example:
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/dashboards/lovelace_markdown_ha-alert.png' alt='Screenshot of the ha-alert elements in a markdown card'>
|
||||
Screenshot of the ha-alert elements in a markdown card.
|
||||
</p>
|
||||
|
||||
```yaml
|
||||
type: markdown
|
||||
content: |
|
||||
<ha-alert alert-type="error">This is an error alert — check it out!</ha-alert>
|
||||
<ha-alert alert-type="warning">This is a warning alert — check it out!</ha-alert>
|
||||
<ha-alert alert-type="info">This is an info alert — check it out!</ha-alert>
|
||||
<ha-alert alert-type="success">This is a success alert — check it out!</ha-alert>
|
||||
<ha-alert title="Test alert">This is an alert with a title</ha-alert>
|
||||
```
|
||||
|
||||
@ -3,7 +3,7 @@ title: "Troubleshooting Automations"
|
||||
description: "Tips on how to troubleshoot your automations."
|
||||
---
|
||||
|
||||
When an automation is run, all steps are recorded and a trace is made. From the UI choose **Configuration** which is located in the sidebar, then click on **Automation** to go to the automation editor or click this button directly: {% my automations badge %}
|
||||
When an automation is run, all steps are recorded and a trace is made. From the UI choose **Settings** which is located in the sidebar, then click on **Automations & Scenes** to go to the automation editor or click this button directly: {% my automations badge %}
|
||||
|
||||
Click on the clock icon next to an automation to enter the debugging screen. Alternatively, click on **Show trace** directly from a Logbook automation entry.
|
||||
|
||||
|
||||
@ -34,6 +34,7 @@ The following selectors are currently available:
|
||||
- [RGB color selector](#rgb-color-selector)
|
||||
- [Select selector](#select-selector)
|
||||
- [Target selector](#target-selector)
|
||||
- [Template selector](#template-selector)
|
||||
- [Text selector](#text-selector)
|
||||
- [Theme selector](#theme-selector)
|
||||
- [Time selector](#time-selector)
|
||||
|
||||
@ -230,7 +230,7 @@ For this tutorial, we're going to share it on GitHub Gists. This is a good optio
|
||||
- Content is the content of the blueprint file.
|
||||
- Click the "Create Gist" button
|
||||
|
||||
You can now copy the URL of your new Gist and share it with other people. They can import it by going to **Configuration**, **Blueprints** and clicking on the blue "Import Blueprint" button.
|
||||
You can now copy the URL of your new Gist and share it with other people. They can import it by going to **Settings** -> **Automations & Scenes** -> **Blueprints** and clicking on the blue "Import Blueprint" button.
|
||||
|
||||
### Share on the Blueprint Exchange
|
||||
|
||||
|
||||
@ -3,7 +3,7 @@ title: "Configuration.yaml"
|
||||
description: "Configuring Home Assistant via text files."
|
||||
---
|
||||
|
||||
While you can configure most of Home Assistant directly from the user interface under {% my config title="Configuration" %}, some parts need you to edit `configuration.yaml`. This file contains integrations to be loaded along with their configurations. Throughout the documentation you will find snippets that you can add to your configuration file to enable specific functionality.
|
||||
While you can configure most of Home Assistant directly from the user interface under {% my config %}, some parts need you to edit `configuration.yaml`. This file contains integrations to be loaded along with their configurations. Throughout the documentation you will find snippets that you can add to your configuration file to enable specific functionality.
|
||||
|
||||
If you run into trouble while configuring Home Assistant, refer to the [configuration troubleshooting page](/docs/configuration/troubleshooting/) and the [`configuration.yaml` examples](/examples/#example-configurationyaml).
|
||||
|
||||
|
||||
@ -205,7 +205,7 @@ This will allow you to `!include` files with `.yml` extensions from within the `
|
||||
- `!include_dir_merge_list` will return the content of a directory as a list by merging all files (which should contain a list) into 1 big list.
|
||||
- `!include_dir_merge_named` will return the content of a directory as a dictionary by loading each file and merging it into 1 big dictionary.
|
||||
|
||||
These work recursively. As an example using `!include_dir_* automation`, will include all 6 files shown below:
|
||||
These work recursively. As an example using `!include_dir_list automation`, will include all 6 files shown below:
|
||||
|
||||
```bash
|
||||
.
|
||||
|
||||
@ -72,7 +72,7 @@ Not supported in [limited templates](#limited-templates).
|
||||
- Iterating `states` will yield each state sorted alphabetically by entity ID.
|
||||
- Iterating `states.domain` will yield each state of that domain sorted alphabetically by entity ID.
|
||||
- `states.sensor.temperature` returns the state object for `sensor.temperature` (avoid when possible, see note below).
|
||||
- `states('device_tracker.paulus')` will return the state string (not the object) of the given entity or `unknown` if it doesn't exist.
|
||||
- `states('device_tracker.paulus')` will return the state string (not the object) of the given entity, `unknown` if it doesn't exist, `unavailable` if the object exists but is not yet available.
|
||||
- `is_state('device_tracker.paulus', 'home')` will test if the given entity is the specified state.
|
||||
- `state_attr('device_tracker.paulus', 'battery')` will return the value of the attribute or None if it doesn't exist.
|
||||
- `is_state_attr('device_tracker.paulus', 'battery', 40)` will test if the given entity attribute is the specified state (in this case, a numeric value). Note that the attribute can be `None` and you want to check if it is `None`, you need to use `state_attr('sensor.my_sensor', 'attr') == None`.
|
||||
@ -119,6 +119,10 @@ Other state examples:
|
||||
Paulus is at {{ states('device_tracker.paulus') }}.
|
||||
{% endif %}
|
||||
|
||||
#check sensor.train_departure_time state
|
||||
{% if states('sensor.train_departure_time') in ("unavailable", "unknown") %}
|
||||
{{ ... }}
|
||||
|
||||
{% set state = states('sensor.temperature') %}{{ state | float + 1 if is_number(state) else "invalid temperature" }}
|
||||
|
||||
{% set state = states('sensor.temperature') %}{{ (state | float * 10) | round(2) if is_number(state)}}
|
||||
|
||||
@ -34,7 +34,7 @@ If you are running Home Assistant in a container, you can use the command line i
|
||||
#### To reset a user's password, as an administrator via the web interface
|
||||
|
||||
1. Confirm that you have "Advanced Mode" activated on your "Profile" page.
|
||||
2. Click "Configuration" in the sidebar.
|
||||
2. Click "Settings" in the sidebar.
|
||||
3. Scroll down to "Users", and click in to that section.
|
||||
4. Click on the user, this should bring up a dialog box.
|
||||
5. At the bottom of the dialog box, click "Change Password".
|
||||
@ -45,7 +45,7 @@ If you are running Home Assistant in a container, you can use the command line i
|
||||
|
||||
#### To delete a user, as an administrator via the web interface
|
||||
|
||||
1. Click "Configuration" in the sidebar.
|
||||
1. Click "Settings" in the sidebar.
|
||||
2. Scroll down to "Users", and click in to that section.
|
||||
3. Click on the user, this should bring up a dialog box.
|
||||
4. At the bottom of the dialog box, click "Delete User".
|
||||
|
||||
@ -5,7 +5,7 @@ description: "Instructions on how to use the scenes editor."
|
||||
|
||||
In Home Assistant 0.102 we introduced the first version of our scene editor. If you just created a new configuration with Home Assistant, then you're all set! Go to the UI and enjoy.
|
||||
|
||||
From the UI choose **Configuration** which is located in the sidebar, then click on **Scenes** to go to the scene editor. Press the **Add Scene** button in the lower right corner to get started.
|
||||
From the UI choose **Settings** which is located in the sidebar, then click on **Automations & Scenes** to go to the scene editor. Press the **Add Scene** button in the lower right corner to get started.
|
||||
|
||||
Choose a meaningful name for your scene.
|
||||
|
||||
|
||||
@ -388,7 +388,7 @@ The sunset/sunrise conditions do not work in locations inside the polar circles,
|
||||
In those cases it is advised to use conditions evaluating the solar elevation instead of the before/after sunset/sunrise conditions.
|
||||
</div>
|
||||
|
||||
This is an example of 1 hour offset after sunset:
|
||||
This is an example of 1 hour offset before sunset:
|
||||
```yaml
|
||||
condition:
|
||||
condition: sun
|
||||
|
||||
@ -8,9 +8,12 @@ description: "Extended instructions how to setup Z-Wave."
|
||||
You need to have a compatible Z-Wave stick or module installed. The following devices have been confirmed to work with Z-Wave JS:
|
||||
|
||||
- 700 series controllers
|
||||
- Aeotec Z-Stick 7
|
||||
- Zooz ZST10 700
|
||||
- Silicon Labs SLUSB7000A
|
||||
- Aeotec Z-Stick 7 USB stick (ZWA010)
|
||||
- Aeotec Z-Pi 7 Raspberry Pi HAT/Shield (ZWA025)
|
||||
- Silicon Labs UZB-7 USB Stick (Silabs SLUSB7000A / SLUSB001A)
|
||||
- Zooz S2 Stick 700 (ZST10 700)
|
||||
- ZWave.me RaZberry 7 (ZME_RAZBERRY7)
|
||||
- ZWave.me RaZberry 7 Pro (ZMEERAZBERRY7_ANT or ZMEURAZBERRY7_ANT)
|
||||
|
||||
- 500 series controllers
|
||||
- Aeotec Z-Stick Gen5 (see note below)
|
||||
|
||||
@ -29,7 +29,7 @@ The same will work for automations.
|
||||
|
||||
### REST API
|
||||
|
||||
Using the [REST API](https://developers.home-assistant.io/docs/api/rest/ to send a message to a given topic.
|
||||
Using the [REST API](https://developers.home-assistant.io/docs/api/rest/) to send a message to a given topic.
|
||||
|
||||
```bash
|
||||
$ curl -X POST \
|
||||
|
||||
@ -49,7 +49,7 @@
|
||||
<li>{% active_link /dashboards/actions/ Actions %}</li>
|
||||
<li>
|
||||
<a
|
||||
href="https://developers.home-assistant.io/docs/frontend/custom-ui/lovelace-custom-card.html"
|
||||
href="https://developers.home-assistant.io/docs/frontend/custom-ui/custom-card/"
|
||||
>Developing Custom Cards
|
||||
<i class="icon-external-link"></i>
|
||||
</a>
|
||||
|
||||
@ -20,7 +20,7 @@ To update Home Assistant Core when you run Home Assistant {{ page.installation_n
|
||||
content: |
|
||||
|
||||
1. Open your Home Assistant UI
|
||||
2. Navigate to the Configuration panel
|
||||
2. Navigate to the Settings panel
|
||||
3. On the top you will be presented with an update notification
|
||||
|
||||
_If you do not see that notification you can click the overflow menu in the top right and select "Check for updates"._
|
||||
|
||||
@ -34,7 +34,7 @@ Once the Home Assistant Container is running Home Assistant should be accessible
|
||||
|
||||
If you change the configuration you have to restart the server. To do that you have 3 options.
|
||||
|
||||
1. In your Home Assistant UI go to the **Configuration** panel -> **Server management** and click the "Restart" button.
|
||||
1. In your Home Assistant UI go to the **Settings** -> **System** and click the "Restart" button.
|
||||
2. You can go to the **Developer Tools** -> **Services**, select the service `homeassistant.restart` and click "Call Service".
|
||||
3. Restart it from a terminal.
|
||||
|
||||
|
||||
@ -26,7 +26,7 @@ The AEMET OpenData service is completely free but is limited to the Spanish terr
|
||||
|
||||
## Configuration
|
||||
|
||||
To add AEMET OpenData integration go to **Configuration** >> **Devices & Services** and find the integration in the list.
|
||||
To add AEMET OpenData integration go to **Settings** -> **Devices & Services** and find the integration in the list.
|
||||
|
||||
{% configuration_basic %}
|
||||
API Key:
|
||||
|
||||
@ -11,6 +11,7 @@ ha_codeowners:
|
||||
ha_domain: airly
|
||||
ha_quality_scale: platinum
|
||||
ha_platforms:
|
||||
- diagnostics
|
||||
- sensor
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
@ -5,8 +5,6 @@ ha_category:
|
||||
- Finance
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_release: '0.60'
|
||||
ha_codeowners:
|
||||
- '@fabaff'
|
||||
ha_domain: alpha_vantage
|
||||
ha_platforms:
|
||||
- sensor
|
||||
|
||||
@ -8,8 +8,6 @@ ha_category:
|
||||
- Switch
|
||||
ha_iot_class: Local Polling
|
||||
ha_release: 0.9
|
||||
ha_codeowners:
|
||||
- '@fabaff'
|
||||
ha_domain: arest
|
||||
ha_platforms:
|
||||
- binary_sensor
|
||||
|
||||
@ -28,7 +28,7 @@ backup:
|
||||
```
|
||||
|
||||
You need to restart Home Assistant after you add this configuration.
|
||||
When it has started up again you will find a new "Backup" entry in the main menu (**Configuration** -> **Backup**).
|
||||
When it has started up again you will find a new "Backup" entry in the main menu (**Settings** -> **System** -> **Backup**).
|
||||
|
||||
The backup files are stored in a new "backups" subdirectory in the root of your configuration directory.
|
||||
|
||||
|
||||
@ -5,8 +5,6 @@ ha_category:
|
||||
- Finance
|
||||
ha_release: pre 0.7
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_codeowners:
|
||||
- '@fabaff'
|
||||
ha_domain: bitcoin
|
||||
ha_platforms:
|
||||
- sensor
|
||||
|
||||
@ -47,7 +47,7 @@ This integration provides the following platforms:
|
||||
|
||||
## Configuration
|
||||
|
||||
Enable the `BMW Connected Drive` integration via **Configuration** > **Devices & Services**.
|
||||
Enable the `BMW Connected Drive` integration via **Settings** -> **Devices & Services**.
|
||||
|
||||
<div class='note'>
|
||||
|
||||
|
||||
@ -56,4 +56,4 @@ automation:
|
||||
{{ trigger.calendar_event.start }}
|
||||
mode: single
|
||||
```
|
||||
{% endraw %}
|
||||
{% endraw %}
|
||||
|
||||
@ -10,6 +10,8 @@ ha_domain: camera
|
||||
ha_codeowners:
|
||||
- '@home-assistant/core'
|
||||
ha_integration_type: integration
|
||||
ha_platforms:
|
||||
- diagnostics
|
||||
---
|
||||
|
||||
The camera integration allows you to use IP cameras with Home Assistant.
|
||||
|
||||
@ -29,7 +29,7 @@ cloud:
|
||||
|
||||
Documentation of further configuration possibilities are located at [NabuCasa](https://www.nabucasa.com/config/)
|
||||
|
||||
Once activated, go to the configuration panel in Home Assistant and create an account and log in. If you are not seeing the **Configuration** panel, make sure you have the following option enabled in your `configuration.yaml` file.
|
||||
Once activated, go to the configuration panel in Home Assistant and create an account and log in. If you are not seeing the **Settings** panel, make sure you have the following option enabled in your `configuration.yaml` file.
|
||||
|
||||
```yaml
|
||||
config:
|
||||
|
||||
@ -25,7 +25,7 @@ Before setting up, you should assign a static IP address/DHCP reservation on you
|
||||
|
||||
## Options
|
||||
|
||||
The Control4 integration offers additional options in **Configuration** -> **Devices & Services** -> **Control4** -> **Options**:
|
||||
The Control4 integration offers additional options in **Settings** -> **Devices & Services** -> **Control4** -> **Options**:
|
||||
|
||||
{% configuration %}
|
||||
Seconds between updates:
|
||||
|
||||
@ -32,7 +32,7 @@ There are two Dexcom Share servers, `US` for United States customers, and `OUS`
|
||||
|
||||
### Unit of measurement
|
||||
|
||||
The integrations allows both `mg/dL` and `mmol/l` units of measurement for blood glucose values. To change your preferred unit of measurement, go to **Configuration** >> **Devices & Services** in the UI, and click `OPTIONS`.
|
||||
The integrations allows both `mg/dL` and `mmol/l` units of measurement for blood glucose values. To change your preferred unit of measurement, go to **Settings** -> **Devices & Services** in the UI, and click `OPTIONS`.
|
||||
|
||||
## Sensor
|
||||
|
||||
|
||||
@ -24,7 +24,7 @@ Please note that some devices, such as Samsung TVs, are rather picky about the s
|
||||
|
||||
## Options
|
||||
|
||||
Options for DLNA DMR devices can be set going to **Configuration** -> **Devices & Services** -> **DLNA Digital Media Renderer** -> **Configuration**.
|
||||
Options for DLNA DMR devices can be set going to **Settings** -> **Devices & Services** -> **DLNA Digital Media Renderer** -> **Configuration**.
|
||||
|
||||
{% configuration_basic %}
|
||||
Event listener port:
|
||||
|
||||
@ -14,7 +14,7 @@ ha_codeowners:
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
The DNS IP integration will expose an IP address, fetched via DNS resolution, as its value. It provides both IPv4 and IPv6 lookup as separate sensors depending on accessibility to resolvers.
|
||||
The DNS IP integration will expose an IP address, fetched via DNS resolution (every 2 minutes), as its value. It provides both IPv4 and IPv6 lookup as separate sensors depending on accessibility to resolvers.
|
||||
|
||||
1. When you enable the integration with the default value, it will query the [OpenDNS](https://www.opendns.com/) nameservers with the hostname `myip.opendns.com`, which will resolve to your external/public IP address.
|
||||
2. If you specify a `hostname`, a regular DNS lookup will be performed, providing you the IP the hostname resolves to.
|
||||
|
||||
@ -39,7 +39,7 @@ A sensor platform for Belgian, Dutch, Luxembourg and Swedish Smart Meters which
|
||||
|
||||
### Options
|
||||
|
||||
To configure options for DSMR integration go to **Configuration** >> **Devices & Services** and press **Options** on the DSMR card.
|
||||
To configure options for DSMR integration go to **Settings** -> **Devices & Services** and press **Options** on the DSMR card.
|
||||
|
||||
#### Time between updates
|
||||
|
||||
|
||||
@ -6,8 +6,6 @@ ha_category:
|
||||
- Sensor
|
||||
ha_release: 0.19
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_codeowners:
|
||||
- '@fabaff'
|
||||
ha_domain: dweet
|
||||
ha_platforms:
|
||||
- sensor
|
||||
|
||||
@ -21,7 +21,7 @@ The UK Environment Agency Flood Monitoring only provides data for England - Nort
|
||||
|
||||
## Configuration
|
||||
|
||||
Home Assistant offers the flood monitoring integration through **Configuration** -> **Devices & Services** -> **Environment Agency Flood Gauges**.
|
||||
Home Assistant offers the flood monitoring integration through **Settings** -> **Devices & Services** -> **Environment Agency Flood Gauges**.
|
||||
|
||||
You will be prompted to select a monitoring station. You can find the name of nearby monitoring stations on the Flood information service [website](https://flood-warning-information.service.gov.uk/river-and-sea-levels).
|
||||
|
||||
|
||||
@ -53,7 +53,7 @@ Your new application will now appear on the left. Upon clicking on the applicati
|
||||
|
||||
## Configuration
|
||||
|
||||
1. In the **Configuration** > **Devices & Services** menu, click **+** and then select "ecobee" from the pop-up menu.
|
||||
1. In the **Settings** -> **Devices & Services** menu, click **+** and then select "ecobee" from the pop-up menu.
|
||||
2. In the pop-up box, enter the API key you obtained from ecobee's [developer portal](https://ecobee.com/developers).
|
||||
3. In the next pop-up box, you will be presented with a unique four-character PIN code which you will need to authorize in the [ecobee consumer portal](https://www.ecobee.com/consumerportal/index.html). You can do this by logging in, selecting **My Apps** from the hamburger menu, clicking **Add Application** on the left, entering the PIN code from Home Assistant, clicking **Validate** and then **Add Application** in the bottom right.
|
||||
4. After authorizing the app with ecobee, return to Home Assistant and click **Submit**. If the authorization was successful, a configuration entry will be created and your thermostats and sensors will be available in Home Assistant.
|
||||
@ -80,7 +80,7 @@ api_key:
|
||||
<img src='/images/screenshots/ecobee-thermostat-card.png' />
|
||||
</p>
|
||||
|
||||
You must [restart Home Assistant](/docs/configuration/#reloading-changes) for the changes to take effect. After restarting, navigate to the **Configuration** > **Devices & Services** menu, hit **Configure** next to the discovered `ecobee` entry, and continue to authorize the app according to the above **Automatic Configuration**, starting at step 2.
|
||||
You must [restart Home Assistant](/docs/configuration/#reloading-changes) for the changes to take effect. After restarting, navigate to the **Settings** -> **Devices & Services** menu, hit **Configure** next to the discovered `ecobee` entry, and continue to authorize the app according to the above **Automatic Configuration**, starting at step 2.
|
||||
|
||||
## Notifications
|
||||
|
||||
|
||||
@ -79,7 +79,7 @@ monitored_variables:
|
||||
description: Talk time used
|
||||
talk_limit:
|
||||
description: Talk time limit
|
||||
talt_remaining:
|
||||
talk_remaining:
|
||||
description: Talk time remaining
|
||||
other_talk_used:
|
||||
description: Other talk time used (It could be international calls)
|
||||
|
||||
@ -5,8 +5,6 @@ ha_category:
|
||||
- Notifications
|
||||
ha_iot_class: Cloud Push
|
||||
ha_release: 0.71
|
||||
ha_codeowners:
|
||||
- '@fabaff'
|
||||
ha_domain: flock
|
||||
ha_platforms:
|
||||
- notify
|
||||
|
||||
@ -26,7 +26,7 @@ You can find your Client ID and Client Secret under "API Access" on the [setting
|
||||
|
||||
The Flume API access is available to Flume Insight users only, which may require a paid subscription.
|
||||
|
||||
To add `Flume` to your installation, go to **Configuration** >> **Devices & Services** in the UI, click the button with `+` sign and from the list of integrations select **Flume**.
|
||||
To add `Flume` to your installation, go to **Settings** -> **Devices & Services** in the UI, click the button with `+` sign and from the list of integrations select **Flume**.
|
||||
|
||||
## Configuration for Binary Sensor
|
||||
|
||||
|
||||
@ -38,7 +38,7 @@ Please consult the [API documentation](https://dev.freebox.fr/sdk/os/) for more
|
||||
|
||||
### Via the frontend
|
||||
|
||||
Menu: **Configuration** -> **Devices & Services**. Search for "Freebox", add your host and port, click submit.
|
||||
Menu: **Settings** -> **Devices & Services**. Search for "Freebox", add your host and port, click submit.
|
||||
|
||||
If you add the integration for the first time, follow the instructions in the [Initial setup](#initial-setup) section.
|
||||
|
||||
|
||||
@ -5,6 +5,7 @@ ha_category:
|
||||
- Binary Sensor
|
||||
- Presence Detection
|
||||
- Sensor
|
||||
- Updates
|
||||
ha_release: '0.10'
|
||||
ha_domain: fritz
|
||||
ha_config_flow: true
|
||||
|
||||
@ -10,6 +10,8 @@ ha_config_flow: true
|
||||
ha_platforms:
|
||||
- sensor
|
||||
ha_integration_type: integration
|
||||
ha_codeowners:
|
||||
- '@cdce8p'
|
||||
---
|
||||
|
||||
The `fritzbox_callmonitor` sensor monitors the call monitor exposed by [AVM FRITZ!Box](https://avm.de/produkte/fritzbox/) routers on TCP port 1012. It will assume the values `idle`, `ringing`, `dialing` or `talking` with the phone numbers involved contained in the state attributes.
|
||||
|
||||
@ -11,6 +11,7 @@ ha_codeowners:
|
||||
ha_domain: gios
|
||||
ha_quality_scale: platinum
|
||||
ha_platforms:
|
||||
- diagnostics
|
||||
- sensor
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
@ -5,8 +5,6 @@ ha_category:
|
||||
- Sensor
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_release: 0.47
|
||||
ha_codeowners:
|
||||
- '@fabaff'
|
||||
ha_domain: gitter
|
||||
ha_platforms:
|
||||
- sensor
|
||||
|
||||
@ -7,7 +7,6 @@ ha_iot_class: Local Polling
|
||||
ha_release: 0.7.3
|
||||
ha_config_flow: true
|
||||
ha_codeowners:
|
||||
- '@fabaff'
|
||||
- '@engrbm87'
|
||||
ha_domain: glances
|
||||
ha_platforms:
|
||||
|
||||
@ -56,6 +56,18 @@ Some groups, like the binary sensors and lights, allow you set the "All entities
|
||||
- Otherwise, the group state is `unknown` if at least one group member is `unknown` or `unavailable`.
|
||||
- Otherwise, the group state is `on`.
|
||||
|
||||
## Managing groups
|
||||
|
||||
To edit a group, **{% my helpers title="Settings -> Devices & Services -> Helpers" %}**. Find and select the group from the list.
|
||||
|
||||
|
||||
|
||||
### Group options
|
||||
|
||||
To add or remove entities from an existing group, click on `Group options`, all the existing entities are listed in the `members` section where you add and remove entities.
|
||||
|
||||
|
||||
|
||||
## YAML Configuration
|
||||
|
||||
Alternatlively, this integration can be configured and set up manually via YAML
|
||||
|
||||
@ -35,7 +35,7 @@ Supported units:
|
||||
|
||||
**Note:** Depending on the firmware, you may need to enable XMPP for this integration to work. From your Harmony app, go to: **Menu** > **Harmony Setup** > **Add/Edit Devices & Activities** > **Remote & Hub** > **Enable XMPP**.
|
||||
|
||||
Once the Logitech Harmony Hub has been configured, the default activity and duration in seconds between sending commands to a device can be adjusted in the settings via **Configuration** >> **Devices & Services** >> **Your Logitech Harmony Hub**
|
||||
Once the Logitech Harmony Hub has been configured, the default activity and duration in seconds between sending commands to a device can be adjusted in the settings via **Settings** -> **Devices & Services** >> **Your Logitech Harmony Hub**
|
||||
|
||||
### Configuration file
|
||||
|
||||
|
||||
@ -313,7 +313,7 @@ The HomeKit Accessory Protocol Specification only allows a maximum of 150 unique
|
||||
|
||||
### Multiple HomeKit instances
|
||||
|
||||
If you create a HomeKit integration via the UI (i.e., **Configuration** >> **Devices & Services**), it must be configured via the UI **only**. While the UI only offers limited configuration options at the moment, any attempt to configure a HomeKit instance created in the UI via the `configuration.yaml` file will result in another instance of HomeKit running on a different port.
|
||||
If you create a HomeKit integration via the UI (i.e., **Settings** -> **Devices & Services**), it must be configured via the UI **only**. While the UI only offers limited configuration options at the moment, any attempt to configure a HomeKit instance created in the UI via the `configuration.yaml` file will result in another instance of HomeKit running on a different port.
|
||||
|
||||
It is recommended to only edit a HomeKit instance in the UI that was created in the UI, and likewise, only edit a HomeKit instance in YAML that was created in YAML.
|
||||
|
||||
@ -636,7 +636,7 @@ Ensure that the [`ffmpeg`](/integrations/ffmpeg) integration is configured corre
|
||||
|
||||
#### Camera streaming is unstable or slow
|
||||
|
||||
If your camera supports native H.264 streams, Home Assistant can avoid converting the video stream, which is an expensive operation. To enable native H.264 streaming when configured via YAML, change the `video_codec` to `copy`. To allow native H.264 streaming when setting up HomeKit via the UI, go to **Configuration** >> **Devices & Services** in the UI, click **Options** for your HomeKit Bridge, and check the box for your camera on the `Cameras that support native H.264 streams` screen.
|
||||
If your camera supports native H.264 streams, Home Assistant can avoid converting the video stream, which is an expensive operation. To enable native H.264 streaming when configured via YAML, change the `video_codec` to `copy`. To allow native H.264 streaming when setting up HomeKit via the UI, go to **Settings** -> **Devices & Services** in the UI, click **Options** for your HomeKit Bridge, and check the box for your camera on the `Cameras that support native H.264 streams` screen.
|
||||
|
||||
#### Multiple camera streams
|
||||
|
||||
|
||||
@ -62,11 +62,7 @@ ifttt:
|
||||
```
|
||||
|
||||
`key` is your API key which can be obtained by viewing the **Settings** of the [Webhooks applet](https://ifttt.com/services/maker_webhooks/settings). It's the last part of the URL (e.g., https://maker.ifttt.com/use/MYAPIKEY) you will find under **My Applets** > **Webhooks** > **Settings**.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/integrations/ifttt/finding_key.png' />
|
||||
Property screen of the Maker Channel
|
||||
</p>
|
||||
|
||||
|
||||
Once you have added your key to your `configuration.yaml` file, restart your Home Assistant instance. This will load up the IFTTT integration and make a service available to trigger events in IFTTT.
|
||||
|
||||
@ -88,18 +84,29 @@ ifttt:
|
||||
|
||||
### Testing your trigger
|
||||
|
||||
You can use **Developer Tools** to test your [Webhooks](https://ifttt.com/maker_webhooks) trigger. To do this, open the Home Assistant sidebar, click on Developer Tools, and then the **Services** tab. Fill in the following values:
|
||||
You can use **Developer Tools** to test your [Webhooks](https://ifttt.com/maker_webhooks) trigger. To do this, open the Home Assistant sidebar, click on **Developer Tools** -> **Services** tab. Select `IFTTT: Trigger` as the service and fill in the following values:
|
||||
|
||||
Field | Value
|
||||
----- | -----
|
||||
domain | `ifttt`
|
||||
service | `trigger`
|
||||
Service Data | `{"event": "EventName", "value1": "Hello World"}`
|
||||
{% configuration_basic %}
|
||||
event:
|
||||
description: The name of the event to send.
|
||||
required: true
|
||||
type: string
|
||||
value1:
|
||||
description: Generic field to send data via the event.
|
||||
required: false
|
||||
type: string
|
||||
value2:
|
||||
description: Generic field to send data via the event.
|
||||
required: false
|
||||
type: string
|
||||
value3:
|
||||
description: Generic field to send data via the event.
|
||||
required: false
|
||||
type: string
|
||||
{% endconfiguration_basic %}
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/integrations/ifttt/testing_service.png' />
|
||||
When your screen looks like this, click the 'call service' button.
|
||||
</p>
|
||||
|
||||
|
||||
By default, the trigger is sent to all the API keys from `configuration.yaml`. If you
|
||||
want to send the trigger to a specific key use the `target` field:
|
||||
@ -112,19 +119,22 @@ Service Data | `{"event": "EventName", "value1": "Hello World", "target": "YOUR_
|
||||
|
||||
The `target` field can contain a single key name or a list of key names.
|
||||
|
||||
### Setting up a recipe
|
||||
### Setting up an applet
|
||||
|
||||
Press the *New applet* button and search for *Webhooks*.
|
||||
Press the *Create* button and *Add* on **If This**. Search for *Webhooks*.
|
||||
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/integrations/ifttt/setup_service.png' />
|
||||
Choose "Webhooks" as service.
|
||||
</p>
|
||||
Choose *Webhooks* service.
|
||||
|
||||
|
||||
Select *Receive a web request*.
|
||||
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/integrations/ifttt/setup_trigger.png' />
|
||||
You need to setup a unique trigger for each event you sent to IFTTT.
|
||||
</p>
|
||||
|
||||
|
||||
Add the *Then That* action. The below example sends a notification to the IFTTT mobile app and adds `value1` to the message:
|
||||
|
||||
|
||||
{% raw %}
|
||||
|
||||
|
||||
@ -7,7 +7,6 @@ ha_category:
|
||||
ha_release: 0.9
|
||||
ha_iot_class: Local Push
|
||||
ha_codeowners:
|
||||
- '@fabaff'
|
||||
- '@mdegat01'
|
||||
ha_domain: influxdb
|
||||
ha_platforms:
|
||||
|
||||
@ -16,7 +16,7 @@ The `input_datetime` integration allows the user to define date and time values
|
||||
that can be controlled via the frontend and can be used within automations and
|
||||
templates.
|
||||
|
||||
The preferred way to configure input datetime is via the user interface at **Configuration** -> **Helpers**. Click the add button and then choose the **Date and/or time** option.
|
||||
The preferred way to configure input datetime is via the user interface at **Settings** -> **Devices & Services** -> **Helpers**. Click the add button and then choose the **Date and/or time** option.
|
||||
|
||||
To be able to add **Helpers** via the user interface you should have `default_config:` in your `configuration.yaml`, it should already be there by default unless you removed it.
|
||||
If you removed `default_config:` from your configuration, you must add `input_datetime:` to your `configuration.yaml` first, then you can use the UI.
|
||||
|
||||
@ -14,7 +14,7 @@ ha_integration_type: helper
|
||||
|
||||
The `input_number` integration allows the user to define values that can be controlled via the frontend and can be used within conditions of automation. The frontend can display a slider, or a numeric input box. Changes to the slider or numeric input box generate state events. These state events can be utilized as `automation` triggers as well.
|
||||
|
||||
The preferred way to configure an input number is via the user interface at **Configuration** -> **Helpers**. Click the add button and then choose the **Number** option.
|
||||
The preferred way to configure an input number is via the user interface at **Settings** -> **Devices & Services** -> **Helpers**. Click the add button and then choose the **Number** option.
|
||||
|
||||
To be able to add **Helpers** via the user interface you should have `default_config:` in your `configuration.yaml`, it should already be there by default unless you removed it.
|
||||
If you removed `default_config:` from you configuration, you must add `input_number:` to your `configuration.yaml` first, then you can use the UI.
|
||||
|
||||
@ -14,7 +14,7 @@ ha_integration_type: helper
|
||||
|
||||
The `input_select` integration allows the user to define a list of values that can be selected via the frontend and can be used within conditions of an automation. When a user selects a new item, a state transition event is generated. This state event can be used in an `automation` trigger.
|
||||
|
||||
The preferred way to configure an input select is via the user interface at **Configuration** -> **Helpers**. Click the add button and then choose the **Dropdown** option.
|
||||
The preferred way to configure an input select is via the user interface at **Settings** -> **Devices & Services** -> **Helpers**. Click the add button and then choose the **Dropdown** option.
|
||||
|
||||
To be able to add **Helpers** via the user interface you should have `default_config:` in your `configuration.yaml`, it should already be there by default unless you removed it.
|
||||
If you removed `default_config:` from you configuration, you must add `input_select:` to your `configuration.yaml` first, then you can use the UI.
|
||||
|
||||
@ -14,7 +14,7 @@ ha_integration_type: helper
|
||||
|
||||
The `input_text` integration allows the user to define values that can be controlled via the frontend and can be used within conditions of automation. Changes to the value stored in the text box generate state events. These state events can be utilized as `automation` triggers as well. It can also be configured in password mode (obscured text).
|
||||
|
||||
The preferred way to configure an input text is via the user interface at **Configuration** -> **Helpers**. Click the add button and then choose the **Text** option.
|
||||
The preferred way to configure an input text is via the user interface at **Settings** -> **Devices & Services** -> **Helpers**. Click the add button and then choose the **Text** option.
|
||||
|
||||
To be able to add **Helpers** via the user interface you should have `default_config:` in your `configuration.yaml`, it should already be there by default unless you removed it.
|
||||
If you removed `default_config:` from you configuration, you must add `input_text:` to your `configuration.yaml` first, then you can use the UI.
|
||||
|
||||
@ -23,6 +23,7 @@ ha_platforms:
|
||||
- light
|
||||
- switch
|
||||
ha_integration_type: integration
|
||||
ha_dhcp: true
|
||||
---
|
||||
|
||||
<p class='note warning'>The Insteon company has shut down and turned off their cloud as of April 2022.</p>
|
||||
|
||||
@ -88,4 +88,3 @@ In some cases, this will restore control to the fireplace, but if it doesn't you
|
||||
#### Power Cycle
|
||||
|
||||
The sure fire way to reset the IFT module is to just power-cycle it. This will work just about every time.
|
||||
|
||||
|
||||
@ -21,4 +21,4 @@ Router running NDMS firmware versions 2.05 and up. It uses telnet connection so
|
||||
|
||||
## Configuration
|
||||
|
||||
To add Keenetic router to your installation, go to **Configuration** >> **Devices & Services** in the UI, click the button with `+` sign and from the list of integrations select **Keenetic NDMS2 Router**.
|
||||
To add Keenetic router to your installation, go to **Settings** -> **Devices & Services** in the UI, click the button with `+` sign and from the list of integrations select **Keenetic NDMS2 Router**.
|
||||
|
||||
@ -23,7 +23,7 @@ ha_codeowners:
|
||||
- '@farmio'
|
||||
- '@marvin-w'
|
||||
ha_domain: knx
|
||||
ha_quality_scale: silver
|
||||
ha_quality_scale: platinum
|
||||
ha_platforms:
|
||||
- binary_sensor
|
||||
- button
|
||||
|
||||
@ -48,7 +48,7 @@ Konnected devices communicate with Home Assistant over your local LAN -- there i
|
||||
|
||||
### Web Interface
|
||||
|
||||
Starting with 0.106.0 Home Assistant requires UI based configuration of Konnected via **Configuration** -> **Devices & Services** in the Home Assistant (web) frontend. If you have Konnected Alarm Panels on your LAN, or in your configuration.yaml, you will see one or more **Konnected.io** entries appear in the **Discovered** integrations list.
|
||||
Starting with 0.106.0 Home Assistant requires UI based configuration of Konnected via **Settings** -> **Devices & Services** in the Home Assistant (web) frontend. If you have Konnected Alarm Panels on your LAN, or in your configuration.yaml, you will see one or more **Konnected.io** entries appear in the **Discovered** integrations list.
|
||||
|
||||
Selecting one of these discovered panels will guide you through connecting and configuring the panel. If your panel was discovered via SSDP, you shouldn't need any information to complete configuration - simply confirm that the information displayed is correct. If the UI prompts you for IP/Port, you'll need to enter it. IP/Port info can be found using the Konnected mobile app.
|
||||
|
||||
@ -56,15 +56,15 @@ Selecting one of these discovered panels will guide you through connecting and c
|
||||
|
||||
If you have an existing `configuration.yaml` completing the UI configuration will do a one time import of the settings contained in `configuration.yaml`. Once the import creates a **Configured** integration the Konnected section of the `configuration.yaml` is no longer used - it is recommended to remove the `konnected` section of `configuration.yaml` and after the import occurs. Any future changes to settings should occur via the settings provided in the Home Assistant web interface.
|
||||
|
||||
If you want to retain `configuration.yaml` and need to re-import any changes or updates you will need to delete the entry in **Configuration** -> **Devices & Services** -> **Configured** and repeat the UI configuration for that device.
|
||||
If you want to retain `configuration.yaml` and need to re-import any changes or updates you will need to delete the entry in **Settings** -> **Devices & Services** -> **Configured** and repeat the UI configuration for that device.
|
||||
|
||||
</div>
|
||||
|
||||
Once configuration is completed you'll see a Konnected.io entry in **Configuration** -> **Devices & Services** => **Configured**. If you imported settings from `configuration.yaml` you are now done! If you are setting up a new Konnected Alarm Panel or modifying settings, you'll need to utilize the settings UI to configure zone behavior.
|
||||
Once configuration is completed you'll see a Konnected.io entry in **Settings** -> **Devices & Services** -> **Configured**. If you imported settings from `configuration.yaml` you are now done! If you are setting up a new Konnected Alarm Panel or modifying settings, you'll need to utilize the settings UI to configure zone behavior.
|
||||
|
||||
#### Using Settings UI to Configure Zone Behavior
|
||||
|
||||
The settings for each panel can be accessed by selecting the entry in **Configuration** -> **Devices & Services** => **Configured** and then clicking on the gear icon in the upper right corner. You can reconfigure these settings at any time and once completed the settings will be immediately applied.
|
||||
The settings for each panel can be accessed by selecting the entry in **Settings** -> **Devices & Services** -> **Configured** and then clicking on the gear icon in the upper right corner. You can reconfigure these settings at any time and once completed the settings will be immediately applied.
|
||||
|
||||
The settings UI starts by having you configure the general behavior of each zone. You need to specify `Disabled`, `Binary Sensor`, `Digital Sensor`, or `Switchable Output` for each zone. After that, you'll be prompted, for each zone that is not disabled, to configure details of the zones' behavior. All zones will allow entry of a Name. Additional fields depend on how you configured the general behavior of the zone.
|
||||
**Note some zones do not support all behaviors. The UI will reflect specific options available to each zone.**
|
||||
@ -310,7 +310,7 @@ konnected:
|
||||
|
||||
## Unique IDs and the Entity Registry
|
||||
|
||||
Beginning in Home Assistant release 0.90, unique IDs are generated for each sensor or switch entity. This enables end users to modify the entity names and entity IDs through the Home Assistant UI at **Configuration** -> **Entities**.
|
||||
Beginning in Home Assistant release 0.90, unique IDs are generated for each sensor or switch entity. This enables end users to modify the entity names and entity IDs through the Home Assistant UI at **Settings** -> **Devices & Services** -> **Entities**.
|
||||
|
||||
Unique IDs are internally generated as follows:
|
||||
|
||||
|
||||
@ -11,6 +11,8 @@ ha_homekit: true
|
||||
ha_platforms:
|
||||
- light
|
||||
ha_integration_type: integration
|
||||
ha_codeowners:
|
||||
- '@Djelibeybi'
|
||||
---
|
||||
|
||||
The `lifx` integration allows you to integrate your [LIFX](https://www.lifx.com) bulbs into Home Assistant.
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Meater Smart Meat Thermometer
|
||||
title: Meater
|
||||
description: Instructions on how to integrate the Meater Temperature Probe within Home Assistant.
|
||||
ha_category:
|
||||
- Sensor
|
||||
@ -8,7 +8,11 @@ ha_iot_class: Cloud Polling
|
||||
ha_config_flow: true
|
||||
ha_codeowners:
|
||||
- '@Sotolotl'
|
||||
- '@emontnemery'
|
||||
ha_domain: meater
|
||||
ha_platforms:
|
||||
- sensor
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
The Meater Smart Meat Thermometer integration allows for communicating with the [Meater Temperature Probe](https://meater.com/) from Apption Labs.
|
||||
@ -25,4 +29,4 @@ Devices will only be returned from the Meater Cloud API after the following crit
|
||||
|
||||
- Device must be seen by the Meater Cloud. Ensure you've completed a cook while connected to Meater Cloud.
|
||||
- The Meater app or Block must have an active Bluetooth connection with the device.
|
||||
- The Meater app or Block must have an active Meater Cloud connection.
|
||||
- The Meater app or Block must have an active Meater Cloud connection.
|
||||
|
||||
@ -34,7 +34,7 @@ It displays the current weather along with a 5 days forecast and create sensors,
|
||||
|
||||
To be used with the weather dashboard card to access current condition, today and next four days forecast.
|
||||
|
||||
The weather platform can be configured in the frontend to decide if the forecast is given daily (default) or hourly. To change the setting go in **Configuration** -> **Devices & Services**, click on the city name in **Météo-France** box and click on **Options**. You can update the `Forecast mode` by choosing between `daily` or `hourly`.
|
||||
The weather platform can be configured in the frontend to decide if the forecast is given daily (default) or hourly. To change the setting go in **Settings** -> **Devices & Services**, click on the city name in **Météo-France** box and click on **Options**. You can update the `Forecast mode` by choosing between `daily` or `hourly`.
|
||||
|
||||
## Sensor platforms
|
||||
|
||||
@ -59,7 +59,7 @@ All the following sensors will be created :
|
||||
|
||||
Warning: The probability entities data are not always provided by the API. They are added only if available.
|
||||
|
||||
To enable an entity disabled by default, go in **Configuration** -> **Devices & Services**, click on the city name in **Météo-France** and then the **X entities** link. You will have the list of the enabled entities. Here click the filter button and select **Show disable entities**. The disabled entities will be visible in the list, select the one you want to enable and click the **Enable Selected** button.
|
||||
To enable an entity disabled by default, go in **Settings** -> **Devices & Services**, click on the city name in **Météo-France** and then the **X entities** link. You will have the list of the enabled entities. Here click the filter button and select **Show disable entities**. The disabled entities will be visible in the list, select the one you want to enable and click the **Enable Selected** button.
|
||||
|
||||
### About `next_rain` condition sensor
|
||||
|
||||
|
||||
@ -25,6 +25,7 @@ Additionally the following brands have been reported to also work with this inte
|
||||
- [Bloc Blinds](https://www.blocblinds.com/)
|
||||
- [Brel Home](https://www.brel-home.nl/)
|
||||
- [3 Day Blinds](https://www.3dayblinds.com/)
|
||||
- [Diaz](https://www.diaz.be/en/)
|
||||
- [Dooya](http://www.dooya.com/)
|
||||
- [Gaviota](https://www.gaviotagroup.com/en/)
|
||||
- [Havana Shade](https://havanashade.com/)
|
||||
|
||||
@ -5,8 +5,6 @@ ha_category:
|
||||
- Media Player
|
||||
ha_release: pre 0.7
|
||||
ha_iot_class: Local Polling
|
||||
ha_codeowners:
|
||||
- '@fabaff'
|
||||
ha_domain: mpd
|
||||
ha_platforms:
|
||||
- media_player
|
||||
|
||||
@ -26,7 +26,6 @@ There is currently support for the following device types within Home Assistant:
|
||||
- [Setup of myStrom Buttons](#setup-of-mystrom-buttons)
|
||||
- [Switch](#switch)
|
||||
- [Setup](#setup)
|
||||
- [Get the current power consumption](#get-the-current-power-consumption)
|
||||
|
||||
## Light
|
||||
|
||||
@ -158,7 +157,7 @@ If you have set [`login_attempts_threshold`](/integrations/http/) and forget to
|
||||
|
||||
## Switch
|
||||
|
||||
The `mystrom` switch platform allows you to control the state of your [myStrom](https://mystrom.ch/en/) switches. The built-in sensor is measuring the power consumption while the switch is on.
|
||||
The `mystrom` switch platform allows you to control the state of your [myStrom](https://mystrom.ch/en/) switches.
|
||||
|
||||
### Setup
|
||||
|
||||
@ -188,23 +187,3 @@ name:
|
||||
type: string
|
||||
default: myStrom Switch
|
||||
{% endconfiguration %}
|
||||
|
||||
|
||||
### Get the current power consumption
|
||||
|
||||
The switch is measuring the current power consumption. To expose this as a sensor use a [`template` sensor](/integrations/template).
|
||||
|
||||
{% raw %}
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
sensor:
|
||||
- platform: template
|
||||
sensors:
|
||||
power:
|
||||
friendly_name: "Current Power"
|
||||
unit_of_measurement: "W"
|
||||
value_template: "{{ state_attr('switch.office', 'current_power_w') }}"
|
||||
```
|
||||
|
||||
{% endraw %}
|
||||
|
||||
@ -465,7 +465,7 @@ This feature is enabled by the following permissions:
|
||||
|
||||
- For general trouble with the SDM API OAuth authorization flow with Google, see [Troubleshooting](https://developers.google.com/nest/device-access/authorize#troubleshooting).
|
||||
|
||||
- Check **Configuration** then **Logs** to see if there are any error messages or misconfigurations then see the error messages below.
|
||||
- Check **Settings** -> **System** -> **Logs** to see if there are any error messages or misconfigurations then see the error messages below.
|
||||
|
||||
- *Reauthentication required often*: If you are getting logged out every 7 days, this means an OAuth Consent Screen misconfiugration or your authentication token was revoked by Google for some other reason.
|
||||
|
||||
|
||||
@ -244,7 +244,7 @@ client_secret:
|
||||
|
||||
**After the `client_id` and `client_secret` are added to your `configuration.yaml` you must restart Home Assistant and then enable Netatmo through the integrations page.**
|
||||
|
||||
Menu: **Configuration** -> **Devices & Services**.
|
||||
Menu: **Settings** -> **Devices & Services**.
|
||||
|
||||
Click on the `+` sign to add an integration and click on **Netatmo**.
|
||||
After completing the configuration flow, the Netatmo integration will be available.
|
||||
|
||||
@ -139,7 +139,7 @@ data:
|
||||
duration: 4
|
||||
position: "bottom-left"
|
||||
fontsize: "medium"
|
||||
transparency: "80%"
|
||||
transparency: "75%"
|
||||
color: "teal"
|
||||
interrupt: 0
|
||||
```
|
||||
|
||||
@ -5,8 +5,6 @@ ha_category:
|
||||
- Network
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_release: 0.57
|
||||
ha_codeowners:
|
||||
- '@fabaff'
|
||||
ha_domain: no_ip
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
@ -13,6 +13,7 @@ ha_platforms:
|
||||
- binary_sensor
|
||||
- button
|
||||
- camera
|
||||
- diagnostics
|
||||
- sensor
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
@ -10,7 +10,6 @@ ha_iot_class: Local Polling
|
||||
ha_config_flow: true
|
||||
ha_release: 0.28
|
||||
ha_codeowners:
|
||||
- '@fabaff'
|
||||
- '@johnluetke'
|
||||
- '@shenxn'
|
||||
ha_domain: pi_hole
|
||||
|
||||
@ -376,5 +376,5 @@ Refresh a Plex library to scan for new and updated media.
|
||||
|
||||
## Notes
|
||||
|
||||
- The Plex integration supports multiple Plex servers. Additional connections can be configured under **Configuration** > **Devices & Services**.
|
||||
- The Plex integration supports multiple Plex servers. Additional connections can be configured under **Settings** -> **Devices & Services**.
|
||||
- Movies must be located under the 'Movies' section in a Plex library to properly view the 'playing' state.
|
||||
|
||||
@ -6,7 +6,6 @@ ha_category:
|
||||
ha_release: 0.33
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_codeowners:
|
||||
- '@fabaff'
|
||||
- '@frenck'
|
||||
ha_config_flow: true
|
||||
ha_domain: pvoutput
|
||||
|
||||
@ -88,7 +88,7 @@ connection: &rfxtrx
|
||||
|
||||
## Settings options
|
||||
|
||||
To configure options for RFXtrx integration go to **Configuration** >> **Devices & Services** and press **Options** on the RFXtrx card.
|
||||
To configure options for RFXtrx integration go to **Settings** -> **Devices & Services** and press **Options** on the RFXtrx card.
|
||||
|
||||
<img src='/images/integrations/rfxtrx/options.png' />
|
||||
|
||||
|
||||
@ -20,7 +20,7 @@ This integration uses Roon Core, a Roon application that runs on a machine on yo
|
||||
|
||||
## Configuration
|
||||
|
||||
1. From the Home Assistant front-end, navigate to **Configuration** then **Integrations**. Under **Set up a new integration** locate 'Roon' and click **Configure**.
|
||||
1. From the Home Assistant front-end, navigate to **Settings** -> **Devices & Services**. Under **Set up a new integration** locate 'Roon' and click **Configure**.
|
||||
2. Home Assistant will then try to find your Roon Core - if it is successful it will display `Authorize HomeAssistant in Roon`. Click **Submit** and skip to step 4
|
||||
3. If your Roon Core is not automatically found you can enter the `Hostname` or `IP address` for the Roon Core machine when requested and click **Submit**.
|
||||
4. Home Assistant will then contact your Roon Core and ask to be authorized. You will need to enable this extension in the Room Application. Go to **Settings** and then **Extensions**, there you will see an entry for Home Assistant with a button next to it. Click **Enable**.
|
||||
|
||||
@ -22,7 +22,7 @@ There is currently support for the following device types within Home Assistant:
|
||||
|
||||
## Configuration
|
||||
|
||||
To add a Ruckus Unleashed device to your installation, go to **Configuration** -> **Devices & Services**, click the `+` button, then select **Ruckus** from the list of integrations.
|
||||
To add a Ruckus Unleashed device to your installation, go to **Settings** -> **Devices & Services**, click the `+` button, then select **Ruckus** from the list of integrations.
|
||||
|
||||
It is required to configure the IP address of your **master access point**. See the section Access Points on the management web interface. And perhaps consider to set a preferred master (Admin & Services>System>System Info>Preferred master).
|
||||
|
||||
|
||||
@ -13,6 +13,9 @@ ha_domain: sabnzbd
|
||||
ha_platforms:
|
||||
- sensor
|
||||
ha_integration_type: integration
|
||||
ha_codeowners:
|
||||
- '@shaiu'
|
||||
ha_config_flow: true
|
||||
---
|
||||
|
||||
The `sabnzbd` integration will allow you to monitor and control your downloads with [SABnzbd](https://sabnzbd.org) from within Home Assistant and setup automations based on the information.
|
||||
|
||||
@ -32,7 +32,7 @@ The Pentair ScreenLogic integration allows you to integrate your Pentair Intelli
|
||||
|
||||
## Options
|
||||
|
||||
ScreenLogic options are set via **Configuration** -> **Devices & Services** -> **Pentair ScreenLogic** -> **Options**.
|
||||
ScreenLogic options are set via **Settings** -> **Devices & Services** -> **Pentair ScreenLogic** -> **Options**.
|
||||
|
||||
* Seconds between scans - How many seconds between each polling of the ScreenLogic gateway.
|
||||
|
||||
|
||||
@ -8,6 +8,7 @@ ha_category:
|
||||
- Number
|
||||
- Select
|
||||
- Sensor
|
||||
- Updates
|
||||
ha_release: 0.44
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_config_flow: true
|
||||
@ -22,6 +23,7 @@ ha_platforms:
|
||||
- number
|
||||
- select
|
||||
- sensor
|
||||
- update
|
||||
ha_homekit: true
|
||||
ha_dhcp: true
|
||||
ha_integration_type: integration
|
||||
|
||||
@ -22,17 +22,18 @@ The type of data a sensor returns impacts how it is displayed in the frontend. T
|
||||
- **None**: Generic sensor. This is the default and doesn't need to be set.
|
||||
- **apparent_power**: Apparent power in VA.
|
||||
- **aqi**: Air Quality Index
|
||||
- **battery**: Percentage of battery that is left.
|
||||
- **battery**: Percentage of battery that is left
|
||||
- **carbon_dioxide**: Carbon Dioxide in CO2 (Smoke)
|
||||
- **carbon_monoxide**: Carbon Monoxide in CO (Gas CNG/LPG)
|
||||
- **current**: Current in A.
|
||||
- **date**: Date string (ISO 8601).
|
||||
- **energy**: Energy in Wh, kWh or MWh.
|
||||
- **frequency**: Frequency in Hz, kHz, MHz or GHz.
|
||||
- **gas**: Gasvolume in m³ or ft³.
|
||||
- **humidity**: Percentage of humidity in the air.
|
||||
- **illuminance**: The current light level in lx or lm.
|
||||
- **monetary**: The monetary value.
|
||||
- **current**: Current in A
|
||||
- **date**: Date string (ISO 8601)
|
||||
- **duration**: Duration in days, hours, minutes or seconds
|
||||
- **energy**: Energy in Wh, kWh or MWh
|
||||
- **frequency**: Frequency in Hz, kHz, MHz or GHz
|
||||
- **gas**: Gasvolume in m³ or ft³
|
||||
- **humidity**: Percentage of humidity in the air
|
||||
- **illuminance**: The current light level in lx or lm
|
||||
- **monetary**: The monetary value
|
||||
- **nitrogen_dioxide**: Concentration of Nitrogen Dioxide in µg/m³
|
||||
- **nitrogen_monoxide**: Concentration of Nitrogen Monoxide in µg/m³
|
||||
- **nitrous_oxide**: Concentration of Nitrous Oxide in µg/m³
|
||||
@ -40,16 +41,16 @@ The type of data a sensor returns impacts how it is displayed in the frontend. T
|
||||
- **pm1**: Concentration of particulate matter less than 1 micrometer in µg/m³
|
||||
- **pm10**: Concentration of particulate matter less than 10 micrometers in µg/m³
|
||||
- **pm25**: Concentration of particulate matter less than 2.5 micrometers in µg/m³
|
||||
- **power_factor**: Power factor in %.
|
||||
- **power**: Power in W or kW.
|
||||
- **pressure**: Pressure in hPa or mbar.
|
||||
- **reactive_power**: Reactive power in var.
|
||||
- **signal_strength**: Signal strength in dB or dBm.
|
||||
- **power_factor**: Power factor in %
|
||||
- **power**: Power in W or kW
|
||||
- **pressure**: Pressure in hPa or mbar
|
||||
- **reactive_power**: Reactive power in var
|
||||
- **signal_strength**: Signal strength in dB or dBm
|
||||
- **sulphur_dioxide**: Concentration of sulphur dioxide in µg/m³
|
||||
- **temperature**: Temperature in °C or °F.
|
||||
- **timestamp**: Datetime object or timestamp string (ISO 8601).
|
||||
- **volatile_organic_compounds**: Concentration of volatile organic compounds in µg/m³.
|
||||
- **voltage**: Voltage in V.
|
||||
- **temperature**: Temperature in °C or °F
|
||||
- **timestamp**: Datetime object or timestamp string (ISO 8601)
|
||||
- **volatile_organic_compounds**: Concentration of volatile organic compounds in µg/m³
|
||||
- **voltage**: Voltage in V
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/screenshots/sensor_device_classes_icons.png' />
|
||||
|
||||
@ -46,6 +46,6 @@ The Sentry integration provides settings to:
|
||||
- Ability to send out events originating from third-party Python packages.
|
||||
- Enable performance tracing and tune the tracing sample rate used.
|
||||
|
||||
To change the settings go in **Configuration** -> **Devices & Services**, find the already installed **Sentry** box and click on **Options**.
|
||||
To change the settings go in **Settings** -> **Devices & Services**, find the already installed **Sentry** box and click on **Options**.
|
||||
|
||||
After changing Sentry settings, you'll need to restart Home Assistant in order to make them effective.
|
||||
|
||||
@ -11,6 +11,7 @@ ha_codeowners:
|
||||
ha_domain: senz
|
||||
ha_platforms:
|
||||
- climate
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
The SENZ integration allows you to control and monitor your nVent RAYCHEM SENZ-WIFI thermostats.
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: SlimProto (Squeezebox Players)
|
||||
title: SlimProto (Squeezebox players)
|
||||
description: Instructions on how to integrate a SlimProto-based player (e.g., Squeezebox) into Home Assistant without the need for a media server.
|
||||
ha_category:
|
||||
- Media Player
|
||||
@ -7,10 +7,11 @@ ha_release: 2022.5
|
||||
ha_iot_class: Local Push
|
||||
ha_domain: slimproto
|
||||
ha_codeowners:
|
||||
- "@marcelveldt"
|
||||
- '@marcelveldt'
|
||||
ha_config_flow: true
|
||||
ha_platforms:
|
||||
- media_player
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
The SlimProto integration allows you to control a [Squeezebox](https://en.wikipedia.org/wiki/Squeezebox_%28network_music_player%29) music player directly from Home Assistant, without the need for an external Media Server such as Logitech Media Server. This lets you control Squeezebox hardware like the Classic, Transporter, Duet, Boom, Radio, and Touch and software players like [Squeezelite](https://github.com/ralph-irving/squeezelite), [PiCorePlayer](https://www.picoreplayer.org/) or [Max2Play](https://www.max2play.com/en/). For the real DIY enthusiast, [there even is a player for the ESP32](https://github.com/sle118/squeezelite-esp32).
|
||||
|
||||
@ -5,8 +5,6 @@ ha_category:
|
||||
- Notifications
|
||||
ha_iot_class: Cloud Push
|
||||
ha_release: pre 0.7
|
||||
ha_codeowners:
|
||||
- '@fabaff'
|
||||
ha_domain: smtp
|
||||
ha_platforms:
|
||||
- notify
|
||||
|
||||
@ -18,4 +18,4 @@ The `Somfy MyLink` integration is used as an interface to a compatible Somfy MyL
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
If any of your devices are reversed, they can be adjusted in **Configuration** >> **Devices & Services** >> **Somfy MyLink** >> `Options`.
|
||||
If any of your devices are reversed, they can be adjusted in **Settings** -> **Devices & Services** -> **Somfy MyLink** >> `Options`.
|
||||
|
||||
@ -225,7 +225,7 @@ condition:
|
||||
# Coordinator
|
||||
- condition: template
|
||||
value_template: >
|
||||
{{ state_attr( trigger.entity_id , 'sonos_group')[0] == trigger.entity_id }}
|
||||
{{ state_attr( trigger.entity_id , 'group_members')[0] == trigger.entity_id }}
|
||||
# Going from queue to queue
|
||||
- condition: template
|
||||
value_template: >
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Logitech Squeezebox
|
||||
title: Squeezebox (Logitech Media Server)
|
||||
description: Instructions on how to integrate a Logitech Squeezebox player into Home Assistant.
|
||||
ha_category:
|
||||
- Media Player
|
||||
|
||||
@ -12,6 +12,9 @@ ha_platforms:
|
||||
ha_codeowners:
|
||||
- '@tkdrob'
|
||||
ha_integration_type: integration
|
||||
ha_codeowners:
|
||||
- '@tkdrob'
|
||||
ha_config_flow: true
|
||||
---
|
||||
|
||||
The Steam integration will allow you to track the online status of public [Steam](https://steamcommunity.com) accounts.
|
||||
|
||||
@ -70,7 +70,7 @@ The current lock status is always unknown due to the fact that the Subaru API do
|
||||
|
||||
Subaru integration options are set via:
|
||||
|
||||
**Configuration** -> **Devices & Services** -> **Subaru** -> **Options**.
|
||||
**Settings** -> **Devices & Services** -> **Subaru** -> **Options**.
|
||||
|
||||
- **Enable vehicle polling *[Default: off]*:** When enabled, vehicle polling will send a remote command to your vehicle every 2 hours to obtain new sensor data. This involves "waking" your vehicle and requesting that it send new data to Subaru servers. Without vehicle polling, new sensor data is only received when the vehicle automatically pushes data (normally after engine shutdown). This option only applies to Gen 2 vehicles with Security Plus subscriptions because it uses a "locate" command to request the data.
|
||||
|
||||
|
||||
@ -5,8 +5,6 @@ ha_category:
|
||||
- Notifications
|
||||
ha_release: pre 0.7
|
||||
ha_iot_class: Local Push
|
||||
ha_codeowners:
|
||||
- '@fabaff'
|
||||
ha_domain: syslog
|
||||
ha_platforms:
|
||||
- notify
|
||||
|
||||
@ -18,6 +18,6 @@ This integration is by default enabled, unless you've disabled or removed the [`
|
||||
system_health:
|
||||
```
|
||||
|
||||
System Health integration data can be viewed at **Configuration** -> **Info**.
|
||||
System Health integration data can be viewed at **Settings** -> **System** -> **System Health**.
|
||||
|
||||
Data includes information about your system architecture, operating system and version, Home Assistant installation type and version, Python version, frontend version, the number of [Dashboards](/dashboards/dashboards/) and [Views](/dashboards/views/) you have, and more.
|
||||
|
||||
@ -9,7 +9,7 @@ ha_domain: system_log
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
The `system_log` integration stores information about all logged errors and warnings in Home Assistant. To view your logs, navigate to **Configuration** -> **Settings** -> **Logs**. In order to not overload Home Assistant with log data, only the 50 last errors and warnings will be stored. Older entries are automatically discarded from the log. It is possible to change the number of stored log entries using the parameter `max_entries`.
|
||||
The `system_log` integration stores information about all logged errors and warnings in Home Assistant. To view your logs, navigate to **Settings** -> **System** -> **Logs**. In order to not overload Home Assistant with log data, only the 50 last errors and warnings will be stored. Older entries are automatically discarded from the log. It is possible to change the number of stored log entries using the parameter `max_entries`.
|
||||
|
||||
## Configuration
|
||||
|
||||
|
||||
@ -49,10 +49,4 @@ scan_interval:
|
||||
default: 60
|
||||
{% endconfiguration %}
|
||||
|
||||
<div class='note'>
|
||||
|
||||
It is only possible to configure the `scan_interval` when setting up the device. If the polling interval needs to be changed after the device is configured it must be changed manually by changing `"scan_interval": 60,` for the device in the file `.storage/core.config_entries`.
|
||||
|
||||
</div>
|
||||
|
||||
The integration will offer configuration through the Home Assistant user interface where it will let you associate it with your Telldus Live account.
|
||||
|
||||
@ -175,4 +175,4 @@ switch:
|
||||
- platform: tellstick
|
||||
```
|
||||
|
||||
[tellstick-gateway]: https://telldus.com/produkt/z-wave-gateway-tellstick-znet-lite-ver-2/
|
||||
[tellstick-gateway]: https://telldus.com
|
||||
|
||||
@ -12,6 +12,7 @@ ha_config_flow: true
|
||||
ha_codeowners:
|
||||
- '@rytilahti'
|
||||
- '@thegardenmonkey'
|
||||
- '@bdraco'
|
||||
ha_domain: tplink
|
||||
ha_platforms:
|
||||
- diagnostics
|
||||
|
||||
@ -14,6 +14,7 @@ ha_domain: tractive
|
||||
ha_platforms:
|
||||
- binary_sensor
|
||||
- device_tracker
|
||||
- diagnostics
|
||||
- sensor
|
||||
- switch
|
||||
ha_integration_type: integration
|
||||
|
||||
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