From 17a8a9e4d664a304afa79aaa4ebb119b3aed5c27 Mon Sep 17 00:00:00 2001 From: Daniel Perna Date: Wed, 5 Dec 2018 23:30:58 +0100 Subject: [PATCH 001/132] Update documentation for HomeMatic --- source/_components/homematic.markdown | 16 ++++++++++++---- 1 file changed, 12 insertions(+), 4 deletions(-) diff --git a/source/_components/homematic.markdown b/source/_components/homematic.markdown index 86ff3df552e..77a06faab93 100644 --- a/source/_components/homematic.markdown +++ b/source/_components/homematic.markdown @@ -16,12 +16,12 @@ featured: false The [Homematic](http://www.homematic.com/) component provides bi-directional communication with your CCU/Homegear. It uses a XML-RPC connection to set values on devices and subscribes to receive events the devices and the CCU emit. If you are using Homegear with paired [Intertechno](http://intertechno.at/) devices, uni-directional communication is possible as well. -Device support is available for most of the wired and wireless devices, as well as a few IP devices. If you have a setup with mixed protocols, you have to configure additional hosts with the appropriate ports. The default is using port 2001, which are wireless devices. Wired devices usually are available through port 2000 and IP devices through port 2010. The virtual thermostatgroups the CCU provides use port 9292 **and** require you to set the `path` setting to `/groups`. +Device support is available for most of the wired and wireless devices, as well as a lot of IP devices. If you have a setup with mixed protocols, you have to configure additional [interfaces](https://www.home-assistant.io/components/homematic#interfaces) with the appropriate ports. The default is using port 2001, which are wireless devices. Wired devices usually are available through port 2000 and IP devices through port 2010. The virtual thermostatgroups the CCU provides use port 9292 **and** require you to set the `path` setting to `/groups`. When using SSL on a CCU3, by default the same ports as usual with a prepended 4 are available. So 2001 becomes 42001, 2010 becomes 42010 etc.. If you want to see if a specific device you have is supported, head over to the [pyhomematic](https://github.com/danielperna84/pyhomematic/tree/master/pyhomematic/devicetypes) repository and browse through the source code. A dictionary with the device identifiers (e.g., HM-Sec-SC-2) can be found within the relevant modules near the bottom. If your device is not supported, feel free to contribute. We automatically detect all devices we currently support and try to generate useful names. If you enable name-resolving, we try to fetch names from Metadata (Homegear), via JSON-RPC or the XML-API you may have installed on your CCU. Since this may fail this is disabled by default. -You can manually rename the created entities by using Home Assistant's [Customizing](/docs/configuration/customizing-devices/) feature. With it you are also able to hide entities you don't want to see in the UI. +You can manually rename the created entities by using Home Assistant's [Customizing](/docs/configuration/customizing-devices/) feature. With it you are also able to hide entities you don't want to see in the UI. The HomeMatic component is also supported by the [Entity Registry](https://developers.home-assistant.io/docs/en/entity_registry_index.html), which allows you to change the friendly name and the entity ID directly in the Home Assistant UI. To set up the component, add the following information to your `configuration.yaml` file: @@ -61,9 +61,17 @@ host: required: true type: string port: - description: "Port of CCU/Homegear XML-RPC Server. Wireless: 2001, wired: 2000, IP: 2010, thermostatgroups: 9292." + description: Port of CCU/Homegear XML-RPC Server. Wireless: 2001, wired: 2000, IP: 2010, thermostatgroups: 9292. With enabled SSL on the CCU3 usually a 4 is prepended to the Port. E.g. 2001 becomes 42001 with enabled SSL. required: false type: integer +ssl: + description: Set to `true` if SSL support is enabled on the CCU3. + required: false + type: bool +verify_ssl: + description: Set to `true` if a valid certificate is being used. The default is `false` as usually a self-signed certificate is configured. + required: false + type: bool callback_ip: description: Set this, if Home Assistant is reachable under a different IP from the CCU (NAT, Docker etc.). required: false @@ -78,7 +86,7 @@ resolvenames: type: string default: false jsonport: - description: Port of CCU JSON-RPC Server. The default is 80, but it may be different when running CCU virtually via Docker. + description: Port of CCU JSON-RPC Server. The default is 80, but it may be different when running CCU virtually via Docker or with enabled SSL. required: false type: integer username: From e63ed201fbb14d4a5aedd820e574e08e4082fc55 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Thu, 6 Dec 2018 09:38:58 +0100 Subject: [PATCH 002/132] Remove Instapush docs (#7749) --- source/_components/notify.instapush.markdown | 87 ------------------- source/images/supported_brands/instapush.png | Bin 6389 -> 0 bytes 2 files changed, 87 deletions(-) delete mode 100644 source/_components/notify.instapush.markdown delete mode 100644 source/images/supported_brands/instapush.png diff --git a/source/_components/notify.instapush.markdown b/source/_components/notify.instapush.markdown deleted file mode 100644 index c725d22e463..00000000000 --- a/source/_components/notify.instapush.markdown +++ /dev/null @@ -1,87 +0,0 @@ ---- -layout: page -title: "Instapush" -description: "Instructions on how to add Instapush notifications to Home Assistant." -date: 2015-05-01 18:00 -sidebar: true -comments: false -sharing: true -footer: true -logo: instapush.png -ha_category: Notifications -ha_release: pre 0.7 ---- - -The `instapush` platform uses [Instapush](https://instapush.im) to delivery notifications from Home Assistant to your Android or iOS device. - -The Instapush [Getting Started page](https://instapush.im/home/start/) will guide through the process of creating the required items. - -To add Instapush to your installation, add the following to your `configuration.yaml` file: - -```yaml -# Example configuration.yaml entry -notify: - - name: NOTIFIER_NAME - platform: instapush - api_key: YOUR_API_KEY - app_secret: YOUR_APP_SECRET - event: PUSH_TO_EVENT - tracker: TRACKER_NAME -``` - -{% configuration %} -name: - description: Setting the optional parameter `name` allows multiple notifiers to be created. The notifier will bind to the service `notify.NOTIFIER_NAME`. - required: false - default: notify - type: string -api_key: - description: Your API key for Instapush. - required: string - type: string -app_secret: - description: The secret for your created application. - required: string - type: string -event: - description: The event to push to. - required: string - type: string -tracker: - description: The name of tracker inside Instapush. - required: string - type: string -{% endconfiguration %} - -To retrieve the needed values for existing settings, log into your account at [https://instapush.im](https://instapush.im) and go to your **Dashboard**. Then click the **APPS** tab, choose an app, and check the **Basic Info** section. The *Application ID* is the `api_key` and `app_secret` is the *Application Secret*. - -Assuming that your setup looks look in the image below... - -

- -

- -...then your entry for the `configuration.yaml` file needs to be like this sample. - -```yaml -notify: - platform: instapush - [...] - event: msg - tracker: state -``` - -It's easy to test your Instapush setup outside of Home Assistant. Assuming you have an event *notification* and a tracker *home-assistant*, just fire a request and check the Instapush dashboard for a new entry. - -```bash -curl -X POST \ - -H "x-instapush-appid: YOUR_APP_KEY" \ - -H "x-instapush-appsecret: YOUR_APP_SECRET" \ - -H "Content-Type: application/json" \ - -d '{"event":"notification","trackers":{"home-assistant":"Switch 1"}}' \ - https://api.instapush.im/v1/post -``` - -For further details, please check the [API](https://instapush.im/developer/rest). - -To use notifications, please see the [getting started with automation page](/getting-started/automation/). diff --git a/source/images/supported_brands/instapush.png b/source/images/supported_brands/instapush.png deleted file mode 100644 index c68becbb531f0603ebfaad1155f4a1ca2210b7f4..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 6389 zcmV004R>004l5008;`004mK004C`008P>0026e000+ooVrmw00006 zVoOIv0RI600RN!9r;`8x00(qQO+^Rd1q%l&8*$@0SO5SQ`AI}URCwC$oq2d%b-Bks zzjJ0LnaSEFO`3E`m$b-MsFbZxpkP5ND&pn(h`2qX_o5dHUX(>d6lK$U6;WKS%DsSy zf{0fIgd()E6r_~Wma=rCZPGMN(yTL??fmW^@9$(zCNq%pGZKEZdeCs4$pjU{*7KJ@oncm0xhU!NZ+1^N#5+yLIG zxj5@@O`Z3RdcJkA7f{6i3)BHMxIDAfHKHzRSpt-z-%+uf=();h<(M!Q0o2l zXDqt2YyImVN9*&IQmcSR4&)?qSqtEOzz=}efy;rN*^c*GmZE?ZF&+p4OYMOFg!=i% zggVx}9!f-`mno%Q)UXT7qH*%%j3@4=7^Tv@_jxVUjxT@zE7HW z3sC0oQs4^Uao}d4DxFx-f)ue&h?JI47LI7gvOsIJ&qwIU_b`1*gTHUX8_NPOzcM%4 zKM*0slrH*#XMv}IFl3Kc3bZos1wI6n05!lB7U~sXf`%;$9S4<2qJs*)3|s@00~Nr} zfF3WgqJR{!PlyNn*nI)dpFoC`j5sr4? zc3^Wlv7&$!u}@HrlM;?(lJ1w+(6?zTRYx2~<@|Y6%{!8=jc+p0z6UIeN_>g)lT*S9 zc*JTg?@{r~6ub&NY)F0(_yn*9_z7tmJr8UJmH}9(qkO2JFA1!)H>-gYY}C;j-K*i5 zJLB^=oaWU2EP?(E@O9w70VkbUQ9z2=CnS{(3Y29L@93oM#nlY<^b+msqkQ&Etcr3< ztE(7j-$N3u7boi?mnWKo3h4F42OhFps(q--fleeQ_!bg7oCmB09?La;mQ2(p;PXN3 zNhg#%6^oF(%a1zSQOaj&u;9{V{x#pdCw{_D<~h|b4w8J#Mmgy;n>z0k0lE5`>oN|0 z+pRYr?ENodjF@xs2Xp@Z_6vU+mvL$iYsUHGU&1stXge5GWp$HCM5Bc2>rka7kVuk< z#@xeIr;1s7RXnMH4i$5gM5iGZM3D-V+kx%^rc#PzsBA!$VD;7pf3tD2Q*(y}OXsPH zoT}>Rv|>E&wAA$I=vO}Jf9d7+$fy6h!)lqP##QwGSu? z?><2x!DlIQJspGr#^T#&MEQ#6c;oq(!jl#))c&cBG%j62ZD$uHb+uTb5QCex5Z|0rOcp8>uK1OPjUesWQ=>DzCrzEjGr z0GB3bb5g9DK}!=ZN$>}~y+)x<-E8gL5kTDwOf|ID0-pnR!Egat2K+1VSEP^;eav{pIA zuDw)EpGu&tjA&mUJ==E@?du;B4i`BD!-a$KVDe1yI>1knVqdLU_l7F%Z?lwowcm*y ze!sPy&e8_jttij32O95Q357AU2L-UoYniL71k{(`d9(C-D}O`xs7bKU{IJ@i3^dBy6+Lj75zKm53E4J}u@ zakN8HJ8=tjPXM*Ny#80cox4AGU7R@44BK<4WwA8xP5~|g5fWwF`$}df@FSojpMx`X z-K(Q?Pkch259j+XJsh4gGtA=#r`$L4!nuDRsGfy#1ag%l3MTI)4RslCS3>;N7D zR^&^@+ivf|E-7K{jklmI>vZ5k^Yx=j+DdvUpcOwK3u2S<&%#Jgiyw&xCL=y=6fue0 zfw;@0S(w(3_{4RFZUV`HzXSBA9UC;qmzj5kWZTNj+@qKVv$XR9z;rW4DdJl6nmM+* z$EOLh-;C$_1Ysa(n>o6)Vx%g?=|~@U!0bsn6DuT;tV5dd zY(uxh%q5(sAi0XB!mO*teAjE}bhu-WyO3y&)*5A5SUw*rSo(*mxy?7ly7ung_57-+ z4=WaIs83?tvRv^;nqUOXda8ilKy_8$KwEohSwsD$N~s!PH}GSi#d}gd@l8GgG6N~z z_mVc3o(_BpI1Uk#a)cRLkZS5LkStmpNfaytmLSYA z&(OFQxWxSaTXT+k(QV*t;FCyC&U7*%O8Mvjf1T zh?$;d#vef3fESVK>$5;IjX9f;)@qmW|70#urmV~I z)D_lNU<0Cg|444_sLlG$HtSk|C^^jjY&3iN0MI?2LZY?C7YI<yucP57&;@YPK^ z(N|UZBee6zj89y6pIsVUog5edrBKl*tyg_*1f6qky@}}DCfL!2*@yECk4#5|y=$gBVv)+nWZ3p@{ncMsR3xV0i_ioo4~3A}z(onq$^` zXxIo--v~@Xg0TNZ8rEveh5E3eaV^61AUC+2XvPR4%re)EXSs_`8{^wZCSxP;Ai_j8 zaHJV$ftmjmhACXs1Lu&+;B7;g_wcm+s4(9hjxgGdz}*aI{t9!^O3mjjkTrGFV8(Uv zqqN^IMif+2hI2zevw59u_UZ;;Z;tDIk)fI18CY*#Cz<{I1`rt!A<6lg~`>twPScppykf<%A+uasro8SmQL-nu-qmvz_G*Ym0CuEO6ic@A3N2z&(L zjnsIKb6VYr$0thyCHC%@*Srz!?foxh+p)1E4Dt~Wja>X1;A%ueeFkX=>o>nw0v|^- z@Cm?Wh?R*O8uQI>)xe#=e;{s30_nP(foRcBnD>7m7Uk#zK{eiGfB=A>P(t71J1N6Ys zAkc;Qz;Q$q{}}kbIra=vrW^Bl3SxD>V=i#SoZF9Bo2!9Ui1uM#|^R7U6IgrZw@l-6SJ}1nO#0p^ylUX#UEQ`bk#>%0lOA$9V?1Uj4vC z%eIdzt*lrasGHP;&mOWwN-2`v-Ng6y;IFR2uC7X@JRL_Nw*=o0yj18K@)ZzeCiw)$ zZSpdohsk%Fi&jp`{{|77Bodr2MS@8OMg;QrAVOAXzfb~Ul>33dyI*EW`PPwYOv{B0 zNWcoDvQ#E`-h|x8FdxZQ*}y_G|G_+H=L0vf;JpTy0(%e(7B=hdK?Jtcb6&PUJ%U)! z-5J*OCSsANjA5?HY(JDwoq`GmhXh0cy=&I7>$z1VqEV`6OsC1AHYDC*ZG{n4+f?(H$+cJn=Uoom~VcPN4DZ#gsNpLpwv>YMr@O z`&B@~q%1-Nf-fp*;%tqJ4c>mPOa5EmSqnqWrzbNPMC-l!fqx zLPUG}K&heD7_Bv>73CQi^#rFhqEjxF1spM!g%#?Q zX~@}0n4U5oUfB(Inp(Wv(!~C38r{NU(nz zJT-71;-Y>Ei4i6tmdZtqdCfO#zaEK?vbjBDYK|HOJCQw}mh&jBu|gpxop2n<=UyNl zi85hU6J@h!4ly@ML4QAq{_qGUS4t7-?L)`oP*NhoVp&wppGTy#i}0RKLbVf_Fn^v{ zkCZSa$!Ibia6Xq*U|o;YfwnUaDcSU zeM>IF9t(38k{aF#d;xK-vYFI;HT^LR&!hpv+CQrB+<#!k&X(~RF{X!3W0pC&Hxc>G z=RqVnunCE`f{3MDWcF*mIj$Z_-!A9CHg^6IsU6K9?LZA!)m2zZq4n_8uhZQ_=eiB( zq%)#TUMWR99A@vj4b(SI7WYjv6u0=x%ZA!n((ng_&kDwY5RmCe#-{>tvEGIeXi|zK`)a`pIuI754XI5m zKrF~g%q^c8gv4z+Ye!s(bOaIY=!Jv$+#p*27^GsKPQMNbV4F!b?b#rTC&NA~q&i=N z^ha$#1aJYO$q(}!y9#k>Tiis{kI)d*&;+$sWCjXUhKXl!SxfkA?zRR1C_+SyD!Mn`d zYDopfAW4B+@H`0vi5Gs4w5U`f!nPPGly)0BZu|T;#HGxXo_!FpGH095%}4@bj~T;# zdZ0JG{3s)9Li-gSHw*I3k||KiVsPs=T9>b2pnVU8w1PN^1RbxerEF#snAjr?{m8W* zt#+3aUIDSv-n|R9$*=m1=UDGXy@vEFeG^Gl9*?A5`^_AtAsVm)X|%hY;Q?<13AD~c zm~IK8A-|8LY}X-eAvYoE<9iXS5+%XhE#Z4M?4+-0W?pT26;q+ieW5 zNqDbku4|~$ejls*otJ>9q{G05*J=6t^F(`k3lWY!pi5cSl>S|9zTWj4sXl2zrWE4S zNDT}an|lSr1>^}tD{Wx7|JsH~qL0z5wFx9WJBi^%G>sGmHv%6(3SBc0#_K~|6!#%v ztMIh5c-*9i5G}qCi4O)C-tK-6;<|klakHi)!m$&{usn>oCLosMNrZ9NT=JzWekJML4>IuGv~Uk5$;?a zglS(w+T&d}D27-nZ$@W3BFF$7b=pT@q~=rRoRvu1Nja&SMU+&lKajOD?KV$7W9Hfnbw6^`)uV<^0MYgdGna6d^Ad=g<_(;)?eQMuHU#fH@=6n@J#>0# zpS9zFGlE1PaBm_WzqNDA){e@C$tp(-;e}h6b?1MVvaBP+U3<&+u6d2x#iyYq^QFz2 zpU#KqXh?smNw%35QUn`8C&R6`VRAfoE4>ji?OaXney0S(|6hm^w9}IVvBap^P$w77 zbm2&|Bp`yE?HRLK_dNrhB%|C!~SSHIOJfM=>jC~ za0A}2U@Yf;e}KUu3XgEqAu;BKTI(sL73G13Q%|OB&TLe$G}WvqG16y&aOH_7(zkjw zPkiaig^UA|aJe2hRcl>S(b(Xdyy#>~rcD8#4@5z(L#*Kg7>hPmH|yQ@fVd(KJp_ Date: Thu, 6 Dec 2018 11:52:25 +0100 Subject: [PATCH 003/132] Update source/_components/homematic.markdown Co-Authored-By: danielperna84 --- source/_components/homematic.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/homematic.markdown b/source/_components/homematic.markdown index 77a06faab93..b79561a3563 100644 --- a/source/_components/homematic.markdown +++ b/source/_components/homematic.markdown @@ -61,7 +61,7 @@ host: required: true type: string port: - description: Port of CCU/Homegear XML-RPC Server. Wireless: 2001, wired: 2000, IP: 2010, thermostatgroups: 9292. With enabled SSL on the CCU3 usually a 4 is prepended to the Port. E.g. 2001 becomes 42001 with enabled SSL. + description: "Port of CCU/Homegear XML-RPC Server. Wireless: 2001, wired: 2000, IP: 2010, thermostatgroups: 9292. With enabled SSL on the CCU3 usually a 4 is prepended to the Port. e.g., 2001 becomes 42001 with enabled SSL." required: false type: integer ssl: From ad00767bf62df3ab1d9c4a6f46ae88f8396b3d67 Mon Sep 17 00:00:00 2001 From: Klaas Schoute Date: Thu, 6 Dec 2018 11:52:40 +0100 Subject: [PATCH 004/132] Update source/_components/homematic.markdown Co-Authored-By: danielperna84 --- source/_components/homematic.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/homematic.markdown b/source/_components/homematic.markdown index b79561a3563..11c575af68d 100644 --- a/source/_components/homematic.markdown +++ b/source/_components/homematic.markdown @@ -67,7 +67,7 @@ port: ssl: description: Set to `true` if SSL support is enabled on the CCU3. required: false - type: bool + type: boolean verify_ssl: description: Set to `true` if a valid certificate is being used. The default is `false` as usually a self-signed certificate is configured. required: false From 790aa4acb62adc8ea3d11096a77be2a8a0375b0d Mon Sep 17 00:00:00 2001 From: Klaas Schoute Date: Thu, 6 Dec 2018 11:52:57 +0100 Subject: [PATCH 005/132] Update source/_components/homematic.markdown Co-Authored-By: danielperna84 --- source/_components/homematic.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/homematic.markdown b/source/_components/homematic.markdown index 11c575af68d..07ac39c17bd 100644 --- a/source/_components/homematic.markdown +++ b/source/_components/homematic.markdown @@ -71,7 +71,7 @@ ssl: verify_ssl: description: Set to `true` if a valid certificate is being used. The default is `false` as usually a self-signed certificate is configured. required: false - type: bool + type: boolean callback_ip: description: Set this, if Home Assistant is reachable under a different IP from the CCU (NAT, Docker etc.). required: false From 3c1bbb0a7291b6e0eed29cc6e99af9881aae8765 Mon Sep 17 00:00:00 2001 From: Klaas Schoute Date: Thu, 6 Dec 2018 11:53:10 +0100 Subject: [PATCH 006/132] Update source/_components/homematic.markdown Co-Authored-By: danielperna84 --- source/_components/homematic.markdown | 1 + 1 file changed, 1 insertion(+) diff --git a/source/_components/homematic.markdown b/source/_components/homematic.markdown index 07ac39c17bd..3f9f186d405 100644 --- a/source/_components/homematic.markdown +++ b/source/_components/homematic.markdown @@ -65,6 +65,7 @@ port: required: false type: integer ssl: + default: false description: Set to `true` if SSL support is enabled on the CCU3. required: false type: boolean From 011200e28e5d94bae796414666f078ad49f6d7a2 Mon Sep 17 00:00:00 2001 From: Klaas Schoute Date: Thu, 6 Dec 2018 11:53:28 +0100 Subject: [PATCH 007/132] Update source/_components/homematic.markdown Co-Authored-By: danielperna84 --- source/_components/homematic.markdown | 1 + 1 file changed, 1 insertion(+) diff --git a/source/_components/homematic.markdown b/source/_components/homematic.markdown index 3f9f186d405..dede62718a4 100644 --- a/source/_components/homematic.markdown +++ b/source/_components/homematic.markdown @@ -70,6 +70,7 @@ ssl: required: false type: boolean verify_ssl: + default: false description: Set to `true` if a valid certificate is being used. The default is `false` as usually a self-signed certificate is configured. required: false type: boolean From 5284931c8cbc56e4eff0c236023cf296e40b54b4 Mon Sep 17 00:00:00 2001 From: Sean Dague Date: Thu, 6 Dec 2018 07:12:59 -0500 Subject: [PATCH 008/132] drop unit parameter from waterfurnace docs (#7744) The unit parameter will no longer be required in the next version of home assistant, which makes it easier for people to use it. --- source/_components/waterfurnace.markdown | 5 ----- 1 file changed, 5 deletions(-) diff --git a/source/_components/waterfurnace.markdown b/source/_components/waterfurnace.markdown index e9288edfb95..4798cd81ec7 100644 --- a/source/_components/waterfurnace.markdown +++ b/source/_components/waterfurnace.markdown @@ -42,7 +42,6 @@ To use Waterfurnace in your installation, add the following to your `configurati waterfurnace: username: YOUR_USERNAME password: YOUR_PASSWORD - unit: 0123456789AB ``` {% configuration %} @@ -54,10 +53,6 @@ password: description: The password for your Symphony WaterFurnace account required: true type: string -unit: - description: The unit serial number for your WaterFurnace - required: true - type: string {% endconfiguration %} #### {% linkable_title Limitations %} From 8ac4f35d7d796f80c2a782f9a6b1f39c928120f9 Mon Sep 17 00:00:00 2001 From: Sean Dague Date: Thu, 6 Dec 2018 07:16:38 -0500 Subject: [PATCH 009/132] update mychevy component docs (#7745) The mychevy component finally is working again due to someone finally fixing their website to be more reliable. This component no longer uses selenium web scraping, which makes it more useful to others. Hopefully their website is more reliable this time around! --- source/_components/mychevy.markdown | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-) diff --git a/source/_components/mychevy.markdown b/source/_components/mychevy.markdown index a737ba764a4..e291ef373cc 100644 --- a/source/_components/mychevy.markdown +++ b/source/_components/mychevy.markdown @@ -13,7 +13,12 @@ ha_release: 0.62 ha_iot_class: "Cloud Polling" --- -The `mychevy` component communicates with the [my.chevrolet](https://my.chevrolet.com) website using selenium to log in as your user and screen scrape the data provided. GM does not make it easy to sign up for any official development program, so this provides a workaround to get access to your data. +The `mychevy` component communicates with +the [my.chevrolet](https://my.chevrolet.com) website using the +javascript API that the website uses (as of Dec 2018). The mychevy +website has been known to be both unstable (interfaces changing +somewhat willy nilly) and have substantial outages. So be forwarned in +using this component. This component provides the following platforms: @@ -43,17 +48,13 @@ password: {% endconfiguration %} -### {% linkable_title Installation %} - -Because this uses selenium behind the scenes, installation is more complicated than merely `pip` install. See the [installation instructions](https://github.com/sdague/mychevy). - ### {% linkable_title Limitations %} The architecture of the GM automotive networking imposes some limitations on the functionality of the component. The OnStar network link is very slow, and takes 1 - 3 minutes to get information back from the car. As such the mychevy component only polls every 30 minutes to not overwhelms that connection. -The OnStar network (or more specifically the gateway used by the my.chevrolet website) appears to suffer more than most networks when the car is a) in a garage, and b) it's cold outside (like < 15 degrees F). One of the provided sensors is a status sensor which indicates if we got connectivity with the car on the last polling cycle or not. - -The "API" for this is written by web scraping. As such, it only currently is known to work if you have a Chevy Bolt EV, and only 1 Chevy car connected to OnStar. Patches for extended support should go to the https://github.com/sdague/mychevy project first, then Home Assistant can be extended. +The OnStar network (or more specifically the gateway used by the my.chevrolet website) appears to suffer more than most networks when the car is a) in a garage, and b) it's cold outside (like < 15 degrees F). One of the provided sensors is a status sensor which indicates if we got connectivity with the car on the last polling cycle or not. +The "API" for this is written through using some existing API calls +from the javascript web ui. As such, it only currently is known to work if you have a Chevy Bolt EV, and only 1 Chevy car connected to OnStar. Patches for extended support should go to the https://github.com/sdague/mychevy project first, then Home Assistant can be extended. From ef275a98407ac2fbbc7aea383851d07065f54831 Mon Sep 17 00:00:00 2001 From: Sean Wilson Date: Thu, 6 Dec 2018 07:25:37 -0500 Subject: [PATCH 010/132] Add CM17A support (#7743) * Added docs for AquaLogic component. * Update AquaLogic docs as per review. * Update as per review. * Add CM17A support. --- source/_components/light.x10.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/light.x10.markdown b/source/_components/light.x10.markdown index 6b89fd85c29..caa789f5632 100644 --- a/source/_components/light.x10.markdown +++ b/source/_components/light.x10.markdown @@ -15,7 +15,7 @@ ha_release: 0.25 The `x10` light platform allows you to control your X10 based lights with Home Assistant. -Requires [Heyu x10](http://www.heyu.org) and a CM11A interface; the CM17A "FireCracker" interface is not supported. +Requires [Heyu x10](http://www.heyu.org) and a CM11A or a CM17A "FireCracker" interface. To enable those lights, add the following lines to your `configuration.yaml` file: From dcc2087531bfd7e2048eec2abc0c48431e0f4226 Mon Sep 17 00:00:00 2001 From: Gamester17 Date: Thu, 6 Dec 2018 13:27:28 +0100 Subject: [PATCH 011/132] =?UTF-8?q?IKEA=20Tr=C3=A5dfri=20Gateway=20compone?= =?UTF-8?q?nt=20-=20Description=20and=20configuration=20nitpicking=20(#773?= =?UTF-8?q?9)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Fixing product name (which is "IKEA Trådfri Gateway"), spelling and grammar, as well as clarifying description and configuration instructions. https://www.ikea.com/us/en/catalog/products/00337813/ https://www.ikea.com/gb/en/customer-service/smart-lighting-support/faq-smart-lighting/compatibility-protocols/#1364355349185 --- source/_components/tradfri.markdown | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/source/_components/tradfri.markdown b/source/_components/tradfri.markdown index 35b277fd191..a642a1959a9 100644 --- a/source/_components/tradfri.markdown +++ b/source/_components/tradfri.markdown @@ -1,7 +1,7 @@ --- layout: page title: "IKEA Trådfri (Tradfri)" -description: "Access and control your Zigbee-based IKEA Trådfri (Tradfri) devices." +description: "Access and control your IKEA Trådfri Gateway (a.k.a. IKEA Tradfri hub/bridge) and via it its connected Zigbee-based devices." date: 2017-04-12 22.04 sidebar: true featured: true @@ -14,12 +14,12 @@ ha_iot_class: "Local Polling" ha_release: 0.43 --- -The `tradfri` component supports for the IKEA Trådfri (Tradfri) gateway. The gateway can control lights connected to it and Home Assistant will automatically discover its presence on your network, if `discovery:` is present in your `configuration.yaml` file. +The `tradfri` component support the IKEA Trådfri Gateway (a.k.a. IKEA Tradfri hub/bridge). The gateway can control compatible Zigbee-based lights (certified ZigBee Light Link products) connected to it and Home Assistant will automatically discover the gateways presence on your local network, if `discovery:` is present in your `configuration.yaml` file. -You will be prompted to configure the gateway through the Home Assistant interface. Enter the security key when prompted and click configure. +You will be prompted to configure the gateway through the Home Assistant interface. The configuration process is very simple, when prompted, enter the security key printed on the physical sticker that is on the bottom of the IKEA Trådfri Gateway, then click configure.

-If you see an "Unable to connect" message, restart the gateway and try again. Don't forget to assign a permanent IP to your Trådfri gateway. +If you see an "Unable to connect" message, restart the gateway and try again. Don't forget to assign a permanent IP to your IKEA Trådfri Gateway in your router / DHCP-server.

## {% linkable_title Configuration %} @@ -34,11 +34,11 @@ tradfri: {% configuration %} host: - description: "The IP address or hostname of your Trådfri gateway." + description: "The IP address or hostname of your IKEA Trådfri Gateway." required: true type: string allow_tradfri_groups: - description: "Set this to `true` to allow Home Assistant to import the groups defined on the Trådfri bridge." + description: "Set this to `true` to allow Home Assistant to import the groups defined on the IKEA Trådfri Gateway." required: false type: boolean default: false @@ -48,7 +48,7 @@ allow_tradfri_groups: ### {% linkable_title Firmware updates %} -After updating the firmware of your Trådfri gateway it might be necessary to repeat the configuration process. If you encounter problems, delete the `.tradfri_psk.conf` file in your `.homeassistant` directory, restart Home Assistant, when prompted enter the security key and click configure, just like during initial setup. Possible errors: `Fatal DTLS error: code 115`. +After updating the firmware of your IKEA Trådfri Gateway it might be necessary to repeat the configuration process. If you encounter problems, delete the `.tradfri_psk.conf` file in your `.homeassistant` directory, restart Home Assistant, when prompted enter the security key and click configure, just like during initial setup. Possible errors: `Fatal DTLS error: code 115`. ### {% linkable_title Compilation issues %} From a10f79666557abeaf5d6410372c2e027bbd38084 Mon Sep 17 00:00:00 2001 From: Gamester17 Date: Thu, 6 Dec 2018 13:46:43 +0100 Subject: [PATCH 012/132] =?UTF-8?q?Update=20zha.markdown=20to=20clearify?= =?UTF-8?q?=20use=20of=20zigpy=20and=20support=20for=20multiple=E2=80=A6?= =?UTF-8?q?=20(#7738)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * Update zha.markdown to clearify use of zigpy and support for multiple radios Update zha.markdown to clarify the use of the zigpy library and support for multiple Zigbee radios from different manufacturers. Also tried to separate radio modules from actual retail products which use those radios under "Known working Zigbee radio modules". Please note that I mostly wanted to add this clarification in the hope that new developers will be made aware and join in improving these existing libraries or maybe even creating new radio module libraries for adding support for additional radios from different manufacturers. One example here is https://github.com/Equidamoid/pyconz/ which begun after he seen discussion in https://github.com/dresden-elektronik/deconz-rest-plugin/issues/158 * Fix list --- source/_components/zha.markdown | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/source/_components/zha.markdown b/source/_components/zha.markdown index 2bc206d73d5..ca12e9807da 100644 --- a/source/_components/zha.markdown +++ b/source/_components/zha.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Zigbee Home Automation" -description: "Instructions on how to integrate your Zigbee Home Automation within Home Assistant." +description: "Instructions on how to integrate your Zigbee Home Automation (ZHA) devices within Home Assistant." date: 2017-02-22 19:59 sidebar: true comments: false @@ -14,7 +14,7 @@ ha_iot_class: "Local Polling" --- [Zigbee Home Automation](http://www.zigbee.org/zigbee-for-developers/applicationstandards/zigbeehomeautomation/) -integration for Home Assistant allows you to connect many off-the-shelf Zigbee devices to Home Assistant, using a compatible Zigbee radio. +integration for Home Assistant allows you to connect many off-the-shelf Zigbee based devices to Home Assistant, using one of the available Zigbee radio modules compatible with [zigpy](https://github.com/zigpy/zigpy) (an open source Python library implementing a Zigbee stack, which in turn relies on seperate libraries which can each interface a with Zigbee radio module a different manufacturer). There is currently support for the following device types within Home Assistant: @@ -24,12 +24,14 @@ There is currently support for the following device types within Home Assistant: - [Switch](../switch.zha) - [Fan](../fan.zha) -Known working Zigbee radios: +Known working Zigbee radio modules: -- Nortek/GoControl Z-Wave & Zigbee USB Adapter - Model HUSBZB-1 -- XBee Series 2C -- [Elelabs Zigbee USB Adapter](https://elelabs.com/products/elelabs_usb_adapter.html) -- [Elelabs Zigbee Raspberry Pi Shield](https://elelabs.com/products/elelabs_zigbee_shield.html) +- EmberZNet based radios using the EZSP protocol (via the [bellows](https://github.com/zigpy/bellows) library for zigpy) + - [Nortek GoControl QuickStick Combo Model HUSBZB-1 (Z-Wave & Zigbee USB Adapter)](https://www.nortekcontrol.com/products/2gig/husbzb-1-gocontrol-quickstick-combo/) + - [Elelabs Zigbee USB Adapter](https://elelabs.com/products/elelabs_usb_adapter.html) + - [Elelabs Zigbee Raspberry Pi Shield](https://elelabs.com/products/elelabs_zigbee_shield.html) +- XBee Zigbee based radios (via the [zigpy-xbee](https://github.com/zigpy/zigpy-xbee) library for zigpy) + Digi XBee Series 2C (S2C) modules ## {% linkable_title Configuration %} From 8ecd8ba7be98b86eec9076d3ddb6d39d90d8eb76 Mon Sep 17 00:00:00 2001 From: Hedda Date: Fri, 7 Dec 2018 09:27:36 +0100 Subject: [PATCH 013/132] zha.markdown fix list of radio modules (#7763) fix list of known working Zigbee radio modules - EmberZNet based radios using the EZSP protocol (via the [bellows](https://github.com/zigpy/bellows) library for zigpy) - [Nortek GoControl QuickStick Combo Model HUSBZB-1 (Z-Wave & Zigbee USB Adapter)](https://www.nortekcontrol.com/products/2gig/husbzb-1-gocontrol-quickstick-combo/) - [Elelabs Zigbee USB Adapter](https://elelabs.com/products/elelabs_usb_adapter.html) - [Elelabs Zigbee Raspberry Pi Shield](https://elelabs.com/products/elelabs_zigbee_shield.html) - XBee Zigbee based radios (via the [zigpy-xbee](https://github.com/zigpy/zigpy-xbee) library for zigpy) - Digi XBee Series 2C (S2C) modules --- source/_components/zha.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/zha.markdown b/source/_components/zha.markdown index ca12e9807da..00f679095df 100644 --- a/source/_components/zha.markdown +++ b/source/_components/zha.markdown @@ -31,7 +31,7 @@ Known working Zigbee radio modules: - [Elelabs Zigbee USB Adapter](https://elelabs.com/products/elelabs_usb_adapter.html) - [Elelabs Zigbee Raspberry Pi Shield](https://elelabs.com/products/elelabs_zigbee_shield.html) - XBee Zigbee based radios (via the [zigpy-xbee](https://github.com/zigpy/zigpy-xbee) library for zigpy) - Digi XBee Series 2C (S2C) modules + - Digi XBee Series 2C (S2C) modules ## {% linkable_title Configuration %} From fe3c33a617d6a01637682530b19185f3aec7a161 Mon Sep 17 00:00:00 2001 From: Mike O'Driscoll Date: Fri, 7 Dec 2018 03:39:50 -0500 Subject: [PATCH 014/132] Update notify.html5 example (#7758) Update the html5 notification example as the service "notify.html5" does not exist, but "notify.notify" does. --- source/_components/notify.html5.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/notify.html5.markdown b/source/_components/notify.html5.markdown index 57b63f0d32d..c92a16c46f3 100644 --- a/source/_components/notify.html5.markdown +++ b/source/_components/notify.html5.markdown @@ -166,7 +166,7 @@ if there already exists one with the same tag. - platform: state entity_id: sensor.sensor action: - service: notify.html5 + service: notify.notify data_template: message: "Last known sensor state is {% raw %}{{ states('sensor.sensor') }}{% endraw %}." data: From 51dced1f4b696f896add844084b48a4a7b90c922 Mon Sep 17 00:00:00 2001 From: heymoe <1672877+heymoe@users.noreply.github.com> Date: Fri, 7 Dec 2018 04:29:00 -0500 Subject: [PATCH 015/132] Corrected option name and added to the example (#7754) * Update for sensor.tautulli I found that monitored_variables did not work in the config but monitored_conditions did so I fixed that in the docs as well as add examples for monitored_conditions and monitored_users. * Update sensor.tautulli.markdown Fix for standards * Keep the configuration sample minimized --- source/_components/sensor.tautulli.markdown | 20 ++++++++++++++++++-- 1 file changed, 18 insertions(+), 2 deletions(-) diff --git a/source/_components/sensor.tautulli.markdown b/source/_components/sensor.tautulli.markdown index 3bb5741e4a4..df0bc1c0414 100644 --- a/source/_components/sensor.tautulli.markdown +++ b/source/_components/sensor.tautulli.markdown @@ -26,7 +26,7 @@ The `Tautulli` sensor platform will monitor activity on a given [Tautulli Server - Transcode count - WAN bandwidth -More user statistics can be added with the `monitored_variables` configuration option, this will add one attribute per user in addition to the users current `activity`. +More user statistics can be added with the `monitored_conditions` configuration option, this will add one attribute per user in addition to the users current `activity`. To find your `api_key` open the Tautulli web interface and navigate to `Settings` and then to `Web interface`, the `api_key` will be at the bottom of that page. @@ -63,11 +63,27 @@ monitored_users: description: A list of Tautulli users you want to monitor, if not set this will monitor **all** users. required: false type: list -monitored_variables: +monitored_conditions: description: A list of attributes to expose for each Tautulli user you monitor, every key in the `session` [section here][tautulliapi] can be used. required: false type: list {% endconfiguration %} +## {% linkable_title Full example for the configuration %} + +```yaml +# Example configuration.yaml entry +sensor: + - platform: tautulli + api_key: TAUTULLI_API_KEY + host: TAUTULLI_HOST + monitored_users: + - USER_1 + - USER_2 + monitored_conditions: + - ATTRIBUTE_1 + - ATTRIBUTE_2 +``` + [tautulli]: https://tautulli.com [tautulliapi]: https://github.com/Tautulli/Tautulli/blob/master/API.md#get_activity From 420e5dee5effcc32f178a62678daf59070f96bcd Mon Sep 17 00:00:00 2001 From: emontnemery Date: Fri, 7 Dec 2018 11:08:33 +0100 Subject: [PATCH 016/132] Update binary_sensor.mqtt.markdown (#7761) --- source/_components/binary_sensor.mqtt.markdown | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/source/_components/binary_sensor.mqtt.markdown b/source/_components/binary_sensor.mqtt.markdown index 132c59298e0..cc42186d29c 100644 --- a/source/_components/binary_sensor.mqtt.markdown +++ b/source/_components/binary_sensor.mqtt.markdown @@ -85,6 +85,10 @@ payload_not_available: required: false type: string default: offline +json_attributes_topic: + description: The MQTT topic subscribed to receive a JSON dictionary payload and then set as sensor attributes. + reqired: false + type: string qos: description: The maximum QoS level to be used when receiving messages. required: false From 436486ddc5933c460f4b6288e43b4e8a68324872 Mon Sep 17 00:00:00 2001 From: Sebastian Muszynski Date: Fri, 7 Dec 2018 23:40:43 +0100 Subject: [PATCH 017/132] Support next generation of the Xiaomi Mi Smart Plug (chuangmi.plug.hmi205) (#7760) --- source/_components/switch.xiaomi_miio.markdown | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/source/_components/switch.xiaomi_miio.markdown b/source/_components/switch.xiaomi_miio.markdown index 11596d6c241..efe0e9c89fd 100644 --- a/source/_components/switch.xiaomi_miio.markdown +++ b/source/_components/switch.xiaomi_miio.markdown @@ -21,12 +21,16 @@ Please follow the instructions on [Retrieving the Access Token](/components/vacu ### Xiaomi Smart WiFi Socket +Supported models: `chuangmi.plug.m1`, `chuangmi.plug.v2`, `chuangmi.plug.hmi205` + * Power (on, off) * Attributes - Temperature ### Xiaomi Chuangmi Plug V1 +Supported models: `chuangmi.plug.v1`, `chuangmi.plug.v3` + * Power (on, off) * USB (on, off) * Attributes @@ -34,6 +38,8 @@ Please follow the instructions on [Retrieving the Access Token](/components/vacu ### Xiaomi Smart Power Strip +Supported models: `qmi.powerstrip.v1`, `zimi.powerstrip.v2` + * Power (on, off) * Wifi LED (on, off) * Power Price (0...999) @@ -72,7 +78,7 @@ name: type: string default: Xiaomi Miio Switch model: - description: The model of your miio device. Valid values are `chuangmi.plug.v1`, `qmi.powerstrip.v1`, `zimi.powerstrip.v2`, `chuangmi.plug.m1` and `chuangmi.plug.v2`. This setting can be used to bypass the device model detection and is recommended if your device isn't always available. + description: The model of your miio device. Valid values are `chuangmi.plug.v1`, `qmi.powerstrip.v1`, `zimi.powerstrip.v2`, `chuangmi.plug.m1`, `chuangmi.plug.v2`, `chuangmi.plug.v3` and `chuangmi.plug.hmi205`. This setting can be used to bypass the device model detection and is recommended if your device isn't always available. required: false type: string {% endconfiguration %} From 297f450a511521f83a2a18c32cfd8369c4508d1a Mon Sep 17 00:00:00 2001 From: Sebastian Muszynski Date: Sat, 8 Dec 2018 14:49:18 +0100 Subject: [PATCH 018/132] Add moonlight section (#7589) --- source/_components/light.xiaomi_miio.markdown | 24 +++++++++++++++++-- 1 file changed, 22 insertions(+), 2 deletions(-) diff --git a/source/_components/light.xiaomi_miio.markdown b/source/_components/light.xiaomi_miio.markdown index 523d6039dd1..a4e95c3d424 100644 --- a/source/_components/light.xiaomi_miio.markdown +++ b/source/_components/light.xiaomi_miio.markdown @@ -13,7 +13,7 @@ ha_iot_class: "Local Polling" ha_release: 0.53 --- -The `xiaomi_miio` platform allows you to control the state of your Xiaomi Philips LED Ball Lamp, Xiaomi Philips Zhirui LED Bulb E14 Candle Lamp, Xiaomi Philips Zhirui Downlight, Xiaomi Philips LED Ceiling Lamp, Xiaomi Philips Eyecare Lamp 2 and Philips Zhirui Desk Lamp. +The `xiaomi_miio` platform allows you to control the state of your Xiaomi Philips LED Ball Lamp, Xiaomi Philips Zhirui LED Bulb E14 Candle Lamp, Xiaomi Philips Zhirui Downlight, Xiaomi Philips LED Ceiling Lamp, Xiaomi Philips Eyecare Lamp 2, Xiaomi Philips Moonlight Bedside Lamp and Philips Zhirui Desk Lamp. ## Features @@ -81,6 +81,26 @@ Supported models: `philips.light.mono1` - scene - delayed_turn_off +### Philips Moonlight Bedside Lamp + +Supported models: `philips.light.moonlight` + +* Power (on, off) +* Brightness +* Color (not implemented) +* Color temperature (153...588 mireds) +* Scene (1, 2, 3, 4) +* Attributes + - model + - scene + - sleep_assistant + - sleep_off_time + - total_assistant_sleep_time + - brand_sleep + - brand + + + Please follow the instructions on [Retrieving the Access Token](/components/vacuum.xiaomi_miio/#retrieving-the-access-token) to get the API token to use in the `configuration.yaml` file. To add a Xiaomi Philips Light to your installation, add the following to your configuration.yaml file: @@ -110,7 +130,7 @@ name: type: string default: Xiaomi Philips Light model: - description: The model of your light. Valid values are `philips.light.sread1`, `philips.light.ceiling`, `philips.light.zyceiling`, `philips.light.bulb`, `philips.light.candle`, `philips.light.candle2`, `philips.light.mono1` and `philips.light.downlight`. This setting can be used to bypass the device model detection and is recommended if your device isn't always available. + description: The model of your light. Valid values are `philips.light.sread1`, `philips.light.ceiling`, `philips.light.zyceiling`, `philips.light.moonlight`, `philips.light.bulb`, `philips.light.candle`, `philips.light.candle2`, `philips.light.mono1` and `philips.light.downlight`. This setting can be used to bypass the device model detection and is recommended if your device isn't always available. required: false type: string {% endconfiguration %} From 21a1096320ec0f4c30817ba4c47577c1dd54ff64 Mon Sep 17 00:00:00 2001 From: pbalogh77 Date: Sat, 8 Dec 2018 18:25:14 +0100 Subject: [PATCH 019/132] Minor updates (#7775) Added mention of scenes and fixed reference to fibaro_id --- source/_components/fibaro.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_components/fibaro.markdown b/source/_components/fibaro.markdown index d7a69c04e73..13b999188b0 100644 --- a/source/_components/fibaro.markdown +++ b/source/_components/fibaro.markdown @@ -15,7 +15,7 @@ ha_iot_class: "Local Push" The [Fibaro](http://fibaro.com) hub is a controller mainly connecting to Z-Wave devices. -Switches, Lights (including Dimmers), Locks, Sensors, Binary sensors and Covers are supported - and will be automatically added when HA connects to your Fibaro controller. +Binary sensors, Covers, Lights (including Dimmers), Sensors, Scenes and Switches are supported - and will be automatically added when HA connects to your Fibaro controller. ## {% linkable_title Configuration %} @@ -53,4 +53,4 @@ plugins: ### {% linkable_title Using Z-Wave devices in automation %} -If you want to use a Z-Wave device from the Fibaro controller in Home Assistant automation, you'll need the entity id. In the Home Assistant UI you'll find all entities listed under the service developer tool icon icon of the Developer Tools section. Look for entities that contain 'Fibaro Device Id' in their attributes, and you'll find the entity id on the left. +If you want to use a Z-Wave device from the Fibaro controller in Home Assistant automation, you'll need the entity id. In the Home Assistant UI you'll find all entities listed under the service developer tool icon icon of the Developer Tools section. Look for entities that contain 'fibaro_id' in their attributes, and you'll find the entity id on the left. From 49ed6d72f9bc88d4f39dce14da08405dd9770ad0 Mon Sep 17 00:00:00 2001 From: Ludovico de Nittis Date: Sun, 9 Dec 2018 11:09:02 +0100 Subject: [PATCH 020/132] Add code optional parameter on iAlarm (#7776) --- source/_components/alarm_control_panel.ialarm.markdown | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/source/_components/alarm_control_panel.ialarm.markdown b/source/_components/alarm_control_panel.ialarm.markdown index 9f4442ab3cb..ae3841f08a4 100644 --- a/source/_components/alarm_control_panel.ialarm.markdown +++ b/source/_components/alarm_control_panel.ialarm.markdown @@ -46,6 +46,10 @@ name: description: Name of device in Home Assistant. required: false type: string +code: + description: Specifies a code to enable or disable the alarm in the frontend. + required: false + type: integer {% endconfiguration %} This platform has also been confirmed to work with the alarm system brands Meian and Emooluxr. From 4feb18fa5edf40a13856dd56edc736358ee49b58 Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Mon, 10 Dec 2018 11:36:13 +0100 Subject: [PATCH 021/132] Update Lovelace docs (#7791) --- .../_includes/asides/lovelace_navigation.html | 11 +- source/lovelace/how-it-works.markdown | 21 +++ source/lovelace/index.markdown | 166 +----------------- source/lovelace/tips.markdown | 46 +++-- source/lovelace/yaml-mode.markdown | 107 +++++++++++ 5 files changed, 162 insertions(+), 189 deletions(-) create mode 100644 source/lovelace/how-it-works.markdown create mode 100644 source/lovelace/yaml-mode.markdown diff --git a/source/_includes/asides/lovelace_navigation.html b/source/_includes/asides/lovelace_navigation.html index 589f838ee21..fd5b58c70ab 100644 --- a/source/_includes/asides/lovelace_navigation.html +++ b/source/_includes/asides/lovelace_navigation.html @@ -7,11 +7,20 @@ +
+

Advanced

+ +
+

Cards