server-development

What problem does it solve?

Centralizes and streamlines development of the God‑Kaiser server for ESP32-based IoT networks so that device logic, safety checks, data processing, and automation rules are implemented server-side instead of on constrained devices. It reduces duplication, enforces safety validation before actuator commands, and provides clear patterns for adding MQTT handlers, REST endpoints, database models, and integration tests.

Core Features & Use Cases

• Service & API Expansion: Guidance to add new FastAPI routers, Pydantic schemas, DI-based services, and repository-backed business logic.
• MQTT & Handlers: Instructions to implement and register MQTT topics, subscriber handlers, and publisher flows for sensor and actuator messages.
• Database & Migrations: Patterns for SQLAlchemy models, repository queries, and Alembic migrations while preserving unique constraints and retention policies.
• Safety, Simulation & Testing: How to use SafetyService validations, SimulationScheduler and Mock-ESP flows, and pytest integration to verify production behavior.
• Use Case: Add a new sensor type with a processing library, persist readings, expose REST endpoints, and create logic rules that trigger actuator sequences with safety gating.

Quick Start

Ask the skill to add a new FastAPI endpoint that registers an ESP device with validation, repository usage, an Alembic migration, and a corresponding integration test.