Instanz iob geht auf gelb; im log kommt: received 404 response from stats with content: "FileNotFound"

[bahnuhr]

I'm sure that

• This issue is still present in the current beta version of this adapter
• There is no other (open) issue with the same topic (use the search!)
• This issue is not described in the adapter documentation / FAQ (read the docs!)

Version of awtrix-light firmware

3.0.0

The problem

Habe die aktuelle V installiert.

Im iob log kommt: received 404 response from stats with content: "FileNotFound"
Und die Instanz ist gelb.

Habe noch 2 andere Instanzen installiert. Dort kommt dieser Fehler nicht.

Bitte mal Rückinfo was das sein könnte.

mfg
Dieter

iobroker.current.log (in debug mode!)

No response

Version of nodejs

22.22.1

Version of ioBroker js-controller

9.0.18

Version of adapter

3.0.0

[github-actions]

Thanks for reporting a new issue @bahnuhr!

1. Please ensure your topic is not covered in the documentation
2. Please attach all necessary log files (in debug mode!), screenshots and other information to reproduce this issue.
3. Search for the issue topic in other/closed issues to avoid duplicates!
4. Check the changelog if the issue has already been covered in a previous release

Otherwise this issue will be closed!

[bahnuhr]

Habe mal die Instanz auf debug gestellt:
im log kommt:
(stats) received error - API is now offline: {"message":"Request failed with status code 404","name":"AxiosError","stack":"AxiosError: Request failed with status code 404\n at settle (/opt/iobroker/node_modules/iobroker.awtrix-light/node_modules/axios/lib/core/settle.js:19:12)\n at IncomingMessage.handleStreamEnd (/opt/iobroker/node_modules/iobroker.awtrix-light/node_modules/axios/lib/adapters/http.js:793:11)\n at IncomingMessage.emit (node:events:531:35)\n at IncomingMessage.emit (node:domain:489:12)\n at endReadableNT (node:internal/streams/readable:1698:12)\n at processTicksAndRejections (node:internal/process/task_queues:89:21)\n at Axios.request (/opt/iobroker/node_modules/iobroker.awtrix-light/node_modules/axios/lib/core/Axios.js:45:41)\n at processTicksAndRejections (node:internal/process/task_queues:103:5)","config":{"transitional":{"silentJSONParsing":true,"forcedJSONParsing":true,"clarifyTimeoutError":false},"adapter":["xhr","http","fetch"],"transformRequest":[null],"transformResponse":[null],"timeout":3000,"xsrfCookieName":"XSRF-TOKEN","xsrfHeaderName":"X-XSRF-TOKEN","maxContentLength":-1,"maxBodyLength":-1,"env":{},"headers":{"Accept":"application/json, text/plain, */*","Content-Type":"application/json","User-Agent":"axios/1.13.2","Accept-Encoding":"gzip, compress, deflate, br"},"baseURL":"http://192.168.243.137:80/api/","responseType":"json","url":"stats","method":"get","allowAbsoluteUrls":true},"code":"ERR_BAD_REQUEST","status":404}

[bahnuhr]

Was meinst du mit "missing log"
Ist doch 1 Beitrag vor dir gepostet.
Oder meinst du was anderes ?

[klein0r]

Eine Zeile ist schon etwas wenig.

[bahnuhr]

M.e. ausreichend

[klein0r]

Der 404 Response kommt ja vom Gerät. Also Netzwerkverbindung läuft. Da ich nichtmal den Payload und die genaue URL sehen kann (weil Log fehlt), kann ich hier nicht helfen.