Universal Tuya docsHomeSupported devicesRequest a deviceFAQChangelogArchitectureKnowledge baseCreditsSourcesContributing

P3072 — Wi-Fi devices: one IP, follow IP changes, honest repair

Status: master (soak), then port. Ideas credited in CREDITS.md (tuya-local, localtuya, tinytuya); text and code are ours.

Problem

What changed

StepChangeWhere
AOne effective IP (effectiveIp), every write mirrored to all keys present, one-time boot heal; onSettings reconnects with the new valueslib/tuya-local/LocalIpSettings.js, TuyaLocalDevice.js
ARepair handlers for wifi_ir_remote and eWeLink/Sonofflib/ewelink-local/eweLinkRepair.js
A'wifi_sonoff_* extend EweLinkLocalDriver (pair + repair + mDNS), own flow cards keptdrivers/wifi_sonoff_*/driver.js
BLanRebindRouter: UDP device-found/device-updated → mirror IP + rebind live client (onLanIpChanged or updateIP); 60 s cooldown per device; 256-entry table; never throws; legacy loop kept as fallbacklib/wifi/LanRebindRouter.js, app.js
CRepair status line (connected, IP, protocol, UDP last seen, IP mismatch, last error, key present — never the key) and Find device on the network (one burst probe, ≤15 s, adopts the answering IP)lib/tuya-local/LanRepairStatus.js, 32 Tuya repair views

Rules kept

Tests

test/critical/p3072-wifi-repair-coherence.test.js, p3072-sonoff-lan-pairing.test.js, p3072b-lan-rebind-router.test.js (includes a 20 000-announcement soak), p3072c-lan-repair-status.test.js.

User-facing

docs/user/FAQ_WIFI_LOCAL.md §2 and §9.

← Knowledge base index · source