search

DrozmotiX / ioBroker.esphome

Control your ESP8266/ESP32 with simple yet powerful configuration files created and managed by ESPHome
MIT License
30 stars 23 forks source link

Failure: Invalid wire type #200

Open j-r79 opened 7 months ago

j-r79 commented 7 months ago

I use some devices with esphome in iobroker which have all the same problem. For many days everything works without any problem, but then this message pops up every second in the log:

ESPHome client 192.168.100.145 Error: Failure: Invalid wire type: %s (at position %s)

I can fix the problem by removing the device in the instance settings (ip & delete device) and adding it again. Then it will work again for some days...

Versions:

j-r79 commented 7 months ago

If i press the update-button when the error is active, the adapter crashes:

`esphome.0 2024-03-01 07:45:10.553 error sendMessage timeout waiting for HelloResponse esphome.0 2024-03-01 07:45:10.553 error Error: sendMessage timeout waiting for HelloResponse at Timeout. (/opt/iobroker/node_modules/@2colors/esphome-native-api/lib/connection.js:201:20) at listOnTimeout (node:internal/timers:569:17) at process.processTimers (node:internal/timers:512:7) esphome.0 2024-03-01 07:45:10.552 error unhandled promise rejection: sendMessage timeout waiting for HelloResponse esphome.0 2024-03-01 07:45:10.551 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

esphome.0 2024-03-01 07:45:05.572 error ESPHome client 192.168.100.145 Error: Failure: Invalid wire type: %s (at position %s)`

After the crash the esphome-device is working again:

ESPHome client 192.168.100.145 connected

DutchmanNL commented 4 months ago

is this still happening and reproducible ? the error itself I cannot solve at its an dependency but the adapter crash should defiantly NOT happen and I have to troubleshoot that + implement proper error handling. but need someone who can test and reproduce :)

j-r79 commented 4 months ago

Yes, it still happens. I can not force it but i wrote a script which reads the iobroker log an restarts the instance if the error is written into the log.

DutchmanNL commented 4 months ago

Yes, it still happens. I can not force it but i wrote a script which reads the iobroker log an restarts the instance if the error is written into the log.

would it be possible to activate debug logging to track & trace it until the crash ? I would need the last 20 log entries before the crash