{"id":55356,"date":"2020-01-18T00:00:00","date_gmt":"2020-01-17T21:00:00","guid":{"rendered":"https:\/\/prohoster.info\/blog\/blog_prohoster\/lytko-obedinyaet"},"modified":"2020-02-18T14:03:28","modified_gmt":"2020-02-18T11:03:28","slug":"lytko-obedinyaet","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/news\/lytko-obedinyaet","title":{"rendered":"Lytko bashkon","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Para nj\u00eb koh\u00eb t\u00eb shkurt\u00ebr, ne ju prezantuam termostatin e men\u00e7ur<\/a><\/noindex>. Artikulli aktualisht \u00ebsht\u00eb menduar si nj\u00eb demostrim i programit t\u00eb tij dhe sistemit t\u00eb menaxhimit. Por p\u00ebr t\u00eb shpjeguar logjik\u00ebn e funksionimit t\u00eb termostatit dhe at\u00eb q\u00eb kemi realizuar, \u00ebsht\u00eb e nevojshme t\u00eb p\u00ebrshkruajm\u00eb gjithashtu konceptin n\u00eb t\u00ebr\u00ebsi.<\/p>\n

\"Lytko
\n<\/a><\/noindex><\/p>\n

P\u00ebr automatizimin<\/h3>\n

\nKushtimisht, e gjith\u00eb automatizimi mund t\u00eb ndahen n\u00eb tri kategori:
\nKategoria 1<\/u> \u2014 pajisje t\u00eb ve\u00e7anta \"smart\". Ju blini nga prodhues t\u00eb ndrysh\u00ebm llamba, kafetiera etj. Avantazhet: secila pajisje zgjeron mund\u00ebsit\u00eb dhe rrit komoditetin. Disavantazhet: p\u00ebr \u00e7do prodhues t\u00eb ri nevojitet aplikacioni i vet. Protokollet e pajisjeve nga prodhues t\u00eb ndrysh\u00ebm shpeshher\u00eb nuk jan\u00eb t\u00eb p\u00ebrputhshme me nj\u00ebra-tjetr\u00ebn.<\/p>\n

Kategoria 2<\/u> \u2014 instalimi i nj\u00eb PC me nj\u00eb tabel\u00eb ose t\u00eb p\u00ebrshtatsh\u00ebm me x86. Kjo heq kufizimet n\u00eb fuqin\u00eb llogarit\u00ebse, dhe n\u00eb k\u00ebt\u00eb aparat instalohet MajorDoMo ose \u00e7do distro tjet\u00ebr server p\u00ebr menaxhimin e sht\u00ebpis\u00eb s\u00eb men\u00e7ur. K\u00ebshtu, pajisjet e shumic\u00ebs s\u00eb prodhuesve lidhen n\u00eb nj\u00eb hap\u00ebsir\u00eb informative t\u00eb p\u00ebrbashk\u00ebt. Pra, krijohet serveri juaj p\u00ebr sht\u00ebpin\u00eb e men\u00e7ur. Avantazhet: p\u00ebrputhshm\u00ebria n\u00ebn nj\u00eb qend\u00ebr t\u00eb vetme, e cila ofron mund\u00ebsi t\u00eb zgjeruara p\u00ebr menaxhim. Disavantazhet: n\u00eb rastin e d\u00ebshtimit t\u00eb serverit, e gjith\u00eb sistemi kthehet n\u00eb faz\u00ebn 1, dmth. b\u00ebhet e ndar\u00eb, ose e padobishme.<\/p>\n

Kategoria 3<\/u> \u2014 opsioni m\u00eb ekstrem. N\u00eb faz\u00ebn e rinovimit, t\u00eb gjitha komunikimet vendosen dhe t\u00eb gjitha sistemet dublohen. Avantazhet: gjith\u00e7ka arrihet n\u00eb ideal e k\u00ebshtu sht\u00ebpia b\u00ebhet v\u00ebrtet e men\u00e7ur. Disavantazhet: kostoja e lart\u00eb krahasuar me kategorit\u00eb 1 dhe 2, nevoja p\u00ebr t\u00eb parashikuar gjith\u00e7ka paraprakisht dhe p\u00ebr t\u00eb marr\u00eb parasysh \u00e7do detaj.<\/p>\n

Shumica e p\u00ebrdoruesve zgjedhin opsionin e par\u00eb dhe pastaj kalojn\u00eb gradualisht n\u00eb opsionin e dyt\u00eb. Nd\u00ebrsa m\u00eb pas, ata m\u00eb t\u00eb q\u00ebndruesh\u00ebm arrijn\u00eb n\u00eb opsionin 3. <\/p>\n

Por ekziston nj\u00eb opsion, i cili mund t\u00eb quhet sistem i shp\u00ebrndar\u00eb: \u00e7do pajisje e ve\u00e7ant\u00eb do t\u00eb jet\u00eb dhe server dhe klient. N\u00eb thelb, kjo \u00ebsht\u00eb nj\u00eb p\u00ebrpjekje p\u00ebr t\u00eb marr\u00eb dhe bashkuar opsionin 1 dhe opsionin 2. T\u00eb merret t\u00eb gjitha p\u00ebrpar\u00ebsit\u00eb e tyre dhe t\u00eb p\u00ebrjashtohen disavantazhet, p\u00ebr t\u00eb kapur nj\u00eb mesatare t\u00eb art\u00eb. <\/p>\n

Mund t\u00eb ndodh\u00eb, q\u00eb dikush t\u00eb thot\u00eb se ky opsion \u00ebsht\u00eb tashm\u00eb zhvilluar. Por k\u00ebto zgjidhje jan\u00eb t\u00eb orientuara ngusht\u00eb; p\u00ebr njer\u00ebzit t\u00eb njohur me programimin. Q\u00ebllimi yn\u00eb \u00ebsht\u00eb t\u00eb ulin shkall\u00ebn e hyrjes n\u00eb k\u00ebto sisteme t\u00eb shp\u00ebrndara si n\u00eb form\u00ebn e pajisjeve p\u00ebrfundimtare, ashtu edhe n\u00eb form\u00ebn e integrimit t\u00eb pajisjeve ekzistuese n\u00eb sistemin ton\u00eb. N\u00eb rastin e termostatit, p\u00ebrdoruesi thjesht heq termostatin e tij t\u00eb vjet\u00ebr,_instalon at\u00eb t\u00eb men\u00e7ur dhe lidh sensor\u00ebt q\u00eb ka me t\u00eb. Pa ndonj\u00eb veprim t\u00eb m\u00ebtejsh\u00ebm.<\/p>\n

Le t\u00eb shqyrtojm\u00eb integrimin n\u00eb sistemin ton\u00eb me nj\u00eb shembull. <\/p>\n

Imagjinojm\u00eb se kemi 8 module Sonoff n\u00eb rrjet. Disa p\u00ebrdorues do t\u00eb jen\u00eb t\u00eb mjaftuesh\u00ebm p\u00ebr t\u00eb menaxhuar p\u00ebrmes re Sonoff (kategoria 1). Disa do t\u00eb p\u00ebrdorin softuer t\u00eb jasht\u00ebm dhe do t\u00eb kalojn\u00eb gradualisht n\u00eb kategorin\u00eb 2. Shumica e firmuer\u00ebve t\u00eb jasht\u00ebm funksionojn\u00eb sipas t\u00eb nj\u00ebjtit parim: transmetimi i t\u00eb dh\u00ebnave n\u00eb serverin MQTT. OpenHub, Majordomo ose ndonj\u00eb sh\u00ebrbim tjet\u00ebr sh\u00ebrben p\u00ebr nj\u00eb q\u00ebllim t\u00eb vet\u00ebm - t\u00eb bashkoj\u00eb pajisjet e shp\u00ebrndara n\u00eb nj\u00eb hap\u00ebsir\u00eb informacioni t\u00eb integruar, e cila ndodhet ose n\u00eb internet, ose n\u00eb nj\u00eb rrjet lokal. Prandaj, ekzistenca e nj\u00eb Serveri \u00ebsht\u00eb e domosdoshme. Nga k\u00ebtu lind problemi kryesor - n\u00eb rastin e d\u00ebshtimit t\u00eb Serverit, e gjith\u00eb sistema ndalon s\u00eb funksionuari autonomisht. P\u00ebr t\u00eb parandaluar k\u00ebt\u00eb, sistemet komplikohet, duke shtuar metoda manuale t\u00eb menaxhimit, t\u00eb cilat dyfishojn\u00eb automatik\u00ebn n\u00eb rast d\u00ebshtimi t\u00eb Serverit. <\/p>\n

Ne kemi ndjekur nj\u00eb rrug\u00eb tjet\u00ebr, ku \u00e7do pajisje \u00ebsht\u00eb e pavarur. K\u00ebshtu, Serveri nuk luan nj\u00eb rol t\u00eb r\u00ebnd\u00ebsish\u00ebm, p\u00ebrve\u00e7se zgjeron funksionalitetin.<\/p>\n

Le t\u00eb kthehemi n\u00eb eksperimentin mendor. S\u00ebrish t\u00eb marrim t\u00eb nj\u00ebjtat 8 module Sonoff dhe t\u00eb instalojm\u00eb n\u00eb to firmuerin Lytko. N\u00eb t\u00eb gjitha firmuer\u00ebt Lytko \u00ebsht\u00eb implementuar funksioni SSDP<\/a><\/noindex>. SSDP - nj\u00eb protokoll rrjeti, i bazuar n\u00eb nj\u00eb grup protokolesh t\u00eb Internetit, q\u00eb sh\u00ebrben p\u00ebr shpalljen dhe zbulimin e sh\u00ebrbimeve rrjeti. P\u00ebrgjigjja n\u00eb k\u00ebrkes\u00eb mund t\u00eb jet\u00eb standarde ose e zgjeruar. Ne e kemi vendosur n\u00eb k\u00ebt\u00eb p\u00ebrgjigje, p\u00ebrve\u00e7 funksioneve standarde, krijimin e nj\u00eb liste pajisjesh n\u00eb rrjet. K\u00ebshtu, pajisjet gjejn\u00eb nj\u00ebra-tjetr\u00ebn, dhe secila prej tyre do t\u00eb ket\u00eb nj\u00eb list\u00eb t\u00eb till\u00eb. Nj\u00eb shembull i listes SSDP:<\/p>\n

"ssdpList": \n\t{\n\t\t"id": 94967291,  \n\t\t"ip": "192.168.x.x",\n                "type": "thermostat"\n\t}, \n\t{\n\t\t"id": 94967282,\n\t\t"ip": "192.168.x.x",\n                "type": "thermostat"\n\t}<\/code><\/pre>\n
\nSi\u00e7 shihet nga shembulli, lista p\u00ebrfshin id e pajisjeve, adres\u00ebn ip n\u00eb rrjet, llojin e nj\u00ebsis\u00eb (n\u00eb rastin ton\u00eb - termostat i bazuar n\u00eb Sonoff). Kjo list\u00eb p\u00ebrdit\u00ebsohet nj\u00eb her\u00eb n\u00eb dy minuta (kjo periudh\u00eb \u00ebsht\u00eb e mjaftueshme p\u00ebr t\u00eb reaguar ndaj ndryshimeve dinamike n\u00eb numrin e pajisjeve n\u00eb rrjet). K\u00ebshtu, ne monitorojm\u00eb shtimin, ndryshimin dhe shk\u00ebputjen e pajisjeve pa ndonj\u00eb veprim nga ana e p\u00ebrdoruesit. Kjo list\u00eb d\u00ebrgohet n\u00eb shfletuesin ose aplikacionin mobil, dhe skripti vet\u00eb formon nj\u00eb faqe me numrin e specifikuar t\u00eb nj\u00ebsive. \u00c7do nj\u00ebsia korrespondon me nj\u00eb pajisje\/sensorr\/kontrollues. Vizualisht lista duket k\u00ebshtu:<\/p>\n
\"Lytko
\n
\nPor n\u00ebse esp8266\/esp32 jan\u00eb t\u00eb lidhur me sensorr\u00eb t\u00eb tjer\u00eb radio p\u00ebrmes cc2530 (ZigBee) ose nrf24 (MySensors)? <\/p>\n
Rreth projekteve<\/h3>\n
\nN\u00eb treg ka sisteme t\u00eb ndryshme t\u00eb shp\u00ebrndara. Sistemi yn\u00eb lejon integrimin me sistemet m\u00eb t\u00eb njohura. <\/p>\n
M\u00eb posht\u00eb jan\u00eb projekte q\u00eb n\u00eb nj\u00eb far\u00eb m\u00ebnyre p\u00ebrpiqen t\u00eb ndryshojn\u00eb situat\u00ebn me moskompatibilitetin e prodhuesve t\u00eb ndrysh\u00ebm me nj\u00ebri-tjetrin. K\u00ebto, p\u00ebr shembull, jan\u00eb SLS Gateway<\/a><\/noindex>, MySensors <\/a><\/noindex> ose ZESP32<\/a><\/noindex>. ZigBee2MQTT <\/a><\/noindex> \u00ebsht\u00eb e lidhur me serverin MQTT, prandaj nuk p\u00ebrshtatet p\u00ebr shembullin. <\/p>\n
Nj\u00eb nga m\u00ebnyrat e realizimit t\u00eb MySensors \u00ebsht\u00eb nj\u00eb port\u00eb e bazuar n\u00eb ESP8266. shembujt e tjer\u00eb jan\u00eb n\u00eb ESP32. N\u00eb to mund t\u00eb implementojm\u00eb parimin ton\u00eb t\u00eb funksionimit p\u00ebr t\u00eb zbuluar dhe krijuar nj\u00eb list\u00eb pajisjesh. <\/p>\n
Le t\u00eb kryejm\u00eb nj\u00eb eksperiment tjet\u00ebr mendor. Kemi nj\u00eb port\u00eb ZESP32 ose SLS Gateway, ose MySensors. Si mund t'i bashkojm\u00eb ato n\u00eb nj\u00eb hap\u00ebsir\u00eb t\u00eb vetme informacioni? N\u00eb funksionet standarde t\u00eb k\u00ebtyre porteve do t'i shtojm\u00eb bibliotek\u00ebn e protokollit SSDP. Kur i qasen k\u00ebtij kontrolluesi p\u00ebrmes SSDP, ai do t'i shtoj\u00eb p\u00ebrgjigjes standarde nj\u00eb list\u00eb pajisjesh q\u00eb jan\u00eb lidhur me t\u00eb. Bazuar n\u00eb k\u00ebt\u00eb informacion, shfletuesi do t\u00eb formoj\u00eb nj\u00eb faqe. N\u00eb p\u00ebrgjith\u00ebsi, kjo do t\u00eb duket k\u00ebshtu:<\/p>\n
\"Lytko
\nNd\u00ebrfaqja Web<\/i><\/p>\n
\"Lytko
\nPWA-aplikacion<\/i><\/p>\n
"ssdpList": \n{\n   "id": 94967291, \/\/ \u0443\u043d\u0438\u043a\u0430\u043b\u044c\u043d\u044b\u0439 \u0438\u0434\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0442\u043e\u0440 \u0443\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432\u0430\n   "ip": "192.168.x.x", \/\/ ip \u0430\u0434\u0440\u0435\u0441 \u0432 \u0441\u0435\u0442\u0438\n   "type": "thermostat" \/\/ \u0442\u0438\u043f \u0443\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432\u0430\n},\n{\n   "id": 94967292,\n   "ip": "192.168.x.x",\n   "type": "thermostat"\n},\n{\n   "id": 94967293,\n   "ip": "192.168.x.x",\n   "type": "thermostat"\n},\n{  \n   "id": 13587532, \n   "type": "switch"  \n},\n{  \n   "id": 98412557, \n   "type": "smoke"\n},\n{  \n   "id": 57995113, \n   "type": "contact_sensor"\n},\n{  \n   "id": 74123668,\n   "type": "temperature_humidity_pressure_sensor"\n},\n{\n    "id": 74621883, \n    "type": "temperature_humidity_sensor"\n}\n<\/code><\/pre>\n
\nNga shembulli shihet se pajisjet shtohen n\u00eb m\u00ebnyr\u00eb t\u00eb pavarur nga nj\u00ebra-tjetra. Jan\u00eb lidhur 3 termostat\u00eb me adresat e tyre ip dhe 5 sensore t\u00eb ndrysh\u00ebm me id t\u00eb ve\u00e7ant\u00eb. N\u00ebse sensori \u00ebsht\u00eb i lidhur n\u00eb rrjetin Wi-Fi, ai do t\u00eb ket\u00eb ip t\u00eb tij, n\u00ebse \u00ebsht\u00eb i lidhur me port\u00ebn, at\u00ebher\u00eb adresa ip e pajisjes do t\u00eb jet\u00eb ajo e port\u00ebs.<\/p>\n
P\u00ebr komunikimin me pajisjet ne p\u00ebrdorim WebSocket. Kjo ndihmon p\u00ebr t\u00eb minimizuar shpenzimet e burimeve krahasuar me k\u00ebrkesat get dhe p\u00ebr t\u00eb marr\u00eb informacion dinamikisht gjat\u00eb lidhjes ose ndryshimit. <\/p>\n
T\u00eb dh\u00ebnat merren drejtp\u00ebrdrejt nga ajo pajisje, e cila i p\u00ebrket bllokut, duke anashkaluar serverin. N\u00eb k\u00ebt\u00eb m\u00ebnyr\u00eb, n\u00eb rast t\u00eb mosfunksionimit t\u00eb ndonj\u00eb pajisje, sistemi vazhdon t\u00eb funksionoj\u00eb. N\u00eb nd\u00ebrfaqen web vet\u00ebm pajisja e humbur nuk do t\u00eb shfaqet n\u00eb list\u00eb. Por sinjali p\u00ebr humbjen, n\u00ebse \u00ebsht\u00eb e nevojshme, do t\u00eb vij\u00eb si nj\u00eb njoftim n\u00eb aplikacionin e p\u00ebrdoruesit. <\/p>\n
P\u00ebrpjekja e par\u00eb p\u00ebr t\u00eb realizuar nj\u00eb qasje t\u00eb till\u00eb ishte aplikacioni PWA. Ky aplikacion mund\u00ebson ruajtjen e baz\u00ebs s\u00eb bllokut n\u00eb pajisjen e p\u00ebrdoruesit dhe k\u00ebrkon vet\u00ebm t\u00eb dh\u00ebnat e nevojshme. Por p\u00ebr shkak t\u00eb ve\u00e7orive t\u00eb struktur\u00ebs, ky variant \u00ebsht\u00eb i pamjaftuesh\u00ebm. Dhe zgjidhja \u00ebsht\u00eb nj\u00eb aplikacion natyror p\u00ebr Android dhe IOS, i cili tani \u00ebsht\u00eb n\u00eb zhvillim aktiv. N\u00eb parazgjedhje, aplikacioni do t\u00eb funksionoj\u00eb vet\u00ebm n\u00eb rrjetin e brendsh\u00ebm. N\u00ebse \u00ebsht\u00eb e nevojshme, gjith\u00e7ka mund t\u00eb kaloj\u00eb n\u00eb menaxhimin e jasht\u00ebm. K\u00ebshtu, kur p\u00ebrdoruesi largohet nga rrjeti lokal, aplikacioni automatikisht kalon n\u00eb cloud. <\/p>\n
Menaxhimi nga jasht\u00eb \u00ebsht\u00eb nj\u00eb kopjim i plot\u00eb i faqeve. Kur aktivizohet faqja, p\u00ebrdoruesi mund t\u00eb hyj\u00eb n\u00eb server dhe t\u00eb menaxhoj\u00eb pajisjet p\u00ebrmes llogaris\u00eb personale. K\u00ebshtu, Serveri zgjeron funksionalitetin, duke lejuar menaxhimin e pajisjeve p\u00ebrtej sht\u00ebpis\u00eb dhe duke e b\u00ebr\u00eb t\u00eb pavendosur lidhjen me portet ose adresat IP t\u00eb dedikuara.<\/p>\n
N\u00eb k\u00ebt\u00eb m\u00ebnyr\u00eb, varianti i p\u00ebrshkruar m\u00eb lart \u00ebsht\u00eb pa disavantazhet e qasjes server dhe ka nj\u00eb s\u00ebr\u00eb p\u00ebrfitimesh si fleksibiliteti i lidhjes s\u00eb pajisjeve t\u00eb reja.<\/p>\n
P\u00ebr termostatin<\/h3>\n
\nLe t\u00eb shqyrtojm\u00eb sistemin e menaxhimit duke p\u00ebrdorur termostatin ton\u00eb si shembull.<\/p>\n
Parashikohet:<\/p>\n
    \n
  1. Rregullimi i temperatur\u00ebs s\u00eb secilit termostat (shfaqet si nj\u00eb bllok i ve\u00e7ant\u00eb);<\/li>\n
  2. Caktoni orarin e pun\u00ebs s\u00eb termostatit (m\u00ebngjes, dit\u00eb, mbr\u00ebmje, nat\u00eb);<\/li>\n
  3. Zgjedhja e rrjetit Wi-Fi dhe lidhja e pajisjes me t\u00eb;<\/li>\n
  4. P\u00ebrdit\u00ebsimi i pajisjes \"n\u00eb aj\u00ebr\";<\/li>\n
  5. Caktoni MQTT;<\/li>\n
  6. Caktoni rrjetin me t\u00eb cilin \u00ebsht\u00eb lidhur pajisja.<\/li>\n<\/ol>\n
    \n\"Lytko
    \n
    \nP\u00ebrve\u00e7 menaxhimit p\u00ebrmes nd\u00ebrfaqes web, \u00ebsht\u00eb parashikuar menaxhimi klasik \u2014 me prekje t\u00eb ekranit. N\u00eb bord \u00ebsht\u00eb nj\u00eb monitor Nextion NX3224T024 2.4 in\u00e7. Zgjedhja ra mbi t\u00eb p\u00ebr shkak t\u00eb thjesht\u00ebsis\u00eb s\u00eb p\u00ebrdorimit t\u00eb pajisjes. Por \u00ebsht\u00eb n\u00eb zhvillim nj\u00eb monitor i vet\u00ebp\u00ebrgatitur mbi baz\u00ebn e STM32. Funksionaliteti i tij nuk \u00ebsht\u00eb aspak m\u00eb i keq se ai i Nextion, por do t\u00eb kushtoj\u00eb m\u00eb pak, q\u00eb do t\u00eb ndikoj\u00eb pozitivisht n\u00eb \u00e7mimin p\u00ebrfundimtar t\u00eb pajisjes.<\/p>\n
    \"Lytko
    \n
    \nSi \u00e7do ekran i nderuar i termostatit, Nextion yn\u00eb di t\u00eb:<\/p>\n