DeepSeek Harness Meets Street Light Monitoring: One Sentence to Check Lamps, Alarms, and Tickets

Stop Clicking Between Lists, Alarms, and Tickets

Street light operators used to hop between the device list, the alarm page, and the work-order queue. DeepSeek Harness (dsh) is now embedded in the "IoT / DSH" menu of the street light monitoring console, so you can check lamps, review alarms, and track tickets with a single sentence. Switching and dimming still require confirmation — the model never operates field equipment on its own.

How It Is Connected

The monitoring platform stays exactly as it is; dsh is only a conversational entry point. Its tools call the existing IoT interfaces — devices, alarms, work orders, projects, and telemetry — so no second business database is introduced.

Local development: start dsh web (it listens on http://127.0.0.1:3080) and point VITE_DSH_URL to it
Production: the release machine's Nginx adds a /dsh/ reverse proxy to local port 3080 (the same pattern as the existing /fuxa), and the admin console embeds it through a same-origin iframe
Trial address: https://ludengjiankong.com/dsh

What You Can Ask

Which lamps are online and which are offline
The detail and latest telemetry of one lamp (for example CA-Y2-001)
Unhandled alarms, pending work orders, and the project list

Queries execute automatically. Switching goes through iot_set_lamp_switch: a preview is shown first, and the lamp_switch property (0 = off, 1 = on) is issued only after confirmation. A device must be on the LUDENG_CONTROL_ALLOWED_DEVICE_IDS whitelist; an empty whitelist rejects all commands. After the command, the latest property is read back and written to the audit log. Dimming follows the same pattern — this release covers switching first. Production interfaces are not exposed to the public network.

Try It

Visit https://ludengjiankong.com/dsh and ask "which lamps are offline" or "show the latest report of CA-Y2-001" — the answer comes back directly.

— cassan (cassan.cn)