Pi with Homegear Died -- Are all me Homematic devices useless now?

English Forums Hardware
#1

I have a bunch of Homematic motion sensors and relays. I was linking them to OpenHAB via Raspberry PI running Homegear, and interfacing to a LAN config box from Homematic (HM-LAN-CFG or CFG-LAN can’t remember, and not at home… But the round little spaceship looking one.).

Being me, I was then messing with the GPIO ports on that Homegear Pi, and fried it. SD card is a loss too. The thing is, I don’t think I ever changed that security code from the default one in the home gear example conf files. I did, however, at some point use Homematic’s webUI to disable encryption/security to devices.

Now, I have a problem because I can’t seem to reset my homematic devices back into learning mode, and get them to attach to a new pi and home gear setup. My german isn’t that good, and practically all info about this stuff is in german (and I called the eQ3 guys who make homematic earlier – talk about unfriendly customer service, and I couldn’t really understand anything). But what I’m beginning to think people are saying is that I’m screwed, and can throw away all my homematic gear.

Does anyone here know more than I do?

#2

Anyone :wink: ? Please :wink:

#3

Hey,

if you didn’t change the security key, you are not screwed. Install and setup Homegear on a fresh SD card. Don’t pair any devices yet, because we need to change the BidCoS address of the Homegear instance to your old one. To find out what your old address was, start Homegear and do something with one of your devices (e. g. open or close a window contact). The packet sent from your device is logged to the Homegear log (/var/log/homegear/homegear.log). Post the packets here and I can tell you the address. After setting the address in “/etc/homegear/families/homematicbidcos.conf” (parameter “centralAddress”), you should be able to pair your devices again. After pairing, you should factory reset them and pair them again. Then everything should work as before :wink:.

Cheers,

Sathya

#4

Many thanks!

Here you go… I had a couple of devices around, so there is packets from more than one… Hope that makes it easier…

Best,
Mattt

root@raspberrypi:/var/log/homegear# tail -f homegear.log
07/18/16 13:16:49.778 Starting CLI server…
07/18/16 13:16:49.779 RPC Server (Port 2003): Info: RPC Server started listening on address 0.0.0.0 and port 2003
07/18/16 13:16:49.779 Initializing event handler…
07/18/16 13:16:49.779 Loading events…
07/18/16 13:16:49.781 Startup complete. Waiting for physical interfaces to connect.
07/18/16 13:16:49.781 All physical interfaces are connected now.
07/18/16 13:16:49.781 Starting UPnP server…
07/18/16 13:16:49.783 Info: UPnP server: Binding to address: 192.168.0.227
07/18/16 13:16:49.783 UPnP Server: Info: Started listening.
07/18/16 13:16:49.859 Module HomeMatic BidCoS: LAN-Konfigurationsadapter “My-HM-CFG-LAN”: Info: Initialization completed.
07/18/16 13:17:53.538 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: -55 dBm): 0D23A41033D080FD43AB0601C800
07/18/16 13:17:56.569 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: -55 dBm): 0D23A41033D080FD43AB0601C800
07/18/16 13:17:59.797 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: -58 dBm): 0D23A41033D080FD43AB0601C800
07/18/16 13:18:04.284 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: -58 dBm): 0D23A41033D080FD43AB0601C800
07/18/16 13:18:10.754 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: -58 dBm): 0D23A41033D080FD43AB0601C800
07/18/16 13:18:21.199 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: -58 dBm): 0D23A41033D080FD43AB0601C800
07/18/16 13:18:30.465 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: -58 dBm): 0D25A41033D080FD43AB06010000
07/18/16 13:18:33.892 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: -56 dBm): 0D25A41033D080FD43AB06010000
07/18/16 13:18:37.879 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: -57 dBm): 0D25A41033D080FD43AB06010000
07/18/16 13:18:40.576 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: -90 dBm): 0DD0A6101C6115FD43AB0601200E
07/18/16 13:18:41.073 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: -91 dBm): 0DD0A6101C6115FD43AB0601200E
07/18/16 13:18:41.545 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: -92 dBm): 0DD0A6101C6115FD43AB0601200E
07/18/16 13:18:42.857 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: -57 dBm): 0D25A41033D080FD43AB06010000
07/18/16 13:18:45.710 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: -42 dBm): 0D00A6101A5276FD43AB06015E00
07/18/16 13:18:46.211 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: -36 dBm): 0D00A6101A5276FD43AB06015E00
07/18/16 13:18:46.599 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: -36 dBm): 0D00A6101A5276FD43AB06015E00
07/18/16 13:18:47.845 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: -43 dBm): 0D0184411A527600000081013580
07/18/16 13:18:49.824 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: -59 dBm): 0D25A41033D080FD43AB06010000
07/18/16 13:19:00.519 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: -59 dBm): 0D25A41033D080FD43AB06010000

#5

Hey Matt,

there you go. Set “centralAddress” in “/etc/homegear/families/homematicbidcos.conf” to “0xFD43AB”. After that restart Homegear and pairing your devices should work again. When pairing was successful factory reset the devices with:

homegear -r
fs 0
ls <-- lists all paired peers to find out the peer ID
peers reset PEERID

Depending on the device you need to press the pairing button. When the reset was successfull the device is removed from the list.

Cheers,

Sathya

#6

Hey Sathya,
do you know by chance, where in the db.sql file of my homegear 0.51 installation I can find the central address. My problem is that my PI also got shredded completely. I got the AES-Key and an old backup of my db.sql. Unfortunately, I repaired all my non-AES devices with a new homegear instance (with another centralAddress). Now, I can´t reset my HM-SEC-DIR2. The solution you suggested above is probably not feasible for me since communication is encrypted (or is it?).

Cheers, Max

#7

Hi,

Actually, I was going to ask about that to… Because I managed to get some of my devices back with that response, but my 6 motion sensors are all refusing. And my wife will shoot me if (after her being rather mad at me for spending so much money on my ‘toys’ I have pay 15 eur each and send them to Germany to get them alive again)…

I mean is there no way that we could do whatever they are doing to do to them? I assume some sort of JTAG or whatever connection?

Best,
Matt

#8

Hey Max,

the solution works for you, too. The communication is not encrypted, only signed. But of course you can also get the address from the database in table “devices”. The address is in “address” where “deviceFamily” is 0.

Cheers,

Sathya

#9

Hey Matt,

They are flashing the firmware again. Problem is, we don’t have it, so we can’t do that…

You can send me the log of the pairing process of the motion sensors. Maybe that will shed some light into why the pairing is not working.

Cheers,

Sathya