Hi Sathya, as I mentioned yesterday I want to listen to the homematic radio traffic. I set up the raspi, homegear is running via “service homegear start”: I can connect with homegear cli. Spy device is created. What else do I have to listen on radio? I cannot see messages in /var/log/homegear/homegear.log. Can you please help me? Thanks in advance! André
it’s either a problem with the configuration or with the COC. I assume you followed the instructions here: ? Make sure again that “ttyAMA0” is not mentioned in “/etc/inittab” and “/boot/cmdline” and make sure “/etc/homegear/physicaldevices.conf” looks like this:
deviceType = coc
device = /dev/ttyAMA0
responseDelay = 95
gpio1 = 17
gpio2 = 18
If everything is ok and the log still does not show anything, first make sure your COC is flashed with the current firmware. Then check if your COC is working with “screen /dev/ttyAMA0 38400” (enter “V” for version for example and see, if there is an answer). When that looks good, set “debugLevel” to “5” in “/etc/homegear/main.conf” and send me the output of “service homegear start” and the log file.
The COC is a little tricky . I just realized, version 0.4.4 of Homegear is still not released… I fixed an error with the COC in that version.
Hi Sathya, thank you, everything is working now! I think the point was, that I used the busware.de firmware, not the culfw. Thanks again! André
BTW: The link to culfw in the wiki article is missing the :
Great, it is working now ! The link is fixed .
Have fun experimenting!
Hello Sathya, i have a similar problem to get Homegear work on a RPI with COC.
First I tried the 1.61 Firmeware from culfw.de then i flash the 1.58 as suggested in your wiki. But im not able to pair a HM-LC-Sw1-PI-2 Socket.
Here is the homegear.log at loglevel 5 from service start to pairing process.
I hope you can help me, after i switch pairing on, long press the button no peers are listed
10/16/14 01:15:53.114 Info: Loading family module mod_insteon.so 10/16/14 01:15:53.255 Info: Loading family module mod_philipshue.so 10/16/14 01:15:53.370 Info: Loading family module mod_homematicbidcos.so 10/16/14 01:15:53.521 Info: Loading family module mod_homematicwired.so 10/16/14 01:15:53.627 Info: Loading family module mod_max.so 10/16/14 01:15:53.945 Initializing database... 10/16/14 01:15:53.967 Initializing family controller... 10/16/14 01:15:53.968 Module HomeMatic BidCoS: Loading XML RPC devices... 10/16/14 01:15:56.249 Info: Not initializing device family HomeMatic Wired, bacause no physical interface was found. 10/16/14 01:15:56.250 Info: Not initializing device family INSTEON, bacause no physical interface was found. 10/16/14 01:15:56.251 Info: Not initializing device family MAX!, bacause no physical interface was found. 10/16/14 01:15:56.253 Info: Not initializing device family Philips hue, bacause no physical interface was found. 10/16/14 01:15:56.254 Loading devices... 10/16/14 01:15:56.257 Module HomeMatic BidCoS: Loading HomeMatic BidCoS device 1 10/16/14 01:15:56.263 Module HomeMatic BidCoS: Loading HomeMatic BidCoS device 2 10/16/14 01:15:56.270 Start listening for packets... 10/16/14 01:15:59.276 Writing: X21 Ar 10/16/14 01:16:00.277 Initializing RPC client... 10/16/14 01:16:00.279 Starting XML RPC server RPCServer1 listening on 0.0.0.0:2001... 10/16/14 01:16:00.287 Starting XML RPC server RPCServer2 listening on 0.0.0.0:2002, SSL enabled... 10/16/14 01:16:00.289 RPC Server (Port 2001): Info: RPC Server started listening on address 0.0.0.0 and port 2001 10/16/14 01:16:00.319 Starting XML RPC server RPCServer3 listening on 0.0.0.0:2003, SSL enabled, authentification enabled... 10/16/14 01:16:00.330 RPC Server (Port 2002): Info: RPC Server started listening on address 0.0.0.0 and port 2002 10/16/14 01:16:00.346 Starting CLI server... 10/16/14 01:16:00.348 Initializing event handler... 10/16/14 01:16:00.349 Loading events... 10/16/14 01:16:00.352 Startup complete. 10/16/14 01:16:00.355 All physical interfaces are connected now. 10/16/14 01:16:00.354 RPC Server (Port 2003): Info: RPC Server started listening on address 0.0.0.0 and port 2003 10/16/14 01:16:03.254 Info: CLI connection accepted. Client number: 8 10/16/14 01:16:58.374 HomeMatic BidCoS packet received (My-COC, RSSI: 0x2C): 0D00A41052910F1697BE06000000 10/16/14 01:16:58.375 Info (My-COC): Packet processing took 1 ms. 10/16/14 01:16:58.775 HomeMatic BidCoS packet received (My-COC, RSSI: 0x29): 0D00A41052910F1697BE06000000 10/16/14 01:16:58.776 Info (My-COC): Packet processing took 1 ms. 10/16/14 01:16:59.176 HomeMatic BidCoS packet received (My-COC, RSSI: 0x2A): 0D00A41052910F1697BE06000000 10/16/14 01:16:59.177 Info (My-COC): Packet processing took 0 ms. 10/16/14 01:17:09.812 HomeMatic BidCoS packet received (My-COC, RSSI: 0x2C): 1A01840052910F0000001C00A14C45513030393137323310010100 10/16/14 01:17:09.820 Module HomeMatic BidCoS: Info: Pushing pending queues. 10/16/14 01:17:09.821 Info (My-COC): Packet processing took 8 ms. 10/16/14 01:17:09.907 Module HomeMatic BidCoS: COC "My-COC": Info: Sending (My-COC): 103CA001FD1BDE52910F00050000000000 10/16/14 01:17:09.907 Writing: As103CA001FD1BDE52910F00050000000000 Ar 10/16/14 01:17:10.110 Module HomeMatic BidCoS: COC "My-COC": Info: Sending (My-COC): 103CA001FD1BDE52910F00050000000000 10/16/14 01:17:10.110 Writing: As103CA001FD1BDE52910F00050000000000 Ar 10/16/14 01:17:10.312 Module HomeMatic BidCoS: COC "My-COC": Info: Sending (My-COC): 103CA001FD1BDE52910F00050000000000 10/16/14 01:17:10.313 Writing: As103CA001FD1BDE52910F00050000000000 Ar 10/16/14 01:17:10.515 Module HomeMatic BidCoS: COC "My-COC": Info: Sending (My-COC): 103CA001FD1BDE52910F00050000000000 10/16/14 01:17:10.515 Writing: As103CA001FD1BDE52910F00050000000000 Ar
it should also work, with version 1.61 of the culfw (1.58 was the current version when I wrote the wiki article). Your log looks ok, there is just no response from the HM-LC-Sw1-Pl-2. There are two possibilities for this behaviour: The HM-LC-Sw1-Pl-2 is out of range (the reception is of the COC is much better than the reception of the switch) or the HM-LC-Sw1-Pl-2 still thinks, it is paired to the old central. Try doing a factory reset of the switch as described in the manual on page 19  and then try to pair it again.
I hope that works .
Is there a detailed description of how to setup a spy device using a raspberry/banana pi with a cc1101 module?
I couldn’t find a anything on the homegear website or through google. Homegear itself seems to be running fine on my side.
just do “tail -f /var/log/homegear/homegear.log”, there all BidCoS packets are logged.