Hallo zusammen,
mein Setup:
- Raspberry pi 3
- OpenHab2 und
- Homegear (jeweils in der aktuellen Version)
- HM-MOD-RPI-PCB von ELV
Mein Problem:
Ich habe homegear installiert, die Config angepasst und versuche nun mit homegear -r, fs 0 und pon meine Fensterkontakte zu koppeln. Leider klappt dies nicht und ich finde im Log keine Informationen über einen Fehler. Dort sehe ich aber, dass mein Fensterkontakt Daten sendet und mein Modul diese empfängt.
mit ls sehe ich keine Geräte.
Lösungsversuche
-
reboot,
-
service neu starten
-
Fensterkontakt in Werkseinstellung
Hat leider alles nicht geholfen. Habt ihr eine Idee, woran es liegen könnte? Sind Homematic Fensterkontakte in der family 0 richtig?`#######################################
########### 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`
Das log sieht wie folgt aus:
04/28/19 18:42:01.355 RPC Server (Port 2001): Info: Client number 109 is calling RPC method: listBidcosInterfaces (2) Parameters:
04/28/19 18:42:16.360 RPC Server (Port 2001): Info: Client number 109 is calling RPC method: ping (2) Parameters:
(String) eb5128e4
04/28/19 18:42:16.364 RPC Server (Port 2001): Info: Client number 109 is calling RPC method: listBidcosInterfaces (2) Parameters:
04/28/19 18:42:20.154 IPC Server: Info: Connection accepted. Client number: 169
04/28/19 18:42:20.156 IPC Server: Info: Client 1 successfully registered RPC method “cliOutput” (this method is registered by 1 client(s)).
04/28/19 18:42:20.157 IPC Server: Info: Client 1 successfully registered RPC method “cliOutput-1” (this method is registered by 1 client(s)).
04/28/19 18:42:24.867 IPC Server: Info: Client number 1 is calling RPC method: familyExists Parameters:
(Integer64) 0
04/28/19 18:42:29.685 HomeMatic BidCoS packet received (My-HM-MOD-RPI-PCB, RSSI: -64 dBm): 3101008F154688F00003103014F711A00000DA498BD1680001000001020110080403119C6288ADB7B98174F8845FF5712BBB
04/28/19 18:42:31.369 RPC Server (Port 2001): Info: Client number 109 is calling RPC method: ping (2) Parameters:
(String) eb5128e4
04/28/19 18:42:31.374 RPC Server (Port 2001): Info: Client number 109 is calling RPC method: listBidcosInterfaces (2) Parameters:
04/28/19 18:42:39.583 HomeMatic BidCoS packet received (My-HM-MOD-RPI-PCB, RSSI: -59 dBm): 3101008F154688F00003103014F711A00000DA498BD1680001000001020110080403119C6288ADB7B98174F8845FF5712BBB
04/28/19 18:42:40.872 HomeMatic BidCoS packet received (My-HM-MOD-RPI-PCB, RSSI: -59 dBm): 3101008F154688F00003103014F711A00000DA498BD1680001000001020110080403119C6288ADB7B98174F8845FF5712BBB
04/28/19 18:42:46.384 RPC Server (Port 2001): Info: Connection from ::ffff:127.0.0.1:44392 accepted. Client number: 171
04/28/19 18:42:46.384 RPC Server (Port 2001): Info: RPC server client id for client number 171 is: 29
04/28/19 18:42:46.386 RPC Server (Port 2001): Info: Client number 171 is calling RPC method: ping (2) Parameters:
(String) eb5128e4
04/28/19 18:42:46.391 RPC Server (Port 2001): Info: Client number 171 is calling RPC method: listBidcosInterfaces (2) Parameters:
04/28/19 18:42:50.710 HomeMatic BidCoS packet received (My-HM-MOD-RPI-PCB, RSSI: -68 dBm): 3101008F154xxxxxxxxxxxxxxx
Danke euch!
