Smart Farm

Issiqxona sensor qiymatlari uzilib yoki sakrab turadi, qurilma vaqti noto'g'ri bo'lishi mumkin, DB yoki backend qisqa to'xtasa ham o'qishlar yo'qolmasligi kerak. Tuproq quriganda odam ekranni ko'rishidan oldin nasos yoqilishi, tarmoq uzilsa ham nasos to'xtamay suv toshib ketmasligi kerak. Boshqa a'zoning fermasiga kirib bo'lmasligi esa asosiy talab.

Haqiqiy ESP32 (DHT22, capacitive tuproq namligi, BH1750 yorug'lik, suv sathi, rele + 12 V nasos) va production demo uchun simulyator bir xil yo'l bilan Mosquitto'ga (TLS 8883, QoS 1) yuboradi. NestJS 11 IoT pipeline qurilma API kaliti, payload shakli, topic ↔ deviceId mosligi, sensor egaligi va kalibrovkani tekshiradi, Redis bufer (qayta urinish, DLQ) orqali MongoDB'ga xom qiymat va 90 kunlik TTL time-series yozadi, soatlik, kunlik va oylik agregatlar quradi. Har sensor uchun Z-score anomaliya (≥ 2 warning, ≥ 3 critical), o'simlik salomatligi indeksi va Open-Meteo ob-havosi (10 daqiqalik kesh) hisoblanadi; avtomatlashtirish qoidasi aktuatorni o'zgartirsa, qurilmaga MQTT orqali RELAY_ON/OFF ketadi. Dashboard GraphQL (51 resolver) va Socket.IO orqali jonli yangilanadi, koreys, ingliz va o'zbek tillarida.

Kattalashtirish

Nima o'zgartirildi

hash + zset bufer, 30/60/120 s backoff, DLQ va qotganlarni tiklash (e49f6d32), DB xatosini "noto'g'ri kalit"dan ajratish (e49f6d32), MQTT doimiy sessiya va onApplicationBootstrap'da ulanish (c4010d09), best-effort xato logi (9ddb7dbb). DB o'chganda handler xatolari 4 tadan 0 ga tushdi. O'lchov production'da sf-outage-check.sh va sf-restart-check.sh bilan, simulyator yuklamasida (~2 xabar / 30 s).

Belgi

Signup mutation'iga memberRole: "ADMIN" yuborilsa, javob ADMIN a'zo qaytarardi (probe before).

Sabab

CreateMemberInput'da memberRole maydoni bor edi va memberModel.create(input) butun inputni yozardi; profil yangilashda MemberUpdateInput ham rol, status, email va parolni qabul qilardi. Shu auditda @Roles(MANAGER) bor, lekin @UseGuards(RolesGuard) yo'qligi sabab a'zolar ro'yxati tokensiz ochiq edi ({"total":7}), guard klass darajasidagi @Roles'ni o'qimagani uchun bufer resolverlari ham ochiq edi.

Yechim

Maydon inputdan olib tashlandi, create va $set faqat ruxsat etilgan maydonlar bilan (22a760bd); guard qo'shildi, getAllAndOverride bilan handler + klass o'qiladi, noto'g'ri token → 401.

Takrorlanmasligi uchun

Tuzatishdan oldin production'da suiiste'mol izlari tekshirildi (7 a'zo, hammasi WORKER/ACTIVE, imtiyozli 0, shubhali chaqiruv 0). member-security.spec.ts'dagi 13 testdan 12 tasi eski kodda yiqiladi; deploy'dan keyin 5 ta tashqi probe'ning hammasi rad etildi.

Testlar soni

89

Qamrov

—

CI

—

Test vositalari

Jest 30, ts-jest, 실제 redis-server, Mosquitto 2.0.18, MicroPython stub harness

Deploy muhiti

Bitta VPS'da docker-compose.prod.yml: mongo (768m), redis (128m, requirepass, AOF), mosquitto (64m, tashqariga faqat 8883 TLS, Caddy sertifikati read-only, allow_anonymous false, password file + ACL, persistence), backend (768m, faqat internal tarmoq, mongo/redis healthy bo'lgach), web (64m), device-simulator (96m, demo profili). Umumiy Caddy HTTPS'ni boshqaradi. Deploy: git pull --ff-only → build backend → up -d backend. Sirlar (MONGO_PASSWORD, REDIS_PASSWORD, MQTT_BACKEND_PASSWORD, SECRET_TOKEN) faqat serverdagi .env'da; ular yo'q bo'lsa compose va backend ishga tushmaydi.

Backup

—

Rollback

—

Monitoring

Bufer holati (pending / retrying / deadLetter) admin uchun GraphQL orqali, DLQ xabarlarini ko'rish va tozalash, Message retry scheduled / Message moved to DLQ loglari. O'zim yozgan skriptlar: sf-incident-check.sh, sf-security-probe-v2.ps1, sf-outage-check.sh, sf-restart-check.sh

• backend/apps/smart-farm/src/iot/iot-pipeline/iot-pipeline.service.ts

  MQTT qabul, qurilma auth, buferlash, har o'qishni saqlash, anomaliya, qoida baholash

• backend/apps/smart-farm/src/iot/iot-pipeline/sensor-payload.ts

  Topic'dan deviceId, envelope tekshiruvi, recordedAt oynasi

• backend/apps/smart-farm/src/mid-iot/message-buffers/message-buffers.service.ts

  Redis bufer: enqueue/ack/markFailed, backoff, DLQ, qotganlarni tiklash

• backend/apps/smart-farm/src/iot/mqtt/mqtt.service.ts

  Doimiy sessiya, onApplicationBootstrap'da ulanish

• backend/apps/smart-farm/src/actuator/actuator.service.ts

  Rele buyrug'i, nasos cheklovi, qoidani atomik egallash

• backend/apps/smart-farm/src/ownership/ownership.interceptor.ts

  Global egalik tekshiruvi, argument → resurs xaritasi, @OwnedArgs

• backend/apps/smart-farm/src/ownership/ownership.service.ts

  Resurs → ota zanjiri farm.memberId gacha

• backend/apps/smart-farm/src/account-context-module/auth/guards/roles.guard.ts

  Handler + klass rollari, 401/403

• backend/apps/smart-farm/src/account-context-module/member/member.service.ts

  Signup va profil — faqat ruxsat etilgan maydonlar

• backend/apps/smart-farm/src/account-context-module/password-reset/password-reset.service.ts

  OTP: randomInt, atomik urinish hisobi

• firmware/esp32/main.py

  Sensorlar, rele, nasos cheklovi, NTP, QoS 1 resubscribe

• deploy/mosquitto/mosquitto.conf

  TLS 8883, persistence, ACL

2026-10-10–11 auditida 9 ta tuzatish commit'i chiqarildi, har biri oldin/keyin o'lchovi bilan. MongoDB 132 s o'chirilganda 24/24 xabar saqlandi (6 qayta urinish, DLQ 0); backend 20 s to'xtatilganda 7/7 yetib keldi, backend o'chiq paytida yuborilgani broker navbatidan keldi. Eski kodda 58 s outage'da 12 dan 1 tasi, deploy restartida 1 tasi yo'qolgan edi. Xavfsizlik tekshiruvida 12+ zaiflik topilib yopildi: signup'da memberRole bilan ADMIN bo'lish (22a760bd), profil orqali ixtiyoriy maydonlarni yozish, boshqa a'zoning fermasi, sektori va alertiga kirish (c2c5ca26), OTP'ni cheksiz taxmin qilish va Math.random OTP, kodga yozilgan JWT kaliti (a5a1b62e), production'da ochiq GraphQL playground. Tuzatishdan oldin production'da suiiste'mol izlari tekshirildi (7 a'zo, imtiyozli 0, shubhali chaqiruv 0). Backend nasosni faqat DB'da yoqib, qurilmaga buyruq yubormagani (3f3eacb2) va NTP sinxronlanmagan ESP32 1970-yil vaqtini yuborgani ham tuzatildi. Birinchi gipotezam (xatolar heartbeat'dan) noto'g'ri chiqqanda log haqiqiy sababni (/sensors) ko'rsatdi; 45 s outage driver'ning 30 s kutishi sabab xato yo'lini umuman ishga tushirmagani ham hujjatlandi.