d2?!9Rb$7Q)4qzLJk_{uXN7pJO{(9$U_fFKQti{_y>4Oyb3V9S$_Tx48b6{Jv5%ZeBn`1$^4
zM-C%2XVYU`94TR=%L(aj5mx)NkpKB+j_G
z4f)eFtaPR(YHC>xU2R>#<+?smo}M~Px}MmB_ZdhoHCv;6#O)38G8Pv^gs_H67W`se2KJ+8EJW97K^NRcj0@Q{0~M^QW@oTmWbSX(5JAopM3xo=_LFL4(^f_LzQWp
zNqOMYnwW69zmrUEX9)Om6P3}@Bx979Xk#!t>)`%w=%sdwh+5v~Z*JyRDy7;YcG`)G
z4__JOEcN$54NZO>Mr&M?yNQ&H5HzcN?!aYjF;>LzIICWa?8@>Vw1FP;na
zdS90_!P5osCzwLIjk6dN-M9U+ZcPQO!z&RHG37yQ-qBFaKA~)$u$ZW{9({Q|ZT~rM
zyUe7d+;neqD>9+%Wp!-cG$uw+aPU(9b2itni#&P++5tg!+3z!>jg9XV$C~W*i5bOL
zN=kAv0>7SfQ-%unc-2tnaa#2=eieCTyZ}n_d3N^s7ccN*GPRrTHtBMcWEoL0UHpOB
z@=xS}1IOjGxHyFAJ^GADq{sz(FgT)yh6++rg1X85#B&^s=zN{|p0T#JML9YA7*j$N
zAgrSJ)JInRIk4@ut&+csbU!>~XSUMe=Ldj9fdhwIdFg=`Z$)LLO_KEE06PcAtk(LE
zO4$!7*}|F&1#7EieYjf~`OYyjF8Old-t^tAkPPyD2m
z?dEN9=A2ux2iET^Z~8JW?(LT>I-)zrt-k1nYd=Zer#
zZlgcmi&j1iLISeD|!CC9e5u?9(BJ3Q!_p86p4qWx6@%;gmwdUr=#TQ{f95`>bJ
z_D6|h_gptvq4}EMV{I?bkbz;cu?f7q^ernZpaHfxkrUJ~XwD^f3-Wp=Bm^)jAO=K4bJu7VXgy1+*pU%k$BS8E3yWG46I><5
z4tsm`XK?{NWY=19lf;GQ=ko@AN>m{xR)hP5+3tZQaF9p_lnB~FX;^@}j-8Vt3-KbE
zM|oi2+=B<&4|7Wj3erlH9|r(Uc+<1U-cGi=%YV(tigQg?_=S#+l)5^2W+D?n9Z}FU
z_4W7bF|zoMOd@r{L8got4Xijp!Kwem;0#qVjKLM3eSF0D4~;_j2xp==)b&2x+B*CZD{FH+N)8}J;_c>
z(SuEUekU|`Vt)@a=*mFKNB4y404hS|tgTsAmAOA8pFJi$&QMjc(fbtfl5ib+QYC?OT*XaI99
zKgfo-2PzStg3}BS{AlTrsEzVC(&T>r
zxikLs%`fMsi_zdiAEoe>t+#Sfc64;E_n_lAt>=7xc^b@SpM-^A96&qH$I{T!>@Ofu
zVD*JriX9yxfFBeP!Qzs!^5_qha`7ex2X0>T(L=f9n0M+*57koa_9Npyl4Doj_=mco
z;MX9wTbl4gNoRMnG3Ojd3ttPsI{6G($G7N}(v#@PTcBl{&!RL(EFRcazqCDxBtCps
zw8X*f$yjr0;tl2xkSz;ihr|*vwL9aUBu87LN6zo+u6ARZ-a`O@9rHZ!7srwZ^(4pP
z;n9q%a}WN!z48ntW^pP>-_QLakHkM+qEQeDWbCbN%15*lk0(BkhmS#Q{ykNHSZRs*0oRET
zxc@z#>o(~x$xc4RB>n$;;ESs%hC=%!+GhzV75_P&D&ISwPp&ROLJt0a=i`r^=hg#4
zv+oITo3y{i{%h$^y(4+faln~g?9o~;V=>s^;_4nd0moWsB
zU=}}F@_)|fq`n|!ER{1>Fg$w0b%K$m&
zQm5-%BTP?OCPv=2yWtF~ctTy0*Q&Zj_JgadYROW3=||-TL9qPPY3R4KbU*E*_`K8%MgV_o4
z6i8c(#>NKVycp}lth2}hAYDpXx1tHpkbs~YZ=p&$uY-x0
z(x2kaF16_U0{g-Geo<6vkmYX
z#(AL%5e*?_W7GOqE`Vr8I~fIK=P7ntM6Tw9;0a3xsa;O$>OiYln`9so+GnhyE?-s|
z8hX49?(uV>AWLew@46p;!tn3iiq|&)qSr9PMh=1Cmkw;zxGDJj<7+J-Nhh#x13}Hq
zsS2bvu!gd!kQ|;F8|(JhEmp0)lx1O8{shJ{%Ds
z9P@zDN_pW0RQMfQS|FJcI;Q~eFHhnS-|6n?NtRCI3Ks3?rO3-qm+a3sphSL_SsNcg<}A&Mk9xs&5c_KhU|p)*3^uod5p)
z2RT`J!%YVt$pQ@>>Nu_X0~qGvrgdX>MbKyZ24#0TluPyP+8!Sfe
zZ`}g-6zI;3_Vk9v*Mvke(lS6xie{JwHvuRU(FC{;>k0fX?BVG%@023bqX{$AM&o6{
zpYljf*8T80@g9E5+R7U<5)uG!@v??ioG*-w-adtpM{rCOR|gq$Bz{Em3E2}a%SXuu
z$(8;a;75@$L#jJCmYEHW_@41ptoc6*!`~|xJC{Ux3K^>q8q@-vi$fqb5fT!Vz;v$*
z-=|gMTR_8IdZpjvQ+Yb`@=2me-Sa>Ql4`vMrn-sCwlOLS{E=Cs9)EUfn5lrkFgLgU
z*zcgg#w6)L1E9G(zrG*~qg5{0syMK)H8Zm@r7QYfkY7OHEeLf14{f*ofBXQ2Asfe|
zXlrf>6g|1UTzA)FwVe0TKv9QucWW&It&S*DdmIp+_oivtLetz_RlpsF3j{2z^mkbx
z0Kezver{}3b==aoD&9#Xi-fe#%!~y0-1mJucAyqvg?Js>8SeRfYG~*R18-}%tSr&D
z;vDmoLFrSCI1inxr!s#f87Y5dX4$;Ja+@oO
z;j!vsU~M!6jpn?s!kP;!Dh8?0d4K!?=f0uEM1k7f%^k3HgLRehjhF_jH#U-DQlM&}
zL_~wATw{Zx0?_V0nHxj_z_*|?1VqH
z_B9YY)(_?3LjXr$gqIhdgD3!aSTGIXWSZXpypE~=SIRMvky4M-?o0*>Bu}28*jUL&
zoWjg>>%=ccl*Ni;4={>{zto4DwJa<_#&o!Bx`4F5{FxjZ9C;9^C|P{$yZOKzgGB&U
z34+>JSO|bVt!wVoySGk0pb@_t8A0rXPA%v8;{fLDTWJeJ^d
zq4{eb%?k^_a0^l>NBBSe`K-?J`Bk#QpC2y*Us&M6BO+jV1LxvHt=C=nEwJe2aq0px
zovf){Ij6(z>1>CKfgrd4%RUv0*10^84z{s3E=eAc{3!+L#P&Nr1;JJ(EAPxf5FxVo9>wpXA
z#8+`}jX;pq$vNuI=RA9RsKp>=>nuN`DNL6R2j?a>Ht`*Zz*tyV7KkJPTPL>Tl>I!%
zd|h|oC$cAV@g+4J6-|CkWudw`Z*Q0~9Ob9)?sHRrW`4yv-@3hSWMHJ6=a7f%r;wu~
z=B$-~>nFr`?ecXs`nwSDIB<7+JuzX8b#{?E!Uvt};5?I~vnnD2nk{v9R=KIEDM^~1
zn4XfYKp-`-;1on0t`V?dd3s=-zffRp1^Qj)J2YA%Jv-U0c;y{F&vleVI%
zT2qZXR`H=yg#Qn_2JE#>D=YJOh%N};#OB|#+}QuUG@IIE$aV+EZhr@2IN!gg#;?a=
zI1BaSot-aZW7m@`$`nf}fUGXzdcwi+@_rlMRp1dC(&RI6yS@TdM5wAV?NAU`qOtH*X2AJq-q0S7Ijiz>{E9NUo+6Z3?KAp|eL?4e$GJ%_*>
zFx;V<^&xHxpM3m4PoIR?c<7$ILcDr~kcYQsW@coBG&Dlwq9~}q&fG_QYulHhC`pq6
z|JQqdY3i-vLh$N=cyn&SXZ!)=0)9k#aehzdUT6KZjGEN61ulp}(Xcr#RBtuW@aUfPiFlV1yX&
zwg7vOd3+LD+uB;2(-%D<@cI>9hzF2HO8RpgfiJ+!(})W>+w4FEm}*f{_-W-bDIjmjvAf6E2aliQ>4tu9)n@piI#pRK@5Ur~r}bqi8K
zT*sUuwferCtvC4)$Z{_)K-Iym0|H3@1#AH<&y7k>-E=VjM+Gds5}rvhZ)9a~VxVs528EGj!8@NXu^{nvWIdC2!TBMngOzj-V3G5i3
zMy}s(#23AQp#LJu{qKqYGcLoRm}_{~u@YQC@$mfzd*B(FxGm}XzPcKdgMb8}8xTqW
z+hD};X@Uf~>X3h+@aFk4ndvORt8|Ns(Bm-PUgS(rRK%gTtbL#{?6G&_M7Ns$A05Fvnmk3{D0QwGsQkETLkJI%tJlCwc
zQNW3UzZ>X(-%g6v(&GB_qjiHAyNFcP>%54TcwXl7&n?DA^~ekYBh8?57Bna6N~S5OVKWelu6`Wd?Ppp#RI(q@#it8FkU6R
zwE+BiE_i}dnNi{x?CD9kKQW^idzOH*u$IrS&ZPCwTR~@(bcfeN@(nOBcx~IlLIz&m
z3nnI6Xns856j|8lwcyEJ;-#vaP#Q&x`MSb_ix9Y+X8WR9@oddNW8*$wk64?pekxg6vVHyAx
z+yJ0tcUNa%bc!c2z;RZR=?2w&PNn!J$m8U49_JGqtb{FHO_Grzvd79xK7Go|l%u1M
z1*Qk+T_kr?czwA32Q%O!YpnVWOwvBtoUT~uP}F1+vr~~EV>cgeYHbddjzKos&7^AK
zF2Xp)Lrbf!s5&!AY6NnVASX$j9M+T&_dIgq_z#eNw3E1MASfH>7$rs1anaqr#tn1b
zz+>uUWo2h%RH4OKWEMPj;U|XU@lNE%2Jlk=UVnZ4`dLB(!2Cdt!v8!r9h~krx@CI}
zU}PCK$iPNtjbUd2mAW_e1jS)xqkv%eNCf@^P;Z$4ax{jt>**dny<`>H$m1b2sgt=C6R9ciRXl1i+>O2WP|wMGNDS!TNE)RdGL
zv1WLR*t>aJwnFdP62JM^#
znqZ)ElU}FynC7MdR|UDMc|zgeWn%COml?w^M9@=IAdzUV$YV^pS1!NT!)Rr8Mm&cv
z7dSAbYR)gLv4*FEjs#p7SObS}e2X{u%@+yrF$Q*fSiUu{yhW@qlct@Wxr$1NR#I%T
zl7lWpMp(+QvxV(q7a5yBIW{^v@8bjM3y|TE_RAgwG#(Z+9V2XYVsZ>(kH%;~3^FfI
zn?VSq_r2GkJaoAJy`#|GMzmCLrR?B_z>r}cD=z>
zIZs92knDp!`HVHEzHQz(aF$UxN&V-1NIT;IkGoJ!Y+^B9v8@
zR~N$0giS0{MX-sy35U#`B}tr<_cOL8J)_V?!ABCqYd$&GGvQj9iAx72tEb6)T9UF2
zuz1jXKxzd9^r+PJ%Hh$WX>^5y@m&uO0QFrr-2oG)hI-7w2U
z2&63?r;ZjCP1)E~oK3>xg$DCyXMu)|FxZwNN}EEnHcpi}~1Sq_L9~
z*Q0Y!<}Fj6dh%W7d2VC|?DS%21XzQo_6zL23E?DIU>0d8*kAGR!MEQVkj#t|(LZ7G
z+1Hi~4HIdC30WNj?TE%$Uc(7F@#%g>h5AvQTu5W!3tN|NHB$|Z%niQRfD|7zHaXRP
zKr?~%;O-ThjdUc5G#({?XDczEdFp
z6z4VLSl8vF)TZz1-sN}k;N;bSjkgd`6OemD^ckg3CyP%$nLA2H5^vuTU0H+d6^s@y
zn3Sb1XVzmWP*PkHv(OLzXE6fYCFJ)o@fLZaS2=FwwYQ|2vUXgfvJ?TFUhEIAOQ-J}
z+Fv5YSg4(xzi^(uJ+ceUO<>_aHY3^QVlbP|x*f`Fm%APMRpvWCh;UQn94i8dCdKR6
zoaOoctlIlzswGZpUFZTF3d!DrN1jHCh9DI#1f<8w7U54s_jJ+p0tU507|nT!CRjST
zI_rt|pKI`Vz)QC6dW^VEH_aOzobP8@>_=q=Q<70@ii6}A{u9vM13*oS
zdxDn9SD`}WUt!|rN?%5sJtUZ43Fr)mO3zw}IW(Nnx8VmTWWi};+TU$Z{04?u`&0x}
zF8?0!0pE6Sl85&E@;g$F**S^btEF55qUfKrz-K#eY;801E_u|*y7}+aEgy+*u1TZ!PVIsJ
zvWWYuYYcVBZU6-IH57MQ-yz!??wDxE=jys
zf8^F)mD&GDnudP}VfbwTiZ32c+cQ%A$Iw$zZ?Pp?vn;80p)$RKhS@y#$6BB5p1Qnl
zr&$GP%Uv&v9(9x3Bh<*&le+Zw)C$X+YnJysBj4;zF5C4p0WmZ!*6X6qxCkAF>HXD9
z5kTU+&KnE0&O;bd)Ny%VvUyP)yhB!dtMC8&-;Y+hGk19S*q-qX{?3s-o(oRj+PmoX
zyYa2~(qZ?Wy7ari9J^+6Zol?p@0I`cG^hVhuUrcv!git5!=(`A^y?)1=b}W1|LXZ_aEGPh=+s^40X0Kq9Dn1loFckx;-aX^Ukt=xw
zF;y?oxFnO=4kN)TTkNlg1JgWz6`i^?+U@bpZ#rLhZpL>YvTAOo>g!7)dq^kANxUcF
zl|~M?S{nKTf%fd_ylvN+gil*rtC5lLcM0ouwV~C3piOzTXQmfXEkjrOJ-X@LyRe+A
z4{p?)ZI`FbWguLnI6!U3MmL4X*2sy}(Jni4=848_>X5shRZATl#x|2w*~@q-ZYh_#
zkrk6!5`JhZJ0&?V(5XDfI><)~r$F0`sl9b;_UqS3ELMT%)0=#UM-N})%^uZl;~m13
z#;UeAy$g(nw|8W&>-DtBNH?`$FEBCE90{a5k~hDVG(H{@!4p?vK=|zMD>hfiM7iT*Z%{E?gw^}m&DTFQbImGT
zy}+iKi`P@lX>T(OwbPTEviYbN7}#d_p{=~`@GB*yj7%1T81AcK32&5?=vmMG;M&RX
z^elG3Ue$g#+}_Su;p1q)q(Cis-9U;r;``eHOk6611m10pNUix+d)oZ#*}1=KDR|j5tWsctr63=^=3lCpCL^gy%i2Wbu}~O
zk%R7VKzHs!|1*P6u*H`2L2gUJzC}$^3jzTq-%9|^>}|8=w2}8
z68cm4*5NZS+PaOD1tc>XfyU}r_&8fDQilXb##F1sGll1e&WqT
zb8R#d^JPi0vXbQ@jNg}-P#=fEO=ze)7SJ7m
zaqpDv^-&I1>h2^=jjYFYcOOQf6zabrO$t7|^4A@862F%F4kUa9%WDM=qDd2P8;U;J
z2_=EH3fbJunVWlOZJO~M)8fYCH(z8UqhSCmGi&RYzA8kv$yM%B;8>{vJQ^P(s;j6P
z`z_q^(#p26@vMHC_Tn<}iBlP_bNpAYDK|G*%}t2uYSyT|QMU;HI<-WT9$ia9_VjH;EW2jtDpN7y5eVIsyf;-+yzH6F6YbMz
z7V%5YWk#zQ1e2x^_0!7k~J|0h5Z@yq$jUN+0;*;4`Zh=wF(H
z4gKA^kG3mbAEmx-S%fu^JI7ug5CGx^k#SAsxYP7S79g90pJPuNe2mp+`)bbg|O!xjdm>x&5q$l_!l
zBY*zI;OHTiN=tZ|-X0u;!CWXv49>{;yKQP|#W3&Zy%Fk@1!9|TH
zo!9QXwyJ8O?lnHtUdvU~#L;RZ*$;yH%}f(ttcM~>MR{9G{=SYBSDMPGtpHbJl-WMA
zB4G32#(_#l#lendVI~5fk={(;lUm)Bh>r|}kOi{?2kHDj>(bPDVU1@=;PW%VZsEW9YnySkv5_f(0OJvQ}S&cec0AVE?@N-ZU6!27a|ux73yHtiv9OHU)L;Aze9
z{RMQSY9r!1FWud`lL81y$vO9I%ZD7?@vtOui;M9)JC)YfFOt=k(j~(z!pA-zS
z?!E|By@-)UNzxrlbF@{)HBFWp_#jO+^&bJ7u(k=#nB(EYZCzV2`t+cSid*kh85YWB
z?vG$LOC`4hWbS&DwwwQ?CRKRpPzS?&bQT@;e0H3Ig2qbm<_+yaaHO!_&tK(F)UG>O
z2(y5YW_@Ldt
z$?VGdL>EnN>o=*>j)N%)@}`MZen^&!Io_+w#+Bt?mSnk#M;F@8#cAKnotT_8ajGC?
zDMiv{HVR2fFf&lH;s{iSC7YXv+`{y%
zqp8R4ag%3`AN8QS3ykf=%x&Fkb8CkW-5;2-ICWLIsmWqyRp$CR2Fj4mN4q9`J~^|=
zts-;oMHoRdOLE+%3oRr&63sJVHIsHhL8}_sBk)5*wS4>lkWr4DG@q~d{uGoVbpLv7mg+pqV@kM}O^q@d)qo(soi4hF!bJ_6
z$IO{3jJ`sC=JDUIRopmynDqvE6iyu&WpOzH#y~+i%HxlYLrr~Cv^<_o1JAto$8Xmh
z+G=VP$oKxdNr4DK2SE=g4j_)Q5l8#Wojdevt;q|kSLU~C%&t!JC;#ud*N#OPPdaSv
zzk>RvDqA0-RDUI%Wv`3=GD3%{itPz^+TYW-$%L&9`=pw~ImoqZhMvU77(CEpLC**&B@Bd|7*ai*>1-bvoTRT3t(>T9c
ze|4}jy`e=>gKjL$U^|61>(e4r1YhI3)o;vC*QC;SmmRn7c68DIP<3v|+H92A@YvzB
z{?aO-{$n7wdMRe7mG%Xv4F^XqKP{8*l7cRS@xAy$dMVsN7rudlIUH(bsDjSl{}^SL
zrNoM(&)dpJ%KDay$@1*F(QOzubE{w~yIzVrSjBJIVcF>Mif3gq_x1ZQ(R!4Z36$
zydJ;OBR$f^G#R(pWD7s)ixTNQ=Gg1iuc~+1m{xCF2XNY)4pB*=4oAyj_m+xnKvoV%
zt>eyH662fp*cLy|^|8CBI*TsXT+ugf#k~9^_lKgORnP9C+{)OE1XTIUZ8g8mwU<|3
z=G-|5xB`OCqJg$;_lxHGD-77bu`g$BuIo?{n^XxNIrL5+|
z;y9w-`@$h}Ly?EWQ(;G*6F-i>>wB>(2Mq&{qbYNrTXB8WlxcQAd42YHqg_l%E>8k|
zXOTN!b;jVC?R
zIviZo+25@k2Qp{}Zfjz8h`R}kL9FduI;nHtcPD8Z(-J4Rn-OOM8e>?Wq10}$HgEsx
zS-$Z@cdUPjhGu`%K5&L+fLG(xmg$ss@Z20R_FMI65)UtT)Q0h{Fxli(%Ny=Weo_7F
z@OElctVM!!s`h%W^xHnK3G4jv{-E`QQSAp!YrEf^*3v8*_^=qtL+PD7*4BpcC{v#u
z+Xloa3)xeZof!g6OlVM*bau73I#^Feol32WbK75wL_fzeZ`}OsOPG(IWBFGYn-QxW
zDLYtH9eI3hiR`AP|lCkf-
z&AH~|iD}tEh*9)0!@CK_f@lVEH|psZ$H%AG)PhJ24$y1=5wO19CSQ>T~JMc9eaHhV6b
zO*G)V(NC(2(4780<{#qZ20C-hKbHMc>u|U5!};-awmo+(GZe<4=i$x~F8Xo4tB6oK
yH$*?ez3W`K_mKIUN2iDAd#X6=162#>{gNO5b@mokx0eF`DBe=LnJ;@U@ZSJ@s%eq{
literal 0
HcmV?d00001
From b2d2becd89b39763f2381c4d5174a59fbfb3f5db Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=89li=20Hamel?=
<88721578+MivraMe@users.noreply.github.com>
Date: Wed, 5 Feb 2025 10:10:25 -0500
Subject: [PATCH 03/13] move contributing section to contributing.md (FR)
---
CONTRIBUTING.md | 136 +++++++++++++++++++++++++-----------------------
README.md | 106 +------------------------------------
2 files changed, 73 insertions(+), 169 deletions(-)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 0bdc2b9..b703d77 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,95 +1,101 @@
-# Contribution guidelines
+# 🤝 Contribuer
-Contributing to this project should be as easy and transparent as possible, whether it's:
+Rapporter tout problème est une excellente manière pour tous de contribuer au projet.
-- Reporting a bug
-- Discussing the current state of the code
-- Submitting a fix
-- Proposing new features
+Si vous rencontrez des problèmes ou observez des comportements étranges, veuillez soumettre une "Issue" en y joignant vos journaux.
-## GitHub is used for everything
+## 📜 Activer la journalisation de débogage
+Pour activer la journalisation de débogage, ajoutez ceci dans votre fichier `configuration.yaml` :
-GitHub is used to host code, to track issues and feature requests, as well as accept pull requests.
+```yaml
+logger:
+ default: info
+ logs:
+ custom_components.hilo: debug
+ pyhilo: debug
+```
-Pull requests are the best way to propose changes to the codebase.
+Si vous avez de l'expérience en Python ou avec Home Assistant et souhaitez contribuer au code, n'hésitez pas à soumettre une pull request.
-1. Fork the repo and create your branch from `master`.
-2. If you've changed something, update the documentation.
-3. Make sure your code lints (using black).
-4. Test you contribution.
-5. Issue that pull request!
+---
-## Any contributions you make will be under the MIT Software License
+# 🛠️ Préparer un environnement de développement via VSCode DevContainer
-In short, when you submit code changes, your submissions are understood to be under the same [MIT License](http://choosealicense.com/licenses/mit/) that covers the project. Feel free to contact the maintainers if that's a concern.
+Pour faciliter le développement, un environnement est disponible via DevContainer de VSCode. Assurez-vous d'avoir **VSCode** et **Docker** installés sur votre ordinateur.
-## Report bugs using GitHub's [issues](../../issues)
+1. Ouvrez le dossier du projet dans VSCode.
+2. Installez l'extension **Remote - Containers**.
+3. Ouvrez la palette de commandes (**Ctrl+Shift+P** ou **Cmd+Shift+P**) et recherchez :
+ ```
+ Remote-Containers: Reopen in Container
+ ```
+4. Attendez que l'environnement soit prêt.
+5. Ouvrez un terminal dans VSCode et exécutez :
+ ```bash
+ scripts/develop
+ ```
+ pour installer les dépendances et lancer Home Assistant.
+6. VSCode devrait vous proposer d'ouvrir un navigateur pour accéder à Home Assistant. Sinon, ouvrez manuellement :
+ ```
+ http://localhost:8123
+ ```
+7. Effectuez la configuration initiale de Home Assistant.
+8. Ajoutez l'intégration **Hilo** via l'interface utilisateur.
+9. Modifiez les fichiers dans le dossier `custom_components/hilo` et observez les changements en temps réel dans Home Assistant.
-GitHub's issues are used to track public bugs.
-Report a bug by [opening a new issue](../../issues/new/choose); it's that easy!
+Dans le terminal où vous avez lancé `scripts/develop`, les journaux de Home Assistant et de l'intégration Hilo devraient défiler.
-## Write bug reports with detail, background, and sample code
+---
-**Great Bug Reports** tend to have:
+# ✅ Avant de soumettre une Pull Request
-- A quick summary and/or background
-- Steps to reproduce
- - Be specific!
- - Give sample code if you can.
-- What you expected would happen
-- What actually happens
-- Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)
-- If you need to add logs, make sure debug log level is enabled in your home-assistant `configuration.yaml`:
-```
-logger:
- default: info
- logs:
- custom_components.hilo: debug
- pyhilo: debug
-```
+Il est essentiel de tester vos modifications sur une installation locale. Vous pouvez modifier les fichiers `.py` de l'intégration directement dans votre dossier `custom_components/hilo`.
-People _love_ thorough bug reports. I'm not even kidding.
+⚠ **N'oubliez pas votre copie de sauvegarde!**
-## Use a Consistent Coding Style
+Si vous devez modifier `python-hilo` pour vos tests, installez votre fork avec la commande suivante dans votre CLI :
-Use [black](https://github.com/ambv/black) to make sure the code follows the style.
+```bash
+pip install -e git+https://github.com/VOTRE_FORK_ICI/python-hilo.git#egg=python-hilo
+```
-Or use the `pre-commit` settings implemented in this repository
-(see dedicated section below).
+Redémarrez ensuite Home Assistant pour que l'installation prenne effet. Pour revenir en arrière :
-## Test your code modification
+```bash
+pip install python-hilo
+```
-This custom component is based on [integration_blueprint template](https://github.com/custom-components/integration_blueprint).
+Puis redémarrez Home Assistant.
-It comes with development environment in a container, easy to launch
-if you use Visual Studio Code. With this container you will have a stand alone
-Home Assistant instance running and already configured with the included
-[`.devcontainer/configuration.yaml`](./.devcontainer/configuration.yaml)
-file.
+---
-You can use the `pre-commit` settings implemented in this repository to have
-linting tool checking your contributions (see dedicated section below).
+# 🚀 Soumettre une Pull Request
-## Pre-commit
+1. **Créez un fork** du dépôt dans votre espace utilisateur.
+2. **Clonez-le** sur votre ordinateur.
+3. Pour maintenir une certaine standardisation du code, nous utilisons des **linters** et des **validateurs** exécutés via des hooks `pre-commit` :
-You can use the [pre-commit](https://pre-commit.com/) settings included in the
-repository to have code style and linting checks.
+ ```bash
+ pre-commit install --install-hooks
+ ```
-With `pre-commit` tool already installed,
-activate the settings of the repository:
+4. Apportez vos modifications au code.
+5. Une fois terminé, ajoutez les fichiers modifiés :
-```console
-$ pre-commit install
-```
+ ```bash
+ git add path/to/file
+ ```
-Now the pre-commit tests will be done every time you commit.
+6. Créez un commit :
-You can run the tests on all repository file with the command:
+ ```bash
+ git commit -m "J'ai changé ceci parce que ..."
+ ```
-```console
-$ pre-commit run --all-files
-```
+7. Poussez les changements vers votre dépôt distant :
-## License
+ ```bash
+ git push
+ ```
-By contributing, you agree that your contributions will be licensed under its MIT License.
+8. Sur le dépôt d'origine, **GitHub** devrait vous proposer de créer une **Pull Request** (PR). Suivez les instructions.
diff --git a/README.md b/README.md
index 0fbdb7d..acd5090 100644
--- a/README.md
+++ b/README.md
@@ -189,111 +189,8 @@ logger:
pyhilo: debug
```
----
-
-# 🤝 Contribuer
-
-Rapporter tout problème est une excellente manière pour tous de contribuer au projet.
-
-Si vous rencontrez des problèmes ou observez des comportements étranges, veuillez soumettre une "Issue" en y joignant vos journaux.
-
-## 📜 Activer la journalisation de débogage
-Pour activer la journalisation de débogage, ajoutez ceci dans votre fichier `configuration.yaml` :
-
-```yaml
-logger:
- default: info
- logs:
- custom_components.hilo: debug
- pyhilo: debug
-```
-
-Si vous avez de l'expérience en Python ou avec Home Assistant et souhaitez contribuer au code, n'hésitez pas à soumettre une pull request.
-
----
-
-# 🛠️ Préparer un environnement de développement via VSCode DevContainer
-
-Pour faciliter le développement, un environnement est disponible via DevContainer de VSCode. Assurez-vous d'avoir **VSCode** et **Docker** installés sur votre ordinateur.
-
-1. Ouvrez le dossier du projet dans VSCode.
-2. Installez l'extension **Remote - Containers**.
-3. Ouvrez la palette de commandes (**Ctrl+Shift+P** ou **Cmd+Shift+P**) et recherchez :
- ```
- Remote-Containers: Reopen in Container
- ```
-4. Attendez que l'environnement soit prêt.
-5. Ouvrez un terminal dans VSCode et exécutez :
- ```bash
- scripts/develop
- ```
- pour installer les dépendances et lancer Home Assistant.
-6. VSCode devrait vous proposer d'ouvrir un navigateur pour accéder à Home Assistant. Sinon, ouvrez manuellement :
- ```
- http://localhost:8123
- ```
-7. Effectuez la configuration initiale de Home Assistant.
-8. Ajoutez l'intégration **Hilo** via l'interface utilisateur.
-9. Modifiez les fichiers dans le dossier `custom_components/hilo` et observez les changements en temps réel dans Home Assistant.
-
-Dans le terminal où vous avez lancé `scripts/develop`, les journaux de Home Assistant et de l'intégration Hilo devraient défiler.
-
----
-
-# ✅ Avant de soumettre une Pull Request
+---
-Il est essentiel de tester vos modifications sur une installation locale. Vous pouvez modifier les fichiers `.py` de l'intégration directement dans votre dossier `custom_components/hilo`.
-
-⚠ **N'oubliez pas votre copie de sauvegarde!**
-
-Si vous devez modifier `python-hilo` pour vos tests, installez votre fork avec la commande suivante dans votre CLI :
-
-```bash
-pip install -e git+https://github.com/VOTRE_FORK_ICI/python-hilo.git#egg=python-hilo
-```
-
-Redémarrez ensuite Home Assistant pour que l'installation prenne effet. Pour revenir en arrière :
-
-```bash
-pip install python-hilo
-```
-
-Puis redémarrez Home Assistant.
-
----
-
-# 🚀 Soumettre une Pull Request
-
-1. **Créez un fork** du dépôt dans votre espace utilisateur.
-2. **Clonez-le** sur votre ordinateur.
-3. Pour maintenir une certaine standardisation du code, nous utilisons des **linters** et des **validateurs** exécutés via des hooks `pre-commit` :
-
- ```bash
- pre-commit install --install-hooks
- ```
-
-4. Apportez vos modifications au code.
-5. Une fois terminé, ajoutez les fichiers modifiés :
-
- ```bash
- git add path/to/file
- ```
-
-6. Créez un commit :
-
- ```bash
- git commit -m "J'ai changé ceci parce que ..."
- ```
-
-7. Poussez les changements vers votre dépôt distant :
-
- ```bash
- git push
- ```
-
-8. Sur le dépôt d'origine, **GitHub** devrait vous proposer de créer une **Pull Request** (PR). Suivez les instructions.
-
----
# 👥 Collaborateurs initiaux
@@ -306,6 +203,7 @@ Puis redémarrez Home Assistant.
- **[Hilo](https://www.hiloenergie.com)** : Merci à Hilo pour son soutien et ses contributions.
---
+💡 **Envie de contribuer ?** Consultez la [section contribution](#contribution) pour voir comment aider au projet.
[integration_blueprint]: https://github.com/custom-components/integration_blueprint
[commits-shield]: https://img.shields.io/github/commit-activity/y/dvd-dev/hilo.svg?style=for-the-badge
From 44347d426215a18e05c649e65e47287ccc8c6d14 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=89li=20Hamel?=
<88721578+MivraMe@users.noreply.github.com>
Date: Wed, 5 Feb 2025 10:36:30 -0500
Subject: [PATCH 04/13] =?UTF-8?q?garder=20des=20=C3=A9l=C3=A9ments=20de=20?=
=?UTF-8?q?l'ancien=20CONTRIBUTING.md?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
---
CONTRIBUTING.md | 112 +++++++++++++++++++++++++++++++++---------------
1 file changed, 77 insertions(+), 35 deletions(-)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index b703d77..d6cd14b 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,11 +1,29 @@
-# 🤝 Contribuer
+# 🤝 Contribuer
-Rapporter tout problème est une excellente manière pour tous de contribuer au projet.
+Contribuer à ce projet doit être aussi simple et transparent que possible, que ce soit pour :
-Si vous rencontrez des problèmes ou observez des comportements étranges, veuillez soumettre une "Issue" en y joignant vos journaux.
+- Signaler un bug
+- Discuter du code existant
+- Proposer des corrections
+- Suggérer de nouvelles fonctionnalités
-## 📜 Activer la journalisation de débogage
-Pour activer la journalisation de débogage, ajoutez ceci dans votre fichier `configuration.yaml` :
+## 🚀 GitHub est utilisé pour tout
+
+GitHub est la plateforme principale pour héberger le code, suivre les problèmes et demandes de fonctionnalités, et accepter les pull requests.
+
+Les pull requests sont le meilleur moyen de proposer des modifications du code :
+
+1. **Créez un fork** du dépôt et créez votre branche à partir de `master`.
+2. Si vous avez modifié quelque chose, mettez à jour la documentation.
+3. Assurez-vous que votre code suit les règles de formatage (utilisation de `black`).
+4. Testez votre contribution.
+5. Soumettez une pull request !
+
+---
+
+## 📜 Activer la journalisation de débogage
+
+Si vous devez signaler un problème, il est recommandé d'activer la journalisation de débogage en ajoutant ceci dans votre fichier `configuration.yaml` :
```yaml
logger:
@@ -15,87 +33,111 @@ logger:
pyhilo: debug
```
-Si vous avez de l'expérience en Python ou avec Home Assistant et souhaitez contribuer au code, n'hésitez pas à soumettre une pull request.
-
---
-# 🛠️ Préparer un environnement de développement via VSCode DevContainer
+## 🛠️ Préparer un environnement de développement via VSCode DevContainer
-Pour faciliter le développement, un environnement est disponible via DevContainer de VSCode. Assurez-vous d'avoir **VSCode** et **Docker** installés sur votre ordinateur.
+Pour faciliter le développement, un environnement est disponible via DevContainer de VSCode. Assurez-vous d'avoir **VSCode** et **Docker** installés sur votre ordinateur.
-1. Ouvrez le dossier du projet dans VSCode.
-2. Installez l'extension **Remote - Containers**.
-3. Ouvrez la palette de commandes (**Ctrl+Shift+P** ou **Cmd+Shift+P**) et recherchez :
+1. Ouvrez le dossier du projet dans VSCode.
+2. Installez l'extension **Remote - Containers**.
+3. Ouvrez la palette de commandes (**Ctrl+Shift+P** ou **Cmd+Shift+P**) et recherchez :
```
Remote-Containers: Reopen in Container
```
-4. Attendez que l'environnement soit prêt.
-5. Ouvrez un terminal dans VSCode et exécutez :
+4. Attendez que l'environnement soit prêt.
+5. Ouvrez un terminal dans VSCode et exécutez :
```bash
scripts/develop
```
- pour installer les dépendances et lancer Home Assistant.
-6. VSCode devrait vous proposer d'ouvrir un navigateur pour accéder à Home Assistant. Sinon, ouvrez manuellement :
+ pour installer les dépendances et lancer Home Assistant.
+6. VSCode devrait vous proposer d'ouvrir un navigateur pour accéder à Home Assistant. Sinon, ouvrez manuellement :
```
http://localhost:8123
```
-7. Effectuez la configuration initiale de Home Assistant.
-8. Ajoutez l'intégration **Hilo** via l'interface utilisateur.
-9. Modifiez les fichiers dans le dossier `custom_components/hilo` et observez les changements en temps réel dans Home Assistant.
+7. Effectuez la configuration initiale de Home Assistant.
+8. Ajoutez l'intégration **Hilo** via l'interface utilisateur.
+9. Modifiez les fichiers dans le dossier `custom_components/hilo` et observez les changements en temps réel dans Home Assistant.
-Dans le terminal où vous avez lancé `scripts/develop`, les journaux de Home Assistant et de l'intégration Hilo devraient défiler.
+Dans le terminal où vous avez lancé `scripts/develop`, les journaux de Home Assistant et de l'intégration Hilo devraient défiler.
---
-# ✅ Avant de soumettre une Pull Request
+## ✅ Avant de soumettre une Pull Request
-Il est essentiel de tester vos modifications sur une installation locale. Vous pouvez modifier les fichiers `.py` de l'intégration directement dans votre dossier `custom_components/hilo`.
+Il est essentiel de tester vos modifications sur une installation locale. Vous pouvez modifier les fichiers `.py` de l'intégration directement dans votre dossier `custom_components/hilo`.
-⚠ **N'oubliez pas votre copie de sauvegarde!**
+⚠ **N'oubliez pas votre copie de sauvegarde !**
-Si vous devez modifier `python-hilo` pour vos tests, installez votre fork avec la commande suivante dans votre CLI :
+Si vous devez modifier `python-hilo` pour vos tests, installez votre fork avec la commande suivante :
```bash
pip install -e git+https://github.com/VOTRE_FORK_ICI/python-hilo.git#egg=python-hilo
```
-Redémarrez ensuite Home Assistant pour que l'installation prenne effet. Pour revenir en arrière :
+Redémarrez ensuite Home Assistant pour que l'installation prenne effet. Pour revenir en arrière :
```bash
pip install python-hilo
```
-Puis redémarrez Home Assistant.
+Puis redémarrez Home Assistant.
---
-# 🚀 Soumettre une Pull Request
+## 🚀 Soumettre une Pull Request
-1. **Créez un fork** du dépôt dans votre espace utilisateur.
-2. **Clonez-le** sur votre ordinateur.
-3. Pour maintenir une certaine standardisation du code, nous utilisons des **linters** et des **validateurs** exécutés via des hooks `pre-commit` :
+1. **Créez un fork** du dépôt dans votre espace utilisateur.
+2. **Clonez-le** sur votre ordinateur.
+3. Pour maintenir une certaine standardisation du code, nous utilisons des **linters** et des **validateurs** exécutés via des hooks `pre-commit` :
```bash
pre-commit install --install-hooks
```
-4. Apportez vos modifications au code.
-5. Une fois terminé, ajoutez les fichiers modifiés :
+4. Apportez vos modifications au code.
+5. Une fois terminé, ajoutez les fichiers modifiés :
```bash
git add path/to/file
```
-6. Créez un commit :
+6. Créez un commit :
```bash
git commit -m "J'ai changé ceci parce que ..."
```
-7. Poussez les changements vers votre dépôt distant :
+7. Poussez les changements vers votre dépôt distant :
```bash
git push
```
-8. Sur le dépôt d'origine, **GitHub** devrait vous proposer de créer une **Pull Request** (PR). Suivez les instructions.
+8. Sur le dépôt d'origine, **GitHub** devrait vous proposer de créer une **Pull Request** (PR). Suivez les instructions.
+
+---
+
+## 🛠️ Utiliser un style de code cohérent
+
+Nous utilisons [black](https://github.com/psf/black) pour garantir un formatage uniforme du code. Vous pouvez également utiliser les paramètres `pre-commit` intégrés dans ce dépôt.
+
+Pour activer `pre-commit` :
+
+```bash
+pre-commit install
+```
+
+Maintenant, les tests `pre-commit` seront exécutés à chaque commit.
+
+Pour les exécuter manuellement sur tous les fichiers :
+
+```bash
+pre-commit run --all-files
+```
+
+---
+
+## 📜 Licence
+
+En contribuant, vous acceptez que vos contributions soient sous licence MIT, comme le reste du projet. Pour plus d'informations, consultez la [licence MIT](http://choosealicense.com/licenses/mit/).
From 076eace0b45e8ea74ce7f6f6aa1338f96db03c18 Mon Sep 17 00:00:00 2001
From: "Ian C." <108159253+ic-dev21@users.noreply.github.com>
Date: Sun, 9 Feb 2025 12:31:13 -0500
Subject: [PATCH 05/13] Linting
---
README.md | 50 +++++++++++++++++++++++++-------------------------
1 file changed, 25 insertions(+), 25 deletions(-)
diff --git a/README.md b/README.md
index acd5090..b3ab7a2 100644
--- a/README.md
+++ b/README.md
@@ -48,25 +48,25 @@ L'API servant à la lecture initial de la liste d'appareils sur votre compte Hil
Plus de détails disponibles dans [issue #564](https://github.com/dvd-dev/hilo/issues/564).
## 📌 Introduction
-Cette intégration non-officielle HACS permet d'utiliser [Hilo](https://www.hiloenergie.com/fr-ca/) avec Home Assistant. **Elle n'est pas affiliée à Hilo ou Hydro-Québec.**
+Cette intégration non-officielle HACS permet d'utiliser [Hilo](https://www.hiloenergie.com/fr-ca/) avec Home Assistant. **Elle n'est pas affiliée à Hilo ou Hydro-Québec.**
**⚠️ Ne contactez pas Hilo ou Hydro-Québec pour les problèmes liés à cette intégration.**
-🔗 [Configuration minimale recommandée](https://github.com/dvd-dev/hilo/wiki/FAQ-%E2%80%90-Français#avez-vous-une-configuration-recommandée)
-🔗 Blueprints : [NumerID](https://github.com/NumerID/blueprint_hilo) | [Arim215](https://github.com/arim215/ha-hilo-blueprints)
-🔗 Exemples d'automatisations YAML : [Automatisations](https://github.com/dvd-dev/hilo/tree/main/doc/automations)
-🔗 Exemples d'interfaces Lovelace : [Interfaces](https://github.com/dvd-dev/hilo/wiki/Utilisation)
+🔗 [Configuration minimale recommandée](https://github.com/dvd-dev/hilo/wiki/FAQ-%E2%80%90-Français#avez-vous-une-configuration-recommandée)
+🔗 Blueprints : [NumerID](https://github.com/NumerID/blueprint_hilo) | [Arim215](https://github.com/arim215/ha-hilo-blueprints)
+🔗 Exemples d'automatisations YAML : [Automatisations](https://github.com/dvd-dev/hilo/tree/main/doc/automations)
+🔗 Exemples d'interfaces Lovelace : [Interfaces](https://github.com/dvd-dev/hilo/wiki/Utilisation)
---
## 🔥 Fonctionnalités principales
-✅ Supporte les interrupteurs et gradateurs comme lumières
-✅ Contrôle des thermostats et lecture des températures
-✅ Suivi de la consommation énergétique des appareils Hilo
-✅ Sensor pour les défis et la passerelle Hilo
-✅ Configuration via l'interface utilisateur
-✅ Authentification via le site web d'Hilo
-✅ Capteur météo extérieure avec icône changeante
+✅ Supporte les interrupteurs et gradateurs comme lumières
+✅ Contrôle des thermostats et lecture des températures
+✅ Suivi de la consommation énergétique des appareils Hilo
+✅ Sensor pour les défis et la passerelle Hilo
+✅ Configuration via l'interface utilisateur
+✅ Authentification via le site web d'Hilo
+✅ Capteur météo extérieure avec icône changeante
📌 **À faire** : Support d'autres appareils, amélioration des compteurs de consommation, documentation API
@@ -102,23 +102,23 @@ Cette intégration non-officielle HACS permet d'utiliser [Hilo](https://www.hilo
## 📌 Suivis de la consommation électrique
Si vous souhaitez utiliser la génération automatique des capteurs de consommation électrique, suivez ces étapes :
-1. **Ajouter la plateforme `utility_meter`**
+1. **Ajouter la plateforme `utility_meter`**
Ajoutez la ligne suivante dans votre fichier `configuration.yaml` :
```yaml
utility_meter:
```
-2. **Activer la génération automatique**
+2. **Activer la génération automatique**
- Dans l'interface utilisateur de l'intégration, cliquez sur `Configurer`.
- Cochez **Générer compteurs de consommation électrique**.
-3. *(Optionnel)* **Redémarrer Home Assistant**
+3. *(Optionnel)* **Redémarrer Home Assistant**
- Attendez environ 5 minutes. L'entité `sensor.hilo_energy_total_low` sera créée et contiendra des données.
- **Le `status`** devrait être `collecting`.
- **L'état `state`** devrait être un nombre supérieur à 0.
- Toutes les entités et capteurs créés seront préfixés ou suffixés par `hilo_energy_` ou `hilo_rate_`.
-4. **Erreur connue (à ignorer)**
+4. **Erreur connue (à ignorer)**
Si vous voyez cette erreur dans le journal de Home Assistant, elle peut être ignorée :
```
2021-11-29 22:03:46 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
@@ -127,7 +127,7 @@ Si vous souhaitez utiliser la génération automatique des capteurs de consommat
ValueError: could not convert string to float: 'None'
```
-5. **Ajout manuel au tableau de bord "Énergie"**
+5. **Ajout manuel au tableau de bord "Énergie"**
Une fois créés, les compteurs devront être ajoutés manuellement.
---
@@ -177,7 +177,7 @@ Vous pouvez configurer des options supplémentaires en cliquant sur `Configurer`
## 📌 FAQ et support
-🔗 [FAQ complète](https://github.com/dvd-dev/hilo/wiki/FAQ)
+🔗 [FAQ complète](https://github.com/dvd-dev/hilo/wiki/FAQ)
💬 Rejoignez la communauté sur [Discord](https://discord.gg/MD5ydRJxpc)
**Problèmes ?** Ouvrez une "Issue" avec les logs `debug` activés dans `configuration.yaml` :
@@ -189,18 +189,18 @@ logger:
pyhilo: debug
```
----
+---
-# 👥 Collaborateurs initiaux
+# 👥 Collaborateurs initiaux
-- **[Francis Poisson](https://github.com/francispoisson/)**
-- **[David Vallee Delisle](https://github.com/valleedelisle/)**
+- **[Francis Poisson](https://github.com/francispoisson/)**
+- **[David Vallee Delisle](https://github.com/valleedelisle/)**
-## 🎖️ Mentions très honorables
+## 🎖️ Mentions très honorables
-- **[Ian Couture](https://github.com/ic-dev21/)** : Il maintient cet addon depuis un certain temps.
-- **[Hilo](https://www.hiloenergie.com)** : Merci à Hilo pour son soutien et ses contributions.
+- **[Ian Couture](https://github.com/ic-dev21/)** : Il maintient cet addon depuis un certain temps.
+- **[Hilo](https://www.hiloenergie.com)** : Merci à Hilo pour son soutien et ses contributions.
---
💡 **Envie de contribuer ?** Consultez la [section contribution](#contribution) pour voir comment aider au projet.
From 6033ff303e7a94f368de44ed64a807c0e152b063 Mon Sep 17 00:00:00 2001
From: "Ian C." <108159253+ic-dev21@users.noreply.github.com>
Date: Sun, 9 Feb 2025 12:34:38 -0500
Subject: [PATCH 06/13] Traduction
---
README.en.md | 426 +++++++++++++++++----------------------------------
1 file changed, 137 insertions(+), 289 deletions(-)
diff --git a/README.en.md b/README.en.md
index 866ea2b..0151a6e 100644
--- a/README.en.md
+++ b/README.en.md
@@ -11,274 +11,175 @@
[![calver][calver-shield]][calver]
[![discord][discord-shield]][discord]
-
**BETA**
-This is a beta release. There will be some bugs, issues, etc. Please bear with us and open issues in the repo.
-
-# Hilo
-[Hilo](https://www.hydroquebec.com/hilo/en/) integration for Home Assistant
-
-# :warning: Breaking change to come, please keep your component updated :warning:
-
-The API we rely on for Hilo Challenges will be closed in the near future, we are currently working on an alternative
-using Websockets/SignalR. **Updating to 2025.2.1 and later is strongly suggested** as prior versions will likely break due to the way
-pip installs dependencies.
-
-Several users and I are in the process of migrating our communications with the Hilo API to Websocket/SignalR instead of
-API calls. This transition will be gradual, and we will do everything we can to avoid breaking existing installations.
-
-The first step will be updating the `python-hilo` library (https://github.com/dvd-dev/python-hilo). This change should be
-seamless for everyone.
-
-Next, we will migrate the challenge sensor (`sensor.defi_hilo`) to Websocket/SignalR. The good news is that this method completely eliminates the temporary "glitches" that occurred with the challenge sensor.
-
-### Remaining tasks:
-- The `allowed_kWh` and `used_kWh` attributes are currently **non-functional**. The data arrives in fragments, and not all cases have been handled yet.
-- The `"completed"` state does not always work, possibly due to a race condition.
-- Some information, such as `total_devices`, `opt_out_devices`, and `pre_heat_devices`, does not persist in memory.
-
-More details are available in **issue #486**.
-
-The API used for the initial retrieval of the device list on your Hilo account will also undergo the same transition.
-
-More details are available in **issue #564**.
-
-## Introduction
-
-This is the unofficial HACS Hilo integration for Home Assistant. [Hilo](https://www.hiloenergie.com/en-ca/) is a smart home platform developed
-by a [Hydro Quebec](https://www.hydroquebec.com/hilo/en/) subsidiary.
-This integration has no direct tie with Hilo or Hydro Quebec. This is a community initiative. Please don't contact
-Hilo or Hydro-Quebec with issues with this Home Assistant integration, you can open an issue in the GitHub repository
-instead.
-
-If you want to help with the development of this integration, you can always submit a feedback form from the Hilo
-application and requesting that they open their API publicly and that they provide a testing environment to the
-developers.
-
-### TL:DR version:
-
-You can find a recommended minimal configuration [in the wiki](https://github.com/dvd-dev/hilo/wiki/FAQ#do-you-have-any-recommended-settings)
-
-
-You can also find sample automations in YAML format [in the doc/automations directory](https://github.com/dvd-dev/hilo/tree/main/doc/automations)
-If you prefer blueprints, there are some available here:
- - [NumerID's repository](https://github.com/NumerID/blueprint_hilo)
- - [Arim215's repository](https://github.com/arim215/ha-hilo-blueprints)
-
-### Shout out
-
-Big shout out to [Francis Poisson](https://github.com/francispoisson/) who's the original author of this integration. Without the work
-he put into this integration, I would probably have never even considered Hilo.
-
-Another big shout out to @ic-dev21 for his implication at multiple levels.
-
-I decided to move the integration here because of the latest updates from Hilo broke the original one, and I took the time to completely
-rewrite it. Hilo is now pushing device readings via websocket from SignalR.
-
-### Features
-- Support for switches and dimmers as light devices
-- Get current and set target temperature of thermostat
-- Get energy usage of pretty much each device
-- Generates energy meters and sensors
-- Sensor for Hilo Events (challenges)
-- Sensor for Hilo Gateway
-- Now configuration is done via the UI
-- Updates are now closer to realtime
-- **NEW**: Authentication directly on Hilo's website
-- **NEW**: Outdoor weather sensor with changing icon like in the Hilo App
-
-### To Do:
-- Add functionalities for other devices
-- unit and functional tests
-- [Adding type hints to the code](https://developers.home-assistant.io/docs/development_typing/)
-- API calls to Hilo documentation now available [here](https://github.com/dvd-dev/python-hilo)
-- Map send energy meters automatically to energy dashboard
-
+This is a Beta version. There will likely be bugs, issues, etc. Thank you for your patience and for opening "Issues".
-## Installation
+# Hilo - Home Assistant
+Home Assistant integration for [Hilo](https://www.hiloenergie.com/fr-ca/)
-### Step 0: Compatible install
-This custom component requires that Hilo has carried out the installation in your home. It will not be possible to set it up otherwise.
+# ⚠️ Major change coming, please keep your component up to date ⚠️
-This custom component has been tested to work by various users on HA OS (as bare metal or VM), Docker with the official (ghcr.io) image and Podman. Other types of install may cause permission issues during the creation of a few files needed by the custom component.
+The API we rely on for Hilo challenges will be shut down soon. We are currently working on an
+alternative using Websocket/SignalR. **Updating to version 2025.2.1 or later is strongly recommended**, as
+previous versions may stop working due to how pip installs dependencies.
-### Step 1: Download files
+Several users and I are migrating our communications with the Hilo API to Websocket/SignalR
+rather than API calls. The process will be gradual and we will do everything we can to avoid
+breaking existing installations.
-#### Option 1: Via HACS
+First, we will update the `python-hilo` library (https://github.com/dvd-dev/python-hilo),
+this change should be transparent for everyone.
-[](https://my.home-assistant.io/redirect/hacs_repository/?owner=dvd-dev&repository=hilo&category=integration)
+Then, we will migrate the challenge sensor (`sensor.defi_hilo`) to Websocket/SignalR. The good news with this is
+that momentary "glitches" of the challenge sensor are completely eliminated by this method.
-Make sure you have [HACS](https://hacs.xyz/docs/setup/download/) installed.
-Under HACS, click the '+ EXPLORE & DOWNLOAD REPOSITORIES' button on the bottom of the page, search for "Hilo", choose it, and click _download_ in HACS.
+### What remains to be done on this side:
+- The `allowed_kWh` and `used_kWh` attributes are currently **non-functional**, the information arrives in fragments and all
+cases are not handled yet.
+- The "completed" state doesn't always work, possibly a race condition
+- Some information like `total_devices`, `opt_out_devices` and `pre_heat_devices` don't persist in memory.
-#### Option 2: Manual
+More details available in [issue #486](https://github.com/dvd-dev/hilo/issues/486).
-Download and copy the `custom_components/hilo` directory from the [latest release](https://github.com/dvd-dev/hilo/releases/latest) to your `custom_components` directory in HA.
+The API used for initially reading the list of devices on your Hilo account will also undergo the same treatment.
-### Step 2: Add integration to HA (<--- this is a step that a lot of people forget)
+More details available in [issue #564](https://github.com/dvd-dev/hilo/issues/564).
-[](https://my.home-assistant.io/redirect/config_flow_start/?domain=hilo)
+## 📌 Introduction
+This unofficial HACS integration allows you to use [Hilo](https://www.hiloenergie.com/fr-ca/) with Home Assistant. **It is not affiliated with Hilo or Hydro-Québec.**
-In HA, go to Settings > Devices & Services > Integrations.
-In the bottom right corner, click the '+ ADD INTEGRATION' button.
+**⚠️ Do not contact Hilo or Hydro-Québec for issues related to this integration.**
-
+🔗 [Recommended minimum configuration](https://github.com/dvd-dev/hilo/wiki/FAQ-%E2%80%90-Français#avez-vous-une-configuration-recommandée)
+🔗 Blueprints: [NumerID](https://github.com/NumerID/blueprint_hilo) | [Arim215](https://github.com/arim215/ha-hilo-blueprints)
+🔗 YAML automation examples: [Automations](https://github.com/dvd-dev/hilo/tree/main/doc/automations)
+🔗 Lovelace interface examples: [Interfaces](https://github.com/dvd-dev/hilo/wiki/Utilisation)
-If the component is properly installed, you should be able to find the 'Hilo integration' in the list. You might need to clear your browser cache for the integration to show up.
-
-
-
-
-## Configuration (new install)
-
-The configuration is done in the UI. When you add the integration, you will be redirected to Hilo's website login page to authenticate.
-
-
-
-
-
-
-You must then accept to link your account. To do so, you must enter your Home Assistant instance's URL or IP address and click Link Account.
-
-
-
-
-
-After this, you will be prompted to assign a room for each one of your devices.
-
-## Configuration (update from a version earlier than v2024.3.1)
-
-After update, you will get an error saying you must reauthenticate for the integration to work.
-
-
-
-
-
-After correctly linking your account like in the previous section, you should see a popup telling you the reauthentification was successful.
-
-### Energy meters
-
-Energy meters are a feature of this integration. We used to manually generate them with template sensors and automation,
-but they now have been fully integrated into the Hilo integration.
-
-#### Warning
+---
-When enabling Hilo generated energy meters, it's recommended to remove the manually generated ones to have the most accurate
-statistics, otherwise we might end up with duplicated data.
+## 🔥 Main Features
+✅ Supports switches and dimmers as lights
+✅ Thermostat control and temperature reading
+✅ Energy consumption monitoring of Hilo devices
+✅ Sensor for Hilo challenges and gateway
+✅ Configuration via user interface
+✅ Authentication via Hilo website
+✅ Outdoor weather sensor with changing icon
-If you're facing an issue, and you want to collaborate, please enable `debug` log level for this integration and provide a copy
-of the `home-assistant.log` file. Details on how to enable `debug` are [below](https://github.com/dvd-dev/hilo/blob/main/README.en.md#contributing).
+📌 **To do**: Support for other devices, improvement of consumption meters, API documentation
-#### Procedure
+---
-If you want to enable the automatic generation of the energy sensors, follow these steps:
+## 📥 Installation
+### 1️⃣ Check Compatibility
+- The integration requires Hilo hardware installed and functional.
+- Tested on HA OS, Docker (ghcr.io), Podman. Other configurations may cause issues.
-* Make sure that the `utility_meter` platform is loaded in your `configuration.yaml` file from
-home assistant. You simply need to add a line like this in your `configuration.yaml`:
+### 2️⃣ File Installation
+#### 🔹 Option 1: Via HACS
+[](https://my.home-assistant.io/redirect/hacs_repository/?owner=dvd-dev&repository=hilo&category=integration)
- ```
- utility_meter:
- ```
+1. Make sure you have [HACS](https://hacs.xyz/docs/setup/download/) installed.
+2. In HACS, click `+ EXPLORE & DOWNLOAD REPOSITORIES`, search for "Hilo" and download it.
+3. Restart Home Assistant
-* Click`Configure` on the integration UI and check the `Generate energy meters` box.
+#### 🔹 Option 2: Manually
+1. Download the latest version from [GitHub](https://github.com/dvd-dev/hilo/releases/latest).
+2. Copy `custom_components/hilo` to Home Assistant's `custom_components` folder.
+3. Restart Home Assistant
-* Restart home assistant and wait 5 minutes until you see the `sensor.hilo_energy_total_low` entity getting created and populated
- with data:
- * The `status` should be in `collecting`
- * The `state` should be a number higher than 0.
+### 3️⃣ Add Integration to Home Assistant
+[](https://my.home-assistant.io/redirect/config_flow_start/?domain=hilo)
-* All generated entities and sensors will be prefixed or suffixed with `hilo_energy_` or `hilo_rate_`.
+1. Go to **Settings > Devices & Services > Integrations**.
+2. Click `+ ADD INTEGRATION` and search for "Hilo".
+3. Authenticate on the Hilo website and link your account.
-* If you see the following error in your logs, this is a bug in Home Assistant, and it's because the power meter in question has 0 W/h
- usage so far. This will disappear once usage has been calculated.
+---
- ```
- 2021-11-29 22:03:46 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
- Traceback (most recent call last):
- [...]
- ValueError: could not convert string to float: 'None'
- ```
-Once created, energy meters will then have to be added manually to the energy dashboard.
+## 📌 Power Consumption Tracking
+If you want to use automatic generation of power consumption sensors, follow these steps:
+
+1. **Add the `utility_meter` platform**
+ Add the following line to your `configuration.yaml`:
+ ```yaml
+ utility_meter:
+ ```
+
+2. **Enable automatic generation**
+ - In the integration's user interface, click `Configure`.
+ - Check **Generate power consumption meters**.
+
+3. *(Optional)* **Restart Home Assistant**
+ - Wait about 5 minutes. The `sensor.hilo_energy_total_low` entity will be created and contain data.
+ - **The `status`** should be `collecting`.
+ - **The `state`** should be a number greater than 0.
+ - All created entities and sensors will be prefixed or suffixed with `hilo_energy_` or `hilo_rate_`.
+
+4. **Known error (to ignore)**
+ If you see this error in the Home Assistant log, it can be ignored:
+ ```
+ 2021-11-29 22:03:46 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
+ Traceback (most recent call last):
+ [...]
+ ValueError: could not convert string to float: 'None'
+ ```
+
+5. **Manual addition to "Energy" dashboard**
+ Once created, meters will need to be added manually.
+---
-### Other configurations
+## ⚠️ Warning
+When activating meters, it is recommended to **remove old manual sensors** to avoid duplicate data.
-Other options are available under the `Configure` button in Home Assistant:
+If you encounter a problem and want to collaborate, enable **debug** logging and provide an excerpt from the `home-assistant.log` file. The method is explained below.
-- `Generate energy meters`: Checkbox
+---
- Automatically generate energy meters, see procedure above for proper setup
- Requires this line to be added to your configuration.yaml file:
- ```
+## ⚙️ Other Configuration Options
+You can configure additional options by clicking `Configure` in Home Assistant:
+
+### ✅ **Generate power consumption meters**
+- Automatically generates power consumption meters.
+- **Requires** the following line in `configuration.yaml`:
+ ```yaml
utility_meter:
```
-- `Generate only total meters for each devices`: Checkbox
-
- Calculate only energy total without splitting between low cost and high cost
-
-- `Also log request data and websocket messages (requires debug log level on both the integration and pyhilo)`: Checkbox
-
- Allows higher logging level for developers/debugging
-
-- `Lock climate entities during Hilo challenges, preventing any changes when a challenge is in progress.`
-
- Prevents modifying temperature setpoints during Hilo Challenges
-
-- `Track unknown power sources in a separate energy sensor. This is a round approximation calculated when we get a reading from the Smart Energy Meter.`: Checkbox
-
- All energy sources other than Hilo hardware are lumped into a single sensor. Uses the reading from the home's smart meter.
-
-- `hq_plan_name`: String
-
- Define the Hydro Quebec rate plan name.
- Only 2 values are supported at this time:
- - `rate d`
- - `flex d`
-
-- `appreciation phase`: Integer (hours)
-
- Add an appreciation phase of X hours before the preheat phase.
+### ✅ **Generate only total meters for each device**
+- Calculates only the total energy **without division** between low and high cost.
-- `pre_cold phase`: Integer (hours)
+### ✅ **Log request data and Websocket messages**
+- Requires **debug logging level** on the integration and `pyhilo`.
+- Allows detailed tracking for development and debugging.
- Add a cooldown phase of X hours to reduce temperatures before the appreciation phase
+### ✅ **Lock `climate` entities during Hilo challenges**
+- Prevents any modification of temperature setpoints **during a challenge** Hilo.
-- `Scan interval (min: 60s)`: Integer
+### ✅ **Track unknown consumption sources in a separate meter**
+- All **non-Hilo** sources are grouped in a dedicated sensor.
+- Uses the house's **smart meter** reading.
- Number of seconds between each device update. Defaults to 60 and, it's not recommended to go below 30 as it might
- result in a suspension from Hilo. Since [2023.11.1](https://github.com/dvd-dev/hilo/releases/tag/v2023.11.1) the minimum has changed from 15s to 60s.
+### 📌 **Hydro-Québec rate name** (`rate d` or `flex d`)
+- Define the **rate plan name**.
+- **Supported values**:
+ - `'rate d'`
+ - `'flex d'`
-## Lovelace sample integration and automation example
+### ⏳ **Update interval (min: 60s)**
+- Sets the **number of seconds** between each update.
+- **Default value**: `60s`.
+- **Don't go below 30s** to avoid suspension from Hilo.
+- Since **2023.11.1**, the minimum has increased from **15s to 60s**.
-You can find multiple examples and ideas for lovelace dashboard, cards and automation here [in the wiki of the project](https://github.com/dvd-dev/hilo/wiki/Utilisation)
+## 📌 FAQ and Support
+🔗 [Complete FAQ](https://github.com/dvd-dev/hilo/wiki/FAQ)
+💬 Join the community on [Discord](https://discord.gg/MD5ydRJxpc)
-You can also find sample automations in YAML format [in the doc/automations directory](https://github.com/dvd-dev/hilo/tree/main/doc/automations)
-
-
-## References
-
-As stated above, this is an unofficial integration. Hilo is not supporting direct API calls and might obfuscate the service or
-prevent us from using it.
-
-For now, these are the swagger links we've found:
-* https://wapphqcdev01-automation.azurewebsites.net/swagger/index.html
-* https://wapphqcdev01-notification.azurewebsites.net/swagger/index.html
-* https://wapphqcdev01-clientele.azurewebsites.net/swagger/index.html
-
-## FAQ
-
-You can find the FAQ in the wiki of the project: https://github.com/dvd-dev/hilo/wiki/FAQ
-
-## Contributing
-
-Reporting any kind of issue is a good way of contributing to the project, and it's available to anyone.
-
-If you face any kind of problem or weird behavior, please submit an issue and ideal, attach debug logs.
-
-To enable debug log level, you need to add this to your `configuration.yaml` file:
-```
+**Problems?** Open an "Issue" with `debug` logs enabled in `configuration.yaml`:
+```yaml
logger:
default: info
logs:
@@ -286,73 +187,20 @@ logger:
pyhilo: debug
```
-If you have any kind of python/home-assistant experience and want to contribute to the code, feel free to submit a pull request.
-
-### Prepare a development environment via VSCode DevContainer
-
-To facilitate development, a development environment is available via VSCode DevContainer. To use it, you must have [VSCode](https://code.visualstudio.com/) and [Docker](https://www.docker.com/) installed on your computer.
-
-1. Open the project folder in VSCode
-2. Install the [Remote - Containers](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) extension
-3. Open the command palette (Ctrl+Shift+P or Cmd+Shift+P) and search for "Remote-Containers: Reopen in Container"
-4. Wait for the environment to be ready
-5. Open a terminal in VSCode and run `scripts/develop` to install dependencies and start Home Assistant
-6. At this point, VSCode should prompt you to open a browser to access Home Assistant. You can also open a browser manually and go to [http://localhost:8123](http://localhost:8123)
-7. You will need to do the initial Home Assistant configuration
-8. You will need to add the Hilo integration via the user interface
-9. You can now modify files in the `custom_components/hilo` folder and see changes in real-time in Home Assistant
-10. In the terminal where you launched `scripts/develop`, Home Assistant and HILO integration logs should be streamed
-
-### Before submitting a Pull Request
-
-It goes without saying you must test your modifications on your local install for problems. You may modify the .py files inside the following folder. Don't forget a backup!
-```
-custom_components/hilo
-```
-
-If you need to modify python-hilo for your tests, you can pull your own fork into Home Assistant with the following on the CLI:
-
-```
-pip install -e git+https://github.com/YOUR_FORK_HERE/python-hilo.git#egg=python-hilo
-```
-
-You must then restart Home Assistant for your install to take effect. To go back to the original, simply type:
-
-```
-pip install python-hilo
-```
-And restart Home Assistant
-
-### Submitting a Pull Request
+---
-- First you need to `fork` the repository into your own userspace.
-- And then, you can `clone` it on your computer.
-- To maintain some kind of tidiness and standard in the code, we have some linters and validators that need to be executed via `pre-commit` hooks:
-```
-pre-commit install --install-hooks
-```
-- You can now proceed with whatever code change you want.
-- Once you're done with the code change, you can `stage` the files for a `commit`:
-```
-git add path/to/file
-```
-- And you can create a `commit`:
-```
-git commit -m "I changed this because blabla"
-```
-- Finally, you can `push` the change in your upstream repository:
-```
-git push
-```
-- At this point, if you visit the [upstream repository](https://github.com/dvd-dev/hilo), GitHub should prompt you to create a Pull Request (aka PR). Just follow the instructions.
+# 👥 Initial Contributors
-### Initial collaborators
+- **[Francis Poisson](https://github.com/francispoisson/)**
+- **[David Vallee Delisle](https://github.com/valleedelisle/)**
-* [Francis Poisson](https://github.com/francispoisson/)
-* [David Vallee Delisle](https://github.com/valleedelisle/)
+## 🎖️ Very Honorable Mentions
+- **[Ian Couture](https://github.com/ic-dev21/)**: He has been maintaining this addon for some time.
+- **[Hilo](https://www.hiloenergie.com)**: Thanks to Hilo for their support and contributions.
---
+💡 **Want to contribute?** Check out the [contribution section](#contribution) to see how to help with the project.
[integration_blueprint]: https://github.com/custom-components/integration_blueprint
[commits-shield]: https://img.shields.io/github/commit-activity/y/dvd-dev/hilo.svg?style=for-the-badge
@@ -374,6 +222,6 @@ git push
[discord-shield]: https://img.shields.io/badge/discord-Chat-green?logo=discord&style=for-the-badge
[discord]: https://discord.gg/MD5ydRJxpc
[Englishshield]: https://img.shields.io/badge/en-English-red?style=for-the-badge
-[English]: https://github.com/dvd-dev/hilo/blob/main/README.md
+[English]: https://github.com/dvd-dev/hilo/blob/main/README.en.md
[Françaisshield]: https://img.shields.io/badge/fr-Français-blue?style=for-the-badge
-[Français]: https://github.com/dvd-dev/hilo/blob/main/README.md
+[Français]: https://github.com/dvd-dev/hilo/blob/main/README.md
\ No newline at end of file
From 814c842b87a4b4b829ec66363c625c71b441945f Mon Sep 17 00:00:00 2001
From: "Ian C." <108159253+ic-dev21@users.noreply.github.com>
Date: Sun, 9 Feb 2025 12:41:00 -0500
Subject: [PATCH 07/13] Typos
---
README.en.md | 3 ++-
README.md | 11 ++++++-----
2 files changed, 8 insertions(+), 6 deletions(-)
diff --git a/README.en.md b/README.en.md
index 0151a6e..cf26c91 100644
--- a/README.en.md
+++ b/README.en.md
@@ -37,7 +37,7 @@ that momentary "glitches" of the challenge sensor are completely eliminated by t
### What remains to be done on this side:
- The `allowed_kWh` and `used_kWh` attributes are currently **non-functional**, the information arrives in fragments and all
cases are not handled yet.
-- The "completed" state doesn't always work, possibly a race condition
+~~- The "completed" state doesn't always work, possibly a race condition~~
- Some information like `total_devices`, `opt_out_devices` and `pre_heat_devices` don't persist in memory.
More details available in [issue #486](https://github.com/dvd-dev/hilo/issues/486).
@@ -75,6 +75,7 @@ This unofficial HACS integration allows you to use [Hilo](https://www.hiloenergi
### 1️⃣ Check Compatibility
- The integration requires Hilo hardware installed and functional.
- Tested on HA OS, Docker (ghcr.io), Podman. Other configurations may cause issues.
+- Ongoing issue on Podman/Kubernetes see [issue #497](https://github.com/dvd-dev/hilo/issues/497).
### 2️⃣ File Installation
#### 🔹 Option 1: Via HACS
diff --git a/README.md b/README.md
index b3ab7a2..89c41c2 100644
--- a/README.md
+++ b/README.md
@@ -32,18 +32,18 @@ briser des installations existantes.
Dans un premier temps, nous mettrons à jour la librairie `python-hilo` (https://github.com/dvd-dev/python-hilo),
ce changement devrait être transparent pour tous.
-Ensuite, nous migrerons le capteur de défi (`sensor.defi_hilo`) vers Websocket/SignalR. La bonne nouvelle avec ça c'est
+Ensuite, nous migrerons le capteur de défi (`sensor.defi_hilo`) vers Websocket/SignalR. La bonne nouvelle avec ça, c'est
que les "glitchs" momentanés du capteur de défi sont complètement éliminés par cette méthode.
### Ce qui reste à faire de ce côté:
-- Les attributs `allowed_kWh` et `used_kWh` sont **non-fonctionnels** actuellement, les information arrivent morcelées et tous
+- Les attributs `allowed_kWh` et `used_kWh` sont **non-fonctionnels** actuellement, les informations arrivent morcelées et tous
les cas ne sont pas traités encore.
-- L'état "completed" ne fonctionne pas toujours, possiblement un race condition
+~~- L'état "completed" ne fonctionne pas toujours, possiblement une "race condition"~~
- Certaines informations comme `total_devices`, `opt_out_devices` et `pre_heat_devices` ne persistent pas en mémoire.
Plus de détails disponibles dans [issue #486](https://github.com/dvd-dev/hilo/issues/486).
-L'API servant à la lecture initial de la liste d'appareils sur votre compte Hilo subira également le même traitement.
+L'API servant à la lecture initiale de la liste d'appareils sur votre compte Hilo subira également le même traitement.
Plus de détails disponibles dans [issue #564](https://github.com/dvd-dev/hilo/issues/564).
@@ -75,7 +75,8 @@ Cette intégration non-officielle HACS permet d'utiliser [Hilo](https://www.hilo
## 📥 Installation
### 1️⃣ Vérifier la compatibilité
- L'intégration nécessite le matériel Hilo installé et fonctionnel.
-- Testée sous HA OS, Docker (ghcr.io), Podman. D'autres configurations peuvent poser problème.
+- Testée sous HA OS, Docker (ghcr.io), Podman. D'autres configurations peuvent poser problèmes.
+- Problème connu sur Podman/Kubernetes see [issue #497](https://github.com/dvd-dev/hilo/issues/497).
### 2️⃣ Installation des fichiers
#### 🔹 Option 1 : Via HACS
From f2196a4311abd6a66e09d4b45f06f0c6ae0fea72 Mon Sep 17 00:00:00 2001
From: "Ian C." <108159253+ic-dev21@users.noreply.github.com>
Date: Sun, 9 Feb 2025 12:58:45 -0500
Subject: [PATCH 08/13] Update README.en.md
---
README.en.md | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/README.en.md b/README.en.md
index cf26c91..c541ebc 100644
--- a/README.en.md
+++ b/README.en.md
@@ -37,6 +37,7 @@ that momentary "glitches" of the challenge sensor are completely eliminated by t
### What remains to be done on this side:
- The `allowed_kWh` and `used_kWh` attributes are currently **non-functional**, the information arrives in fragments and all
cases are not handled yet.
+
~~- The "completed" state doesn't always work, possibly a race condition~~
- Some information like `total_devices`, `opt_out_devices` and `pre_heat_devices` don't persist in memory.
@@ -225,4 +226,4 @@ logger:
[Englishshield]: https://img.shields.io/badge/en-English-red?style=for-the-badge
[English]: https://github.com/dvd-dev/hilo/blob/main/README.en.md
[Françaisshield]: https://img.shields.io/badge/fr-Français-blue?style=for-the-badge
-[Français]: https://github.com/dvd-dev/hilo/blob/main/README.md
\ No newline at end of file
+[Français]: https://github.com/dvd-dev/hilo/blob/main/README.md
From 48826ab2fa13afd7b7efc40ad0c461e6af518d23 Mon Sep 17 00:00:00 2001
From: "Ian C." <108159253+ic-dev21@users.noreply.github.com>
Date: Sun, 9 Feb 2025 12:59:11 -0500
Subject: [PATCH 09/13] Update README.en.md
---
README.en.md | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/README.en.md b/README.en.md
index c541ebc..4abeffe 100644
--- a/README.en.md
+++ b/README.en.md
@@ -37,8 +37,7 @@ that momentary "glitches" of the challenge sensor are completely eliminated by t
### What remains to be done on this side:
- The `allowed_kWh` and `used_kWh` attributes are currently **non-functional**, the information arrives in fragments and all
cases are not handled yet.
-
-~~- The "completed" state doesn't always work, possibly a race condition~~
+-~~ The "completed" state doesn't always work, possibly a race condition~~
- Some information like `total_devices`, `opt_out_devices` and `pre_heat_devices` don't persist in memory.
More details available in [issue #486](https://github.com/dvd-dev/hilo/issues/486).
From f5feb9b817de7c48a8a64efc234c82533a9c8c67 Mon Sep 17 00:00:00 2001
From: "Ian C." <108159253+ic-dev21@users.noreply.github.com>
Date: Sun, 9 Feb 2025 13:00:10 -0500
Subject: [PATCH 10/13] Update README.en.md
---
README.en.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/README.en.md b/README.en.md
index 4abeffe..241466a 100644
--- a/README.en.md
+++ b/README.en.md
@@ -37,7 +37,7 @@ that momentary "glitches" of the challenge sensor are completely eliminated by t
### What remains to be done on this side:
- The `allowed_kWh` and `used_kWh` attributes are currently **non-functional**, the information arrives in fragments and all
cases are not handled yet.
--~~ The "completed" state doesn't always work, possibly a race condition~~
+-~~- The "completed" state doesn't always work, possibly a race condition~~
- Some information like `total_devices`, `opt_out_devices` and `pre_heat_devices` don't persist in memory.
More details available in [issue #486](https://github.com/dvd-dev/hilo/issues/486).
From 27c52071dc35976261d88a080f1575ad7d1e2364 Mon Sep 17 00:00:00 2001
From: "Ian C." <108159253+ic-dev21@users.noreply.github.com>
Date: Sun, 9 Feb 2025 13:00:30 -0500
Subject: [PATCH 11/13] Update README.en.md
---
README.en.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/README.en.md b/README.en.md
index 241466a..140261f 100644
--- a/README.en.md
+++ b/README.en.md
@@ -37,7 +37,7 @@ that momentary "glitches" of the challenge sensor are completely eliminated by t
### What remains to be done on this side:
- The `allowed_kWh` and `used_kWh` attributes are currently **non-functional**, the information arrives in fragments and all
cases are not handled yet.
--~~- The "completed" state doesn't always work, possibly a race condition~~
+- ~~- The "completed" state doesn't always work, possibly a race condition~~
- Some information like `total_devices`, `opt_out_devices` and `pre_heat_devices` don't persist in memory.
More details available in [issue #486](https://github.com/dvd-dev/hilo/issues/486).
From 2521c20056e377c48ce847d1ba31d9c93f38b7d8 Mon Sep 17 00:00:00 2001
From: "Ian C." <108159253+ic-dev21@users.noreply.github.com>
Date: Sun, 9 Feb 2025 13:00:54 -0500
Subject: [PATCH 12/13] Update README.en.md
---
README.en.md | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/README.en.md b/README.en.md
index 140261f..bbe5c01 100644
--- a/README.en.md
+++ b/README.en.md
@@ -60,13 +60,20 @@ This unofficial HACS integration allows you to use [Hilo](https://www.hiloenergi
## 🔥 Main Features
✅ Supports switches and dimmers as lights
+
✅ Thermostat control and temperature reading
+
✅ Energy consumption monitoring of Hilo devices
+
✅ Sensor for Hilo challenges and gateway
+
✅ Configuration via user interface
+
✅ Authentication via Hilo website
+
✅ Outdoor weather sensor with changing icon
+
📌 **To do**: Support for other devices, improvement of consumption meters, API documentation
---
From 48c4119a8cb98b65bce77621ac2f8445b26552d4 Mon Sep 17 00:00:00 2001
From: "Ian C." <108159253+ic-dev21@users.noreply.github.com>
Date: Sun, 9 Feb 2025 13:01:30 -0500
Subject: [PATCH 13/13] Update README.md
---
README.md | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/README.md b/README.md
index 89c41c2..7251855 100644
--- a/README.md
+++ b/README.md
@@ -38,7 +38,7 @@ que les "glitchs" momentanés du capteur de défi sont complètement éliminés
### Ce qui reste à faire de ce côté:
- Les attributs `allowed_kWh` et `used_kWh` sont **non-fonctionnels** actuellement, les informations arrivent morcelées et tous
les cas ne sont pas traités encore.
-~~- L'état "completed" ne fonctionne pas toujours, possiblement une "race condition"~~
+- ~~- L'état "completed" ne fonctionne pas toujours, possiblement une "race condition"~~
- Certaines informations comme `total_devices`, `opt_out_devices` et `pre_heat_devices` ne persistent pas en mémoire.
Plus de détails disponibles dans [issue #486](https://github.com/dvd-dev/hilo/issues/486).
@@ -61,11 +61,17 @@ Cette intégration non-officielle HACS permet d'utiliser [Hilo](https://www.hilo
## 🔥 Fonctionnalités principales
✅ Supporte les interrupteurs et gradateurs comme lumières
+
✅ Contrôle des thermostats et lecture des températures
+
✅ Suivi de la consommation énergétique des appareils Hilo
+
✅ Sensor pour les défis et la passerelle Hilo
+
✅ Configuration via l'interface utilisateur
+
✅ Authentification via le site web d'Hilo
+
✅ Capteur météo extérieure avec icône changeante
📌 **À faire** : Support d'autres appareils, amélioration des compteurs de consommation, documentation API