HM-CC-RT-DN nicht ansteuerbar via CUL

Hallo zusammen,

die Suche habe ich bereits bemüght und leider kein entsprechendes Thema gefunden.
Ich hoffe, ihr könnt einem Neuling bei Homegear helfen. Ich nutze Homegear und Openhab2 und war lange recht stabil erfolgreich.
Seit kurzem habe ich Probleme mit den Thermostaten HM-CC-RT-DN.
Das Verhalten ist wie folgt:
Nach einem kompletten löschen der Homegear-DB kann ich nach einem Pairing das erste von 5 Thermostaten normal bedienen. Wenn ich die anderen Thermostate dann auch paire tritt nach einigen Minuten bei allen Thermostaten das Problem auf, dass ich kein SET_TEMPERATURE mehr machen kann.

Das Homegear-Log mit hohem Loglevel zeigt folgende Dinge:

    01/18/18 21:51:22.482 RPC Server (Port 2001): Info: Client number 11 is calling RPC method: setValue (2) Parameters:
(String) MEQ0558727:4
(String) SET_TEMPERATURE
(Float) 22
01/18/18 21:51:22.483 Module HomeMatic BidCoS: Debug: SET_TEMPERATURE of peer 1 with serial number MEQ0558727:4 was set to 2C.
01/18/18 21:51:22.516 Debug: Thread priority successfully set to: 45
01/18/18 21:51:22.516 Module HomeMatic BidCoS: Debug: Sending packet 0C0FB011FDDD8C3A39C486042C immediately, because it seems it is no response (no packet information found).
01/18/18 21:51:22.516 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0C0FB011FDDD8C3A39C486042C
01/18/18 21:51:23.076 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0C0FB011FDDD8C3A39C486042C
01/18/18 21:51:23.636 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0C0FB011FDDD8C3A39C486042C
01/18/18 21:51:25.071 RPC Server (Port 2001): Response:
(Struct length=2)
{
  [faultCode]
  {
    (Integer) -100
  }
  [faultString]
  {
    (String) No answer from device.
  }
}
01/18/18 21:51:25.071 RPC Server (Port 2001): Response binary:
42696EFF0000004A0000010100000002000000096661756C74436F646500000001FFFFFF9C0000000B6661756C74537472696E6700000003000000164E6F20616E737765722066726F6D206465766963652E
01/18/18 21:51:25.075 RPC Server (Port 2001): Debug: Connection to client number 11 closed (3).
01/18/18 21:51:25.078 RPC Server (Port 2001): Info: Connection from ::ffff:127.0.0.1:60532 accepted. Client number: 15
01/18/18 21:51:25.079 RPC Server (Port 2001): Info: RPC server client id for client number 15 is: 6
01/18/18 21:51:25.081 RPC Server (Port 2001): Listening for incoming packets from client number 15.
01/18/18 21:51:25.082 RPC Server (Port 2001): Debug: Packet received: 42696E00000000470000000873657456616C756500000003000000030000000C4D4551303535383732373A34000000030000000F5345545F54454D5045524154555245000000042C00000000000005

01/18/18 21:51:25.082 RPC Server (Port 2001): Info: Client number 15 is calling RPC method: setValue (2) Parameters:
(String) MEQ0558727:4
(String) SET_TEMPERATURE
(Float) 22
01/18/18 21:51:25.083 Module HomeMatic BidCoS: Debug: SET_TEMPERATURE of peer 1 with serial number MEQ0558727:4 was set to 2C.
01/18/18 21:51:27.639 RPC Server (Port 2001): Response:
(Struct length=2)
{
  [faultCode]
  {
    (Integer) -100
  }
  [faultString]
  {
    (String) No answer from device.
  }
}
01/18/18 21:51:27.640 RPC Server (Port 2001): Response binary:
42696EFF0000004A0000010100000002000000096661756C74436F646500000001FFFFFF9C0000000B6661756C74537472696E6700000003000000164E6F20616E737765722066726F6D206465766963652E
01/18/18 21:51:28.127 Module HomeMatic BidCoS: Debug: Deleting queue 6 for BidCoS peer with address 0x3A39C4
01/18/18 21:51:28.128 Module HomeMatic BidCoS: Info: Setting peer to unreachable, because the queue processing was interrupted.
01/18/18 21:51:28.128 Module HomeMatic BidCoS: Info: Queue is not finished (peer: 1). Retrying...
01/18/18 21:51:28.228 Debug: Thread priority successfully set to: 45
01/18/18 21:51:28.228 Module HomeMatic BidCoS: Debug: Sending packet 0C10B011FDDD8C3A39C486042C immediately, because it seems it is no response (no packet information found).
01/18/18 21:51:28.228 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0C10B011FDDD8C3A39C486042C
01/18/18 21:51:28.788 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0C10B011FDDD8C3A39C486042C
01/18/18 21:51:29.348 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0C10B011FDDD8C3A39C486042C
01/18/18 21:51:31.232 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
01/18/18 21:51:31.234 Module HomeMatic BidCoS: Debug: Deleting queue 7 for BidCoS peer with address 0x3A39C4
01/18/18 21:51:31.235 Module HomeMatic BidCoS: Info: Setting peer to unreachable, because the queue processing was interrupted.
01/18/18 21:51:31.235 Module HomeMatic BidCoS: Info: Queue is not finished (peer: 1). Retrying...
01/18/18 21:51:31.334 UPnP Server: Debug: Sending notify packets.
01/18/18 21:51:31.338 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.2.5:46528 accepted. Client number: 16
01/18/18 21:51:31.339 RPC Server (Port 2001): Info: RPC server client id for client number 16 is: 7
01/18/18 21:51:31.339 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.2.5:46529 accepted. Client number: 17
01/18/18 21:51:31.339 Debug: Thread priority successfully set to: 45
01/18/18 21:51:31.340 Module HomeMatic BidCoS: Debug: Sending packet 0C10B011FDDD8C3A39C486042C immediately, because it seems it is no response (no packet information found).
01/18/18 21:51:31.340 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0C10B011FDDD8C3A39C486042C
01/18/18 21:51:31.341 RPC Server (Port 2001): Info: RPC server client id for client number 17 is: 8
01/18/18 21:51:31.341 RPC Server (Port 2001): Listening for incoming packets from client number 16.
01/18/18 21:51:31.342 RPC Server (Port 2001): Debug: Packet received: 474554202F6465736372697074696F6E2E786D6C20485454502F312E310D0A484F53543A203139322E3136382E322E35323A323030310D0A444154453A205468752C203138204A616E20323031382032303A35313A333120474D540D0A434F4E4E454354494F4E3A20636C6F73650D0A555345522D4147454E543A204C696E75782F322E362E32322E31382C2055506E502F312E302C20506F727461626C652053444B20666F722055506E5020646576696365732F312E362E300D0A0D0A
01/18/18 21:51:31.342 RPC Server (Port 2001): Listening for incoming packets from client number 17.
01/18/18 21:51:31.343 RPC Server (Port 2001): Debug: Packet received: 474554202F6465736372697074696F6E2E786D6C20485454502F312E310D0A484F53543A203139322E3136382E322E35323A323030310D0A444154453A205468752C203138204A616E20323031382032303A35313A333120474D540D0A434F4E4E454354494F4E3A20636C6F73650D0A555345522D4147454E543A204C696E75782F322E362E32322E31382C2055506E502F312E302C20506F727461626C652053444B20666F722055506E5020646576696365732F312E362E300D0A0D0A
01/18/18 21:51:31.365 RPC Server (Port 2001): Debug: Connection to client number 16 closed.
01/18/18 21:51:31.366 RPC Server (Port 2001): Debug: Connection to client number 17 closed.
01/18/18 21:51:31.369 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.2.5:46530 accepted. Client number: 18
01/18/18 21:51:31.370 RPC Server (Port 2001): Info: RPC server client id for client number 18 is: 9
01/18/18 21:51:31.371 RPC Server (Port 2001): Listening for incoming packets from client number 18.
01/18/18 21:51:31.372 RPC Server (Port 2001): Debug: Packet received: 474554202F6465736372697074696F6E2E786D6C20485454502F312E310D0A484F53543A203139322E3136382E322E35323A323030310D0A444154453A205468752C203138204A616E20323031382032303A35313A333120474D540D0A434F4E4E454354494F4E3A20636C6F73650D0A555345522D4147454E543A204C696E75782F322E362E32322E31382C2055506E502F312E302C20506F727461626C652053444B20666F722055506E5020646576696365732F312E362E300D0A0D0A
01/18/18 21:51:31.394 RPC Server (Port 2001): Debug: Connection to client number 18 closed.
01/18/18 21:51:31.900 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0C10B011FDDD8C3A39C486042C
01/18/18 21:51:32.460 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0C10B011FDDD8C3A39C486042C
01/18/18 21:51:34.345 Module HomeMatic BidCoS: Debug: Deleting queue 8 for BidCoS peer with address 0x3A39C4
01/18/18 21:51:34.346 Module HomeMatic BidCoS: Info: Setting peer to unreachable, because the queue processing was interrupted.
01/18/18 21:51:34.347 Module HomeMatic BidCoS: Info: Queue is not finished (peer: 1). Retrying...
01/18/18 21:51:34.446 Debug: Thread priority successfully set to: 45
01/18/18 21:51:34.447 Module HomeMatic BidCoS: Debug: Sending packet 0C10B011FDDD8C3A39C486042C immediately, because it seems it is no response (no packet information found).
01/18/18 21:51:34.447 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0C10B011FDDD8C3A39C486042C
01/18/18 21:51:35.007 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0C10B011FDDD8C3A39C486042C
01/18/18 21:51:35.567 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0C10B011FDDD8C3A39C486042C
01/18/18 21:51:36.138 RPC Server (Port 2001): Debug: Packet received: 42696E000000001C000000146C697374426964636F73496E746572666163657300000000
01/18/18 21:51:36.138 RPC Server (Port 2001): Info: Client number 15 is calling RPC method: listBidcosInterfaces (2) Parameters:
01/18/18 21:51:36.138 RPC Server (Port 2001): Response:
(Array length=1)
{
  (Struct length=4)
  {
    [ADDRESS]
    {
      (String) VBC0970134
    }
    [CONNECTED]
    {
      (Boolean) 1
    }
    [DEFAULT]
    {
      (Boolean) 1
    }
    [DESCRIPTION]
    {
      (String) Homegear default BidCoS interface
    }
  }
}
01/18/18 21:51:36.139 RPC Server (Port 2001): Response binary:
42696E0100000087000001000000000100000101000000040000000741444452455353000000030000000A5642433039373031333400000009434F4E4E454354454400000002010000000744454641554C5400000002010000000B4445534352495054494F4E0000000300000021486F6D65676561722064656661756C7420426964436F5320696E74657266616365
01/18/18 21:51:37.452 Module HomeMatic BidCoS: Debug: Deleting queue 9 for BidCoS peer with address 0x3A39C4
01/18/18 21:51:37.453 Module HomeMatic BidCoS: Info: Setting peer to unreachable, because the queue processing was interrupted.
01/18/18 21:51:37.453 Info: Peer 1 is unreachable.
01/18/18 21:51:37.470 Info: Peer 1 is reachable again.

Hallo @Christoph,

tut mir Leid für die späte Antwort. Empfängt der CUL denn noch BidCoS-Pakete nachdem das Problem auftritt? Falls ja, liegt das Problem am Gerät - es kommt wirklich keine Antwort. Dann würde ich noch einmal einen Werksreset machen und die Geräte neu anlernen. Wie ist der RSSI?

Viele Grüße

Sathya