FAQ

Installation and network

The LCD shows NO-LAN and a red LED. No IP: check the Ethernet cable, the PoE switch port, and whether the gateway’s DHCP is running (journalctl -u dnsmasq -f on the gateway).

The LCD shows NO-MQTT and a yellow LED. Ethernet is up, the broker is unreachable. Gateway mode: make sure the gateway’s Mosquitto is running (docker compose ps) and the firewall is not blocking. Also make sure the router on the LAN is the DC Gateway; if not, set mqtt_host to the broker address.

The LCD shows AUTH!. The broker rejected the credentials or client_id. In direct mode check mqtt_user and mqtt_pass, and that the device is connected to the channel with the publish type. The node retries every 60 seconds.

Data does not appear in Celestian although the LCD says ONLINE. Make sure the gateway has a publish connection to the channel, the channel has a storage rule, and the Sentinel is registered as a device with Serial = MAC (Using Sentinel in Celestian).

The time in Celestian is wrong or data is flagged “Estimated time”. The node is not getting NTP, or the gateway has no NTP upstream. Check chronyc tracking on the gateway, and ntp_server_effective in the configuration report. Telemetry without a synchronized clock uses receive time.

I do not know the Sentinel’s IP or MAC. On the LCD, press OK, then Jaringan (IP) and Device (MAC). Or look at the DHCP table on the gateway. The web interface opens at http://sentinel-<last 6 digits of MAC>.local.

Sensors

Temperature does not appear / -- on the LCD. The DS18B20 is not being read: check the data wire and the 4.7 kΩ pull-up to 3V3. Run rescan and see whether the sensor is listed in discovered. A slot with tN_en = false or whose sensor is not yet bound is not shown.

A new sensor did not go into the slot I wanted. Automatic binding picks the lowest empty slot. Bind manually with tN_rom (Temperature sensors).

A digital input is not read. All inputs are off by default; set dN_type (not off). If the value is inverted, swap dN_active (high / low).

voltage: null or power metrics are missing. The PZEM-004T is not connected or not answering. Check the UART wiring and level shifter, or set pzem = false if it is not used.

The LCD is blank or not detected, i2cscan shows every address answering. The I2C pull-ups are too strong (PCF8574 modules often carry 1 kΩ pull-ups). Remove the pull-up resistors on the PCF8574 module (Hardware).

The touch buttons do not respond. Check expander_ok: false means the PCF8574 is not answering; match exp_addr with the module’s A0…A2 pads. The TTP223 does not work through a metal plate.

Alarms and configuration

The alarm does not sound. Make sure its limit is set (not 0), alarm_buzzer = true, maintenance mode is not active, and the condition persisted beyond alarm_delay_s. A new alarm sounds again after being silenced with BACK.

The alarm does not stop after the value is normal. An alarm ends after the value returns past the limit by the hysteresis (temp_alarm_hyst_c, 2% for power). An unreadable sensor does not change alarm status.

My configuration does not apply. Compare cfg_ver in config/reported with the one sent, and look at rejected for the reason per key (Config and reports). Remember: configuration from the server can overwrite changes made in the web on every reconnect.

After a reset, the old rack’s settings came back. Celestian re-sends the last configuration and rules to a node with an older cfg_ver. Replace or empty the configuration in Celestian first (Reset and moving racks).

Renaming a sensor broke the graph. The name becomes the metric name; renaming starts a new data series. To move a function to another slot, swap names between slots (the series is not broken).

Web and firmware

Forgot the web password. Only a factory reset returns it to default (sentinel): the touch sequence, reset_factory over USB serial. This also erases settings (Reset and moving racks).

The web says someone signed in from another device. Only one session at a time; another login takes over. A session also ends after 10 minutes without activity.

A firmware update returned to the old version. A new image is rolled back if Ethernet and MQTT are not stable for 60 seconds (or, through the web, you did not log in). fw_rolled_back names the cancelled version. The node does not install the same version again until fw_version is changed (Firmware and OTA).

image untuk model lain. The firmware file is for a different model. Use edge-snt-g1-idf-<version>.bin for SNT-G1.

Modbus

A source has status no_response. Check in order: A/B wires swapped, slave address, baud and parity, 120 Ω termination, 0- or 1-based register address (Modbus sources).

A source is rejected with melebihi batas metrik. The 400-metric or message size limit was exceeded; use short prefixes and compact profiles (Capacity).

A telemetry message is not sent, oversize_dropped rises. The message exceeds 12,086 B. Reduce metrics, shorten names, or use telemetry groups.

A rule using a Modbus metric is not active. That rule is dormant while the metric does not yet exist (see rules/reported.dormant); once its source runs and produces a value, the rule is evaluated.