From c8fcddb92b2b6c679197fda86c4109c12288733f Mon Sep 17 00:00:00 2001 From: schlac Date: Fri, 1 Oct 2021 12:03:16 +0200 Subject: [PATCH 01/29] Fix dead link to pysma library (#19544) --- source/_integrations/sma.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/sma.markdown b/source/_integrations/sma.markdown index 2051184b10a..9444ff6bb4f 100644 --- a/source/_integrations/sma.markdown +++ b/source/_integrations/sma.markdown @@ -22,7 +22,7 @@ The integration uses the web interface of the device. Before you start, make sur ## Sensors -The SMA WebConnect module supports a wide variety of sensors, but not all of these have been mapped in the `pysma` library. Currently available sensors can be found below. Feel free to submit additional sensors to be added as standard sensors to the [pysma library](https://github.com/rklomp/pysma/blob/dev/pysma/definitions.py). +The SMA WebConnect module supports a wide variety of sensors, but not all of these have been mapped in the `pysma` library. Currently available sensors can be found below. Feel free to submit additional sensors to be added as standard sensors to the [pysma library](https://github.com/rklomp/pysma/blob/master/pysma/definitions.py). ### Solar Inverter From 68727665fc161703d2d9a1aa1fdd8c81570c626b Mon Sep 17 00:00:00 2001 From: Mike Eriksson Date: Fri, 1 Oct 2021 11:49:09 +0100 Subject: [PATCH 02/29] Update index.html (#19545) --- source/blue/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/blue/index.html b/source/blue/index.html index 0419884d72e..8a741f05aee 100644 --- a/source/blue/index.html +++ b/source/blue/index.html @@ -358,7 +358,7 @@ frontpage_image: /images/frontpage/blue-frontpage.jpg
No Wi-Fi or Bluetooth
- Support for Z-Wave and Zigbee by external USB adaptor + Support for Z-Wave and Zigbee by external USB adapter (not included)
From ecb1d54f11a8acfa3512fc451e486d5b7b023b33 Mon Sep 17 00:00:00 2001 From: Milan Meulemans Date: Fri, 1 Oct 2021 15:19:32 +0200 Subject: [PATCH 03/29] Remove Linux Battery logo (#19551) --- source/_integrations/linux_battery.markdown | 1 - source/images/supported_brands/linux_battery.png | Bin 3868 -> 0 bytes 2 files changed, 1 deletion(-) delete mode 100644 source/images/supported_brands/linux_battery.png diff --git a/source/_integrations/linux_battery.markdown b/source/_integrations/linux_battery.markdown index 2cfaa13d0cf..9f549ce4c90 100644 --- a/source/_integrations/linux_battery.markdown +++ b/source/_integrations/linux_battery.markdown @@ -1,7 +1,6 @@ --- title: Linux Battery description: Instructions on how to integrate Linux Battery information into Home Assistant. -logo: linux_battery.png ha_category: - System Monitor ha_release: 0.28 diff --git a/source/images/supported_brands/linux_battery.png b/source/images/supported_brands/linux_battery.png deleted file mode 100644 index 935227eeef5ed8e411d9e5bc817a4a2904c1de54..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 3868 zcmV+%599EOP)f5{!XN`RH8em!J~}!%y}i(xnXr(M zsBLX+larG~L`3O}DdmABnVFfbt-{2_*8j}_Vq#*?MG$CcXj@xcwzkR3%iMy3oJmPZ zqocXrZXeT76tlClQBhHrmX_gnBDuM_t*orpSr_Qfp8mo-r>CdBzP^o&jNYnf+h!cu zUmD}Thv2ev<;RnGd3nOY!J?v~o}QlJxP9KEUH-;2ARr)`Oa`)D5wVU($a5g;z6a-& zIM%KVl`S6nmoCXoAC7n+b90QuKp|{cCi%ch!JihZj~aSoNn=$;lX+Q}Trs(xh0?gC z@}NygA{_L&Lx1)essI203UpFVQvmk=|9)Ad>?_EpBtO^y01dE7L_t(|+U%JNU)tId z#p@HKVbpq_kpII-QmzSw=K~1LsDUktj<_wvbBYaw$>;tZWwG5`clb8Yp&UZSP4=XH&Ui zF^9!5@dHXp%TMe1$Z|j$qbsX`l$1gdD@Uj)z!og21PX#Bz>-|e1_WMYAr@Pg({_U7Ov6S{wn(|ayKq%pEoUeC#Cik`3K#{#}e|W~k zqyVZYIk!@?y;(tNHl>(K@k5d}F1x)R`nxiA9KlE+j#4?B3D81TNx6ema4F5EvNC~E zEP&7ZM6NG3x{Aog@QSsMVzW{z2hW=0l!_~fQejysvP|1cwMq=@qjouh$TE*K7XUzu zxfDDpE+ir~<*mVAOqoFY|PcR^TLh;^GUBZlOa+U+I%B$+X< zq~>$V&SFsVW1f0GxZ|myvztL?G3VxrP@alNf2bs4Wi%G4w8K$kK8&m(L?p*_w%1nb zN#&G^{gvd)JD^fuS7W{A!wqE?T^%kIe3Y70C)0vj`+-T7q&`wfhF4;-#>0y+`jnaT z@igntbhVdPD#?R8$S~Tv2D9=|p({>sl}Y85795`Xw>O>U_Y(Q5mQ+Y?jmm zf~T)_mp~PvyF!BRKq_Qu8HK)3Bqx=*T1bucRPy&!RBDE9fKpenyAKrV#pIPz=&PP8 ze)*N80ZLu_5Q+6|sNG*)tH08TJWbo4$^;q#XoG_mb49mQJUH-5k*WA7eR@hOOsYqK z2{dLx$!cIo*H+5H8EIlqB_-`G6_rAeIOq-E-=b5hA{87^-`yamZKZChFfw=d7WC!H z)nEQvqrd^*XCsN17&&dWUc{#DozFubs^gTxg%o}>Tk!By;*ro>C9QB$9YfQ-v!Q<@ zwN`W|nBTw(&bdMlMDG3qQI?2I5y|fdZ0_AB2L1D3Whp1jDt|sJkn;ijE_*_Te3Hps zt98>VNae7XM5hHMQdxpM15D3h9MlQYVR0T$1N z_W2Kh-2FtB6Uu3|sePNtL;wEu0@SUC+mYiEXCDg-c83d2ofPe<)f`X86rr^nf^FT7 z>}ANEAUGyFU~^bS@l)zRI-sYgwHNI1*4E4DO1RcI8|<)DF^}M!QcfyqY@K5Yo&xmr zv;txg+bWMdg2dY@x+=uiUJx6AtcysOQYh$gYm3xv)zs@4)s$a+vkvSJAl6Nh_2*CH zpfxCp&16vT*_Cx)=;5mM)(XATu$bF$qgJoiiOl-Pj{w~rrxdDkQ>It~9*)jZ9%JKj zm2$7QhXiOM>wqNCPyU|PfLf_lDwXPO%cN$$W-_hY+u`WT@mWE@@~)EZe)};THX3zW z2qeTYP+n=JasySqZM6vZt678%RVsZUm4!d0Qt8_@ezVbNG@Es?K3es(nu z>Vy=}d<)dwT}!EjB+x^o9$pC4&jh=>JC#ybe_LBEH}%j(r9wYXr!{X+9ZJRSez%pH^*p`Os=uc~lC1bn?WrTZ zWv0}GI+@>@($7MFXPDEnIH%6`x|Ieor&V!Ix&2S1x+Z42IrZu<^VGW3Sxhs&_I8-g zQ?9#yo{mw<_cws_3PH*Q?dj>Ob80Un$DB^@Y0ckL8lzsO}*VEHOho|$I z)33pKdOBuKg*A96TxC2weGbM`VGRcEY3)5ct-RuCCJaw&6YO43r6J6zwH)R!r|va4 zk*CiA&1r_;gY%kG7T$^G^fAym%>+NEr>^w6Jhhe1Z%%{v)I+IrPRA$>WB2+fozBz# zuQ$!3!0K4u3h%y_JbPooY^h$4%&Vd48VWFEQx$ACI?mX7ki1 zz4yO=GU#8!KjNh=EKh-HLpO%@MygeUm{V`)@1IK?bYoZ!-_!fwOG_LSsM{m{y}>Z% z^nU553wm}H?(RjI9?+|iBfVAruI+7e>P#<0$Qycgb~dux8>FY;CS|&no*f?_k80!Z zWnN9M8`@1+NFV5zFC#*&-UQ@nx3`#FT6zsyDwRePdFq{B0Xpa&EiO(11?soba5%fC z0}y$zI2jb*BZs;k4!w?`lX?1FAM_}3a;3n${_$gbdpI1H-{dJEpYQICB z!{}`S5Gp)O@p_IhaE!6pE)C^I0XNG05Sejh6qiya-|JOB}y znpd&esc&C~1odpa(?`|q)P^Z9q#z58?9y|&VBU+;7pdbbywo6<&G-7!mT>%GM} z?B2bG1~9GN>2%r}z%~6SRHex5YsfLor%f6h22)m|9s#qL@ZP1iKd zuwH{6*LJ$VoK>j@R8Lx4K?kLPVzI)Pqle*X8=&m!(kAA@gt7sGgmq?6>U%xK98suB z8>=S`J4v08m39oXuWc6RS(T23(ry~MN~e`h&8(h|NpFV*he6wIDj9#G&#JWKJ*P=x zrK-UxMJ1oW;lX?riP`4Vee83{fkQwuMpa}bVFyrAlFgG9(o zFVULKXrG}8XCw`oa5CH6JeXan=Ml7lt1r<}Eu;$PQDExkVQ^+o zy${AidCQn7c6 z$X+j}d&eidG{khV=fK(Xt83e~g9268#O{U@ejOEb=Y%l7DRz3Zp`|l=c_rVHy>%?H zK|9JTtmsmAr9a`XX0I~p2&=4I70r^tDKqyRa87g0`0@jqmH6pZn%wAgHKwP5KeeMY zDN)%wxoRuuo71)IjTMrqSIyGZZE);#A*NQRHTZ<(GK@W??21k#rl!~6)E3h^$|suO zl|VLKHY}N~*;{*&J7K5kY@*5SV$a^p*rr1`1-l=e~WBYDz>N3iD+tDrx>RaU}@oIDp|qhH1~Ur>(svY z7Lr{VB4C-Id%j`zUe}Vn@VS)4&_Oj8lqXf0%D?y7-aD+*S(AC@R4WE(5NfE1tDJ#w zX!RDt|GaS=_|mi@?w??k8hV1i!qH)%AxT18_KLi%o3%{Ib&=b(%B2BazNH7 zJz?<=KwZgw*2+qqzHX;=Sj8B=AUV4JKM;#UUm~YR+J->_Dd+z$m^qZ%ns*%#_yvUY e)N84Rm-_*AJ>b=zSAJmt0000 Date: Fri, 1 Oct 2021 15:15:48 +0100 Subject: [PATCH 04/29] Changed remaining adoptor's to adapter (#19546) --- source/_integrations/aurora_abb_powerone.markdown | 8 ++++---- source/_integrations/homeworks.markdown | 2 +- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/source/_integrations/aurora_abb_powerone.markdown b/source/_integrations/aurora_abb_powerone.markdown index 0752dce0833..e0ab3265ead 100644 --- a/source/_integrations/aurora_abb_powerone.markdown +++ b/source/_integrations/aurora_abb_powerone.markdown @@ -13,17 +13,17 @@ ha_platforms: - sensor --- -This implements a direct RS485 connection to a solar inverter in the +This implements a direct RS485 connection to a solar inverter in the PVI-3.0/3.6/4.2-TL-OUTD ABB series, and may work on others. The inverter was formerly made by PowerOne who got taken over by ABB. -The TCP/IP method of communicating with inverters is supported by the +The TCP/IP method of communicating with inverters is supported by the Python library, but not by this implementation in this integration. This integration provides a single sensor which reports the live power output in watts. -Note the PV inverter will be unresponsive to communications when in darkness, +Note the PV inverter will be unresponsive to communications when in darkness, so the value 'unknown' will be displayed during the night. ## Configuration @@ -39,7 +39,7 @@ sensor: {% configuration %} device: - description: The serial port your RS485 adaptor is connected to. + description: The serial port your RS485 adapter is connected to. required: true type: string address: diff --git a/source/_integrations/homeworks.markdown b/source/_integrations/homeworks.markdown index 40112375148..4698ad22a14 100644 --- a/source/_integrations/homeworks.markdown +++ b/source/_integrations/homeworks.markdown @@ -42,7 +42,7 @@ homeworks: {% configuration %} host: - description: The IP address of the ethernet to serial adapter. It is assumed that the adaptor has been preconfigured. + description: The IP address of the ethernet to serial adapter. It is assumed that the adapter has been preconfigured. required: true type: string port: From ec238a41e0fd14bd02c28436a43b2ce0c7fb0c5d Mon Sep 17 00:00:00 2001 From: Milan Meulemans Date: Fri, 1 Oct 2021 17:04:08 +0200 Subject: [PATCH 05/29] Remove lametric.png (#19552) --- source/_integrations/lametric.markdown | 1 - source/images/supported_brands/lametric.png | Bin 2021 -> 0 bytes 2 files changed, 1 deletion(-) delete mode 100644 source/images/supported_brands/lametric.png diff --git a/source/_integrations/lametric.markdown b/source/_integrations/lametric.markdown index dbbdf083411..04a322e8f3b 100644 --- a/source/_integrations/lametric.markdown +++ b/source/_integrations/lametric.markdown @@ -1,7 +1,6 @@ --- title: LaMetric description: Instructions on how to integrate LaMetric with Home Assistant. -logo: lametric.png ha_category: - Hub - Notifications diff --git a/source/images/supported_brands/lametric.png b/source/images/supported_brands/lametric.png deleted file mode 100644 index 1202a68a3783b62700d72eaf6a8ac5f12f26baa5..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 2021 zcmVQKgxLr=L>DTv65n2HMQYN%4o z^*_hKOZl7`Oev*s_G;uBtNK38sX1EggG4P{f6gm__=_b50PN|;nE=4N12F`fzhflP z0IaZ<)}M0zMEMDX%*Da~CkXcf0BlUf>g4wIau=fphnYb0$C&8!6)SfKZ1To1Qi2r0h@c~HbvpoIvRh~gni^IB^YD+{1JE28;g zOb$m7=4B)%WI)TgqBot|htW3Q5kdVRxB&3vvF;+yJbWYMz3`a%W zQUwu-y1320@Bq?lJ|(u_*NUjvYGyl!5hPpGjus+>8bNracG_A!Ok$|M4P$HuEk*#V zX@eqew*7{VF&_Jh`2ylnFPpAFrU-y60idD>5H5!WKM6=afP@MFYpE^O34|I*6o9o< z4~pnw4>w$Bx9JEWz8N)bH+B#X-40zwTSAr37`wy16g(S-ovvnmll4UB~{&vOKX zpXXVv33Q#J_`ye%04ObLNd!p6{CfUhK)3`gcZy6~GIE7_r$qCG%9Fvfx>z_U2?3tvD&1?D?NvfWCN5c{(+fK{xt)0&B82qDV$ zNRVx}WK4*9#+Drpc_hRhd!`6TW`|_>1w?zaYU2WA*IcK5ixp(qixgKuc>q}eYBB`b zT~MDC5$ZFKa0&R`E@I=fFCeTCqPtPV+=D35uR28tK7g3LrFU^}!A>AUWv~n&G!LS& zaoRVK#kMBtH$}o;q^wNeK=eJxL6LF-nf?lr?K=5J5xN0!dy%pblKV*!eXmIOycxhN zkV{2`Xq~_Zh@N{Uoq?jSLBhW%LiXpSb*IRrcWm`NB5kj&5+DDjXj4>K|*bbtnX$lun3v1Q%*pDcQGe|E|xImoFAlZcw zLYUtB2xE*fF<9C`LXENLpYq6di5&3(5^8(ynNZycgkoKXeXR&%jIlZt*&Sq(?dSny ziYk|k7tQ#w@ePo*#!{0!Z*uv-y$W&yjTaO^D5N6$)5q1Hx zjek)j+r2h@2GM0R@LCbKL;^tdBWkg1ku+m2u2vkEmW+MO|KKCju(qB-LhLgy`;lY; zP&C1Rfbg|Q*_{6D?E7Hv713p%_zbexy{GvE2?+qi%s&(28g@BjS**3%W%wP(8y{JZ z=UMa$~?*;G^h&I&wqYFhs1jM@QZ~?+*P+{7) zd;g-ypM7LKv_9%5kbTyrB7Ea4*;Sxlfbvp=`+gvx(UPS!CN8BDpvjFN) zD|x$a2vO8_Mm+%((4;Ca|w zyitTL1jr@0u*l=r6}nZgu(Bo#$W+%4AJ)R-tOyC&N6~E$Th!FPWmy-|4x$s#m(Ji& zO0?5x*!y0M%#S{@J{nt7wHQ)$TOX!coQ6pG^R0C`&Y3l1EX)0z&Hllc%kWNmj0~pV zaox$?jWo}SFdq92<3~>s@*D;AOUqi+#mjen1;SK&(_wv1wu4Xu$+Z6--;b=HjsOtz z@KjaoGyEM0<7s^eHeGhBlQMIvG1fFMcVA0ne;92!Po_#CQ+6!mc}?No`)PAQ?>AE? z?|qMgnwKg?^v5U0XW1&$Wk0W7v6~&1B!x^%V2u3_+1%4V$9}cF00000NkvXXu0mjf DOc1Pu From fe652c5e233108cfb6159a991db9b9b702386cea Mon Sep 17 00:00:00 2001 From: jugla <59493499+jugla@users.noreply.github.com> Date: Sat, 2 Oct 2021 09:19:18 +0200 Subject: [PATCH 06/29] cron option is optional (#19559) --- source/_integrations/utility_meter.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/utility_meter.markdown b/source/_integrations/utility_meter.markdown index 9093f3d0e66..42c250e3e51 100644 --- a/source/_integrations/utility_meter.markdown +++ b/source/_integrations/utility_meter.markdown @@ -56,7 +56,7 @@ offset: type: integer cron: description: This option is *mutually exclusive* of `cycle` and `offset`. It provides an advanced method of defining when should the counter be reset. It follows common [crontab syntax](https://crontab.guru). - required: true + required: false type: string net_consumption: description: Set this to True if you would like to treat the source as a net meter. This will allow your counter to go both positive and negative. From 232ba4c13072091f90c22978744060940693a2d5 Mon Sep 17 00:00:00 2001 From: boc-the-git <3479092+boc-the-git@users.noreply.github.com> Date: Sun, 3 Oct 2021 00:47:17 +1000 Subject: [PATCH 07/29] Fix grammar (#19561) --- source/_integrations/kodi.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/kodi.markdown b/source/_integrations/kodi.markdown index 1d59971c579..5d6ee2eb141 100644 --- a/source/_integrations/kodi.markdown +++ b/source/_integrations/kodi.markdown @@ -19,7 +19,7 @@ ha_platforms: The `kodi` platform allows you to control a [Kodi](https://kodi.tv/) multimedia system from Home Assistant. -The preferred way to set up the Kodi platform is by through discovery, which requires an enabled [web interface](https://kodi.wiki/view/Web_interface) on your Kodi installation. +The preferred way to set up the Kodi platform is through discovery, which requires an enabled [web interface](https://kodi.wiki/view/Web_interface) on your Kodi installation. There is currently support for the following device types within Home Assistant: From b72e413d30fe1c94429c0b5042fdd8c12fb2a813 Mon Sep 17 00:00:00 2001 From: N1c093 <59510296+N1c093@users.noreply.github.com> Date: Sun, 3 Oct 2021 21:39:10 +0200 Subject: [PATCH 08/29] Fix link to integration 'media_player' (#19580) --- source/_integrations/denonavr.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/denonavr.markdown b/source/_integrations/denonavr.markdown index 989734ab63c..59beef92ead 100644 --- a/source/_integrations/denonavr.markdown +++ b/source/_integrations/denonavr.markdown @@ -125,7 +125,7 @@ So for example, the above command `/goform/formiPhoneAppDirect.xml?VSMONI2` will
-The denonavr platform supports the standard media player controls such as `turn_on` and `volume_up`. Thus calling the service `media_player.turn_on` is equivalent to calling `denonavr.get_command` with the command `/goform/formiPhoneAppDirect.xml?PWON`. See [media_player](/integrations/meida_player/) for more details. +The denonavr platform supports the standard media player controls such as `turn_on` and `volume_up`. Thus calling the service `media_player.turn_on` is equivalent to calling `denonavr.get_command` with the command `/goform/formiPhoneAppDirect.xml?PWON`. See [media_player](/integrations/media_player/) for more details.
From 199211423578f2b66a6adbcba4d68345345be9f5 Mon Sep 17 00:00:00 2001 From: N1c093 <59510296+N1c093@users.noreply.github.com> Date: Sun, 3 Oct 2021 21:40:56 +0200 Subject: [PATCH 09/29] Fix wrong URL to automation templating (#19579) --- source/_integrations/zwave_js.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/zwave_js.markdown b/source/_integrations/zwave_js.markdown index 7e482530d89..de8fd6230d2 100644 --- a/source/_integrations/zwave_js.markdown +++ b/source/_integrations/zwave_js.markdown @@ -465,7 +465,7 @@ trigger: #### Available Trigger Data -In addition to the [standard automation trigger data](docs/automation/templating/#all), the `zwave_js.value_updated` trigger platform has additional trigger data available for use. +In addition to the [standard automation trigger data](/docs/automation/templating/#all), the `zwave_js.value_updated` trigger platform has additional trigger data available for use. | Template variable | Data | |------------------------------|--------------------------------------------------------------------------------------------| From 4c484c329946aafe8da3be72456ba0228e87ee2c Mon Sep 17 00:00:00 2001 From: Robert Date: Sun, 3 Oct 2021 21:41:53 +0200 Subject: [PATCH 10/29] Update todoist.markdown (#19576) Fix link to page with API token --- source/_integrations/todoist.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/todoist.markdown b/source/_integrations/todoist.markdown index 7c619067b54..2ed6c8cc104 100644 --- a/source/_integrations/todoist.markdown +++ b/source/_integrations/todoist.markdown @@ -16,7 +16,7 @@ This platform allows you to connect to your [Todoist Projects](https://todoist.c ### Prerequisites -You need to determine your Todoist API token. This is fairly simple to do; just go [to the Integrations section on your Todoist settings page](https://todoist.com/Users/viewPrefs?page=authorizations) and find the section labeled "API token" at the bottom of the page. Copy that token and use it in your configuration file. +You need to determine your Todoist API token. This is fairly simple to do; just go [to the Integrations section on your Todoist settings page](https://todoist.com/app/settings/integrations) and find the section labeled "API token" at the bottom of the page. Copy that token and use it in your configuration file. ### Basic Setup From 5034014d290e1a1cc65203b7d12a4220bd6f8730 Mon Sep 17 00:00:00 2001 From: boc-the-git <3479092+boc-the-git@users.noreply.github.com> Date: Mon, 4 Oct 2021 06:43:07 +1100 Subject: [PATCH 11/29] Fix typos (#19562) --- source/_integrations/recorder.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_integrations/recorder.markdown b/source/_integrations/recorder.markdown index 7e39856c2c2..2d20498c83b 100644 --- a/source/_integrations/recorder.markdown +++ b/source/_integrations/recorder.markdown @@ -9,7 +9,7 @@ ha_domain: recorder ha_iot_class: Local Push --- -The `recorder` integration is responsible for storing details in a database, which then are handled by the [`history` ](/integrations/history/) integration. +The `recorder` integration is responsible for storing details in a database, which then are handled by the [`history`](/integrations/history/) integration.
@@ -232,7 +232,7 @@ The following database engines are tested when major changes are made to the rec - SQLite 3.32.1+ - MariaDB 10.3+ - MySQL 5.7+ -- PostgresSQL 12+ +- PostgreSQL 12+ ## Custom database engines From 6bf120427475158513d367795f45df193a979258 Mon Sep 17 00:00:00 2001 From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com> Date: Mon, 4 Oct 2021 11:04:20 +0200 Subject: [PATCH 12/29] Bump tzinfo-data from 1.2021.2 to 1.2021.3 (#19592) Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> --- Gemfile.lock | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Gemfile.lock b/Gemfile.lock index 771743499e4..d01c28d6d85 100644 --- a/Gemfile.lock +++ b/Gemfile.lock @@ -114,7 +114,7 @@ GEM tilt (2.0.10) tzinfo (2.0.4) concurrent-ruby (~> 1.0) - tzinfo-data (1.2021.2) + tzinfo-data (1.2021.3) tzinfo (>= 1.0.0) unicode-display_width (1.8.0) From 186200bd1c5799abb7ae7f97d1f9eeaa7868ff50 Mon Sep 17 00:00:00 2001 From: scheric <38077357+scheric@users.noreply.github.com> Date: Mon, 4 Oct 2021 11:25:22 +0200 Subject: [PATCH 13/29] Repair broken link in System Health (#19584) --- source/_integrations/system_health.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/system_health.markdown b/source/_integrations/system_health.markdown index 2de5fc1cae6..d71bd8879b8 100644 --- a/source/_integrations/system_health.markdown +++ b/source/_integrations/system_health.markdown @@ -19,4 +19,4 @@ system_health: System Health integration data can be viewed at **Configuration** -> **Info**. -Data includes information about your system architecture, operating system and version, Home Assistant installation type and version, Python version, frontend version, the number of [Lovelace Dashboards and Views](/lovelace/dashboards-and-views/) you have, and more. +Data includes information about your system architecture, operating system and version, Home Assistant installation type and version, Python version, frontend version, the number of Lovelace [Dashboards](/lovelace/dashboards/) and [Views](/lovelace/views/) you have, and more. From b9a219a425126e65f8e249b6af85e809b6af86c7 Mon Sep 17 00:00:00 2001 From: N1c093 <59510296+N1c093@users.noreply.github.com> Date: Mon, 4 Oct 2021 11:38:42 +0200 Subject: [PATCH 14/29] Improve readability on the update URL of the Telegram integration (#19577) --- source/_integrations/telegram.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/telegram.markdown b/source/_integrations/telegram.markdown index fd1d2a104ed..cef6b4e2e4d 100644 --- a/source/_integrations/telegram.markdown +++ b/source/_integrations/telegram.markdown @@ -22,7 +22,7 @@ The requirements are: **Method 1:** You can get your `chat_id` by sending any message to the [GetIDs bot](https://t.me/getidsbot). -**Method 2:** To retrieve your `chat_id` you can visit `https://api.telegram.org/botYOUR_API_TOKEN/getUpdates` or to use `$ curl -X GET https://api.telegram.org/botYOUR_API_TOKEN/getUpdates` **after** you have sent the bot a message. Replace `YOUR_API_TOKEN` with your actual token. +**Method 2:** To retrieve your `chat_id` you can visit `https://api.telegram.org/bot/getUpdates` or to use `$ curl -X GET https://api.telegram.org/bot/getUpdates` **after** you have sent the bot a message. Replace `` with your actual token. The result set will include your chat ID as `id` in the `chat` section: From b5ffcfe6e51b940aa658591affeba573aaf811b3 Mon Sep 17 00:00:00 2001 From: boc-the-git <3479092+boc-the-git@users.noreply.github.com> Date: Mon, 4 Oct 2021 21:29:18 +1100 Subject: [PATCH 15/29] Fix minor typos for 17Track (#19560) --- source/_integrations/seventeentrack.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_integrations/seventeentrack.markdown b/source/_integrations/seventeentrack.markdown index d2f0e6913a6..0bbf6aaac74 100644 --- a/source/_integrations/seventeentrack.markdown +++ b/source/_integrations/seventeentrack.markdown @@ -14,7 +14,7 @@ The `seventeentrack` sensor platform allows users to get package data tied to th
-Although the 17track.net website states that account passwords cannot be longer than 16 characters, users can technically set long-than-16-character passwords. These passwords **will not** work with the used API. Therefore, please ensure that your 17track.net password does not exceed 16 characters. +Although the 17track.net website states that account passwords cannot be longer than 16 characters, users can technically set longer-than-16-character passwords. These passwords **will not** work with the used API. Therefore, please ensure that your 17track.net password does not exceed 16 characters.
@@ -55,7 +55,7 @@ show_delivered: ### Lovelace summary card -Use the following templated Markdown card to list all packages in transit along their status: +Use the following templated Markdown card to list all packages in transit along with their status: {% raw %} From a93a1e65c88727077bb8e315020b354d496a4272 Mon Sep 17 00:00:00 2001 From: boc-the-git <3479092+boc-the-git@users.noreply.github.com> Date: Mon, 4 Oct 2021 21:35:43 +1100 Subject: [PATCH 16/29] Fixing errors with Workday (#19563) Co-authored-by: Franck Nijhof --- source/_integrations/workday.markdown | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/source/_integrations/workday.markdown b/source/_integrations/workday.markdown index 22169dfba7a..f8a930b35ee 100644 --- a/source/_integrations/workday.markdown +++ b/source/_integrations/workday.markdown @@ -87,8 +87,7 @@ One other thing to watch is how the `holiday` keyword is used. Your first instin ## Full examples -This example excludes Saturdays, Sundays but not a holiday. Two custom holidays are added. -Even though `sat` and `sun` was not included in `workdays` and in theory, it would not need to be excluded, but because we do not what holidays excluded, we add them so exclude would not default and skip the holidays. Therefore as the note above, 2/17/2020 in the US would still be a workday. +This example excludes Saturdays and Sundays but not holidays. Two custom holidays are added. ```yaml # Example 1 configuration.yaml entry @@ -97,9 +96,12 @@ binary_sensor: country: US workdays: [mon, tue, wed, thu, fri] excludes: [sat, sun] + add_holidays: + - "2020-02-24" + - "2020-04-25" ``` -This example excludes Saturdays, Sundays and holidays. Two custom holidays are added. +This example excludes Saturdays, Sundays and holidays. One custom holiday is added. The date February 24th, 2020 is a Monday but will be excluded because it was added to the `add_holidays` configuration. ```yaml From c2117858cd0e867448cf8a0098c4a1da36d6b2bd Mon Sep 17 00:00:00 2001 From: scheric <38077357+scheric@users.noreply.github.com> Date: Mon, 4 Oct 2021 12:37:39 +0200 Subject: [PATCH 17/29] Fix broken external link in Bosch BMP280 Environmental Sensor (#19585) --- source/_integrations/bmp280.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/bmp280.markdown b/source/_integrations/bmp280.markdown index 8172c8e9524..5ae64297615 100644 --- a/source/_integrations/bmp280.markdown +++ b/source/_integrations/bmp280.markdown @@ -15,7 +15,7 @@ ha_platforms: - sensor --- -The `bmp280` sensor platform allows you to read temperature and pressure values of a [Bosch BMP280 Environmental sensor](https://www.bosch-sensortec.com/products/environmental-sensors/pressure-sensors/pressure-sensors-bmp280-1.html) connected via [I2C](https://en.wikipedia.org/wiki/I²C) bus (SDA, SCL pins). +The `bmp280` sensor platform allows you to read temperature and pressure values of a [Bosch BMP280 Environmental sensor](https://www.bosch-sensortec.com/products/environmental-sensors/pressure-sensors/bmp280/) connected via [I2C](https://en.wikipedia.org/wiki/I²C) bus (SDA, SCL pins). This integration has been tested on a Raspberry Pi 4B, but it should work on any device which is supported by [CircuitPython](https://circuitpython.org/). From 006aa06d29aec56db03f3b3d022f74d003f2a81c Mon Sep 17 00:00:00 2001 From: jonasgustavsson <36690764+jonasgustavsson@users.noreply.github.com> Date: Mon, 4 Oct 2021 13:53:15 +0300 Subject: [PATCH 18/29] Various improvements to documentation for TP-Link LTE (#19567) --- source/_integrations/tplink_lte.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_integrations/tplink_lte.markdown b/source/_integrations/tplink_lte.markdown index e4a2c7b8eb5..1c575a67bb1 100644 --- a/source/_integrations/tplink_lte.markdown +++ b/source/_integrations/tplink_lte.markdown @@ -11,7 +11,7 @@ ha_platforms: - notify --- -The TP-Link LTE integration for Home Assistant allows you to observe and control TP-Link LTE routers, currently only tested with TL-MR6400 (firmware 1.4.0). +The TP-Link LTE integration for Home Assistant makes it possible to send SMS's from the TP-Link LTE router. Phone numbers have to be pre-defined as part of the YAML configuration, and each phone number will turn up as additional notify service in Home Assistant. The integration adds a new notify service for each adds a notification service to Home Assistant that can be used to send SMSs provides a notification service that will send an SMS. Tested only with TL-MR6400 v4. The integration provides a notification service that will send an SMS. @@ -45,7 +45,7 @@ notify: required: false type: list keys: - target: + recipient: description: The phone number of a default recipient or a list with multiple recipients. required: true type: [string, list] From 6578f745c8bd3540ed6a92a63147935281781985 Mon Sep 17 00:00:00 2001 From: Terence Eden Date: Mon, 4 Oct 2021 11:58:41 +0100 Subject: [PATCH 19/29] Better alt text on Etcher screenshots (#19565) --- source/_includes/installation/operating_system.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/source/_includes/installation/operating_system.md b/source/_includes/installation/operating_system.md index 7fb69b791e7..87d3385479d 100644 --- a/source/_includes/installation/operating_system.md +++ b/source/_includes/installation/operating_system.md @@ -87,7 +87,7 @@ If you prefer to use a live operating system, follow the instructions of your Li {% endif %} 2. Download and start Balena Etcher 3. Select "Flash from URL" -![etcher_from_url](/images/installation/etcher1.png) +![Screenshot of the Etcher software showing flash from URL selected.](/images/installation/etcher1.png) 4. Get the URL for your {{site.installation.types[page.installation_type].board}}: {% if site.installation.types[page.installation_type].variants.size > 1 %} @@ -121,15 +121,15 @@ If you prefer to use a live operating system, follow the instructions of your Li _Select and copy the URL or use the "copy" button that appear when you hover it._ 1. Paste the URL for your {{site.installation.types[page.installation_type].board}} into Balena Etcher and click "OK" -![etcher_from_url_paste](/images/installation/etcher2.png) +![Screenshot of the Etcher software showing the URL bar with a URL pasted in.](/images/installation/etcher2.png) 6. Balena Etcher will now download the image, when that is done click "Select target" -![etcher_select_target](/images/installation/etcher3.png) +![Screenshot of the Etcher software showing the select target button highlighted.](/images/installation/etcher3.png) 7. Select the {{site.installation.types[page.installation_type].installation_media}} you want to use for your {{site.installation.types[page.installation_type].board}} -![etcher_select_target](/images/installation/etcher4.png) +![Screenshot of the Etcher software showing teh targets available.](/images/installation/etcher4.png) 8. Click on "Flash!" to start writing the image -![etcher_select_target](/images/installation/etcher5.png) +![Screenshot of the Etcher software showing the Flash button highlighted.](/images/installation/etcher5.png) 9. When Balena Etcher is finished writing the image you will get this confirmation -![etcher_select_target](/images/installation/etcher6.png) +![Screenshot of the Etcher software showing that the installation has completed.](/images/installation/etcher6.png) ### Start up your {{site.installation.types[page.installation_type].board}} From 1c4d8f18ac0da16a5ff1b0b635d385ba3b30bfa5 Mon Sep 17 00:00:00 2001 From: Niek Beernink <652353+nbeernink@users.noreply.github.com> Date: Mon, 4 Oct 2021 13:17:47 +0200 Subject: [PATCH 20/29] Add clarification on brand names (#19583) --- source/_integrations/hunterdouglas_powerview.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/hunterdouglas_powerview.markdown b/source/_integrations/hunterdouglas_powerview.markdown index 1ba5a0b9e21..a5838e5a35c 100644 --- a/source/_integrations/hunterdouglas_powerview.markdown +++ b/source/_integrations/hunterdouglas_powerview.markdown @@ -20,7 +20,7 @@ ha_zeroconf: true ha_dhcp: true --- -The `hunterdouglas_powerview` integration allows you to integrate your [Hunter Douglas PowerView](https://www.hunterdouglas.com/operating-systems/powerview-motorization/support) devices in Home Assistant. +The `hunterdouglas_powerview` integration allows you to integrate your [Hunter Douglas PowerView](https://www.hunterdouglas.com/operating-systems/powerview-motorization/support) devices in Home Assistant. The product is also known by the brand name Luxaflex Powerview in Europe and Australia [as explained on their website](https://www.hunterdouglasgroup.com/company/brands-in-action/), however this integration should work for both brands. There is currently support for the following device types within Home Assistant: From 657186ce7bc8a0598c0203c62e0d76f570e5b887 Mon Sep 17 00:00:00 2001 From: scheric <38077357+scheric@users.noreply.github.com> Date: Mon, 4 Oct 2021 14:18:58 +0200 Subject: [PATCH 21/29] Fix broken link in TP-Link Kasa Smart (#19586) * Fix broken link * Add smart wall switches to usecase * Update tplink.markdown * Add power strips Co-authored-by: Teemu R. Co-authored-by: Teemu R. --- source/_integrations/tplink.markdown | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/source/_integrations/tplink.markdown b/source/_integrations/tplink.markdown index bf70b799081..c64a1e6dbbe 100644 --- a/source/_integrations/tplink.markdown +++ b/source/_integrations/tplink.markdown @@ -20,7 +20,7 @@ ha_platforms: ha_dhcp: true --- -The `tplink` integration allows you to control your [TP-Link Smart Home Devices](https://www.tp-link.com/kasa-smart/) such as smart plugs and smart bulbs. +The `tplink` integration allows you to control your [TP-Link Smart Home Devices](https://www.tp-link.com/kasa-smart/) such as plugs, power strips, wall switches and bulbs. There is currently support for the following device types within Home Assistant: @@ -32,10 +32,6 @@ In order to activate the support, you will have to enable the integration inside The supported devices in your network are automatically discovered, but if you want to control devices residing in other networks you will need to configure them manually as shown below. ## Supported Devices - -This integration supports devices that are controllable with the [KASA app](https://www.tp-link.com/us/kasa-smart/kasa.html). -The following devices are known to work with this component. - ### Plugs Plugs are type `switch` when autodiscovery has been disabled. From 5a22ec5e7c387a4a5b4b47599dd0ea28b05fae0c Mon Sep 17 00:00:00 2001 From: MeIchthys <10717998+meichthys@users.noreply.github.com> Date: Tue, 5 Oct 2021 03:08:49 -0400 Subject: [PATCH 22/29] Clarify Mullvad integration (#19591) --- source/_integrations/mullvad.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/mullvad.markdown b/source/_integrations/mullvad.markdown index b6d2bf1ab86..19c751976c8 100644 --- a/source/_integrations/mullvad.markdown +++ b/source/_integrations/mullvad.markdown @@ -14,7 +14,7 @@ ha_platforms: - binary_sensor --- -The Mullvad VPN integration pulls [Mullvad](https://mullvad.net/) VPN status information into Home Assistant. +The Mullvad VPN integration uses the [Mullvad](https://mullvad.net/) VPN API to detect if your Home Assistant instance is connected to the Mullvad VPN service. ![](/images/screenshots/mullvad_vpn_sample_sensor_connected.png) From 08193f3b9946ec8a023be89d41a844cfd5c7dfb9 Mon Sep 17 00:00:00 2001 From: David Beitey Date: Tue, 5 Oct 2021 19:41:04 +1000 Subject: [PATCH 23/29] Use https for MaterialDesignIcons project links (#19607) --- source/_docs/configuration/customizing-devices.markdown | 2 +- source/lovelace/badges.markdown | 4 ++-- source/lovelace/dashboards.markdown | 4 ++-- source/lovelace/header-footer.markdown | 2 +- source/lovelace/views.markdown | 2 +- 5 files changed, 7 insertions(+), 7 deletions(-) diff --git a/source/_docs/configuration/customizing-devices.markdown b/source/_docs/configuration/customizing-devices.markdown index 29d66e54b92..384d1172667 100644 --- a/source/_docs/configuration/customizing-devices.markdown +++ b/source/_docs/configuration/customizing-devices.markdown @@ -39,7 +39,7 @@ entity_picture: required: false type: string icon: - description: "Any icon from [MaterialDesignIcons.com](http://materialdesignicons.com). Prefix name with `mdi:`, ie `mdi:home`. Note: Newer icons may not yet be available in the current Home Assistant release. You can check when an icon was added to MaterialDesignIcons.com at [MDI History](https://materialdesignicons.com/history)." + description: "Any icon from [MaterialDesignIcons.com](https://materialdesignicons.com). Prefix name with `mdi:`, ie `mdi:home`. Note: Newer icons may not yet be available in the current Home Assistant release. You can check when an icon was added to MaterialDesignIcons.com at [MDI History](https://materialdesignicons.com/history)." required: false type: string assumed_state: diff --git a/source/lovelace/badges.markdown b/source/lovelace/badges.markdown index 18f40ebb0c2..61e0bc7819e 100644 --- a/source/lovelace/badges.markdown +++ b/source/lovelace/badges.markdown @@ -30,7 +30,7 @@ name: default: Name of entity icon: required: false - description: Overwrites icon or entity picture. You can use any icon from [MaterialDesignIcons.com](http://materialdesignicons.com). Prefix the icon name with `mdi:`, ie `mdi:home`. + description: Overwrites icon or entity picture. You can use any icon from [MaterialDesignIcons.com](https://materialdesignicons.com). Prefix the icon name with `mdi:`, ie `mdi:home`. type: string default: Entity domain icon image: @@ -87,7 +87,7 @@ name: type: string icon: required: false - description: Overwrites icon or entity picture. You can use any icon from [MaterialDesignIcons.com](http://materialdesignicons.com). Prefix the icon name with `mdi:`, ie `mdi:home`. + description: Overwrites icon or entity picture. You can use any icon from [MaterialDesignIcons.com](https://materialdesignicons.com). Prefix the icon name with `mdi:`, ie `mdi:home`. type: string image: required: false diff --git a/source/lovelace/dashboards.markdown b/source/lovelace/dashboards.markdown index b1448a8db71..2a4d909c6ef 100644 --- a/source/lovelace/dashboards.markdown +++ b/source/lovelace/dashboards.markdown @@ -110,7 +110,7 @@ dashboards: type: string icon: required: false - description: The icon to show in the sidebar. You can use any icon from [MaterialDesignIcons.com](http://materialdesignicons.com). Prefix the icon name with `mdi:`, ie `mdi:home`. + description: The icon to show in the sidebar. You can use any icon from [MaterialDesignIcons.com](https://materialdesignicons.com). Prefix the icon name with `mdi:`, ie `mdi:home`. type: string show_in_sidebar: required: false @@ -191,4 +191,4 @@ views: title: Lovelace content: > Welcome to your **Lovelace UI**. -``` \ No newline at end of file +``` diff --git a/source/lovelace/header-footer.markdown b/source/lovelace/header-footer.markdown index b8dee843bdc..f7257f96c09 100644 --- a/source/lovelace/header-footer.markdown +++ b/source/lovelace/header-footer.markdown @@ -69,7 +69,7 @@ entities: type: string icon: required: false - description: Override the entity icon. You can use any icon from [MaterialDesignIcons.com](http://materialdesignicons.com). Prefix the icon name with `mdi:`, ie `mdi:home`. + description: Override the entity icon. You can use any icon from [MaterialDesignIcons.com](https://materialdesignicons.com). Prefix the icon name with `mdi:`, ie `mdi:home`. type: string image: required: false diff --git a/source/lovelace/views.markdown b/source/lovelace/views.markdown index c8fa471b74b..c8d9f0deb01 100644 --- a/source/lovelace/views.markdown +++ b/source/lovelace/views.markdown @@ -155,7 +155,7 @@ views: default: view index icon: required: false - description: Icon-name from Material Design Icons. You can use any icon from [MaterialDesignIcons.com](http://materialdesignicons.com). Prefix the icon name with `mdi:`, ie `mdi:home`. + description: Icon-name from Material Design Icons. You can use any icon from [MaterialDesignIcons.com](https://materialdesignicons.com). Prefix the icon name with `mdi:`, ie `mdi:home`. type: string background: required: false From 4ab03eef1110b88b0bc019300b8354117acc4c49 Mon Sep 17 00:00:00 2001 From: bouni Date: Tue, 5 Oct 2021 14:31:58 +0200 Subject: [PATCH 24/29] Updating Bluesound documentation (#19609) --- source/_integrations/bluesound.markdown | 1 - 1 file changed, 1 deletion(-) diff --git a/source/_integrations/bluesound.markdown b/source/_integrations/bluesound.markdown index ffa051049c0..a8c5bd8562f 100644 --- a/source/_integrations/bluesound.markdown +++ b/source/_integrations/bluesound.markdown @@ -1,7 +1,6 @@ --- title: Bluesound description: Instructions on how to integrate Bluesound devices into Home Assistant. -logo: bluesound.png ha_category: - Media Player ha_release: 0.51 From cad81757ada515f6eda2532cce329a65832c6b9c Mon Sep 17 00:00:00 2001 From: bouni Date: Tue, 5 Oct 2021 14:52:52 +0200 Subject: [PATCH 25/29] Updating EverLights documentation (#19611) --- source/_integrations/everlights.markdown | 1 - 1 file changed, 1 deletion(-) diff --git a/source/_integrations/everlights.markdown b/source/_integrations/everlights.markdown index 00bee6f113d..810bfcd4d30 100644 --- a/source/_integrations/everlights.markdown +++ b/source/_integrations/everlights.markdown @@ -1,7 +1,6 @@ --- title: EverLights description: Instructions on how to set up EverLights within Home Assistant. -logo: everlights.png ha_category: - Light ha_iot_class: Local Polling From 804e1ebbcce282ffcac2ed9753eac14a127d006e Mon Sep 17 00:00:00 2001 From: David Beitey Date: Tue, 5 Oct 2021 23:37:09 +1000 Subject: [PATCH 26/29] Update documentation URLs for security and privacy (#19612) --- source/_docs/backend/database.markdown | 2 +- source/_docs/configuration/basic.markdown | 2 +- source/_docs/configuration/splitting_configuration.markdown | 2 +- source/_docs/configuration/troubleshooting.markdown | 2 +- source/_docs/configuration/yaml.markdown | 2 +- source/_docs/mqtt/broker.markdown | 4 ++-- source/_docs/mqtt/testing.markdown | 2 +- source/_docs/tools/dev-tools.markdown | 2 +- source/_docs/z-wave/control-panel.markdown | 2 +- source/_includes/common-tasks/development_version.md | 2 +- source/_includes/installation/container/alternative.md | 6 +++--- source/developers/cla.markdown | 2 +- source/help/index.markdown | 6 +++--- source/help/trivia.markdown | 2 +- 14 files changed, 19 insertions(+), 19 deletions(-) diff --git a/source/_docs/backend/database.markdown b/source/_docs/backend/database.markdown index a0ad7b94c40..5b261ac78c9 100644 --- a/source/_docs/backend/database.markdown +++ b/source/_docs/backend/database.markdown @@ -5,7 +5,7 @@ description: "Details about the database used by Home Assistant." Home Assistant uses database to store events and parametersis for history and tracking. The default database used is [SQLite](https://www.sqlite.org/) and the database file is stored in your [configuration directory](/getting-started/configuration/) (e.g., `/home-assistant_v2.db`); however, other databases can be used. If you prefer to run a database server (e.g., PostgreSQL), use the [`recorder` component](/integrations/recorder/). -To work with SQLite database manually from the command-line, you will need an [installation](http://www.sqlitetutorial.net/download-install-sqlite/) of `sqlite3`. Alternatively [DB Browser for SQLite](http://sqlitebrowser.org/) provides a viewer for exploring the database data and an editor for executing SQL commands. +To work with SQLite database manually from the command-line, you will need an [installation](https://www.sqlitetutorial.net/download-install-sqlite/) of `sqlite3`. Alternatively [DB Browser for SQLite](https://sqlitebrowser.org/) provides a viewer for exploring the database data and an editor for executing SQL commands. First load your database with `sqlite3`: ```bash diff --git a/source/_docs/configuration/basic.markdown b/source/_docs/configuration/basic.markdown index 9487c1fba62..641519be50c 100644 --- a/source/_docs/configuration/basic.markdown +++ b/source/_docs/configuration/basic.markdown @@ -57,7 +57,7 @@ temperature_unit: required: false type: string time_zone: - description: "Pick your time zone from the column **TZ** of [Wikipedia's list of tz database time zones](http://en.wikipedia.org/wiki/List_of_tz_database_time_zones)" + description: "Pick your time zone from the column **TZ** of [Wikipedia's list of tz database time zones](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones)" required: false type: string currency: diff --git a/source/_docs/configuration/splitting_configuration.markdown b/source/_docs/configuration/splitting_configuration.markdown index 50300264f93..c8e24c09584 100644 --- a/source/_docs/configuration/splitting_configuration.markdown +++ b/source/_docs/configuration/splitting_configuration.markdown @@ -22,7 +22,7 @@ homeassistant: longitude: -121 # 'metric' for Metric, 'imperial' for Imperial unit_system: imperial - # Pick yours from here: http://en.wikipedia.org/wiki/List_of_tz_database_time_zones + # Pick yours from here: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones time_zone: "America/Los_Angeles" customize: !include customize.yaml ``` diff --git a/source/_docs/configuration/troubleshooting.markdown b/source/_docs/configuration/troubleshooting.markdown index b6880bde4a3..4484bcbed99 100644 --- a/source/_docs/configuration/troubleshooting.markdown +++ b/source/_docs/configuration/troubleshooting.markdown @@ -26,7 +26,7 @@ One of the most common problems with Home Assistant is an invalid `configuration - [Supervised](/common-tasks/supervised/#configuration-check) - The configuration files, including `configuration.yaml` must be UTF-8 encoded. If you see error like `'utf-8' codec can't decode byte`, edit the offending configuration and re-save it as UTF-8. -- You can verify your configuration's YAML structure using [this online YAML parser](http://yaml-online-parser.appspot.com/) or [YAML Lint](http://www.yamllint.com/). +- You can verify your configuration's YAML structure using [this online YAML parser](https://yaml-online-parser.appspot.com/) or [YAML Validator](https://codebeautify.org/yaml-validator/). - To learn more about the quirks of YAML, read [YAML IDIOSYNCRASIES](https://docs.saltstack.com/en/latest/topics/troubleshooting/yaml_idiosyncrasies.html) by SaltStack (the examples there are specific to SaltStack, but do explain YAML issues well). `configuration.yaml` does not allow multiple sections to have the same name. If you want to load multiple platforms for one component, you can append a [number or string](/getting-started/devices/#style-2-list-each-device-separately) to the name or nest them using [this style](/getting-started/devices/#style-1-collect-every-entity-under-the-parent): diff --git a/source/_docs/configuration/yaml.markdown b/source/_docs/configuration/yaml.markdown index e0e4ff9d4de..e914c141ffe 100644 --- a/source/_docs/configuration/yaml.markdown +++ b/source/_docs/configuration/yaml.markdown @@ -25,7 +25,7 @@ Note that indentation is an important part of specifying relationships using YAM Getting the right indentation can be tricky if you're not using an editor with a fixed width font. Tabs are not allowed to be used for indentation. Convention is to use 2 spaces for each level of indentation. -You can use the online service [YAMLLint](http://www.yamllint.com/) to check if your YAML syntax is correct before loading it into Home Assistant which will save you some time. If you do so, be aware that this is a third-party service and is not maintained by the Home Assistant community. +You can use the online service [YAML Validator](https://codebeautify.org/yaml-validator/) to check if your YAML syntax is correct before loading it into Home Assistant which will save you some time. If you do so, be aware that this is a third-party service and is not maintained by the Home Assistant community.
diff --git a/source/_docs/mqtt/broker.markdown b/source/_docs/mqtt/broker.markdown index 364bc1572f6..e5e42f02a38 100644 --- a/source/_docs/mqtt/broker.markdown +++ b/source/_docs/mqtt/broker.markdown @@ -78,7 +78,7 @@ If you are running a Mosquitto instance on a different server with proper SSL en ### Public broker -The Mosquitto project runs a [public broker](http://test.mosquitto.org). This is the easiest to set up, but there is no privacy as all messages are public. Use this only for testing purposes and not for real tracking of your devices or controlling your home. +The Mosquitto project runs a [public broker](https://test.mosquitto.org). This is the easiest to set up, but there is no privacy as all messages are public. Use this only for testing purposes and not for real tracking of your devices or controlling your home. ```yaml mqtt: @@ -88,7 +88,7 @@ mqtt: # Optional, replace port 1883 with following if you want encryption # (doesn't really matter because broker is public) port: 8883 - # Download certificate from http://test.mosquitto.org/ssl/mosquitto.org.crt + # Download certificate from https://test.mosquitto.org/ssl/mosquitto.org.crt certificate: /home/paulus/downloads/mosquitto.org.crt ``` diff --git a/source/_docs/mqtt/testing.markdown b/source/_docs/mqtt/testing.markdown index 0c7bd51ced2..6a26d86159d 100644 --- a/source/_docs/mqtt/testing.markdown +++ b/source/_docs/mqtt/testing.markdown @@ -4,7 +4,7 @@ description: "Instructions on how to test your MQTT setup." logo: mqtt.png --- -The `mosquitto` broker package ships commandline tools (often as `*-clients` package) to send and receive MQTT messages. As an alternative have a look at [hbmqtt_pub](http://hbmqtt.readthedocs.org/en/latest/references/hbmqtt_pub.html) and [hbmqtt_sub](http://hbmqtt.readthedocs.org/en/latest/references/hbmqtt_sub.html) which are provided by HBMQTT. For sending test messages to a broker running on localhost check the example below: +The `mosquitto` broker package ships commandline tools (often as `*-clients` package) to send and receive MQTT messages. As an alternative have a look at [hbmqtt_pub](https://hbmqtt.readthedocs.org/en/latest/references/hbmqtt_pub.html) and [hbmqtt_sub](https://hbmqtt.readthedocs.org/en/latest/references/hbmqtt_sub.html) which are provided by HBMQTT. For sending test messages to a broker running on localhost check the example below: ```bash mosquitto_pub -h 127.0.0.1 -t home-assistant/switch/1/on -m "Switch is ON" diff --git a/source/_docs/tools/dev-tools.markdown b/source/_docs/tools/dev-tools.markdown index f1de345d3bb..8167a02c335 100644 --- a/source/_docs/tools/dev-tools.markdown +++ b/source/_docs/tools/dev-tools.markdown @@ -110,4 +110,4 @@ The Template Editor provides a way to quickly test templates prior to placing th By default this will contain sample code that illustrates how templates can be written and tested. This sample code can be removed and replaced with your own. You can restore the default example by pressing the "Reset to Demo Template" button beneath the code editor. -For more information about Jinja2, visit [Jinja2 documentation](http://jinja.pocoo.org/docs/dev/templates/), and also read templating document [here](/topics/templating/). +For more information about Jinja2, visit [Jinja2 documentation](https://jinja.palletsprojects.com/templates/), and also read templating document [here](/topics/templating/). diff --git a/source/_docs/z-wave/control-panel.markdown b/source/_docs/z-wave/control-panel.markdown index 8d53023c1b2..8d71fd04d54 100644 --- a/source/_docs/z-wave/control-panel.markdown +++ b/source/_docs/z-wave/control-panel.markdown @@ -144,7 +144,7 @@ If your node has user codes, you can set and delete them. The format is raw hex \x39 = 9 ``` Some non compliant device like tag readers, have implemented to use raw hex code. -Please refer to a hex ASCII table to set your code. Example: http://www.asciitable.com/ +Please refer to a hex ASCII table to set your code. Example: https://www.asciitable.com/ Here is a small Python program than will take numbers on the command line and print the correct sequence for compliant devices: diff --git a/source/_includes/common-tasks/development_version.md b/source/_includes/common-tasks/development_version.md index 96cde097ae7..a163cdd5269 100644 --- a/source/_includes/common-tasks/development_version.md +++ b/source/_includes/common-tasks/development_version.md @@ -53,7 +53,7 @@ docker pull {{ site.installation.container.base }}:dev 3. Download and install the version you want ```bash - pip3 install --upgrade git+git://github.com/home-assistant/core.git@dev + pip3 install --upgrade git+https://github.com/home-assistant/core.git@dev ``` 4. When that is complete restart the service for it to use the new files. diff --git a/source/_includes/installation/container/alternative.md b/source/_includes/installation/container/alternative.md index ec9aa89e7e7..f62d55ec85b 100644 --- a/source/_includes/installation/container/alternative.md +++ b/source/_includes/installation/container/alternative.md @@ -15,7 +15,7 @@ The steps would be: - Set "Enable auto-restart" if you like - Within "Volume" click on "Add Folder" and choose either an existing folder or add a new folder. The "mount path" has to be "/config", so that Home Assistant will use it for the configs and logs. It is therefore recommended that the folder you choose should be named "config" or "homeassistant/config" to avoid confusion when referencing it within service calls. - Within "Network" select "Use same network as Docker Host" -- To ensure that Home Assistant displays the correct timezone go to the "Environment" tab and click the plus sign then add `variable` = `TZ` & `value` = `Europe/London` choosing [your correct timezone](http://en.wikipedia.org/wiki/List_of_tz_database_time_zones) +- To ensure that Home Assistant displays the correct timezone go to the "Environment" tab and click the plus sign then add `variable` = `TZ` & `value` = `Europe/London` choosing [your correct timezone](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones) - Confirm the "Advanced Settings" - Click on "Next" and then "Apply" - Your Home Assistant within Docker should now run and will serve the web interface from port 8123 on your Docker host (this will be your Synology NAS IP address - for example `http://192.168.1.10:8123`) @@ -37,7 +37,7 @@ Adjust the following Terminal command as follows : - Replace `/PATH_TO_YOUR_CONFIG` points at the folder where you want to store your configuration - Replace `/PATH_TO_YOUR_USB_STICK` matches the path for your USB stick (e.g., `/dev/ttyACM0` for most Synology users) -- Replace "Australia/Melbourne" with [your timezone](http://en.wikipedia.org/wiki/List_of_tz_database_time_zones) +- Replace "Australia/Melbourne" with [your timezone](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones) Run it in Terminal. @@ -83,7 +83,7 @@ The steps would be: - Click on "Advanced Settings" - Within "Shared Folders" click on "Volume from host" > "Add" and choose either an existing folder or add a new folder. The "mount point has to be `/config`, so that Home Assistant will use it for the configuration and logs. - Within "Network" and select Network Mode to "Host" -- To ensure that Home Assistant displays the correct timezone go to the "Environment" tab and click the plus sign then add `variable` = `TZ` & `value` = `Europe/London` choosing [your correct timezone](http://en.wikipedia.org/wiki/List_of_tz_database_time_zones) +- To ensure that Home Assistant displays the correct timezone go to the "Environment" tab and click the plus sign then add `variable` = `TZ` & `value` = `Europe/London` choosing [your correct timezone](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones) - Click on "Create" - Wait for some time until your NAS has created the container - Your Home Assistant within Docker should now run and will serve the web interface from port 8123 on your Docker host (this will be your Qnap NAS IP address - for example `http://192.xxx.xxx.xxx:8123`) diff --git a/source/developers/cla.markdown b/source/developers/cla.markdown index b703da1bace..831db758425 100644 --- a/source/developers/cla.markdown +++ b/source/developers/cla.markdown @@ -30,7 +30,7 @@ By making a contribution to this project, I certify that: ## Attribution -The text of this license is available under the [Creative Commons Attribution-ShareAlike 3.0 Unported License](http://creativecommons.org/licenses/by-sa/3.0/). It is based on the Linux [Developer Certificate Of Origin](http://elinux.org/Developer_Certificate_Of_Origin), but is modified to explicitly use the Apache 2.0 license +The text of this license is available under the [Creative Commons Attribution-ShareAlike 3.0 Unported License](https://creativecommons.org/licenses/by-sa/3.0/). It is based on the Linux [Developer Certificate Of Origin](https://elinux.org/Developer_Certificate_Of_Origin), but is modified to explicitly use the Apache 2.0 license and not mention sign-off. ## Signing diff --git a/source/help/index.markdown b/source/help/index.markdown index 47654de0d16..bf8aa0a7638 100644 --- a/source/help/index.markdown +++ b/source/help/index.markdown @@ -67,8 +67,8 @@ Don't miss the regular [Home Assistant podcasts](https://hasspodcast.io/). - [The winners of the Thomas-Krenn-Awards 2018](https://www.thomas-krenn.com/de/tkmag/allgemein/die-gewinner-des-thomas-krenn-awards-2018-stehen-fest/) - March 2018 - [Best of Open Source Smart Home: Home Assistant vs OpenHAB](https://smarthome.university/your-smart-home-platform-home-assistant-vs-openhab/) - February 2018 - [Hausautomations-Schaltzentrale Home Assistant auf Python-Basis](https://www.heise.de/ct/ausgabe/2017-26-Hausautomations-Schaltzentrale-Home-Assistant-3909532.html) - December 2017 -- [Using Home Assistant the ARTIK Cloud](http://web.archive.org/web/20191028191303/https://developer.artik.io/documentation/developer-guide/wireless-iot/hass.html) - September 2017 -- [Control home automation hardware with Home Assistant](http://www.linux-magazine.com/Issues/2017/203/Home-Assistant) - August 2017 +- [Using Home Assistant the ARTIK Cloud](https://web.archive.org/web/20191028191303/https://developer.artik.io/documentation/developer-guide/wireless-iot/hass.html) - September 2017 +- [Control home automation hardware with Home Assistant](https://www.linux-magazine.com/Issues/2017/203/Home-Assistant) - August 2017 - [Smart Home Home Assistant KNX Alexa Sprachsteuerung](https://onesmarthome.de/smart-home-home-assistant-knx-alexa-sprachsteuerung/) - August 2017 - [Episode #122: Home Assistant: Pythonic Home Automation](https://talkpython.fm/episodes/show/122/home-assistant-pythonic-home-automation) - July 2017 - [Smart Home Home Assistant Konfiguration mit YAML](https://onesmarthome.de/smart-home-home-assistant-konfiguration/) - July 2017 @@ -84,7 +84,7 @@ Don't miss the regular [Home Assistant podcasts](https://hasspodcast.io/). - [Episode #11](https://pythonbytes.fm/episodes/show/11/django-2.0-is-dropping-python-2-entirely-pipenv-for-profile-functionality-and-pythonic-home-automation) at minute 15:20 by [Python Bytes](https://pythonbytes.fm/) - January 2017 - [Now you can hide your smart home on the darknet](https://www.wired.com/2016/07/now-can-hide-smart-home-darknet/) - July 2016 - [Home Assistant: The Python Approach to Home Automation](https://www.linux.com/news/home-assistant-python-approach-home-automation-video) - June 2016 -- [Secure home automation, without clouds or dedicated hubs](http://linuxgizmos.com/secure-home-automation-without-clouds-or-dedicated-hubs/) - June 2016 +- [Secure home automation, without clouds or dedicated hubs](https://linuxgizmos.com/secure-home-automation-without-clouds-or-dedicated-hubs/) - June 2016 - [Weekend Project: Setting up Home Assistant on your PC or Mac](https://www.automatedhome.co.uk/software/weekend-project-setting-up-home-assistant-on-your-pc-or-mac.html) by [automated home](https://www.automatedhome.co.uk/) - April 2016 - [Episode 105 - DIY Home Automation Roundup](https://www.hometech.fm/shows/105) by [HomeTech.fm](https://www.hometech.fm/) - April 2016 - [5 open source home automation tools](https://opensource.com/life/16/3/5-open-source-home-automation-tools) by [opensource.com](https://opensource.com) - March 2016 diff --git a/source/help/trivia.markdown b/source/help/trivia.markdown index 094b1e4762a..532c7c82a30 100644 --- a/source/help/trivia.markdown +++ b/source/help/trivia.markdown @@ -16,7 +16,7 @@ The website [https://www.home-assistant.io](/) was launched on December 18, 2014 ## Logo -The current logo was created by [Jeremy Geltman](http://jeremygeltman.com/). Further details can be found in the [announcement](/blog/2015/03/08/new-logo/). +The current logo was created by [Jeremy Geltman](https://jeremygeltman.com/). Further details can be found in the [announcement](/blog/2015/03/08/new-logo/). ## License From 7d2156456c36a8ec646f37a32ad917ad1a8946f8 Mon Sep 17 00:00:00 2001 From: bouni Date: Tue, 5 Oct 2021 16:46:56 +0200 Subject: [PATCH 27/29] Updating Etherscan documentation (#19608) --- source/_integrations/etherscan.markdown | 1 - 1 file changed, 1 deletion(-) diff --git a/source/_integrations/etherscan.markdown b/source/_integrations/etherscan.markdown index 9d66ece6a68..60ee4ad9de8 100644 --- a/source/_integrations/etherscan.markdown +++ b/source/_integrations/etherscan.markdown @@ -1,7 +1,6 @@ --- title: Etherscan description: Instructions on how to integrate Etherscan.io data within Home Assistant. -logo: etherscan.png ha_category: - Finance ha_release: 0.47 From 8e39f213ace949ce8cc103a10fe1f9758f0186cb Mon Sep 17 00:00:00 2001 From: bouni Date: Tue, 5 Oct 2021 17:39:53 +0200 Subject: [PATCH 28/29] Updating Graphite documentation (#19614) --- source/_integrations/graphite.markdown | 1 - 1 file changed, 1 deletion(-) diff --git a/source/_integrations/graphite.markdown b/source/_integrations/graphite.markdown index 03b766a0650..887f5acf636 100644 --- a/source/_integrations/graphite.markdown +++ b/source/_integrations/graphite.markdown @@ -1,7 +1,6 @@ --- title: Graphite description: Instructions on how to record Home Assistant history in Graphite. -logo: graphite.png ha_category: - History ha_release: 0.13 From 5b0fb3fd6c7f6cc75a908c507b82653fffabb33d Mon Sep 17 00:00:00 2001 From: Stefan <37924749+stefanroelofs@users.noreply.github.com> Date: Tue, 5 Oct 2021 17:56:27 +0200 Subject: [PATCH 29/29] Fix broken links in documentation (#19610) Co-authored-by: Franck Nijhof --- source/_integrations/universal.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/universal.markdown b/source/_integrations/universal.markdown index 32a1e5c3aa0..d1fbfac37b4 100644 --- a/source/_integrations/universal.markdown +++ b/source/_integrations/universal.markdown @@ -94,7 +94,7 @@ It is also recommended that the command `volume_up`, the command `volume_down`, When providing `select_source` as a command, it is recommended to also provide the attributes `source`, and `source_list`. The `source` attribute is the currently select source, while the `source_list` attribute is a list of all available sources. -When using `state_template`, if you use a template that depends on the current time or some other non-deterministic result not sourced from entities, the template won't repeatedly update but will only update when the state of a referenced entity updates. For ways to deal with this issue, see the [example](/integrations/binary_sensor.template/#working-without-entities) in the template binary_sensor. +When using `state_template`, if you use a template that depends on the current time it is recommended to use `now()`. Using `now()` will cause templates to be refreshed at the start of every new minute. For more information see the [time](/docs/configuration/templating/#time) section in the template documentation. ## Usage examples