Device states not updated using homegear and hmland

Hi together,

I could need a little help with the following problem: I am using a Homematic USB Stick (HM-CFG-USB-2) and got hmland and homegear working. Everything seems great, the devices are paired with Homegear and all are found and usable in openHAB, which I like very much. That’s the good news. :slight_smile:

What I just don’t get is, why is the state in OpenHAB not updated? I mean, if I manually switch something on or off (physically, not in openHAB), this is not shown in OpenHAB. (Also not after waiting for a few minutes, when refreshing the page, re-opening the browser, …) It’ll only be updated after a complete restart of OpenHAB on the server.

I’ve checked the homegear logs: The switch event is correctly registered there and as I interpret it, homegear then connects to openHAB on Port 9126 and sends the corresponding message, which is replied with an answer (please see log below). Strange enough I don’t see anything corresponding in the openHAB logs, even if I set the level to debug. :astonished: I can’t make head or tail of it. :confused:

The same seems to be the case when using e. g. the network binding: If a device goes offline, this is not recognized. (But a haven’t investigated this one in detail yet, so this might be misleading…)

Can you give me any hint?

(Disclaimer: Please forgive me, if this is a n00b or answered-a-thousand-times-already question! I have really been searching a lot before posting here… :nerd_face: )

Many thanks in advance!!

08/11/17 21:43:21.364 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "hmland": Debug: Packet received from HM-CFG-LAN: E30C363,0000,0583FE1E,FF,FFC9,3AA41030C363FD2EF406010000
08/11/17 21:43:21.365 Debug (hmland): Packet 0D3AA41030C363FD2EF406010000 enters raisePacketReceived.
08/11/17 21:43:21.365 Debug (hmland): Packet 0D3AA41030C363FD2EF406010000 is now passed to the EventHandler.
08/11/17 21:43:21.365 HomeMatic BidCoS packet received (hmland, RSSI: -55 dBm): 0D3AA41030C363FD2EF406010000
08/11/17 21:43:21.366 Module HomeMatic BidCoS: Info: STATE on channel 1 of HomeMatic BidCoS peer 2 with serial number LEQ1170731 was set to 0x00.
08/11/17 21:43:21.366 Module HomeMatic BidCoS: Info: WORKING on channel 1 of HomeMatic BidCoS peer 2 with serial number LEQ1170731 was set to 0x00.
08/11/17 21:43:21.366 RPC client: Debug: Calling RPC method "system.multicall" on server 127.0.0.1.
08/11/17 21:43:21.366 RPC client: Parameters:
(Array length=1)
{
  (Struct length=2)
  {
    [methodName]
    {
      (String) event
    }
    [params]
    {
      (Array length=4)
      {
        (String) RF-e4d585e4
        (String) LEQ1170731:0
        (String) RSSI_DEVICE
        (Integer) -55
      }
    }
  }
}
08/11/17 21:43:21.367 Debug: Calling getFileDescriptor...
08/11/17 21:43:21.367 Debug: Connecting to host 127.0.0.1 on port 9126...
08/11/17 21:43:21.368 Debug: Connected to host 127.0.0.1 on port 9126. Client number is: 3834
08/11/17 21:43:21.368 RPC client: Debug: Sending packet: 42696E00000000970000001073797374656D2E6D756C746963616C6C00000001000001000000000100000101000000020000000A6D6574686F644E616D6500000003000000056576656E7400000006706172616D730000010000000004000000030000000B52462D6534643538356534000000030000000C4C4551313137303733313A30000000030000000B525353495F44455649434500000001FFFFFFC9
08/11/17 21:43:21.372 RPC client: Debug: Packet received: 42696E0100000015000001000000000100000003000000056576656E74
08/11/17 21:43:21.373 RPC client: Debug: Received packet from server 127.0.0.1: 42696E0100000015000001000000000100000003000000056576656E74
08/11/17 21:43:21.373 RPC client: Response was:
(Array length=1)
{
  (String) event
}
08/11/17 21:43:21.425 RPC client: Debug: Calling RPC method "system.multicall" on server 127.0.0.1.
08/11/17 21:43:21.425 RPC client: Parameters:
08/11/17 21:43:21.425 Debug (hmland): Packet processing of packet 0D3AA41030C363FD2EF406010000 took 60 ms.
(Array length=2)
{
  (Struct length=2)
  {
    [methodName]
    {
      (String) event
    }
    [params]
    {
      (Array length=4)
      {
        (String) RF-e4d585e4
        (String) LEQ1170731:1
        (String) STATE
        (Boolean) 0
      }
    }
  }
  (Struct length=2)
  {
    [methodName]
    {
      (String) event
    }
    [params]
    {
      (Array length=4)
      {
        (String) RF-e4d585e4
        (String) LEQ1170731:1
        (String) WORKING
        (Boolean) 0
      }
    }
  }
}
08/11/17 21:43:21.425 Debug: Calling getFileDescriptor...
08/11/17 21:43:21.425 Debug: Connecting to host 127.0.0.1 on port 9126...
08/11/17 21:43:21.426 Debug: Connected to host 127.0.0.1 on port 9126. Client number is: 3835
08/11/17 21:43:21.427 RPC client: Debug: Sending packet: 42696E00000000FE0000001073797374656D2E6D756C746963616C6C00000001000001000000000200000101000000020000000A6D6574686F644E616D6500000003000000056576656E7400000006706172616D730000010000000004000000030000000B52462D6534643538356534000000030000000C4C4551313137303733313A3100000003000000055354415445000000020000000101000000020000000A6D6574686F644E616D6500000003000000056576656E7400000006706172616D730000010000000004000000030000000B52462D6534643538356534000000030000000C4C4551313137303733313A310000000300000007574F524B494E470000000200
08/11/17 21:43:21.429 RPC client: Debug: Packet received: 42696E0100000015000001000000000100000003000000056576656E74
08/11/17 21:43:21.430 RPC client: Debug: Received packet from server 127.0.0.1: 42696E0100000015000001000000000100000003000000056576656E74
08/11/17 21:43:21.431 RPC client: Response was:
(Array length=1)
{
  (String) event
}
08/11/17 21:43:24.738 RPC Server (Port 39487): Debug: Packet received: 42696E000000001C000000146C697374426964636F73496E746572666163657300000000
08/11/17 21:43:24.739 RPC Server (Port 39487): Info: Client number 3823 is calling RPC method: listBidcosInterfaces (2) Parameters:
08/11/17 21:43:24.739 RPC Server (Port 39487): Response:
(Array length=1)
{
  (Struct length=4)
  {
    [ADDRESS]
    {
      (String) VBC3139065
    }
    [CONNECTED]
    {
      (Boolean) 1
    }
    [DEFAULT]
    {
      (Boolean) 1
    }
    [DESCRIPTION]
    {
      (String) Homegear default BidCoS interface
    }
  }
}
08/11/17 21:43:24.739 RPC Server (Port 39487): Response binary:
42696E0100000087000001000000000100000101000000040000000741444452455353000000030000000A5642433331333930363500000009434F4E4E454354454400000002010000000744454641554C5400000002010000000B4445534352495054494F4E0000000300000021486F6D65676561722064656661756C7420426964436F5320696E74657266616365

In OH, how did you set the log level?

A log from OH is the best way to dig into this…

Hi manraccr,

thank you for getting back on me! In OH, I had issued log:set DEBUG and afterwards log:tail, but didn’t see anything.

But, I think, I might have found something: Some of my devices were discovered twice at the initial setup (for whatever reason). As I found the first ones working, I ignored the clones, which I remembered now. Trying one of them I see the state updates working now like a charm. (Strange, that the rest would do for the first ones…)

To make sure everything works, I think I’ll clean up everything, re-pair my devices and have a fresh setup. If I should run into this problem again, I would get back on this topic. But I’m almost sure, it’ll be resolved this way.

Anyway, thank you for your help and have a nice weekend!

1 Like