Kein Pairing nach Update auf 0.6

Deutsche Foren Konfiguration
#1

Hallo zusammen
Nach dem Update von homegear auf die aktuelle Verion 0.6.0-1281 läuft das System jetzt wieder ohne Fehler.
Jedoch kann ich kein Gerät verbinden.
Das Error Log ist leer.
Und im Systemlog steht folgendes

04/15/16 17:39:33.756 RPC Server (Port 2001): Info: Client number 437 is calling RPC method: setInstallMode Parameters: (Boolean) 1 04/15/16 17:39:33.756 Module HomeMatic BidCoS: Info: Pairing mode enabled. 04/15/16 17:39:33.759 RPC Server (Port 2001): Info: Client number 437 is calling RPC method: getInstallMode Parameters: 04/15/16 17:39:33.762 RPC Server (Port 2001): Info: Connection to client number 437 closed (3). 04/15/16 17:39:33.850 RPC Server (Port 2001): Info: Connection from 192.168.1.251:57977 accepted. Client number: 438 04/15/16 17:39:33.850 RPC Server (Port 2001): Info: RPC server client id for client number 438 is: 424 04/15/16 17:39:33.851 RPC Server (Port 2001): Info: Client number 438 is calling RPC method: getInstallMode Parameters: 04/15/16 17:39:33.854 RPC Server (Port 2001): Info: Client number 438 is calling RPC method: getKeyMismatchDevice Parameters: (Boolean) 1 04/15/16 17:39:33.857 RPC Server (Port 2001): Info: Connection to client number 438 closed (3). 04/15/16 17:39:36.868 RPC Server (Port 2001): Info: Connection from 192.168.1.251:57982 accepted. Client number: 439 04/15/16 17:39:36.868 RPC Server (Port 2001): Info: RPC server client id for client number 439 is: 425 04/15/16 17:39:36.869 RPC Server (Port 2001): Info: Client number 439 is calling RPC method: listDevices Parameters: (Boolean) 0 04/15/16 17:39:36.879 RPC Server (Port 2001): Info: Connection to client number 439 closed (3). 04/15/16 17:39:36.949 RPC Server (Port 2001): Info: Connection from 192.168.1.251:57988 accepted. Client number: 440 04/15/16 17:39:36.950 RPC Server (Port 2001): Info: RPC server client id for client number 440 is: 426 04/15/16 17:39:36.951 RPC Server (Port 2001): Info: Client number 440 is calling RPC method: getServiceMessages Parameters: 04/15/16 17:39:36.961 RPC Server (Port 2001): Info: Connection to client number 440 closed (3). 04/15/16 17:39:38.524 RPC Server (Port 2001): Info: Connection from 192.168.1.251:57989 accepted. Client number: 441 04/15/16 17:39:38.531 RPC Server (Port 2001): Info: RPC server client id for client number 441 is: 427 04/15/16 17:39:38.533 RPC Server (Port 2001): Info: Client number 441 is calling RPC method: listBidcosInterfaces Parameters: 04/15/16 17:39:38.536 RPC Server (Port 2001): Info: Connection to client number 441 closed (3). 04/15/16 17:39:38.845 RPC Server (Port 2001): Info: Connection from 192.168.1.251:57993 accepted. Client number: 442 04/15/16 17:39:38.846 RPC Server (Port 2001): Info: RPC server client id for client number 442 is: 428 04/15/16 17:39:38.847 RPC Server (Port 2001): Info: Client number 442 is calling RPC method: getInstallMode Parameters: 04/15/16 17:39:38.850 RPC Server (Port 2001): Info: Client number 442 is calling RPC method: getKeyMismatchDevice Parameters: (Boolean) 1 04/15/16 17:39:38.853 RPC Server (Port 2001): Info: Connection to client number 442 closed (3). 04/15/16 17:39:41.838 RPC Server (Port 2001): Info: Connection from 192.168.1.251:57998 accepted. Client number: 443 04/15/16 17:39:41.839 RPC Server (Port 2001): Info: RPC server client id for client number 443 is: 429 04/15/16 17:39:41.840 RPC Server (Port 2001): Info: Client number 443 is calling RPC method: listDevices Parameters: (Boolean) 0 04/15/16 17:39:41.849 RPC Server (Port 2001): Info: Connection to client number 443 closed (3). 04/15/16 17:39:41.918 RPC Server (Port 2001): Info: Connection from 192.168.1.251:58004 accepted. Client number: 444 04/15/16 17:39:41.919 RPC Server (Port 2001): Info: RPC server client id for client number 444 is: 430 04/15/16 17:39:41.920 RPC Server (Port 2001): Info: Client number 444 is calling RPC method: getServiceMessages Parameters: 04/15/16 17:39:41.929 RPC Server (Port 2001): Info: Connection to client number 444 closed (3). 04/15/16 17:39:43.524 RPC Server (Port 2001): Info: Connection from 192.168.1.251:58005 accepted. Client number: 445 04/15/16 17:39:43.530 RPC Server (Port 2001): Info: RPC server client id for client number 445 is: 431 04/15/16 17:39:43.531 RPC Server (Port 2001): Info: Client number 445 is calling RPC method: listBidcosInterfaces Parameters: 04/15/16 17:39:43.534 RPC Server (Port 2001): Info: Connection to client number 445 closed (3). 04/15/16 17:39:43.850 RPC Server (Port 2001): Info: Connection from 192.168.1.251:58009 accepted. Client number: 446 04/15/16 17:39:43.851 RPC Server (Port 2001): Info: RPC server client id for client number 446 is: 432 04/15/16 17:39:43.852 RPC Server (Port 2001): Info: Client number 446 is calling RPC method: getInstallMode Parameters: 04/15/16 17:39:43.854 RPC Server (Port 2001): Info: Client number 446 is calling RPC method: getKeyMismatchDevice Parameters: (Boolean) 1 04/15/16 17:39:43.857 RPC Server (Port 2001): Info: Connection to client number 446 closed (3). 04/15/16 17:39:46.850 RPC Server (Port 2001): Info: Connection from 192.168.1.251:58016 accepted. Client number: 447 04/15/16 17:39:46.851 RPC Server (Port 2001): Info: RPC server client id for client number 447 is: 433 04/15/16 17:39:46.852 RPC Server (Port 2001): Info: Client number 447 is calling RPC method: listDevices Parameters: (Boolean) 0 04/15/16 17:39:46.861 RPC Server (Port 2001): Info: Connection to client number 447 closed (3). 04/15/16 17:39:46.956 RPC Server (Port 2001): Info: Connection from 192.168.1.251:58020 accepted. Client number: 448 04/15/16 17:39:46.957 RPC Server (Port 2001): Info: RPC server client id for client number 448 is: 434 04/15/16 17:39:46.958 RPC Server (Port 2001): Info: Client number 448 is calling RPC method: getServiceMessages Parameters: 04/15/16 17:39:46.967 RPC Server (Port 2001): Info: Connection to client number 448 closed (3). 04/15/16 17:39:48.524 RPC Server (Port 2001): Info: Connection from 192.168.1.251:58021 accepted. Client number: 449 04/15/16 17:39:48.525 RPC Server (Port 2001): Info: RPC server client id for client number 449 is: 435 04/15/16 17:39:48.531 RPC Server (Port 2001): Info: Client number 449 is calling RPC method: listBidcosInterfaces Parameters: 04/15/16 17:39:48.534 RPC Server (Port 2001): Info: Connection to client number 449 closed (3). 04/15/16 17:39:48.840 RPC Server (Port 2001): Info: Connection from 192.168.1.251:58025 accepted. Client number: 450 04/15/16 17:39:48.841 RPC Server (Port 2001): Info: RPC server client id for client number 450 is: 436 04/15/16 17:39:48.842 RPC Server (Port 2001): Info: Client number 450 is calling RPC method: getInstallMode Parameters: 04/15/16 17:39:48.845 RPC Server (Port 2001): Info: Client number 450 is calling RPC method: getKeyMismatchDevice Parameters: (Boolean) 1 04/15/16 17:39:48.848 RPC Server (Port 2001): Info: Connection to client number 450 closed (3). 04/15/16 17:39:51.888 RPC Server (Port 2001): Info: Connection from 192.168.1.251:58033 accepted. Client number: 451 04/15/16 17:39:51.889 RPC Server (Port 2001): Info: RPC server client id for client number 451 is: 437 04/15/16 17:39:51.890 RPC Server (Port 2001): Info: Client number 451 is calling RPC method: listDevices Parameters: (Boolean) 0 04/15/16 17:39:51.899 RPC Server (Port 2001): Info: Connection to client number 451 closed (3). 04/15/16 17:39:51.962 RPC Server (Port 2001): Info: Connection from 192.168.1.251:58037 accepted. Client number: 452 04/15/16 17:39:51.962 RPC Server (Port 2001): Info: RPC server client id for client number 452 is: 438 04/15/16 17:39:51.964 RPC Server (Port 2001): Info: Client number 452 is calling RPC method: getServiceMessages Parameters: 04/15/16 17:39:51.973 RPC Server (Port 2001): Info: Connection to client number 452 closed (3). 04/15/16 17:39:53.524 RPC Server (Port 2001): Info: Connection from 192.168.1.251:58038 accepted. Client number: 453 04/15/16 17:39:53.530 RPC Server (Port 2001): Info: RPC server client id for client number 453 is: 439 04/15/16 17:39:53.531 RPC Server (Port 2001): Info: Client number 453 is calling RPC method: listBidcosInterfaces Parameters: 04/15/16 17:39:53.534 RPC Server (Port 2001): Info: Connection to client number 453 closed (3). 04/15/16 17:39:53.848 RPC Server (Port 2001): Info: Connection from 192.168.1.251:58042 accepted. Client number: 454 04/15/16 17:39:53.849 RPC Server (Port 2001): Info: RPC server client id for client number 454 is: 440 04/15/16 17:39:53.850 RPC Server (Port 2001): Info: Client number 454 is calling RPC method: getInstallMode Parameters: 04/15/16 17:39:53.853 RPC Server (Port 2001): Info: Client number 454 is calling RPC method: getKeyMismatchDevice Parameters: (Boolean) 1 04/15/16 17:39:53.855 RPC Server (Port 2001): Info: Connection to client number 454 closed (3). 04/15/16 17:39:56.856 RPC Server (Port 2001): Info: Connection from 192.168.1.251:58049 accepted. Client number: 455 04/15/16 17:39:56.857 RPC Server (Port 2001): Info: RPC server client id for client number 455 is: 441 04/15/16 17:39:56.858 RPC Server (Port 2001): Info: Client number 455 is calling RPC method: listDevices Parameters: (Boolean) 0 04/15/16 17:39:56.868 RPC Server (Port 2001): Info: Connection to client number 455 closed (3). 04/15/16 17:39:56.933 RPC Server (Port 2001): Info: Connection from 192.168.1.251:58053 accepted. Client number: 456 04/15/16 17:39:56.934 RPC Server (Port 2001): Info: RPC server client id for client number 456 is: 442 04/15/16 17:39:56.935 RPC Server (Port 2001): Info: Client number 456 is calling RPC method: getServiceMessages Parameters: 04/15/16 17:39:56.944 RPC Server (Port 2001): Info: Connection to client number 456 closed (3). 04/15/16 17:39:58.390 RPC Server (Port 2001): Info: Connection from 192.168.1.251:58060 accepted. Client number: 457 04/15/16 17:39:58.391 RPC Server (Port 2001): Info: RPC server client id for client number 457 is: 443 04/15/16 17:39:58.392 RPC Server (Port 2001): Info: Client number 457 is calling RPC method: setInstallMode Parameters: (Boolean) 0 04/15/16 17:39:58.423 RPC Server (Port 2001): Info: Connection from 192.168.1.251:58061 accepted. Client number: 458 04/15/16 17:39:58.424 RPC Server (Port 2001): Info: RPC server client id for client number 458 is: 444 04/15/16 17:39:58.425 RPC Server (Port 2001): Info: Client number 458 is calling RPC method: listBidcosInterfaces Parameters: 04/15/16 17:39:58.428 RPC Server (Port 2001): Info: Client number 458 is calling RPC method: listDevices Parameters: (Boolean) 0 04/15/16 17:39:58.437 RPC Server (Port 2001): Info: Connection to client number 458 closed (3). 04/15/16 17:39:58.515 Module HomeMatic BidCoS: Info: Pairing mode disabled. 04/15/16 17:39:58.518 RPC Server (Port 2001): Info: Client number 457 is calling RPC method: getInstallMode Parameters: 04/15/16 17:39:58.521 RPC Server (Port 2001): Info: Connection to client number 457 closed (3). 04/15/16 17:39:58.525 RPC Server (Port 2001): Info: Connection from 192.168.1.251:58062 accepted. Client number: 459 04/15/16 17:39:58.526 RPC Server (Port 2001): Info: RPC server client id for client number 459 is: 445 04/15/16 17:39:58.527 RPC Server (Port 2001): Info: Client number 459 is calling RPC method: listBidcosInterfaces Parameters: 04/15/16 17:39:58.530 RPC Server (Port 2001): Info: Connection to client number 459 closed (3).

Hat jemand eine Idee?

Beste Grüsse

Silvan

#2

Hey Silvan,

ich sehe im Log überhaupt keine Pakete. Du versuchst HomeMatic-BidCoS-Geräte anzulernen? Die Konfiguration liegt jetzt in “/etc/homegear/families/homematicbidcos.conf”. Hast du diese entsprechend deiner alten Einstellungen angepasst?

Viele Grüße

Sathya

#3

Hey Sathya
Ja ich versuche HomeMatic BidCos Geräte anzulernen.
Folgende Konfiguration habe ich.

[quote]#######################################
########## General Settings ##########
#######################################

[General]

The BidCoS address of Homegear. It is recommended to change this to a random 3 byte hexadecimal

value starting with 0xFD (e. g. 0xFD43AB). Only change this, when no HomeMatic BidCoS devices

are paired to Homegear as existing pairings will not work anymore!

#centralAddress = 0xFD0001

Specify a 16 byte (32 characters) long AES key here to protect your wireless communication

!!! IMPORTANT: It is highly recommended to change this key before pairing the first device.

!!! IMPORTANT: Never ever lose this key. That would render your devices useless.

To remove the key from your devices, you need to factory reset them

rfKey = hier steht der AES key…

With each key change currentRFKeyIndex needs to be

incremented by 1

currentRFKeyIndex = 1

When you change rfKey, put the old key here. To change the key Homegear needs to know the

old and the new one.

!!! Do not set oldRFKey when you set rfKey for the first time !!!

##oldRFKey = 00112233445566778899AABBCCDDEEFF[/quote]

und

[quote]#######################################
######### COC, SCC, CSM, CCD #########
#######################################

The device family this interface is for

[COC, SCC, CSM, CCD]

Specify an unique id here to identify this device in Homegear

id = My-COC

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

Also use “coc” for SCC, CCD and CSM

deviceType = coc

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

“17” for COC, SCC and CCD. Empty for CSM.

gpio1 = 17

Default: gpio2 = 0

“18” for COC and SCC. “22” for CCD. Empty for CSM.

gpio2 = 18

Default: stackPosition = 0 (= no stacking)

Set stackPosition if you use the SCC and stacked multiple devices.

Set stackPosition to “1” for the lowest device, to “2” for the device

above that and so on.

stackPosition = 0
[/quote]

Der Grund für mein Update auf das 0.6 war ein Stromausfall, eventuell hat dieser auch das SCC zerstört?
Viele Grüsse

Silvan

#4

Hey Silvan,

zumindest sieht auf den ersten Blick die Konfiguration soweit ok aus. Im Log stehen ansonsten keine Fehlermeldungen? Ist /dev/ttyAMA0 frei - also ist ttyAMA aus der /boot/cmdline.txt und /etc/inittab entfernt? Wenn du das Homegear-Image verwendest, ist das standardmäßig bereits korrekt eingestellt.

Falls an der Stelle alles passt, kannst du, wie auf der busware-Seite beschrieben, den SCC einmal manuell starten und dann mit “screen /dev/ttyAMA0” und anschließendem “V” mal sehen, ob eine Versionsnummer ausgegeben wird. Ist das der Fall, kannst du in screen “Ar” eintippen und schauen, ob dort HomeMatic-BidCoS-Pakete geloggt werden. Ist das nicht der Fall, ist dein Modul vermutlich tatsächlich defekt.

Viele Grüße

Sathya