iobroker-community-adapters / ioBroker.shelly

Integrate your Shelly devices into ioBroker via MQTT or CoIoT
Other
162 stars 64 forks source link

[Bug]: After update to 7.0.0 the Adapter spams [onFileChange] Log Messages #979

Open esusxunil opened 4 months ago

esusxunil commented 4 months ago

I'm sure that

Shelly device

Shelly EM

Shelly firmware version

20230913-114150/v1.14.0-gcb84623

Protocol

CoAP / CoIoT

The problem

Ich habe zwei Instanzen des Adapters laufen, einmal für MQTT, einmal für das letzte VErbliebende CoAp Gerät den Shelly EM.

Nach dem Update auf 7.00 schmiest diese CoAp Instanz folgende Fehlermeldungen:

shelly.0 | 2024-05-08 09:21:46.164 | error | [onFileChange]: id: shelly.0, fileName: httpDebug/shellyem-A4E57CBA9CB8/_status.json, size: 970
shelly.0 | 2024-05-08 09:21:31.096 | error | [onFileChange]: id: shelly.0, fileName: httpDebug/shellyem-A4E57CBA9CB8/_settings_relay_0.json, size: 134
shelly.0 | 2024-05-08 09:21:31.030 | error | [onFileChange]: id: shelly.0, fileName: httpDebug/shellyem-A4E57CBA9CB8/_settings.json, size: 1978

Vollständiges Log habe ich angehängt

iobroker.current.log (in debug mode!)

shelly.log

Version of nodejs

18.20.2

Version of ioBroker js-controller

5.0.19

Version of adapter

7.0.0

github-actions[bot] commented 4 months ago

Thanks for reporting a new issue @esusxunil!

  1. Please make sure 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!

    Otherwise this issue will be closed.

klein0r commented 4 months ago

Danke, das Loglevel der Meldung ist falsch gewesen. Aber warum hast Du httpDebug aktiviert? Suchst Du einen Fehler?

esusxunil commented 4 months ago

Gute Frage, war mir garnicht aufgefallen - vielen dank.

Imperial929 commented 2 months ago

Any news when the new version of the adapter (probably 7.0.1) will come out officially? Asking because 7.0.0 is from April and since then some issues have already been fixed :)