Settings¶
Most device settings can be changed via four different paths:
- Web interface — Local UI directly on the device, reachable at
http://wattwaechter-XXXXXXXXXXXX.localfrom the same network - Smartphone app — iOS & Android (the same app used for initial setup)
- Cloud Portal — Remote access via login.wattwächter.de
- REST API — Directly over HTTP, with all technical details and JSON schemas
What does XXXXXXXXXXXX mean?
The twelve X's represent your WattWächter's individual device ID (the last 12 characters of its MAC address, hexadecimal). You can find it e.g. in the Cloud Portal or in the app.
This page explains what the individual settings do. The concrete JSON fields, endpoints and the full schema are documented in the REST API reference.
WiFi¶
Connection to your home network. By default, the WattWächter automatically connects to the stored WiFi on every boot.
| Setting | Description |
|---|---|
| Network name (SSID) | Name of the WiFi network |
| Password | WiFi password (WPA2) |
| Enabled | Whether the stored WiFi is used |
API key: wifi.primary — see REST API reference.
MQTT¶
Sends telemetry data to an MQTT broker — for example to integrate with Home Assistant, ioBroker or other smart home systems. Disabled by default.
→ All fields (broker, port, TLS, user/password, topic prefix, publish interval, CA certificate), topic structure, payload format and Home Assistant auto-discovery are documented under Interfaces → MQTT.
Status LED¶
The multicolor status LED on the device shows the current connection and error state (see LED status). It can be turned off entirely, e.g. if the device is operated in a bedroom.
API key: ledEnable — see REST API reference.
API Authentication¶
By default, the local REST API is reachable without a token to keep initial setup as simple as possible. On shared networks, we recommend enabling token-based authentication.
When enabled, there are two token levels:
- READ Token — Read data (history, status, view settings)
- WRITE Token — Change settings, start OTA updates, trigger reboot
Tokens are renewed via a two-phase process to prevent accidental lockout.
Recommendation
Enable authentication when the device is operated on a shared network or the REST API could be reachable by third parties.
API keys: api_auth_required (activation), /api/v1/auth/tokens/* (token rotation) — see REST API reference.