How shivthakar18/sentry works
SENTRY is an early smart-home display project. Its implemented runtime is the Philips Hue adapter, which exchanges device data and commands through MQTT; the broker is configured in the repository. The README describes a future FastAPI core and React touch UI, so these appear as planned components rather than inspected implementations. The Hue excerpt shows API access, state merging, and MQTT publishing, but omits much of the adapter’s orchestration; uncertain internal links are omitted.
Main entry points: mosquitto.conf Mosquitto broker · main.py Hue adapter · ui Touch UI · send_mqtt.py MQTT debug CLI
Components 13
Hue integration
- Hue adapter
adapters/hue/main.py - State merging
adapters/hue/main.py
MQTT messaging
- Mosquitto broker
deploy/config/mosquitto.conf - Device topics
- MQTT debug CLI
adapters/send_mqtt.py
Core and interface
- FastAPI core
- Device registry
- Scenes and automations
- Touch UI
ui
Other components
- Home user
- Hue Bridge
- Hue lights
- Touch display
Connections 12
- Hue adapter → Hue Bridge: reads and controls
adapters/hue/main.py - Hue adapter → Hue lights: publishes device data
README.md - Hue adapter → State merging: merges updates
adapters/hue/main.py - Hue adapter → Mosquitto broker: exchanges MQTT
README.md - Mosquitto broker → Device topics: routes messages
README.md - MQTT debug CLI → Mosquitto broker: publishes commands
adapters/send_mqtt.py - FastAPI core → Mosquitto broker: subscribes and publishes
README.md - Mosquitto broker → Device registry: updates device state
README.md - FastAPI core → Scenes and automations: manages
README.md - Touch UI → FastAPI core: uses HTTP/WebSocket
README.md - Home user → Touch UI: interacts with
README.md - Touch UI → Touch display: runs on
README.md