Feature status
This page is honest about how far each feature has been tested. The documentation describes behavior that is designed and tested on a computer; the status column shows the evidence on devices. Consult this page before relying on a feature in production. Applies to SNT-G1 firmware series 0.21 (October 2026).
| Feature | Status |
|---|---|
Ethernet, MQTT 5, NTP, retained configuration, SenFlat v2 telemetry, sequence number q |
Proven on a device through the gateway to Celestian |
| DS18B20 sensors (1-Wire), PZEM-004T, digital inputs, digital outputs, local alarms | Proven on a device (telemetry identical to the earlier Arduino firmware). A real door, SHT41, buzzer silencing, and outputs o2…o4 have not been physically tested |
| LCD, menu, touch buttons | Proven: display and touch seen directly |
On-device rules (rules v1), confirm_s confirmation, rules_rollback |
Proven on a device (22 confirmation scenarios passed) |
| Rules v2 (expressions, status sources, flags, schedules) | Passed computer tests; not yet tried on a device |
| OTA through the gateway, automatic rollback (crash, hang, unhealthy) | Proven on a device, including moving between two firmware generations |
| Firmware upload from the web | Proven on a device |
| Web interface: login, sessions, status, configuration, language | Partly proven (firmware upload, language, rejections); other tabs tested against a mock server, not yet entirely on a device |
| Factory reset (touch sequence, web, serial) | Logic tested on a computer; not yet tested on a device |
History in PSRAM (direct mode, hist_kb) |
Proven on a device: 61 consecutive points without duplicates after a 5-minute outage |
mqtt_mode (TLS, automatic fallback, MQTT 3.1.1) and mqtt_ca |
Logic tested on a computer; not yet tested on a device (TLS with a private CA against a server) |
| Modbus sources and profiles (SDM120, PZEM-016) on SNT-G1 | Passed computer tests with a mock bus and devices; not yet tested on a G1 board with real devices (DE/RE direction, response time, two devices at once). The PZEM-016 default address and behavior below 80 V are not yet proven |
| 40 Modbus devices at once | Capacity simulated on a computer, not measured on a board and broker |
Telemetry groups (tgroups, firmware 0.21) |
Passed computer tests; not yet released and not yet tested on a device |
| Gateway: DHCP, firewall, Mosquitto, bridge, OTA, history | Configuration passed syntax checks and runs on a temporary gateway (MacBook); not yet run on the industrial mini PC |
| WireGuard | Prepared, not yet used and not yet tested |
| UPS publisher (NUT) | Not yet tested with a real UPS |
Limitations to be aware of
Section titled “Limitations to be aware of”- No storage on the node without a gateway (gateway mode): when the gateway is unreachable, measurements during that time are lost. The queue during a WAN outage is handled by the gateway; in direct mode the node stores up to
hist_kbin RAM. - Events (door, alarm) are not stored in node history; alarm status remains in telemetry.
- The gateway’s local broker accepts anonymous connections; its security depends on rack LAN isolation.
- The web interface uses plain HTTP; the password and cookie travel as-is on the LAN.
- OTA over HTTPS does not yet verify the server certificate; OTA through the gateway uses HTTP on the rack LAN (integrity protected by SHA-256).
- Anti-cloning is not yet enabled: flash encryption and secure boot are not enabled; anyone with physical access or the web password can install firmware.
- All nodes on one gateway go into one channel.
- The reason a publish was rejected by the broker does not reach the firmware.
- The LCD is Indonesian-only; Modbus source metrics do not yet appear on the LCD.