Openhab2 + Homematic on 1 Raspberry Pi

ThomDietrich · February 24, 2017, 1:54pm

Wow are you the owner of an apartment complex?

Nawygator · February 24, 2017, 2:26pm

Nope, just a 2 family-house with used cellar-rooms

siod · February 24, 2017, 8:26pm

Hi guys,

succesfully set up my new RasPi3 with openhabian! So openhab 2is running and I already installed Homegear and made the settings described here https://doc.homegear.eu/data/homegear-homematicbidcos/configuration.html#config-hm-mod-rpi-pcb (5.2.5). Also I already entered my RasPi3 IP in the Homegear settings (bridge).
I launched PaperUI and everything looks fine, but now I don´t know how to discover/pair my homegear device. I just pressed the “config” button on the device (a roller shutter switch) and hoped it would apper in my Paper UI inbox, what not happened. This is what I got now:

Please help me with the next steps, don´t get it how to add the device…

Nawygator · February 24, 2017, 8:34pm

As Thom explained, there are multiple ways to pair your devices.
I would recommend using the CLI.
To do so, you ssh into openhabian and use the following commands:

sudo homegear -r
fs 0
pon

then you should bring the device in pairing mode

siod · February 24, 2017, 8:36pm

sorry, forgot to mention that I already tried that, but I had no success:

Nawygator · February 24, 2017, 8:38pm

do you edited homematicbidcos.conf (5.2.5.2) and restartet homegear?

siod · February 24, 2017, 8:42pm

aargh, dammit. missed that step

thanks for your quick support, will go on now and report back

edit: Ok, that worked now, unfortunately pairing doesn´t

maybe you understand what the debug log says, this is a snapshot of the 60 seconds in paring mode on:

02/24/17 22:25:00.871 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
02/24/17 22:25:10.511 RPC Server (Port 2001): Debug: Packet received: 42696E000000001C000000146C697374426964636F73496E746572666163657300000000
02/24/17 22:25:10.511 RPC Server (Port 2001): Info: Client number 86 is calling RPC method: listBidcosInterfaces (2) Parameters:
02/24/17 22:25:10.512 RPC Server (Port 2001): Response: 
(Array length=1)
{
  (Struct length=4)
  {
    [ADDRESS]
    {
      (String) VBC0468654
    }
    [CONNECTED]
    {
      (Boolean) 1
    }
    [DEFAULT]
    {
      (Boolean) 1
    }
    [DESCRIPTION]
    {
      (String) Homegear default BidCoS interface
    }
  }
}
02/24/17 22:25:10.512 RPC Server (Port 2001): Response binary:
42696E0100000087000001000000000100000101000000040000000741444452455353000000030000000A5642433034363836353400000009434F4E4E454354454400000002010000000744454641554C5400000002010000000B4445534352495054494F4E0000000300000021486F6D65676561722064656661756C7420426964436F5320696E74657266616365
02/24/17 22:25:10.924 RPC Server (Port 2001): Debug: Packet received: 42696E000000002F00000004696E697400000001000000030000001B62696E6172793A2F2F3139322E3136382E312E3136363A39313236
02/24/17 22:25:10.925 RPC Server (Port 2001): Info: Client number 86 is calling RPC method: init (2) Parameters:
(String) binary://192.168.1.166:9126
02/24/17 22:25:10.925 Info: Removing server "binary://192.168.1.166".
02/24/17 22:25:10.926 RPC Server (Port 2001): Response: 
(void)
02/24/17 22:25:10.926 RPC Server (Port 2001): Response binary:
42696E01000000080000000300000000
02/24/17 22:25:10.930 RPC Server (Port 2001): Debug: Packet received: 42696E000000004200000004696E697400000002000000030000001B62696E6172793A2F2F3139322E3136382E312E3136363A39313236000000030000000B52462D6231323133666336
02/24/17 22:25:10.931 RPC Server (Port 2001): Info: Client number 86 is calling RPC method: init (2) Parameters:
(String) binary://192.168.1.166:9126
(String) RF-b1213fc6
02/24/17 22:25:10.931 Info: Adding server "binary://192.168.1.166".
02/24/17 22:25:10.932 RPC Server (Port 2001): Response: 
(void)
02/24/17 22:25:10.932 Info: Calling init methods on server "binary://192.168.1.166".
02/24/17 22:25:10.932 RPC Server (Port 2001): Response binary:
42696E01000000080000000300000000
02/24/17 22:25:10.935 RPC Server (Port 2001): Info: Connection to client number 86 closed (3).
02/24/17 22:25:10.981 UPnP Server: Debug: Discovery packet received from 239.255.255.250:1900
02/24/17 22:25:11.001 Debug: Sleeping 2630ms before sending response.
02/24/17 22:25:11.432 RPC client: Info: Calling RPC method "system.listMethods" on server binary://192.168.1.166.
02/24/17 22:25:11.432 RPC client: Parameters:
02/24/17 22:25:11.432 Debug: Calling getFileDescriptor...
02/24/17 22:25:11.432 Debug: Connecting to host 192.168.1.166 on port 9126...
02/24/17 22:25:11.433 Debug: Connected to host 192.168.1.166 on port 9126. Client number is: 91
02/24/17 22:25:11.433 RPC client: Debug: Sending packet: 42696E000000001A0000001273797374656D2E6C6973744D6574686F647300000000
02/24/17 22:25:11.434 RPC client: Debug: Packet received: 42696E01000000540000010000000004000000030000001073797374656D2E6D756C746963616C6C00000003000000056576656E74000000030000000D64656C65746544657669636573000000030000000A6E657744657669636573
02/24/17 22:25:11.434 RPC client: Debug: Received packet from server 192.168.1.166: 42696E01000000540000010000000004000000030000001073797374656D2E6D756C746963616C6C00000003000000056576656E74000000030000000D64656C65746544657669636573000000030000000A6E657744657669636573
02/24/17 22:25:11.434 RPC client: Response was:
(Array length=4)
{
  (String) system.multicall
  (String) event
  (String) deleteDevices
  (String) newDevices
}
02/24/17 22:25:11.434 Debug: Adding method system.multicall
02/24/17 22:25:11.434 Debug: Adding method event
02/24/17 22:25:11.434 Debug: Adding method deleteDevices
02/24/17 22:25:11.434 Debug: Adding method newDevices
02/24/17 22:25:13.632 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
02/24/17 22:25:13.732 UPnP Server: Debug: Sending notify packets.
02/24/17 22:25:13.732 UPnP Server: Debug: Discovery packet received from 239.255.255.250:1900
02/24/17 22:25:13.752 Debug: Sleeping 2496ms before sending response.
02/24/17 22:25:16.249 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
02/24/17 22:25:16.349 UPnP Server: Debug: Sending notify packets.
02/24/17 22:25:16.680 Info: CLI connection accepted. Client number: 92
02/24/17 22:25:16.680 Listening for incoming commands from client number 92.
02/24/17 22:25:25.517 RPC Server (Port 2001): Info: Connection from 192.168.1.166:34492 accepted. Client number: 93
02/24/17 22:25:25.518 RPC Server (Port 2001): Info: RPC server client id for client number 93 is: 14
02/24/17 22:25:25.519 RPC Server (Port 2001): Listening for incoming packets from client number 93.
02/24/17 22:25:25.519 RPC Server (Port 2001): Debug: Packet received: 42696E000000001C000000146C697374426964636F73496E746572666163657300000000
02/24/17 22:25:25.520 RPC Server (Port 2001): Info: Client number 93 is calling RPC method: listBidcosInterfaces (2) Parameters:
02/24/17 22:25:25.520 RPC Server (Port 2001): Response: 
(Array length=1)
{
  (Struct length=4)
  {
    [ADDRESS]
    {
      (String) VBC0468654
    }
    [CONNECTED]
    {
      (Boolean) 1
    }
    [DEFAULT]
    {
      (Boolean) 1
    }
    [DESCRIPTION]
    {
      (String) Homegear default BidCoS interface
    }
  }
}
02/24/17 22:25:25.521 RPC Server (Port 2001): Response binary:
42696E0100000087000001000000000100000101000000040000000741444452455353000000030000000A5642433034363836353400000009434F4E4E454354454400000002010000000744454641554C5400000002010000000B4445534352495054494F4E0000000300000021486F6D65676561722064656661756C7420426964436F5320696E74657266616365
02/24/17 22:25:29.835 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No init packet received.
02/24/17 22:25:29.835 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Connecting to HM-MOD-RPI-PCB...
02/24/17 22:25:31.836 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Connected to HM-MOD-RPI-PCB.
02/24/17 22:25:31.836 Debug: GPIO 18 set to 0.
02/24/17 22:25:31.937 Debug: GPIO 18 set to 1.
02/24/17 22:25:31.973 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 000C000000436F
02/24/17 22:25:31.973 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Too large packet received: 000C000000436F
02/24/17 22:25:31.973 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 4350555F424C72
02/24/17 22:25:31.973 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Too large packet received: 4350555F424C72
02/24/17 22:25:40.525 RPC Server (Port 2001): Debug: Packet received: 42696E000000001C000000146C697374426964636F73496E746572666163657300000000
02/24/17 22:25:40.526 RPC Server (Port 2001): Info: Client number 93 is calling RPC method: listBidcosInterfaces (2) Parameters:
02/24/17 22:25:40.526 RPC Server (Port 2001): Response: 
(Array length=1)
{
  (Struct length=4)
  {
    [ADDRESS]
    {
      (String) VBC0468654
    }
    [CONNECTED]
    {
      (Boolean) 1
    }
    [DEFAULT]
    {
      (Boolean) 1
    }
    [DESCRIPTION]
    {
      (String) Homegear default BidCoS interface
    }
  }
}
02/24/17 22:25:40.527 RPC Server (Port 2001): Response binary:
42696E0100000087000001000000000100000101000000040000000741444452455353000000030000000A5642433034363836353400000009434F4E4E454354454400000002010000000744454641554C5400000002010000000B4445534352495054494F4E0000000300000021486F6D65676561722064656661756C7420426964436F5320696E74657266616365
02/24/17 22:25:49.949 RPC Server (Port 2001): Debug: Joining read thread of client 13
02/24/17 22:25:49.949 RPC Server (Port 2001): Debug: Client 13 removed.
02/24/17 22:25:55.531 RPC Server (Port 2001): Debug: Packet received: 42696E000000001C000000146C697374426964636F73496E746572666163657300000000
02/24/17 22:25:55.531 RPC Server (Port 2001): Info: Client number 93 is calling RPC method: listBidcosInterfaces (2) Parameters:
02/24/17 22:25:55.532 RPC Server (Port 2001): Response: 
(Array length=1)
{
  (Struct length=4)
  {
    [ADDRESS]
    {
      (String) VBC0468654
    }
    [CONNECTED]
    {
      (Boolean) 1
    }
    [DEFAULT]
    {
      (Boolean) 1
    }
    [DESCRIPTION]
    {
      (String) Homegear default BidCoS interface
    }
  }
}
02/24/17 22:25:55.533 RPC Server (Port 2001): Response binary:
42696E0100000087000001000000000100000101000000040000000741444452455353000000030000000A5642433034363836353400000009434F4E4E454354454400000002010000000744454641554C5400000002010000000B4445534352495054494F4E0000000300000021486F6D65676561722064656661756C7420426964436F5320696E74657266616365
02/24/17 22:26:01.938 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No init packet received.
02/24/17 22:26:02.520 UPnP Server: Debug: Discovery packet received from 239.255.255.250:1900
02/24/17 22:26:02.541 Debug: Sleeping 2863ms before sending response.
02/24/17 22:26:02.999 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
02/24/17 22:26:03.000 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Connecting to HM-MOD-RPI-PCB...
02/24/17 22:26:05.000 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Connected to HM-MOD-RPI-PCB.
02/24/17 22:26:05.001 Debug: GPIO 18 set to 0.
02/24/17 22:26:05.101 Debug: GPIO 18 set to 1.
02/24/17 22:26:05.137 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 000C000000436F
02/24/17 22:26:05.137 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Too large packet received: 000C000000436F
02/24/17 22:26:05.137 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 4350555F424C72
02/24/17 22:26:05.138 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Too large packet received: 4350555F424C72
02/24/17 22:26:05.404 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
02/24/17 22:26:05.505 UPnP Server: Debug: Sending notify packets.
02/24/17 22:26:05.506 UPnP Server: Debug: Discovery packet received from 239.255.255.250:1900
02/24/17 22:26:05.526 Debug: Sleeping 2243ms before sending response.
02/24/17 22:26:07.769 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
02/24/17 22:26:07.870 UPnP Server: Debug: Sending notify packets.
02/24/17 22:26:10.537 RPC Server (Port 2001): Debug: Packet received: 42696E000000001C000000146C697374426964636F73496E746572666163657300000000
02/24/17 22:26:10.538 RPC Server (Port 2001): Info: Client number 93 is calling RPC method: listBidcosInterfaces (2) Parameters:
02/24/17 22:26:10.538 RPC Server (Port 2001): Response: 
(Array length=1)
{
  (Struct length=4)
  {
    [ADDRESS]
    {
      (String) VBC0468654
    }
    [CONNECTED]
    {
      (Boolean) 1
    }
    [DEFAULT]
    {
      (Boolean) 1
    }
    [DESCRIPTION]
    {
      (String) Homegear default BidCoS interface
    }
  }
}
02/24/17 22:26:10.538 RPC Server (Port 2001): Response binary:
42696E0100000087000001000000000100000101000000040000000741444452455353000000030000000A5642433034363836353400000009434F4E4E454354454400000002010000000744454641554C5400000002010000000B4445534352495054494F4E0000000300000021486F6D65676561722064656661756C7420426964436F5320696E74657266616365
02/24/17 22:26:10.976 RPC Server (Port 2001): Debug: Packet received: 42696E000000002F00000004696E697400000001000000030000001B62696E6172793A2F2F3139322E3136382E312E3136363A39313236
02/24/17 22:26:10.977 RPC Server (Port 2001): Info: Client number 93 is calling RPC method: init (2) Parameters:
(String) binary://192.168.1.166:9126
02/24/17 22:26:10.977 Info: Removing server "binary://192.168.1.166".
02/24/17 22:26:10.978 RPC Server (Port 2001): Response: 
(void)
02/24/17 22:26:10.978 RPC Server (Port 2001): Response binary:
42696E01000000080000000300000000
02/24/17 22:26:10.982 RPC Server (Port 2001): Debug: Packet received: 42696E000000004200000004696E697400000002000000030000001B62696E6172793A2F2F3139322E3136382E312E3136363A39313236000000030000000B52462D6231323133666336
02/24/17 22:26:10.982 RPC Server (Port 2001): Info: Client number 93 is calling RPC method: init (2) Parameters:
(String) binary://192.168.1.166:9126
(String) RF-b1213fc6
02/24/17 22:26:10.983 Info: Adding server "binary://192.168.1.166".
02/24/17 22:26:10.984 RPC Server (Port 2001): Response: 
(void)
02/24/17 22:26:10.984 Info: Calling init methods on server "binary://192.168.1.166".
02/24/17 22:26:10.984 RPC Server (Port 2001): Response binary:
42696E01000000080000000300000000
02/24/17 22:26:10.989 RPC Server (Port 2001): Info: Connection to client number 93 closed (3).
02/24/17 22:26:11.484 RPC client: Info: Calling RPC method "system.listMethods" on server binary://192.168.1.166.
02/24/17 22:26:11.485 RPC client: Parameters:
02/24/17 22:26:11.485 Debug: Calling getFileDescriptor...
02/24/17 22:26:11.485 Debug: Connecting to host 192.168.1.166 on port 9126...
02/24/17 22:26:11.486 Debug: Connected to host 192.168.1.166 on port 9126. Client number is: 98
02/24/17 22:26:11.486 RPC client: Debug: Sending packet: 42696E000000001A0000001273797374656D2E6C6973744D6574686F647300000000
02/24/17 22:26:11.487 RPC client: Debug: Packet received: 42696E01000000540000010000000004000000030000001073797374656D2E6D756C746963616C6C00000003000000056576656E74000000030000000D64656C65746544657669636573000000030000000A6E657744657669636573
02/24/17 22:26:11.488 RPC client: Debug: Received packet from server 192.168.1.166: 42696E01000000540000010000000004000000030000001073797374656D2E6D756C746963616C6C00000003000000056576656E74000000030000000D64656C65746544657669636573000000030000000A6E657744657669636573
02/24/17 22:26:11.488 RPC client: Response was:
(Array length=4)
{
  (String) system.multicall
  (String) event
  (String) deleteDevices
  (String) newDevices
}
02/24/17 22:26:11.488 Debug: Adding method system.multicall
02/24/17 22:26:11.488 Debug: Adding method event
02/24/17 22:26:11.489 Debug: Adding method deleteDevices
02/24/17 22:26:11.489 Debug: Adding method newDevices
02/24/17 22:26:25.543 RPC Server (Port 2001): Info: Connection from 192.168.1.166:34520 accepted. Client number: 99
02/24/17 22:26:25.544 RPC Server (Port 2001): Info: RPC server client id for client number 99 is: 15
02/24/17 22:26:25.545 RPC Server (Port 2001): Listening for incoming packets from client number 99.
02/24/17 22:26:25.545 RPC Server (Port 2001): Debug: Packet received: 42696E000000001C000000146C697374426964636F73496E746572666163657300000000
02/24/17 22:26:25.545 RPC Server (Port 2001): Info: Client number 99 is calling RPC method: listBidcosInterfaces (2) Parameters:
02/24/17 22:26:25.545 RPC Server (Port 2001): Response: 
(Array length=1)
{
  (Struct length=4)
  {
    [ADDRESS]
    {
      (String) VBC0468654
    }
    [CONNECTED]
    {
      (Boolean) 1
    }
    [DEFAULT]
    {
      (Boolean) 1
    }
    [DESCRIPTION]
    {
      (String) Homegear default BidCoS interface
    }
  }
}
02/24/17 22:26:25.546 RPC Server (Port 2001): Response binary:
42696E0100000087000001000000000100000101000000040000000741444452455353000000030000000A5642433034363836353400000009434F4E4E454354454400000002010000000744454641554C5400000002010000000B4445534352495054494F4E0000000300000021486F6D65676561722064656661756C7420426964436F5320696E74657266616365
02/24/17 22:26:35.101 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No init packet received.
02/24/17 22:26:36.168 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
02/24/17 22:26:36.168 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Connecting to HM-MOD-RPI-PCB...
02/24/17 22:26:38.169 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Connected to HM-MOD-RPI-PCB.
02/24/17 22:26:38.170 Debug: GPIO 18 set to 0.
02/24/17 22:26:38.270 Debug: GPIO 18 set to 1.
02/24/17 22:26:38.306 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 000C000000436F
02/24/17 22:26:38.306 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Too large packet received: 000C000000436F
02/24/17 22:26:38.306 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 4350555F424C72
02/24/17 22:26:38.307 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Too large packet received: 4350555F424C72
02/24/17 22:26:40.552 RPC Server (Port 2001): Debug: Packet received: 42696E000000001C000000146C697374426964636F73496E746572666163657300000000
02/24/17 22:26:40.553 RPC Server (Port 2001): Info: Client number 99 is calling RPC method: listBidcosInterfaces (2) Parameters:
02/24/17 22:26:40.553 RPC Server (Port 2001): Response: 
(Array length=1)
{
  (Struct length=4)
  {
    [ADDRESS]
    {
      (String) VBC0468654
    }
    [CONNECTED]
    {
      (Boolean) 1
    }
    [DEFAULT]
    {
      (Boolean) 1
    }
    [DESCRIPTION]
    {
      (String) Homegear default BidCoS interface
    }
  }
}
02/24/17 22:26:40.554 RPC Server (Port 2001): Response binary:
42696E0100000087000001000000000100000101000000040000000741444452455353000000030000000A5642433034363836353400000009434F4E4E454354454400000002010000000744454641554C5400000002010000000B4445534352495054494F4E0000000300000021486F6D65676561722064656661756C7420426964436F5320696E74657266616365
02/24/17 22:26:49.977 RPC Server (Port 2001): Debug: Joining read thread of client 14
02/24/17 22:26:49.977 RPC Server (Port 2001): Debug: Client 14 removed.
02/24/17 22:26:54.542 UPnP Server: Debug: Discovery packet received from 239.255.255.250:1900
02/24/17 22:26:54.562 Debug: Sleeping 1660ms before sending response.
02/24/17 22:26:55.557 RPC Server (Port 2001): Debug: Packet received: 42696E000000001C000000146C697374426964636F73496E746572666163657300000000
02/24/17 22:26:55.558 RPC Server (Port 2001): Info: Client number 99 is calling RPC method: listBidcosInterfaces (2) Parameters:
02/24/17 22:26:55.558 RPC Server (Port 2001): Response: 
(Array length=1)
{
  (Struct length=4)
  {
    [ADDRESS]
    {
      (String) VBC0468654
    }
    [CONNECTED]
    {
      (Boolean) 1
    }
    [DEFAULT]
    {
      (Boolean) 1
    }
    [DESCRIPTION]
    {
      (String) Homegear default BidCoS interface
    }
  }
}
02/24/17 22:26:55.558 RPC Server (Port 2001): Response binary:
42696E0100000087000001000000000100000101000000040000000741444452455353000000030000000A5642433034363836353400000009434F4E4E454354454400000002010000000744454641554C5400000002010000000B4445534352495054494F4E0000000300000021486F6D65676561722064656661756C7420426964436F5320696E74657266616365
02/24/17 22:26:56.223 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
02/24/17 22:26:56.323 UPnP Server: Debug: Sending notify packets.
02/24/17 22:26:56.324 UPnP Server: Debug: Discovery packet received from 239.255.255.250:1900
02/24/17 22:26:56.344 Debug: Sleeping 469ms before sending response.
02/24/17 22:26:56.813 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
02/24/17 22:26:56.914 UPnP Server: Debug: Sending notify packets.
02/24/17 22:27:08.271 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No init packet received.
02/24/17 22:27:09.333 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
02/24/17 22:27:09.333 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Connecting to HM-MOD-RPI-PCB...
02/24/17 22:27:10.562 RPC Server (Port 2001): Debug: Packet received: 42696E000000001C000000146C697374426964636F73496E746572666163657300000000
02/24/17 22:27:10.562 RPC Server (Port 2001): Info: Client number 99 is calling RPC method: listBidcosInterfaces (2) Parameters:
02/24/17 22:27:10.563 RPC Server (Port 2001): Response: 
(Array length=1)
{
  (Struct length=4)
  {
    [ADDRESS]
    {
      (String) VBC0468654
    }
    [CONNECTED]
    {
      (Boolean) 1
    }
    [DEFAULT]
    {
      (Boolean) 1
    }
    [DESCRIPTION]
    {
      (String) Homegear default BidCoS interface
    }
  }
}
02/24/17 22:27:10.563 RPC Server (Port 2001): Response binary:
42696E0100000087000001000000000100000101000000040000000741444452455353000000030000000A5642433034363836353400000009434F4E4E454354454400000002010000000744454641554C5400000002010000000B4445534352495054494F4E0000000300000021486F6D65676561722064656661756C7420426964436F5320696E74657266616365
02/24/17 22:27:11.028 RPC Server (Port 2001): Debug: Packet received: 42696E000000002F00000004696E697400000001000000030000001B62696E6172793A2F2F3139322E3136382E312E3136363A39313236
02/24/17 22:27:11.028 RPC Server (Port 2001): Info: Client number 99 is calling RPC method: init (2) Parameters:
(String) binary://192.168.1.166:9126
02/24/17 22:27:11.029 Info: Removing server "binary://192.168.1.166".
02/24/17 22:27:11.029 RPC Server (Port 2001): Response: 
(void)
02/24/17 22:27:11.030 RPC Server (Port 2001): Response binary:
42696E01000000080000000300000000
02/24/17 22:27:11.334 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Connected to HM-MOD-RPI-PCB.
02/24/17 22:27:11.335 Debug: GPIO 18 set to 0.
02/24/17 22:27:11.435 Debug: GPIO 18 set to 1.
02/24/17 22:27:11.470 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 000C000000436F
02/24/17 22:27:11.471 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Too large packet received: 000C000000436F
02/24/17 22:27:11.471 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (3). Trying to reconnect...
02/24/17 22:27:12.471 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
02/24/17 22:27:22.321 Connection to client number 92 closed.
02/24/17 22:27:25.568 RPC Server (Port 2001): Debug: Packet received: 42696E000000001C000000146C697374426964636F73496E746572666163657300000000
02/24/17 22:27:25.569 RPC Server (Port 2001): Info: Client number 99 is calling RPC method: listBidcosInterfaces (2) Parameters:
02/24/17 22:27:25.569 RPC Server (Port 2001): Response: 
(Array length=1)
{
  (Struct length=4)
  {
    [ADDRESS]
    {
      (String) VBC0468654
    }
    [CONNECTED]
    {
      (Boolean) 1
    }
    [DEFAULT]
    {
      (Boolean) 1
    }
    [DESCRIPTION]
    {
      (String) Homegear default BidCoS interface
    }
  }
}
02/24/17 22:27:25.570 RPC Server (Port 2001): Response binary:
42696E0100000087000001000000000100000101000000040000000741444452455353000000030000000A5642433034363836353400000009434F4E4E454354454400000002010000000744454641554C5400000002010000000B4445534352495054494F4E0000000300000021486F6D65676561722064656661756C7420426964436F5320696E74657266616365

ThomDietrich · February 25, 2017, 1:16pm

you have to enter pon, then bring your device into pairing mode (check manual), then you’ll see the device in the list shown by the command ls. You can then even name the device if you like: pn 1 Switch xyz
If pairing didn’t succeed yet, just try again.

Your log can’t tell us much, other than that your module seems to be tranceiving, which is a good start.

siod · February 25, 2017, 5:14pm

Ok, reinstalled everything a few times, now it´s working very fine! In the end I must say it was quiet easy, just a little tricky here and there.

Thanks for your help!!

logobg · March 1, 2018, 1:12pm

Hi, for the past 2 weeks I’m trying to instal openhabian, homegear, HM‑MOD‑RPI‑PCB on PaspberryPi 3 with WiFi on and I cannot succeed. I’ve done all steps in the whole google but nothing… my HM‑MOD‑RPI‑PCB is with RTC-Clock (homematic-guru.de/wp-content/uploads/2017/11/Funkmodul_RTC_Homematic_RaspberryMatic_CCU2_Raspberry_2.png)
step1 - flashing the latest official openhabian 1.4 and importing wifi settings in the openhabian.conf before first run
step2 - ssh login with openhabian for username and pass (waithing till first run setup to be done)
step3 - openhabian-config - update, update software add additinal packages, install homegear, disabling serial,disable bt, and no star on add…
step4 - /etc/homegear/families/homematicbidcos.conf - configurating so i have the fs 0 option for my HM‑MOD‑RPI‑PCB device, editing the /boot/cmdline.txt (dwc_otg.lpm_enable=0 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait), /boot/config.txt (enable_uart=1 , dtparam=spi=on , dtparam=i2c_arm=on , dtoverlay=pi3-miniuart-bt)
step5 - restart

step6 - sudo su, homegera -r, fs 0, pon = NOTHING

step7 - scream! (http://i0.kym-cdn.com/entries/icons/original/000/012/073/7686178464_fdc8ea66c7.jpg)

the Raaspberry 3 + HM‑MOD‑RPI‑PCB + WiFi configuration is working with raspberrymatic without problems!!
can someone give me a working openhabian+homegear+HM‑MOD‑RPI‑PCB .img file for rpi3 PLEASE!
Thank You!

logobg · March 1, 2018, 7:08pm

The long story short (openhabian, homegear, HM‑MOD‑RPI‑PCB with RTC-Clock on PaspberryPi 3 with WiFi

Flash openhabianpi-raspbian-201712171718-git30faec3-crccc053823.img to Verbatim 16GB MicroSD Class 10 with Win32 Disk Image
Befor putting the card in the RaspberryPi 3 edit openhabian.conf and add:
wifi_ssid="WIFIName"
wifi_psk=“PASSWORD”
Put the SD card in the RaspberryPi 3 (no LAN cabe/power on) and after 2 min find the device IP in your network with some NetworkScanner
Connect to the device IP with putty (SSH connection)
username=openhabian
password=openhabian
now waith till end of the starting instalation script (~20 minutes, depends and on your internet connection), than press CTRL+C to get back to the console
Type sudo su and enter the password (openhabian), than start openhabian-config
In openhabian-config go to:
01 | Update Pull the latest revision of the openHABian Configuration Tool
02 | Upgrade System Upgrade all installed software packages to their newest version
In openhabian-config:
30 | System Settings A range of system and hardware related configuration steps
-35 | Serial Port Prepare serial ports for peripherals like Razberry, SCC, Pine64 ZWave, …
– [] 1 (RPi) Disable serial console (Razberry, SCC, Enocean)
– [] 2 (RPi3) Disable Bluetooth module (Razberry)
– [ ] 3 Add common serial ports to openHAB JVM (Razberry, Enocean)
press enter

8.In openhabian-config:
20 | Optional Components Choose from a set of optional software components
-26 | Homegear Homematic specific, the CCU2 emulation software Homegear
and install Homegear, than exit openhabian-config

Edit homematicbidcos.conf “nano /etc/homegear/families/homematicbidcos.conf” like this (uncomment - delete the # in front of the text fields under every !!! mark):
#######################################
########### HM-MOD-RPI-PCB ###########
#######################################

The device family this interface is for !!!

[HomeMatic Wireless Module for Raspberry Pi]

Specify an unique id here to identify this device in Homegear !!!

id = My-HM-MOD-RPI-PCB

When default is set to “true” Homegear will assign this device

to new peers.

#default = true

Options: cul, cc1100, coc, cunx, hmcfglan, hmlgw, hm-mod-rpi-pcb, homegeargateway !!!

deviceType = hm-mod-rpi-pcb

!!!

device = /dev/ttyAMA0

Default: responseDelay = 95

Should be “95” for CUL or COC, “100” for TI CC1101 and “60” for HM-CFG-LAN or HM-LGW !!!

responseDelay = 95

Default: gpio1 = 0

“18” for HM-MOD-RPI-PCB !!!

gpio1 = 18

now press CTRL+X, than “y”, than enter

Edit cmdline.txt “nano /boot/cmdline.txt” to look like this:

dwc_otg.lpm_enable=0 console=tty1 root=PARTUUID=005b14ef-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait

now press CTRL+X, than “y”, than enter

Edit config.txt “nano /boot/config.txt” and uncomment (delete the # in front of the lines, again look for my marks !!! here):

For more options and information see

http://rpf.io/configtxt

Some settings may impact device functionality. See link above for details

uncomment if you get no picture on HDMI for a default “safe” mode

#hdmi_safe=1

uncomment this if your display has a black border of unused pixels visible

and your display can output without overscan

#disable_overscan=1

uncomment the following to adjust overscan. Use positive numbers if console

goes off screen, and negative if there is too much border

#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

uncomment to force a console size. By default it will be display’s size minus

overscan.

#framebuffer_width=1280
#framebuffer_height=720

uncomment if hdmi display is not detected and composite is being output

#hdmi_force_hotplug=1

uncomment to force a specific HDMI mode (this will force VGA)

#hdmi_group=1
#hdmi_mode=1

uncomment to force a HDMI mode rather than DVI. This can make audio work in

DMT (computer monitor) modes

#hdmi_drive=2

uncomment to increase signal to HDMI, if you have interference, blanking, or

no display

#config_hdmi_boost=4

uncomment for composite PAL

#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800

Uncomment some or all of these to enable the optional hardware interfaces !!!

dtparam=i2c_arm=on
#dtparam=i2s=on
dtparam=spi=on

Uncomment this to enable the lirc-rpi module

#dtoverlay=lirc-rpi

Additional overlays and parameters are documented /boot/overlays/README

Enable audio (loads snd_bcm2835) !!!

dtparam=audio=on
gpu_mem=16
enable_uart=1
dtoverlay=pi3-miniuart-bt

now press CTRL+X, than “y”, than enter

Restart the RaspberryPi 3 “reboot”
Test Homegear and the HM-MOD-RPI-PCB device by entering:
homegear -r
fs 0
pon

put your device in connection mode (how to do that depends on your peripheral device, so read your device manual)

??? nothing ??? what ??? how ??? why ??? ?!%@!@&!! ??? now what?

by the way:
###############################################################################
################# openHABianPi ################################################
###############################################################################

Ip = 192.168.10.119

Release = Raspbian GNU/Linux 9 (stretch)

Kernel = Linux 4.9.59-v7+

Platform = Raspberry Pi 3 Model B Rev 1.2

Uptime = 0 day(s). 0:0:42

CPU Usage = 46.85 % avg over 4 cpu(s) (4 core(s) x 1 socket(s))

CPU Load = 1m: 2.02, 5m: 0.54, 15m: 0.19

Memory = Free: 0.67GB (71%), Used: 0.27GB (29%), Total: 0.95GB

Swap = Free: 0.09GB (100%), Used: 0.00GB (0%), Total: 0.09GB

Root = Free: 11.63GB (85%), Used: 1.92GB (15%), Total: 14.16GB

Updates = 0 apt updates available.

Sessions = 1 sessions

Processes = 132 running processes of 32768 maximum processes

###############################################################################

          Welcome to            __  _____    ____  _
        ____  ____  ___  ____  / / / /   |  / __ )(_)___ _____
       / __ \/ __ \/ _ \/ __ \/ /_/ / /| | / __  / / __ `/ __ \
      / /_/ / /_/ /  __/ / / / __  / ___ |/ /_/ / / /_/ / / / /
      \____/ .___/\___/_/ /_/_/ /_/_/  |_/_____/_/\__,_/_/ /_/
          /_/
              openHAB 2.2.0-1 (Release Build)

Icho · January 8, 2019, 1:47pm

Thank you so much for this detailed walkthrough which is exactly what a NOOB like myself needs!! Does it apply to the new RPI-FR-MOD in a RPI B+ as well?

nibbs · September 10, 2019, 6:45pm

Hi everyone, did anyone tried the HB-RF-USB module for integration into OH2?

IvanTerrible79 · October 14, 2020, 1:06pm

Hi Georgi,
Thank you for your post, it did sure helped me to move forward a lot.
I have tried it with my new RPI4, and freshly downloaded Openhabian. Unfortunately the result was the same: no devices dicovered.
I sorted the issue by installing the Pivccu3, that runs nicely and I could even easy look up the status of the radio module to eliminate problems there.