Weather and Legacy Remote Resources
The current active source is the single "Seniverse weather" live component on the device screen. Legacy remote MQTT channels, custom HTTP sources, and multi-weather sources have exited the active configuration; do not keep creating remote switches, scenes, or writable values per the early documentation.
Configuring Weather
In the "Device Screen" Seniverse weather component, configure the city and API Key, and choose automatic refresh every 15, 30, or 60 minutes. The source is fixed to seniverse, the live now.json endpoint, and Celsius units; custom URLs, three-day forecasts, and arbitrary JSON path reads are not provided. The API Key is a private credential — public examples and reports must not contain real values.
The firmware must be compiled with remoteResources, depends on network, time, and resource admission, and reports availability per device state. Sources and credentials from old configurations are kept as migration material; after confirming a kept Seniverse source or creating a new one, the system normalizes to at most one active weather source. If a removed source is still referenced by rules — including disabled rules — migration rejects it and requires adjusting the references first; configuration is not silently dropped.
Refresh and Display
Manual refresh and rule action 34 only request an update from the configured source, subject to the minimum interval and pending state. accepted=true only means the request was received; continue to check pending, the result, the original sample time, and quality. Throttling, no network, service errors, and expired results must not be disguised as fresh weather with zero values. Repeated refreshes do not extend the validity of an old sample.
For action 34, targetPeriphId is the actual weather source ID returned by the device, and actionValue must be empty. Do not fill in a URL, and do not use it to query MQTT channels.
Current Endpoints
| Path | Method and purpose |
|---|---|
/api/screen-panel/weather | GET to view; POST to save weather configuration |
/api/screen-panel/weather/refresh?id=<sourceId> | POST to request refresh; GET to view refresh state |
/api/remote-resources | GET/POST both return 410; legacy endpoint retired |
/api/remote-resources/weather-test | GET/POST both return 410; legacy test endpoint retired |
Endpoints require login; saving and refresh state/request also require the developer-mode feature to be enabled. Saving uses the version returned by the device; on conflict a 409 is returned — refresh the configuration first. The full configuration body is limited to 8 KiB.
Handling Legacy Rules
Action 33 keeps its ID only to recognize retired configurations and cannot execute remote channel control. Rules bound to the legacy remote. data sources or ds:remote. events pause the entire rule, including other OR triggers in it. Check the rule state and pause reason before modifying, re-select the current source and action, and do not auto-switch to another device. This protection does not mean the actual state of legacy remote loads has been confirmed.
For screen cards and weather state, see Device Screen; for local sensor display, see Display Actions.