Runtime error: GET /api/states/sensor.nordpool_kwh_se2_sek_2_10_025

[Doodlehusse]

bess-debug-2026-08-18-155345.md

What happened

Operation: GET /api/states/sensor.nordpool_kwh_se2_sek_2_10_025
Category: other
Time: 2026-08-18 13:10:14

502 Server Error: Bad Gateway for url: http://supervisor/core/api/states/sensor.nordpool_kwh_se2_sek_2_10_025

Debug bundle

Please drag-and-drop bess-debug-2026-08-18-155559.md from your Downloads folder into the editor below before submitting.
The file contains your version, settings, recent logs, and the raw HA discovery dump that the maintainers need to reproduce the issue.

[bess-product-owner]

Closing as a duplicate of #643 — same incident, filed twice by the error reporter.

Both are 502 Server Error: Bad Gateway from http://supervisor/core/api/states/..., 42 seconds apart (13:10:14 and 13:10:56), from the same debug bundle. A 502 from supervisor/core means Home Assistant Core itself was unavailable — restarting or briefly wedged — so every BESS operation that touched the API in that window failed, and each one filed its own issue.

Tracking it on #643, which covers the same outage. Nothing is lost: both endpoints failing is evidence for the single root cause rather than two separate faults.

Thanks for sending both bundles — having two different endpoints fail in the same 40-second window is what makes the diagnosis unambiguous.