Zum Inhalt springen

WetterCubePlus/Diagnose und Fehlersuche/en

Aus WetterCube Wiki
Dies ist die englische Fassung. Zur deutschen Fassung

Reading /log

The cube keeps a small log in memory (the last 40 entries, empty after a restart). Open it in the browser:

Header line Meaning
Aktueller freier Heap free internal RAM, with the lowest level since start in brackets
PSRAM free external RAM (of 8 MB), lowest level, largest free block
Uptime minutes since start
LVGL-Speicher "Pool im PSRAM" with the free PSRAM
Letzter Neustart power connected, software restart (e.g. after an update), crash, watchdog or brownout
WLAN beim Start duration and signal strength, or the failure reason
WLAN jetzt network, signal strength and IP address
Standort city with coordinates (0.0000 means: not found yet)
Letzter erfolgreicher Abruf how long ago the last successful request per data source was (weather, DWD pollen, pollen/air, DWD warnings, radar, biowetter)
Update installed and latest known version, last check
Letzte /api/ampel-Anfrage how long ago the WetterAmpel last reported (normally 30 s at most)

Below are the events, newest first. Successful requests are not listed one by one (the log would fill up quickly); they appear as a time in the header instead. Failures are listed with their reason:

Entry Meaning
[Boot] v1.6.2, Neustart-Grund: … start with the restart reason
[WLAN] verbunden nach 1.6 s, Signal -61 dBm Wi-Fi is up
[WLAN] Versuch … fehlgeschlagen: … / Verbindung beim Start fehlgeschlagen, Einrichtungsmodus … Wi-Fi not reached, with reason; the portal opens next
[Start] mDNS: wettercubeplus.local, [Start] Web-UI laeuft: http://…/ name and web interface are reachable (with "mDNS konnte nicht gestartet werden" only via IP address)
[Portal] Einrichtungsmodus offen … the setup portal is on
[Geo] Suche 'Berlin' / Gefunden: 52.5200, 13.4050 the city was found
[Geo] Fehlgeschlagen für '…': kein Treffer / HTTP … / JSON-Fehler city name not found (umlauts? typo?) or no connection
[Wetter] HTTP-Fetch fehlgeschlagen: Code 503 (freeHeap=…) … weather request failed; the beginning of the server's answer follows. A second try comes after 3 s, then after 60 s
[Wetter] JSON-Parse fehlgeschlagen: … the response could not be parsed
[Pollen] DWD-Abruf fehlgeschlagen: HTTP … / DWD JSON-Fehler / DWD-Region … nicht gefunden DWD pollen forecast (3-day values)
[Pollen] Open-Meteo-Abruf fehlgeschlagen: HTTP … / JSON-Fehler pollen and air-quality data (Open-Meteo)
[Warnungen] DWD-Abruf fehlgeschlagen: HTTP … / JSON-Fehler DWD weather warnings
[Biowetter] DWD-Abruf fehlgeschlagen … / Zone … nicht gefunden biowetter
[Radar] Abruf fehlgeschlagen … / PNG-Fehler … / zu wenig PSRAM … the radar image could not be loaded or decoded
[Config] gespeichert / Standort geaendert: … changes made through the web interface
[Sicherung] … Einstellungen wiederhergestellt, Neustart settings restored from a backup
[Update] Pruefung: installiert …, verfuegbar … / Pruefung fehlgeschlagen … version check, see Updates
[Update] Neue Version verfuegbar: … a newer update is available
[OTA] Lade …, … Bytes geschrieben, Neustart / Fehler: … update running, finished or failed
[Rechner] geoeffnet, Speicher frei: … calculator opened (memory needed)

Typical values (operation): lowest heap level well above 100 KB, PSRAM peak about 1.4 MB of 8 MB.

Common problems

Problem Cause and remedy
Cube shows the setup mode although Wi-Fi was configured "WLAN-Verbindung fehlgeschlagen": the credentials are still saved. Is the router reachable? Is 2.4 GHz Wi-Fi active? The cube retries by itself every 60 seconds. The reason is in /log under "WLAN beim Start"
"Bitte den WetterCube konfigurieren" The settings are empty (e.g. after "erase device" in the web installer). Repeat the first setup
Glitches after plugging in Suspect power supply/cable: does /log say "Letzter Neustart: BROWNOUT"? Use a supply of at least 5 V / 2 A and a short cable
Wi-Fi reason "Netzwerk nicht gefunden" Name misspelled, router too far away or only 5 GHz active
Wi-Fi reason "Passwort?" Wrong password: enter it again via the portal
Update icon does not appear It only appears when a newer version is released, and only on the main screen. In the web interface "Auf Updates prüfen" forces an immediate check
Update aborts with "download error" GitHub Pages sometimes serves the new firmware only after a few minutes. Wait a moment and retry
Weather values stand still Look at /log: fetch errors are listed there with the heap level. The lowest levels show whether memory was tight
Traffic light always shows the same color Check "Letzte /api/ampel-Anfrage" in /log: well above 30 s means the light is not reporting (check Wi-Fi or the device)
Touch is off Hold a finger on the display while powering on and re-calibrate