ioBroker/ioBroker.hm-rpc

Lot off logentries hm-rpc.1.CENTRAL.PONG discarded, no matching device

dedeha1 opened this issue · 2 comments

Describe the bug
Lot of entries in the log with the information:
xmlrpc <- event: hm-rpc.1.CENTRAL.PONG:IoBroker1:hm-rpc.1:c09c4bbb552545804e1e044a4722b4f8 discarded, no matching device
I didn't know if this appears after upgrade of hm-rpc or after upgrade JS-Controller.

Expected behavior
This is a fault and it should not end in the log.

Versions:

  • hm-rpc version: 1.15.18
  • hm-rega version: 3.0.46
  • JS-Controller version: 4.0.24
  • Node version: 18.17.0
  • Operating system: Raspbian GNU/Linux Buster
  • CCU model: CCU3
  • CCU firmware: 3.69.7

Additional context
Add any other context about the problem here.

I also noticed this error in the log, while having connection issues. I try to summarize based on my assumption what happened:

  1. the server lost connection to raspberrymatic, which is connected via WIFI (the adapter restarts with "PING Error" in log.
  2. the adapter restarts a few times, after a few tries the connection is back and the adapter says "connected" in the log
  3. somehow the adapter now ended up in a corrupt state. When I write changes to hm-rpc objects, they are successfully transferred to the devices but not vice versa. Whenever a homematic device changes itself (door opened, button pressed) I don't get the changes into ioBroker.

This happened about 3 times in the last months, so not completely new.
The log doesn't give any errors and the adapter is green, so for me I can not identify that I have problems. Raspberrymatic itself also doesn't show any problems.
I have then increased the log level and pressed a button on a homematic device:
Fehler

Every time I press, I get the above error messages.
After restarting the adapter, it works correctly again
Reboot

It would be great if the adapter could identify this corrupt state and reboot itself.