Openhab with homegear and hmland

[Bernd Böhm]

Heya

I'm facing a problem while configuring my existing OH installation to work additionally with homematic.

I'm runnning OH on a Raspi2 with a couple of bindings (e.g. knx, xmpp, etc.) and I got myselb the HomeMatic USB Stick HM-CFG-USB2

To get it running I've isntalled an configured hmland and Homegear. With the latter I was able to bind a new sensor that was subsequently listed when checking via the CLI. -> So I presume this part of my installation is working fine.

The next step would was to add the homematic.jar into the addons and edit the openhab.cfg

My version of the homematic configuration looks like this: and the output of openhab.log

Things I have tried so far:

- use 127.0.0.1 or 192.168.0.110 as IP

-use callback host or not

-use 2001 or 9123 as Port

############################### Homematic Binding #####################################
#
# Hostname / IP address of the Homematic CCU
homematic:host=192.168.0.110 #extern IP

# Hostname / IP address for the callback server (optional, default is auto-discovery)
# This is normally the IP / hostname of the local host
# (but not "localhost" or "127.0.0.1").
#homematic:callback.host=192.168.0.110
# Port number for the callback server. (optional, defaults to 9123)
homematic:callback.port=2001 #port used by the xml-rpc service from Homegear

12:08:18.870 INFO  o.o.b.h.i.bus.HomematicBinding[:92]- HomematicConfig[host=192.168.0.110,callbackHost=192.168.0.110,callbackPort=2001,aliveInterval=300]
12:08:18.872 INFO  o.o.b.h.i.c.HomematicCommunicator[:66]- Starting Homematic communicator
12:08:18.879 DEBUG o.o.b.h.i.c.ItemDisabler[:54]- Starting ItemDisabler
12:08:18.905 ERROR o.o.b.h.i.c.HomematicCommunicator[:93]- Could not start Homematic communicator: -32601 : Requested method not found. (sending BinRpcRequest[methodName=getDeviceDescription,args={BidCoS-RF}])
org.openhab.binding.homematic.internal.communicator.client.HomematicClientException: -32601 : Requested method not found. (sending BinRpcRequest[methodName=getDeviceDescription,args={BidCoS-RF}])
    at org.openhab.binding.homematic.internal.communicator.client.BinRpcClient.sendMessage(BinRpcClient.java:224)
    at org.openhab.binding.homematic.internal.communicator.client.BinRpcClient.getDeviceDescription(BinRpcClient.java:104)
    at org.openhab.binding.homematic.internal.communicator.client.BinRpcClient.getServerId(BinRpcClient.java:116)
    at org.openhab.binding.homematic.internal.communicator.HomematicCommunicator.start(HomematicCommunicator.java:75)
    at org.openhab.binding.homematic.internal.bus.HomematicBinding.updated(HomematicBinding.java:95)
    at org.eclipse.equinox.internal.cm.ManagedServiceTracker$1.run(ManagedServiceTracker.java:183)
    at org.eclipse.equinox.internal.cm.SerializedTaskQueue$1.run(SerializedTaskQueue.java:36)
Caused by: java.io.IOException: -32601 : Requested method not found.
    at org.openhab.binding.homematic.internal.communicator.client.BinRpcClient.sendMessage(BinRpcClient.java:210)
    ... 6 common frames omitted
12:08:18.907 INFO  o.o.b.h.i.c.HomematicCommunicator[:120]- Shutting down Homematic communicator
12:08:18.909 DEBUG o.o.b.h.i.c.s.BinRpcCallbackServer[:55]- Shutting down BinRpcCallbackServer
12:08:18.910 DEBUG o.o.b.h.i.c.ItemDisabler[:63]- Stopping ItemDisabler
12:08:18.913 INFO  o.o.c.s.AbstractActiveService[:169]- Homematic server keep alive thread has been started

[honkt...@gmail.com]

I'll post my identical (Wandboard instead of raspberry pi) setup in the evening, stand by 😉

[honkt...@gmail.com]

So, this is my setup:

1. Linux on Wandboard
2. HM-CFG-USB-2 with hmland HEAD-18e63b2
3. homegear 0.5.24-6

openhab.cfg:

######################## Homematic Binding ###########################

# Hostname / IP address of the Homematic CCU

homematic:host=ccu

# The communication with the CCU. xml for xmlrpc or bin for the lightweight binrpc, (optional, default is bin).

# homematic:rpc=

# Hostname / IP address for the callback server (optional, default is auto-discovery)

# This is normally the IP / hostname of the local host

# (but not "localhost" or "127.0.0.1").

#homematic:callback.host=

# Port number for the callback server. (optional, defaults to 9123)

#homematic:callback.port=9123

# The interval in seconds to check if the communication with the CCU is still alive.

# If no message receives from the CCU, the binding restarts. (optional, default is 300)

homematic:alive.interval=86400

I've set the alive-interval because I only have a few sensors so nearly no regular traffic causing the binding to reconnect.

Could you please verify your versions and test if another rpc method works?

Besides, please use 127.0.0.1 as ccu address - I added "ccu" as alias to 127.0.0.1 in /etc/hosts. Works ;)

Sascha

[Bernd Böhm]

Cheers, that did help a bit. In fact I've discovered a typo in my openhab items configuration

Nevertheless I still have an issue. It appears that the rpc method getDeviceDescription is not available in homegear. Google didn't have much to say about this issue :\

I am using the latest git version of hmland and 0.61 of homegear.

homegear log:

04/01/15 10:35:49.323 RPC Server (Port 2001): Info: Connection from 127.0.0.1:58682 accepted. Client number: 1183

04/01/15 10:35:49.325 RPC Server (Port 2001): Warning: RPC method not found: getDeviceDescription

04/01/15 10:35:49.335 RPC Server (Port 2001): Info: Connection to client number 1183 closed (3).

openhab.log

10:13:08.612 TRACE o.o.b.h.i.c.c.BinRpcClient[:191]- Client BinRpcRequest BinRpcRequest[methodName=getDeviceDescription,args={BidCoS-RF}]

10:13:08.616 WARN  o.j.s.util.PacketParserUtils[:408]- Failed to parse extension packet in Presence packet.

10:13:08.625 TRACE o.o.b.h.i.c.c.BinRpcClient[:199]- Client BinRpcResponse: {

        faultCode=-32601

        faultString=: Requested method not found.

}

10:13:08.631 ERROR o.o.b.h.i.c.HomematicCommunicator[:93]- Could not start Homematic communicator: -32601 : Requested method not found. (sending BinRpcRequest[methodName=getDeviceDescription,args={BidCoS-RF}])

org.openhab.binding.homematic.internal.communicator.client.HomematicClientException: -32601 : Requested method not found. (sending BinRpcRequest[methodName=getDeviceDescription,args={BidCoS-RF}])

        at org.openhab.binding.homematic.internal.communicator.client.BinRpcClient.sendMessage(BinRpcClient.java:224)

        at org.openhab.binding.homematic.internal.communicator.client.BinRpcClient.getDeviceDescription(BinRpcClient.java:104)

        at org.openhab.binding.homematic.internal.communicator.client.BinRpcClient.getServerId(BinRpcClient.java:116)

        at org.openhab.binding.homematic.internal.communicator.HomematicCommunicator.start(HomematicCommunicator.java:75)

        at org.openhab.binding.homematic.internal.bus.HomematicBinding.updated(HomematicBinding.java:95)

        at org.eclipse.equinox.internal.cm.ManagedServiceTracker$1.run(ManagedServiceTracker.java:183)

Caused by: java.io.IOException: -32601 : Requested method not found.

        at org.openhab.binding.homematic.internal.communicator.client.BinRpcClient.sendMessage(BinRpcClient.java:210)

        at org.openhab.binding.homematic.internal.communicator.client.BinRpcClient.getDeviceDescription(BinRpcClient.java:104)

        at org.openhab.binding.homematic.internal.communicator.client.BinRpcClient.getServerId(BinRpcClient.java:116)

        at org.openhab.binding.homematic.internal.communicator.HomematicCommunicator.start(HomematicCommunicator.java:75)

        at org.openhab.binding.homematic.internal.bus.HomematicBinding.updated(HomematicBinding.java:95)

        at org.eclipse.equinox.internal.cm.ManagedServiceTracker$1.run(ManagedServiceTracker.java:183)

10:13:08.633 INFO  o.o.b.h.i.c.HomematicCommunicator[:120]- Shutting down Homematic communicator

10:13:08.635 DEBUG o.o.b.h.i.c.s.BinRpcCallbackServer[:55]- Shutting down BinRpcCallbackServer

I have tried to clear the queue in homegear und to reset and repair the device. Did not improve my situation...

[Sascha]

Cheers,

Are you using the current homematic Binding?

[Bernd Böhm]

Yes I do

I found the reason finally...
I didn't consider that I was using a nightly build. And this one was broken. ..The new build works fine