OpenHabian und Homegear auf Pi2 mit HM-MOD-RPI-PCB - GELÖST

Hallo Zusammen,

wie oben beschrieben versuche ich auf einem Pi2 OpenHAB und Homegear einzurichten. Bislang nutzte ich Raspberrymatic, ich bin von OpenHAB allerdings mehr überzeugt und möchte wechseln. Ich habe auch bereits erfolgreich mein TRADFRI-Gateway hinzugefügt, die Lichter ließen sich auch schalten. Hier also alles toll.

Leider schaffe ich es einfach nicht, Homegear mit dem Homematic-Binding zum Laufen zu bekommen. Ich habe:

  • Openhabian installiert
  • alles auf den neuesten Stand gebracht
  • Homegear installiert (über config)
  • die Serialports geändert
    57%20-%20PuTTY
  • die homematicbidcos.conf abgeändert

-#######################################
-########### 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

  • alles neu gestartet
  • das entsprechende Binding hinzugefügt und adressiert
  • erneuter reboot

leider tut sich nichts. Weder über putty noch direkt in PaperUI.

[10:01:19] openhabian@openHABianPi:~$ sudo homegear -r
Connected to Homegear (version 0.7.17-1798).

fs 0
Device family “HomeMatic BidCoS” selected.
For information about the family’s commands type: “help”
(Family)> pon
Pairing mode enabled for 60 seconds.
(Family)>

Ich bin langsam echt ratlos, vielleicht hat jemand einen Tipp für mich oder kann mir sonst helfen.

Entschuldigt bitte die Formatierung, ich bin mit dieser noch nicht so richtig warm.

Vielen Dank und Grüße

Jan

Du kannst deinen Beitrag nachträglich bearbeiten und die Formatierung hiermit anpassen:
grafik


Du musst die Sektion für das HM-MOD-RPI-PCB in deiner homematicbidcos.conf auch einkommentieren:

#[HomeMatic Wireless Module for Raspberry Pi]

wird

[HomeMatic Wireless Module for Raspberry Pi]

Gruß,
Patrik

1 Like

Hallo Patrik,

erstmal vielen Dank. Leider bewirkt auch das keine Veränderung.
Ich habe mir das Homegear-Log angeschaut und irgendwie scheint mein HM-MOD-RPI-PCB dort nirgends aufzutauchen. Sollte es das nicht?

05/22/18 09:11:39.642 Starting Homegear...

05/22/18 09:11:39.643 Homegear version 0.7.17-1798
05/22/18 09:11:39.643 Git commit SHA of libhomegear-base: -
05/22/18 09:11:39.643 Git branch of libhomegear-base: -
05/22/18 09:11:39.643 Git commit SHA of Homegear: -
05/22/18 09:11:39.643 Git branch of Homegear: -
05/22/18 09:11:39.644 Info: Setting allowed core file size to “4294967295” for user with id 0 and group with id 0.
05/22/18 09:11:39.645 Info: Core file size now is “4294967295”.
05/22/18 09:11:39.645 Info: Setting maximum thread priority to “4294967295” for user with id 0 and group with id 0.
05/22/18 09:11:39.645 Info: Maximum thread priority now is “4294967295”.
05/22/18 09:11:39.648 Warning: No database found. Trying to restore backup.
05/22/18 09:11:40.046 Warning: Database could not be restored. Creating new database.
05/22/18 09:11:40.083 Initializing database…
05/22/18 09:11:44.303 Default password for user “homegear” set to: ^Dts|UA$PqFh
05/22/18 09:11:44.317 Info: Loading family module mod_homematicbidcos.so
05/22/18 09:11:44.344 /etc/homegear/families/homematicbidcos.conf
05/22/18 09:11:44.347 Info: Loading family module mod_miscellaneous.so
05/22/18 09:11:44.354 /etc/homegear/families/miscellaneous.conf
05/22/18 09:11:44.356 Info: Loading family module mod_homematicwired.so
05/22/18 09:11:44.369 /etc/homegear/families/homematicwired.conf
05/22/18 09:11:44.370 Info: Setting up physical interfaces and GPIOs…
05/22/18 09:11:44.370 Info: Dropping privileges to user homegear (110) and group homegear (115)
05/22/18 09:11:44.372 Info: Homegear is (now) running as user with id 110 and group with id 115.
05/22/18 09:11:44.393 Starting script engine server…
05/22/18 09:11:44.408 Initializing licensing controller…
05/22/18 09:11:44.408 Loading licensing controller data…
05/22/18 09:11:44.408 Loading devices…
05/22/18 09:11:44.409 Loading XML RPC devices…
05/22/18 09:11:46.083 Module HomeMatic BidCoS: Created HomeMatic BidCoS central with id 0, address 0xFD7DC2 and serial number VBC4563666
05/22/18 09:11:46.094 Loading XML RPC devices…
05/22/18 09:11:46.189 Module HomeMatic Wired: Created HomeMatic Wired central with id 0, address 0x00000001 and serial number VWC4281800
05/22/18 09:11:46.200 Loading XML RPC devices…
05/22/18 09:11:46.221 Module Miscellaneous: Created Miscellaneous central with id 0.
05/22/18 09:11:46.240 Initializing RPC client…
05/22/18 09:11:46.241 Starting XML RPC server RPCServer1 listening on :::2001…
05/22/18 09:11:46.249 RPC Server (Port 2001): Warning: SSL is not enabled for this RPC server. It is strongly recommended to disable all unencrypted RPC servers when the connected clients support it.
05/22/18 09:11:46.250 RPC Server (Port 2001): Warning: RPC server has no authorization enabled. Everybody on your local network can login into this installation. It is strongly recommended to enable authorization on all RPC servers when$
05/22/18 09:11:46.251 Starting XML RPC server RPCServer2 listening on :::2002, SSL enabled…
05/22/18 09:11:46.252 RPC Server (Port 2001): Info: RPC Server started listening on address :: and port 2001
05/22/18 09:11:46.258 RPC Server (Port 2002): Warning: RPC server has no authorization enabled. Everybody on your local network can login into this installation. It is strongly recommended to enable authorization on all RPC servers when$
05/22/18 09:11:46.326 Starting XML RPC server RPCServer3 listening on :::2003, SSL enabled, authentication enabled…
05/22/18 09:11:46.327 RPC Server (Port 2002): Info: RPC Server started listening on address :: and port 2002
05/22/18 09:11:46.384 Starting CLI server…
05/22/18 09:11:46.384 RPC Server (Port 2003): Info: RPC Server started listening on address :: and port 2003
05/22/18 09:11:46.385 Initializing event handler…
05/22/18 09:11:46.386 Loading events…
05/22/18 09:11:46.387 Start listening for packets…
05/22/18 09:11:46.387 Starting Node-BLUE server…
05/22/18 09:11:46.397 Starting IPC server…
05/22/18 09:11:46.404 Startup complete. Waiting for physical interfaces to connect.
05/22/18 09:11:46.405 All physical interfaces are connected now.
05/22/18 09:11:46.405 Starting UPnP server…
05/22/18 09:11:46.407 Info: Created new UPnP UDN: 8EF8B307-2C89-4686-1B95-5DCB792C3A72
05/22/18 09:11:46.408 Info: UPnP server: Binding to address: 192.168.178.57
05/22/18 09:11:46.408 UPnP Server: Info: Started listening.
05/22/18 09:12:46.074 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.178.29:49815 accepted. Client number: 8
05/22/18 09:12:46.075 RPC Server (Port 2001): Info: RPC server client id for client number 8 is: 0
05/22/18 09:12:46.399 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.178.39:57877 accepted. Client number: 9

Viel kann ich leider nicht damit anfangen.

Außerdem erscheint im Log von OpenHAB folgendes:

2018-05-22 10:22:51.710 [INFO ] [ng.homematic.internal.misc.MiscUtils] - Datapoint name 'Connect.php' contains invalid characters, new Datapoint name 'Connect_php'

2018-05-22 10:22:51.720 [INFO ] [ng.homematic.internal.misc.MiscUtils] - Datapoint name 'RestoreHomegear.sh' contains invalid characters, new Datapoint name 'RestoreHomegear_sh'

2018-05-22 10:22:51.724 [INFO ] [ng.homematic.internal.misc.MiscUtils] - Datapoint name 'Test.php' contains invalid characters, new Datapoint name 'Test_php'

2018-05-22 10:22:51.748 [INFO ] [ng.homematic.internal.misc.MiscUtils] - Datapoint name 'ReadMe.txt' contains invalid characters, new Datapoint name 'ReadMe_txt'

2018-05-22 10:22:51.754 [INFO ] [ng.homematic.internal.misc.MiscUtils] - Datapoint name 'BackupHomegear.sh' contains invalid characters, new Datapoint name 'BackupHomegear_sh'

2018-05-22 10:30:12.733 [INFO ] [ng.homematic.internal.misc.MiscUtils] - Datapoint name 'Connect.php' contains invalid characters, new Datapoint name 'Connect_php'

2018-05-22 10:30:12.750 [INFO ] [ng.homematic.internal.misc.MiscUtils] - Datapoint name 'RestoreHomegear.sh' contains invalid characters, new Datapoint name 'RestoreHomegear_sh'

2018-05-22 10:30:12.753 [INFO ] [ng.homematic.internal.misc.MiscUtils] - Datapoint name 'Test.php' contains invalid characters, new Datapoint name 'Test_php'

2018-05-22 10:30:12.756 [INFO ] [ng.homematic.internal.misc.MiscUtils] - Datapoint name 'ReadMe.txt' contains invalid characters, new Datapoint name 'ReadMe_txt'

2018-05-22 10:30:12.766 [INFO ] [ng.homematic.internal.misc.MiscUtils] - Datapoint name 'BackupHomegear.sh' contains invalid characters, new Datapoint name 'BackupHomegear_sh'

Das Errorlog zeigt an, dass keine Kommunikation zum Funkmodul stattfinden kann.

05/22/18 09:11:46.083 Module HomeMatic BidCoS: Created HomeMatic BidCoS central with id 0, address 0xFD7DC2 and serial number VBC4563666
05/22/18 09:11:46.094 Loading XML RPC devices…
[...]
05/22/18 09:11:46.405 All physical interfaces are connected now.

Sieht aber schon ganz gut aus.

Stell bitte mal das debuglevel auf 4 und poste mal das Log des Anlernvorgangs.
Du kannst das mit der homegear-Konsoel (sudo homegear -r) mit dl 4 zur Laufzeit machen.

1 Like

Du machst mir Hoffnung!

Das Debuglevel habe ich hochgesetzt (oder runter?!), leider weiß ich nicht, welches das Log des Anlernvorganges ist. Findet sich das auch in homegear.log oder in homegear.err oder an einer anderen Stelle?

Ich habe hier auch mal das homegear.err-Log, hier scheint ein ganz grundlegendes Problem vorhanden zu sein, da das Modul gar nicht reagiert.

homegear.err-Log

05/22/18 18:07:38.878 Warning: No database found. Trying to restore backup.
05/22/18 18:07:39.274 Warning: Database could not be restored. Creating new database.
05/22/18 18:07:45.629 RPC Server (Port 2001): Warning: SSL is not enabled for this RPC server. It is strongly recommended to disable all unencrypted RPC servers when the connected clients support it.
05/22/18 18:07:45.629 RPC Server (Port 2001): Warning: RPC server has no authorization enabled. Everybody on your local network can login into this installation. It is strongly recommended to enable authorization on all RPC servers when$
05/22/18 18:07:45.637 RPC Server (Port 2002): Warning: RPC server has no authorization enabled. Everybody on your local network can login into this installation. It is strongly recommended to enable authorization on all RPC servers when$
05/22/18 18:17:37.229 RPC Server (Port 2001): Warning: SSL is not enabled for this RPC server. It is strongly recommended to disable all unencrypted RPC servers when the connected clients support it.
05/22/18 18:17:37.231 RPC Server (Port 2001): Warning: RPC server has no authorization enabled. Everybody on your local network can login into this installation. It is strongly recommended to enable authorization on all RPC servers when$
05/22/18 18:17:37.239 RPC Server (Port 2002): Warning: RPC server has no authorization enabled. Everybody on your local network can login into this installation. It is strongly recommended to enable authorization on all RPC servers when$
05/22/18 18:17:46.405 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
05/22/18 18:17:46.405 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
05/22/18 18:17:47.977 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
05/22/18 18:18:03.913 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
05/22/18 18:18:03.913 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
05/22/18 18:18:05.490 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
05/22/18 18:18:13.630 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
05/22/18 18:18:13.630 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
05/22/18 18:18:15.206 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
05/22/18 18:18:23.346 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
05/22/18 18:18:23.346 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
05/22/18 18:18:24.923 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
05/22/18 18:18:33.062 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
05/22/18 18:18:33.063 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
05/22/18 18:18:34.639 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
05/22/18 18:18:42.778 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
05/22/18 18:18:42.779 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
05/22/18 18:18:44.353 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
05/22/18 18:18:52.493 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
05/22/18 18:18:52.493 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
05/22/18 18:18:58.160 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
05/22/18 18:19:06.299 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
05/22/18 18:19:06.300 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
05/22/18 18:19:07.876 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
05/22/18 18:19:16.015 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
05/22/18 18:19:16.016 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
05/22/18 18:19:17.592 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
05/22/18 18:19:25.731 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
05/22/18 18:19:25.732 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
05/22/18 18:19:27.308 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
05/22/18 18:19:35.447 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
05/22/18 18:19:35.448 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
05/22/18 18:19:37.020 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
05/22/18 18:19:45.159 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
05/22/18 18:19:45.159 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
05/22/18 18:19:46.736 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
05/22/18 18:19:54.875 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
05/22/18 18:19:54.875 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
05/22/18 18:19:56.452 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
05/22/18 18:20:04.591 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
05/22/18 18:20:04.591 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
05/22/18 18:20:06.163 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
05/22/18 18:20:14.302 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
05/22/18 18:20:14.303 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
05/22/18 18:20:15.878 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...

Das homegear.log-Log ist das Folgende

homegear.log-Log

05/22/18 18:07:38.873 Starting Homegear...
05/22/18 18:07:38.873 Homegear version 0.7.17-1798
05/22/18 18:07:38.874 Git commit SHA of libhomegear-base: -
05/22/18 18:07:38.874 Git branch of libhomegear-base:     -
05/22/18 18:07:38.874 Git commit SHA of Homegear:         -
05/22/18 18:07:38.874 Git branch of Homegear:             -
05/22/18 18:07:38.875 Info: Setting allowed core file size to "4294967295" for user with id 0 and group with id 0.
05/22/18 18:07:38.875 Info: Core file size now is "4294967295".
05/22/18 18:07:38.876 Info: Setting maximum thread priority to "4294967295" for user with id 0 and group with id 0.
05/22/18 18:07:38.876 Info: Maximum thread priority now is "4294967295".
05/22/18 18:07:38.878 Warning: No database found. Trying to restore backup.
05/22/18 18:07:39.274 Warning: Database could not be restored. Creating new database.
05/22/18 18:07:39.519 Initializing database...
05/22/18 18:07:41.656 Default password for user "homegear" set to: !CHXF)Z%0za4
05/22/18 18:07:42.298 Info: Loading family module mod_homematicbidcos.so
05/22/18 18:07:42.316 /etc/homegear/families/homematicbidcos.conf
05/22/18 18:07:42.319 Info: Loading family module mod_miscellaneous.so
05/22/18 18:07:42.324 /etc/homegear/families/miscellaneous.conf
05/22/18 18:07:42.325 Info: Loading family module mod_homematicwired.so
05/22/18 18:07:42.334 /etc/homegear/families/homematicwired.conf
05/22/18 18:07:42.335 Info: Setting up physical interfaces and GPIOs...
05/22/18 18:07:42.335 Info: Dropping privileges to user homegear (110) and group homegear (115)
05/22/18 18:07:42.336 Info: Homegear is (now) running as user with id 110 and group with id 115.
05/22/18 18:07:42.351 Starting script engine server...
05/22/18 18:07:42.365 Initializing licensing controller...
05/22/18 18:07:42.366 Loading licensing controller data...
05/22/18 18:07:42.366 Loading devices...
05/22/18 18:07:42.366 Loading XML RPC devices...
05/22/18 18:07:44.026 Module HomeMatic BidCoS: Created HomeMatic BidCoS central with id 0, address 0xFD2F78 and serial number VBC0637429
05/22/18 18:07:45.444 Loading XML RPC devices...
05/22/18 18:07:45.564 Module HomeMatic Wired: Created HomeMatic Wired central with id 0, address 0x00000001 and serial number VWC4828930
05/22/18 18:07:45.574 Loading XML RPC devices...
05/22/18 18:07:45.604 Module Miscellaneous: Created Miscellaneous central with id 0.
05/22/18 18:07:45.622 Initializing RPC client...
05/22/18 18:07:45.622 Starting XML RPC server RPCServer1 listening on :::2001...
05/22/18 18:07:45.628 RPC Server (Port 2001): Warning: SSL is not enabled for this RPC server. It is strongly recommended to disable all unencrypted RPC servers when the connected clients support it.
05/22/18 18:07:45.629 RPC Server (Port 2001): Warning: RPC server has no authorization enabled. Everybody on your local network can login into this installation. It is strongly recommended to enable authorization on all RPC servers when$
05/22/18 18:07:45.630 Starting XML RPC server RPCServer2 listening on :::2002, SSL enabled...
05/22/18 18:07:45.631 RPC Server (Port 2001): Info: RPC Server started listening on address :: and port 2001
05/22/18 18:07:45.637 RPC Server (Port 2002): Warning: RPC server has no authorization enabled. Everybody on your local network can login into this installation. It is strongly recommended to enable authorization on all RPC servers when$
05/22/18 18:07:45.698 Starting XML RPC server RPCServer3 listening on :::2003, SSL enabled, authentication enabled...
05/22/18 18:07:45.698 RPC Server (Port 2002): Info: RPC Server started listening on address :: and port 2002
05/22/18 18:07:45.754 Starting CLI server...
05/22/18 18:07:45.754 RPC Server (Port 2003): Info: RPC Server started listening on address :: and port 2003
05/22/18 18:07:45.754 Initializing event handler...
05/22/18 18:07:45.755 Loading events...
05/22/18 18:07:45.756 Start listening for packets...
05/22/18 18:07:45.756 Starting Node-BLUE server...
05/22/18 18:07:45.765 Starting IPC server...
05/22/18 18:07:45.773 Startup complete. Waiting for physical interfaces to connect.
05/22/18 18:07:45.773 All physical interfaces are connected now.
05/22/18 18:07:45.773 Starting UPnP server...
05/22/18 18:07:45.775 Info: Created new UPnP UDN: D1CD3E13-2A7B-A704-E5FC-86627128F4FE
05/22/18 18:07:45.776 Info: UPnP server: Binding to address: 192.168.178.57
05/22/18 18:07:45.776 UPnP Server: Info: Started listening.
05/22/18 18:08:45.151 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.178.29:37961 accepted. Client number: 8
05/22/18 18:08:45.152 RPC Server (Port 2001): Info: RPC server client id for client number 8 is: 0
05/22/18 18:08:45.316 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.178.39:60738 accepted. Client number: 9

Ps.: Wie sichere ich den Server? Der hier genannte Client ist mein FireTV-Stick. Warum auch immer der hier auftaucht…

05/22/18 18:07:45.629 RPC Server (Port 2001): Warning: SSL is not enabled for this RPC server. It is strongly recommended to disable all unencrypted RPC servers when the connected clients support it.

05/22/18 18:08:45.151 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.178.29:37961 accepted. Client number: 8

Dein FireTV taucht wegen UPNP auf… UPNPAV…

Ich habe selbst kein HM-MOD-RPI-PCB aber ich denke, dass du ein Firmwareupdate des Moduls machen musst.

Such danach mal hier im Forum/Google.

1 Like

Hab sowas schon befürchtet. Na dann mal los :unamused:

Danke für Deine Hilfe

1 Like

Erledigt und siehe da, anlernen erfolgreich.
Perfekt, Danke nochmal!

1 Like

Schreib noch kurz rein wo du es gefunden hast/wie du es gemacht hast…

Kein Problem, gerne. Ich habe hier in Forum gesucht und mich schlussendlich an die Anleitung aus dem FHEM-Wiki (ohne FHEM) gehalten und die Firmware aktualisiert.

#Superuser
sudo su

#Homegear stoppen
systemctl stop homegear

#Homegear aus dem Autostart nehmen
update-rc.d homegear disable

#Raspberry herunterfahren
halt

#Raspberry vom Netz nehmen (ein paar Sekunden)

#Superuser
sudo su

#Entsprechend [FHEM-Anleitung](https://wiki.fhem.de/wiki/HM-MOD-RPI-PCB_HomeMatic_Funkmodul_f%C3%BCr_Raspberry_Pi#Alternative_Methode_zum_Firmware_Update_ohne_FHEM) vorgehen
apt-get update && apt-get -y install libusb-1.0-0-dev build-essential git

systemctl stop fhem

git clone git://git.zerfleddert.de/hmcfgusb

cd hmcfgusb/

make

#Firmware laden
wget https://raw.githubusercontent.com/eq-3/occu/ee68faf77e42ed5e3641790b43a710a3301cea7e/firmware/HM-MOD-UART/coprocessor_update.eq3

#Firmware flashen
./flash-hmmoduart -U /dev/ttyAMA0 coprocessor_update.eq3

#Homegear wieder in den Autostart
update-rc.d homegear enable

#Homegear starten
systemctl start homegear

#Pi neustarten
reboot

Das war es auch schon. Sofort danach konnte ich meine Homematic-Geräte anlernen.

1 Like