XML RPC mit FHEM

trilu · October 2, 2016, 5:19pm

Hallo Zusammen,
ich betreibe seit kurzem Homegear (Max und HM Geräte )in Verbindung mit FHEM. Funktioniert soweit auch gut und stabil, jedoch ist mir ein Fehler aufgefallen - wenn ich in Homegear/HM-Manager das Wochenprogramm eines MAX Heizungsreglers ändere, versucht Homegear das an FHEM zu melden, allerdings über eine Funktion die von FHEM nicht angemeldet wurde.

09/27/15 10:29:33.295 Info: Calling RPC method "updateDevice" on server 127.0.0.1. 09/27/15 10:29:33.296 Info: Connecting to host 127.0.0.1 on port 8083... ...snip... 09/27/15 10:29:33.366 Error in RPC response from 127.0.0.1. faultCode: 200 faultString: Method lookup error: No method 'Unknown method: updateDevice' on server 09/27/15 10:29:33.372 Info: Calling RPC method "error" on server 127.0.0.1. 09/27/15 10:29:33.375 Info: Connecting to host 127.0.0.1 on port 8083... ...snip... 09/27/15 10:29:33.419 Error in RPC response from 127.0.0.1. faultCode: 200 faultString: Method lookup error: No method 'Unknown method: error' on server

Der Entwickler des RPC Moduls für FHEM hat mir das so erklärt:

[quote]Die “Spezifikation” für das XML-RPC-Interface von eQ-3 spezifiziert das zwar leider nicht, aber sowohl die defacto-Implementierung der Original-CCU als auch Homegear’s eigene Dokumentation (homegear.eu/index.php/XML_R … _Functions) stimmen überein: Ein XML-RPC-Client muss nicht alle Callbacks implementieren, stattdessen wird bei Registrierung über system.listMethods() abgefragt, welche existieren, und dann nur diese verwendet. Das HMRPC-Modul hat zur Zeit nur newDevices() (Callback das Informationen über neue Geräte bekommt) und event() (Callback über das alle Events eingekippt werden), sowie einen Dummy für listDevices() der immer behauptet, wir würden gar keine Geräte kennen.

In deinen Logs versucht Homegear updateDevice() (eine Gerätekonfiguration wurde geändert) aufzurufen. Da das nicht klappt, kommt es zu einem Fehler, und einem doppelten: Homegear versucht jetzt den Fehler über error() (ein Fehler in Homegear ist aufgetreten, das ist übrigens gar nicht Teil der eQ-3-XML-RPC-Spezifikation) zu melden.[/quote]
Viele Grüße
Horst

sathya · October 2, 2016, 5:19pm

Hallo Horst,

der Entwickler des RPC-Moduls hat absolut recht. Aber: Homegear beachtet die Rückgabe von system.listMethods(), außer system.listMethods() gibt nichts zurück, dann werden alle Funktionen aufgerufen. Magst du einmal den Loglevel auf 5 setzen und mir das Log vom Anmelden an FHEM schicken (es reicht der Aufruf von init() und system.listMethods())? Das Problem sollte schnell gelöst sein .

Viele Grüße

Sathya

trilu · October 2, 2016, 5:19pm

Hi Sathya,
reicht das?

[code]09/29/15 17:38:44.762 Info: CLI connection accepted. Client number: 10603
09/29/15 17:39:03.261 UPnP Server: Debug: Discovery packet received from 239.255.255.250:1900
09/29/15 17:39:03.282 Debug: Sleeping 357ms before sending response.
09/29/15 17:39:03.640 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
09/29/15 17:39:03.708 Connection to client number 10603 closed.
09/29/15 17:39:03.741 UPnP Server: Debug: Sending notify packets.
09/29/15 17:39:03.743 UPnP Server: Debug: Discovery packet received from 239.255.255.250:1900
09/29/15 17:39:03.764 Debug: Sleeping 278ms before sending response.
09/29/15 17:39:04.042 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
09/29/15 17:39:04.143 UPnP Server: Debug: Sending notify packets.
09/29/15 17:39:06.774 Module HomeMatic BidCoS: LAN-Konfigurationsadapter “My-HM-CFG-LAN”: Debug: Sending: K
09/29/15 17:39:06.800 Module HomeMatic BidCoS: LAN-Konfigurationsadapter “My-HM-CFG-LAN”: Debug: Packet received from HM-CFG-LAN: HHM-LAN-IF,03C7,JEQ0534974,1DB017,631963,04D02E33,0001
09/29/15 17:39:09.555 MAX packet received (My-MAX-CUL, RSSI: 0x41): 0CE7044206A37D069FED0018CF
09/29/15 17:39:09.557 Info (My-MAX-CUL): Packet processing took 1 ms.
09/29/15 17:39:09.602 MAX packet received (My-MAX-CUL, RSSI: 0x51): 0EE70202069FED06A37D0001390018
09/29/15 17:39:09.603 Info (My-MAX-CUL): Packet processing took 1 ms.
09/29/15 17:39:13.028 RPC Server (Port 2001): Info: Connection from 127.0.0.1:51004 accepted. Client number: 10604
09/29/15 17:39:13.033 RPC Server (Port 2001): Listening for incoming packets from client number 10604.
09/29/15 17:39:13.041 RPC Server (Port 2001): Debug: Packet received: 504F5354202F20485454502F312E300D0A4163636570742D456E636F64696E673A206465666C6174650D0A486F73743A203132372E302E302E313A323030310D0A557365722D4167656E743A205250433A3A584D4C3A3A436C69656E742F312E3432206C69627777772D7065726C2F362E30380D0A436F6E74656E742D4C656E6774683A203230340D0A436F6E74656E742D547970653A20746578742F786D6C0D0A0D0A3C3F786D6C2076657273696F6E3D22312E302220656E636F64696E673D2275732D6173636969223F3E3C6D6574686F6443616C6C3E3C6D6574686F644E616D653E696E69743C2F6D6574686F644E616D653E3C706172616D733E3C706172616D3E3C76616C75653E3C737472696E673E687474703A2F2F3132372E302E302E313A383038332F6668656D2F484D5250435F686D72662F726571756573743C2F737472696E673E3C2F76616C75653E3C2F706172616D3E3C2F706172616D733E3C2F6D6574686F6443616C6C3E
09/29/15 17:39:13.042 RPC Server (Port 2001): Info: Client number 10604 is calling RPC method: init Parameters:
(String) http://127.0.0.1:8083/fhem/HMRPC_hmrf/request
09/29/15 17:39:13.043 Debug: Server path set to: /fhem/HMRPC_hmrf/request
09/29/15 17:39:13.043 Debug: Server port set to: 8083
09/29/15 17:39:13.047 RPC Server (Port 2001): Response:
(void)
09/29/15 17:39:13.048 RPC Server (Port 2001): Response packet: HTTP/1.1 200 OK
Connection: close
Content-Type: text/xml
Content-Length: 96

<?xml version="1.0"?>

09/29/15 17:39:13.079 RPC Server (Port 2001): Info: Connection to client number 10604 closed.
09/29/15 17:39:21.809 Module HomeMatic BidCoS: LAN-Konfigurationsadapter “My-HM-CFG-LAN”: Debug: Sending: K
09/29/15 17:39:21.842 Module HomeMatic BidCoS: LAN-Konfigurationsadapter “My-HM-CFG-LAN”: Debug: Packet received from HM-CFG-LAN: HHM-LAN-IF,03C7,JEQ0534974,1DB017,631963,04D068E4,0001
09/29/15 17:39:28.043 RPC Server (Port 2001): Debug: Joining read thread of client 59
09/29/15 17:39:28.044 RPC Server (Port 2001): Debug: Client 59 removed.
09/29/15 17:39:34.687 RPC Server (Port 2001): Info: Connection from 127.0.0.1:51016 accepted. Client number: 10605
09/29/15 17:39:34.691 RPC Server (Port 2001): Listening for incoming packets from client number 10605.
09/29/15 17:39:34.699 RPC Server (Port 2001): Info: Connection to client number 10605 closed (3).
09/29/15 17:39:34.762 RPC Server (Port 2001): Info: Connection from 127.0.0.1:51017 accepted. Client number: 10606
09/29/15 17:39:34.766 RPC Server (Port 2001): Listening for incoming packets from client number 10606.
09/29/15 17:39:34.777 RPC Server (Port 2001): Debug: Packet received: 504F5354202F20485454502F312E300D0A4163636570742D456E636F64696E673A206465666C6174650D0A486F73743A203132372E302E302E313A323030310D0A557365722D4167656E743A205250433A3A584D4C3A3A436C69656E742F312E3432206C69627777772D7065726C2F362E30380D0A436F6E74656E742D4C656E6774683A203235340D0A436F6E74656E742D547970653A20746578742F786D6C0D0A0D0A3C3F786D6C2076657273696F6E3D22312E302220656E636F64696E673D2275732D6173636969223F3E3C6D6574686F6443616C6C3E3C6D6574686F644E616D653E696E69743C2F6D6574686F644E616D653E3C706172616D733E3C706172616D3E3C76616C75653E3C737472696E673E687474703A2F2F3132372E302E302E313A383038332F6668656D2F484D5250435F686D72662F726571756573743C2F737472696E673E3C2F76616C75653E3C2F706172616D3E3C706172616D3E3C76616C75653E3C737472696E673E4342313C2F737472696E673E3C2F76616C75653E3C2F706172616D3E3C2F706172616D733E3C2F6D6574686F6443616C6C3E
09/29/15 17:39:34.779 RPC Server (Port 2001): Info: Client number 10606 is calling RPC method: init Parameters:
(String) http://127.0.0.1:8083/fhem/HMRPC_hmrf/request
(String) CB1
09/29/15 17:39:34.779 Debug: Server path set to: /fhem/HMRPC_hmrf/request
09/29/15 17:39:34.780 Debug: Server port set to: 8083
09/29/15 17:39:34.783 RPC Server (Port 2001): Response:
(void)
09/29/15 17:39:34.784 RPC Server (Port 2001): Response packet: HTTP/1.1 200 OK
Connection: close
Content-Type: text/xml
Content-Length: 96

<?xml version="1.0"?>

09/29/15 17:39:34.819 RPC Server (Port 2001): Info: Connection to client number 10606 closed.
09/29/15 17:39:36.849 Module HomeMatic BidCoS: LAN-Konfigurationsadapter “My-HM-CFG-LAN”: Debug: Sending: K
09/29/15 17:39:36.884 Module HomeMatic BidCoS: LAN-Konfigurationsadapter “My-HM-CFG-LAN”: Debug: Packet received from HM-CFG-LAN: HHM-LAN-IF,03C7,JEQ0534974,1DB017,631963,04D0A3A4,0001
09/29/15 17:39:41.120 Info: CLI connection accepted. Client number: 10607
09/29/15 17:39:41.121 Listening for incoming commands from client number 10607.[/code]

Viele Grüße
Horst

sathya · October 2, 2016, 5:19pm

Hallo Horst,

super! Das “listMethods” fehlt noch. Das kommt etwa 10 Sekunden nach dem “init”. Das “init” brauche ich, um FHEM in einem möglichen Fix identifizieren zu können.

Viele Grüße

Sathya

trilu · October 2, 2016, 5:19pm

[code]
09/30/15 15:09:55.142 MAX packet received (My-MAX-CUL, RSSI: 0x4D): 0C89044203178D069F750018EE
09/30/15 15:09:55.188 MAX packet received (My-MAX-CUL, RSSI: 0x44): 0E890202069F7503178D0001190018
09/30/15 15:09:56.861 UPnP Server: Debug: Sending notify packets.
09/30/15 15:09:56.864 UPnP Server: Debug: Discovery packet received from 239.255.255.250:1900
09/30/15 15:09:56.884 Debug: Sleeping 1288ms before sending response.
09/30/15 15:09:58.173 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
09/30/15 15:09:58.274 UPnP Server: Debug: Sending notify packets.
09/30/15 15:10:01.016 UPnP Server: Debug: Discovery packet received from 239.255.255.250:1900
09/30/15 15:10:01.037 Debug: Sleeping 127ms before sending response.
09/30/15 15:10:01.164 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
09/30/15 15:10:01.265 UPnP Server: Debug: Sending notify packets.
09/30/15 15:10:01.267 UPnP Server: Debug: Discovery packet received from 239.255.255.250:1900
09/30/15 15:10:01.288 Debug: Sleeping 399ms before sending response.
09/30/15 15:10:01.688 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
09/30/15 15:10:01.789 UPnP Server: Debug: Sending notify packets.
09/30/15 15:10:03.663 Module HomeMatic BidCoS: LAN-Konfigurationsadapter “My-HM-CFG-LAN”: Debug: Sending: K
09/30/15 15:10:03.697 Module HomeMatic BidCoS: LAN-Konfigurationsadapter “My-HM-CFG-LAN”: Debug: Packet received from HM-CFG-LAN: HHM-LAN-IF,03C7,JEQ0534974,1DB017,631963,096E0E92,0001
09/30/15 15:10:13.668 MAX packet received (My-MAX-CUL, RSSI: 0x59): 0E09020206A1BD0316CF000118002A
09/30/15 15:10:13.670 Info (My-MAX-CUL): Packet processing took 1 ms.
09/30/15 15:10:18.713 Module HomeMatic BidCoS: LAN-Konfigurationsadapter “My-HM-CFG-LAN”: Debug: Sending: K
09/30/15 15:10:18.739 Module HomeMatic BidCoS: LAN-Konfigurationsadapter “My-HM-CFG-LAN”: Debug: Packet received from HM-CFG-LAN: HHM-LAN-IF,03C7,JEQ0534974,1DB017,631963,096E4960,0001
09/30/15 15:10:27.458 RPC Server (Port 2001): Info: Connection from 127.0.0.1:56844 accepted. Client number: 14399
09/30/15 15:10:27.463 RPC Server (Port 2001): Listening for incoming packets from client number 14399.
09/30/15 15:10:27.477 RPC Server (Port 2001): Debug: Packet received: 504F5354202F20485454502F312E300D0A4163636570742D456E636F64696E673A206465666C6174650D0A486F73743A203132372E302E302E313A323030310D0A557365722D4167656E743A205250433A3A584D4C3A3A436C69656E742F312E3432206C69627777772D7065726C2F362E30380D0A436F6E74656E742D4C656E6774683A203230340D0A436F6E74656E742D547970653A20746578742F786D6C0D0A0D0A3C3F786D6C2076657273696F6E3D22312E302220656E636F64696E673D2275732D6173636969223F3E3C6D6574686F6443616C6C3E3C6D6574686F644E616D653E696E69743C2F6D6574686F644E616D653E3C706172616D733E3C706172616D3E3C76616C75653E3C737472696E673E687474703A2F2F3132372E302E302E313A383038332F6668656D2F484D5250435F686D72662F726571756573743C2F737472696E673E3C2F76616C75653E3C2F706172616D3E3C2F706172616D733E3C2F6D6574686F6443616C6C3E
09/30/15 15:10:27.479 RPC Server (Port 2001): Info: Client number 14399 is calling RPC method: init Parameters:
(String) http://127.0.0.1:8083/fhem/HMRPC_hmrf/request
09/30/15 15:10:27.480 Debug: Server path set to: /fhem/HMRPC_hmrf/request
09/30/15 15:10:27.480 Debug: Server port set to: 8083
09/30/15 15:10:27.487 RPC Server (Port 2001): Response:
(void)
09/30/15 15:10:27.497 RPC Server (Port 2001): Response packet: HTTP/1.1 200 OK
Connection: close
Content-Type: text/xml
Content-Length: 96

<?xml version="1.0"?>

09/30/15 15:10:27.521 RPC Server (Port 2001): Info: Connection to client number 14399 closed.
09/30/15 15:10:31.362 MAX packet received (My-MAX-CUL, RSSI: 0x3A): 0C430442031752069F830028C9
09/30/15 15:10:31.363 Info (My-MAX-CUL): Packet processing took 1 ms.
09/30/15 15:10:31.407 MAX packet received (My-MAX-CUL, RSSI: 0x40): 0E430202069F830317520001180D28
09/30/15 15:10:31.409 Info (My-MAX-CUL): Packet processing took 2 ms.
09/30/15 15:10:33.749 Module HomeMatic BidCoS: LAN-Konfigurationsadapter “My-HM-CFG-LAN”: Debug: Sending: K
09/30/15 15:10:33.781 Module HomeMatic BidCoS: LAN-Konfigurationsadapter “My-HM-CFG-LAN”: Debug: Packet received from HM-CFG-LAN: HHM-LAN-IF,03C7,JEQ0534974,1DB017,631963,096E8418,0001
09/30/15 15:10:39.893 MAX packet received (My-MAX-CUL, RSSI: 0x3B): 0C3B04420317210603420028D8
09/30/15 15:10:39.895 Info (My-MAX-CUL): Packet processing took 1 ms.
09/30/15 15:10:39.940 MAX packet received (My-MAX-CUL, RSSI: 0x38): 0E3B02020603420317210001180028
09/30/15 15:10:39.941 Info (My-MAX-CUL): Packet processing took 1 ms.
09/30/15 15:10:48.789 Module HomeMatic BidCoS: LAN-Konfigurationsadapter “My-HM-CFG-LAN”: Debug: Sending: K
09/30/15 15:10:48.822 Module HomeMatic BidCoS: LAN-Konfigurationsadapter “My-HM-CFG-LAN”: Debug: Packet received from HM-CFG-LAN: HHM-LAN-IF,03C7,JEQ0534974,1DB017,631963,096EBED7,0001
09/30/15 15:10:49.663 RPC Server (Port 2001): Info: Connection from 127.0.0.1:56852 accepted. Client number: 14400
09/30/15 15:10:49.666 RPC Server (Port 2001): Listening for incoming packets from client number 14400.
09/30/15 15:10:49.675 RPC Server (Port 2001): Info: Connection to client number 14400 closed (3).
09/30/15 15:10:49.794 RPC Server (Port 2001): Info: Connection from 127.0.0.1:56854 accepted. Client number: 14401
09/30/15 15:10:49.798 RPC Server (Port 2001): Listening for incoming packets from client number 14401.
09/30/15 15:10:49.818 RPC Server (Port 2001): Debug: Packet received: 504F5354202F20485454502F312E300D0A4163636570742D456E636F64696E673A206465666C6174650D0A486F73743A203132372E302E302E313A323030310D0A557365722D4167656E743A205250433A3A584D4C3A3A436C69656E742F312E3432206C69627777772D7065726C2F362E30380D0A436F6E74656E742D4C656E6774683A203235340D0A436F6E74656E742D547970653A20746578742F786D6C0D0A0D0A3C3F786D6C2076657273696F6E3D22312E302220656E636F64696E673D2275732D6173636969223F3E3C6D6574686F6443616C6C3E3C6D6574686F644E616D653E696E69743C2F6D6574686F644E616D653E3C706172616D733E3C706172616D3E3C76616C75653E3C737472696E673E687474703A2F2F3132372E302E302E313A383038332F6668656D2F484D5250435F686D72662F726571756573743C2F737472696E673E3C2F76616C75653E3C2F706172616D3E3C706172616D3E3C76616C75653E3C737472696E673E4342313C2F737472696E673E3C2F76616C75653E3C2F706172616D3E3C2F706172616D733E3C2F6D6574686F6443616C6C3E
09/30/15 15:10:49.820 RPC Server (Port 2001): Info: Client number 14401 is calling RPC method: init Parameters:
(String) http://127.0.0.1:8083/fhem/HMRPC_hmrf/request
(String) CB1
09/30/15 15:10:49.821 Debug: Server path set to: /fhem/HMRPC_hmrf/request
09/30/15 15:10:49.821 Debug: Server port set to: 8083
09/30/15 15:10:49.832 RPC Server (Port 2001): Response:
(void)
09/30/15 15:10:49.833 RPC Server (Port 2001): Response packet: HTTP/1.1 200 OK
Connection: close
Content-Type: text/xml
Content-Length: 96

<?xml version="1.0"?>

09/30/15 15:10:49.859 RPC Server (Port 2001): Info: Connection to client number 14401 closed.
09/30/15 15:10:50.708 UPnP Server: Debug: Discovery packet received from 239.255.255.250:1900
09/30/15 15:10:50.729 Debug: Sleeping 2327ms before sending response.
09/30/15 15:10:51.212 MAX packet received (My-MAX-CUL, RSSI: 0x52): 0BDF063004DC1806A6230012
09/30/15 15:10:51.214 Info (My-MAX-CUL): Packet processing took 1 ms.
09/30/15 15:10:52.770 MAX packet received (My-MAX-CUL, RSSI: 0x4D): 0BE0063004DC1806A6230010
09/30/15 15:10:52.772 Info (My-MAX-CUL): Packet processing took 1 ms.
09/30/15 15:10:53.057 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
09/30/15 15:10:53.157 UPnP Server: Debug: Sending notify packets.
09/30/15 15:10:53.160 UPnP Server: Debug: Discovery packet received from 239.255.255.250:1900
09/30/15 15:10:53.180 Debug: Sleeping 4239ms before sending response.
09/30/15 15:10:54.147 MAX packet received (My-MAX-CUL, RSSI: 0x3F): 0CAA044206A37D069FED0018CD
09/30/15 15:10:54.149 Info (My-MAX-CUL): Packet processing took 2 ms.
09/30/15 15:10:54.192 MAX packet received (My-MAX-CUL, RSSI: 0x48): 0EAA0202069FED06A37D0001390018
09/30/15 15:10:54.194 Info (My-MAX-CUL): Packet processing took 1 ms.
09/30/15 15:10:55.685 MAX packet received (My-MAX-CUL, RSSI: 0x48): 0BE0063004DC1806A6230050
09/30/15 15:10:55.686 Info (My-MAX-CUL): Packet processing took 1 ms.
09/30/15 15:10:57.420 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
09/30/15 15:10:57.521 UPnP Server: Debug: Sending notify packets.
09/30/15 15:10:59.807 RPC Server (Port 2001): Debug: Joining read thread of client 79
09/30/15 15:10:59.807 RPC Server (Port 2001): Debug: Client 79 removed.
09/30/15 15:10:59.808 RPC Server (Port 2001): Debug: Joining read thread of client 80
09/30/15 15:10:59.808 RPC Server (Port 2001): Debug: Client 80 removed.
09/30/15 15:10:59.809 RPC Server (Port 2001): Debug: Joining read thread of client 81
09/30/15 15:10:59.809 RPC Server (Port 2001): Debug: Client 81 removed.
09/30/15 15:10:59.838 Info: Calling RPC method “system.listMethods” on server http://127.0.0.1.
09/30/15 15:10:59.839 Parameters:
(String) CB1
09/30/15 15:10:59.840 Debug: Calling getFileDescriptor…
09/30/15 15:10:59.840 Info: Connecting to host 127.0.0.1 on port 8083…
09/30/15 15:10:59.848 Info: Connected to host 127.0.0.1 on port 8083. Client number is: 14402
09/30/15 15:10:59.849 Sending packet: POST /fhem/HMRPC_hmrf/request HTTP/1.1
User-Agent: Homegear 0.6.0
Host: 127.0.0.1:8083
Content-Type: text/xml
Content-Length: 142
Connection: close

<?xml version="1.0"?>

system.listMethodsCB1

09/30/15 15:10:59.882 Debug: Received packet from server 127.0.0.1:

<?xml version="1.0" encoding="us-ascii"?>[/code]

Jetzt aber
Das Code Feld scheint eingeschränkt in der Größe
das ganze Log ist im Anhang als Datei
homegear.log (104 KB)

sathya · October 2, 2016, 5:19pm

Hallo Horst,

Problem gefunden . fhem gibt in system.listMethods nichts zurück. Hab’s im aktuellen Nightly gefixt und die unterstützten Methoden manuell hinzugefügt .

Viele Grüße

Sathya

trilu · October 2, 2016, 5:19pm

Vielen Dank - ist das im Nightly vom 13.10. bereits drin?
Gerade Nightly aufgespielt, mein CUL für MAX wird nicht mehr erkannt?

[code]## The device family this interface is for
[MAX]

Specify an unique id here to identify this device in Homegear

id = My-MAX-CUL

When default is set to “true” Homegear will assign this device

to new peers.

default = true

Options: cul, coc, cc1100

deviceType = cul

device = /dev/ttyACM0

Should be “40” for MAX!

responseDelay = 40
[/code]

Aber im Log steht sowas:

10/13/15 19:58:52.672 Module HomeMatic BidCoS: Loading XML RPC devices... 10/13/15 19:59:00.776 Info: Skipping file rf_central.xml: File is not needed. 10/13/15 19:59:01.905 Info: Not initializing device family HomeMatic Wired, because no physical interface was found. 10/13/15 19:59:01.912 Info: Not initializing device family INSTEON, because no physical interface was found. 10/13/15 19:59:01.913 Info: Not initializing device family MAX!, because no physical interface was found. 10/13/15 19:59:01.914 Info: Not initializing device family Philips hue, because no physical interface was found. 10/13/15 19:59:01.916 Info: Not initializing device family Sonos, because no physical interface was found. 10/13/15 19:59:01.917 Module Miscellaneous: Loading XML RPC devices... 10/13/15 19:59:01.928 Loading devices... 10/13/15 19:59:01.948 Module HomeMatic BidCoS: Loading HomeMatic BidCoS device 2 10/13/15 19:59:01.975 Module HomeMatic BidCoS: Loading HomeMatic BidCoS device 8 10/13/15 19:59:02.005 Module HomeMatic BidCoS: Loading peer 19 10/13/15 19:59:02.246 Module HomeMatic BidCoS: Loading peer 20 10/13/15 19:59:02.312 Module HomeMatic BidCoS: Loading peer 21 10/13/15 19:59:02.608 Module HomeMatic BidCoS: Loading peer 22 10/13/15 19:59:02.646 Module Miscellaneous: Loading Miscellaneous device 5

sathya · October 2, 2016, 5:19pm

Hallo Horst,

nein, da ich es gerade gestern geändert hatte, ist es noch nicht im kompilierten Nightly. Dass dein MAX-CUL nicht mehr erkannt wird, ist komisch. Das schaue ich mir morgen gleich an. Beim Problem mit den übertragenen Temperaturen an fhem schaue ich mal, ob sich da was machen lässt. Dein MAX-Stellantrieb-Fenster-offen-Problem ist am schnellsten über ein Homegear-Skript gelöst. Aktuell kannst du ihm aber nicht “Fenster offen” senden. Das ließe sich zwar leicht einprogrammieren, aber da gerade so viel zu tun ist, würde das etwas dauern.

Viele Grüße

Sathya

trilu · October 2, 2016, 5:19pm

Juhu - ich habe den Fehler mit MAX gefunden.
Es liegt an dem Titelfeld in der physicalinterface.conf
Das Feld muss [MAX!] anstatt [MAX] heissen, dann klappts auch mit dem Nachbarn…

Viele Grüße
Horst

sathya · October 2, 2016, 5:19pm

Hallo Horst,

hups, das habe ich verursacht… Wow, dass du den Fehler gefunden hast . In der Basisbibliothek waren noch familienspezifische Informationen, welche ich entfernt habe. In dem Zusammenhang hat sich auch der Eintrag in der physicalinterfaces.conf geändert. Nur wird noch die alte physicalinterfaces.conf installiert… Habs gleich mal korrigiert.

Viele Grüße

Sathya

trilu · October 2, 2016, 5:19pm

mit Geduld und Spucke ))