I think mine has firmware version 1.3 and runs pretty well.
You could try Raspberrymatic to check whether the module is not broken. Raspberrymatic is nothing more than the original CCU2 firmware wrapped as an SD-Card image for a Raspberry (you’ll only need another card). The pairing dialog of the CCU software will refuse to start if it is not able to communicate with the HM-MOD-RPI-PCB.
But don’t forget to unpair a device after the test (really unpair, not just the “remove from CCU” option). Otherwise you will end up with a device that cannot be paired to any other CCU or Homegear anymore.
Ok if you have installed fw version 1.3 it would work.
I read that you get the module from ELV.de with fw version 1.2.1… that should be too old for openhabian.
When I install Raspberrymatic to another card, is there an opportunity to update the firmware permanently?
How would I really unpair the device? 5 seconds waiting for blink, then again 5 seconds waiting for fast blink?
Thanks Alexander.
I checked out that configuration tutorial before.
Nothing changed. I tried to test the HM-MOD-RPI-PCB with RaspberryMatic but here I have no chance to activate Pairing Mode. Maybe the HM-MOD-RPI-PCB has problems?
I think in this case the device seems to be broken. As far as I know RaspberryMatic and the CCU software in it should automatically configure the RPI ports to allow access to the module and should also automatically update the firmware on it. So this potential failure points should be eliminated.
One thing I forgot to mention is that you can set the log level of homegear to debug to see if there is any communication with the module: