search

openhab / openhab-addons

Add-ons for openHAB
https://www.openhab.org/
Eclipse Public License 2.0
1.86k stars 3.58k forks source link

HomeMatic Binding #88

Closed gerrieg closed 8 years ago

gerrieg commented 9 years ago

will start after the completion of Astro Binding

gerrieg commented 9 years ago

@kaikreuzer can't add labels, please add newbinding to HomeMatic and Astro issue, thanks.

Best, Gerhard

fluidblue commented 9 years ago

@gerrieg Are you still working on the HomeMatic binding?

gerrieg commented 9 years ago

Yes, the main part is done and it works basically. Now i'm testing, bugfixing, optimizing...

fluidblue commented 9 years ago

Very nice! I am looking forward to using it.

Will the binding support Homegear, like the binding for openHAB v1 did?

gerrieg commented 9 years ago

Yes, it will have all the features as the existing v1 binding.

itn3rd77 commented 9 years ago

@gerrieg Hi Gerhard any progress with the binding or alpha version we can play with?

gerrieg commented 9 years ago

not yet, i had two longer vacations and finished the Astro binding. But now i am going to continue with the Homematic binding.

matthewatdiferit commented 9 years ago

Hi All,

I'm quite excited about getting a real OpenHAB 2 binding for Homematic running. I've downloaded the fork, and built it, (and some may notice that I've cross posted on the new OpenHAB forum and old mailing list as well as this). However, I'm getting some funny errors in my logs about a -32601 : Requested method not found. (sending getAllScripts().

I'm having trouble attaching things, so I've uploaded my log file to this URL, does this make sense to anyone? (I'm running Homegear on Pi, and OpenHAB 2 on OS X)....

http://www.heimatt.io/uploads/section.log

best, matt

gerrieg commented 9 years ago

Hi Matt!

This version was only a basis for a discussion with the openHab team. It does NOT work! I will delete the branch to avoid confusion.

The status of the binding today: I rewrote the binding from scratch for OH2 in the last three weeks. It has all the features from 1.x plus support for the MASTER parameters. So you can display/control the settings of your devices too. Homegear with Bridge/Thing discovery is working already, now i am adding CCU support.

I will announce it if it's ready for public testing.

Best, Gerhard

abrancato commented 8 years ago

Hi, where can I get the openhab2 homematic binding please? I have openhab2 and homematic (CCU2) in place and really want to test it. I'm willing to reporting on my findings ;)

sja commented 8 years ago

You have to checkout https://github.com/gerrieg/openhab2.git and change to homematic branch. There you'll find the code. I think you can do a mvn clean install to get the neccessary jar you can test with.

abrancato commented 8 years ago

Thank you sja. I found it (branch:homematic / openhab2 / addons / binding / org.openhab.binding.homematic). As I'm fairly new to openhab,- could you give me a kick-start on how to compile the necessary jar file from what I see on git? Thank you so much.

patrickse commented 8 years ago

I´ve just tried the extension and it looks really promising. The scanning for devices works quite well.

So that´s why did to get it up and running

git clone https://github.com/gerrieg/openhab2.git
cd openhab2
git checkout homematic
mvn clean install
cd distribution
cd target
unzip distribution-2.0.0-SNAPSHOT-runtime.zip
unzip distribution-2.0.0-SNAPSHOT-addons.zip

And that's it. The next step is to configure the homematic bridge as a thing and then the magic starts and all these Things popup in the Setup dialog. :)

Hope that helps.

Patrick

gerrieg commented 8 years ago

Hi!

I just pushed some changes to my repository and i think the binding is ready now for public testing. Binding is complete, only bugfixing and optimizing.

You can also compile the binding from my repository as Patrick has described.

I mentioned in the docs, that the binding has a gateway type autodetection. But i don't know, if the autodetection works with a CCU1. It would be great, if a CCU1 user can start the binding and check the 'HmGatewayInfo' logentry. If you see type=CCU, autodetection works. Otherwise please switch the binding to trace mode, start openHAB2 and send me the logfile. With the tracelog, i can quickly fix it.

Regards, Gerhard

patrickse commented 8 years ago

:+1:

abrancato commented 8 years ago

I always get stuck on "openHAB Core 1.x Compatibility Layer" - see below. What am I doing wrong?


mvn -version
  Apache Maven 3.0.4
  Maven home: /usr/share/maven
  Java version: 1.6.0_27, vendor: Sun Microsystems Inc.
  Java home: /usr/lib/jvm/java-6-openjdk-amd64/jre
  Default locale: en_US, platform encoding: ANSI_X3.4-1968
  OS name: "linux", version: "3.2.0-4-amd64", arch: "amd64", family: "unix"

git clone https://github.com/gerrieg/openhab2.git
cd openhab2
git checkout homematic
mvn clean install
...

[INFO] openHAB ........................................... SUCCESS [0.259s]
[INFO] openHAB Add-ons ................................... SUCCESS [0.012s]
[INFO] openHAB Bindings .................................. SUCCESS [0.018s]
[INFO] Astro Binding ..................................... SUCCESS [3.503s]
[INFO] Autelis Binding ................................... SUCCESS [0.904s]
[INFO] AVM FRITZ! Binding ................................ SUCCESS [1.764s]
[INFO] openHAB Bundles ................................... SUCCESS [0.021s]
[INFO] openHAB Core Components ........................... SUCCESS [0.025s]
[INFO] openHAB Core 1.x Compatibility Layer .............. FAILURE [1.811s]
[INFO] Freebox Binding ................................... SKIPPED
[INFO] HDanywhere Binding ................................ SKIPPED
[INFO] Homematic Binding ................................. SKIPPED
[INFO] IPP Binding ....................................... SKIPPED
...
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
kaikreuzer commented 8 years ago

Simple: You are not using Java 7 or above!

abrancato commented 8 years ago

Thanks Kai, that was the issue. So I was able to build and run it on my pi, but homematic won't appear as a binding in the UI - even though the jar (org.openhab.binding.homematic-1.7.0.jar) is in place in the /addons directory... dummguck

kaikreuzer commented 8 years ago

You noticed that this discussion is about openHAB 2 (and hence the Homematic binding 2.0 and not 1.7)?

abrancato commented 8 years ago

Yes, but that's what I get when I clone and build "https://github.com/gerrieg/openhab2.git" like described by patrickse above... no 2.0 binding for homematic... sorry if I'm missing something obvious.

kaikreuzer commented 8 years ago

Yes, you are missing https://github.com/openhab/openhab2/issues/88#issuecomment-141926233.

abrancato commented 8 years ago

It sounds strange, but after redoing the whole thing on another system it's there now - you have to love PC deterministics ;) Thank you so much for the support and this great community - I'll work hard to become an openHAB(2) pro and contribute... 


root@appengine-java ~# git clone https://github.com/gerrieg/openhab2.git
Cloning into 'openhab2'...
remote: Counting objects: 9597, done.
remote: Compressing objects: 100% (111/111), done.
remote: Total 9597 (delta 57), reused 0 (delta 0), pack-reused 9455
Receiving objects: 100% (9597/9597), 10.03 MiB | 3.88 MiB/s, done.
Resolving deltas: 100% (4236/4236), done.
root@appengine-java ~# cd openhab2/
root@appengine-java ~/openhab2# git checkout homematic
Branch homematic set up to track remote branch homematic from origin.
Switched to a new branch 'homematic'
root@appengine-java ~/openhab2# mvn clean install
[INFO] Scanning for projects...
...snip...
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] openHAB ........................................... SUCCESS [0.359s]
[INFO] openHAB Add-ons ................................... SUCCESS [0.018s]
[INFO] openHAB Bindings .................................. SUCCESS [0.017s]
[INFO] Astro Binding ..................................... SUCCESS [3.180s]
[INFO] Autelis Binding ................................... SUCCESS [0.717s]
[INFO] AVM FRITZ! Binding ................................ SUCCESS [1.203s]
[INFO] openHAB Bundles ................................... SUCCESS [0.031s]
[INFO] openHAB Core Components ........................... SUCCESS [0.020s]
[INFO] openHAB Core 1.x Compatibility Layer .............. SUCCESS [2.691s]
[INFO] Freebox Binding ................................... SUCCESS [1.037s]
[INFO] HDanywhere Binding ................................ SUCCESS [0.460s]
[INFO] Homematic Binding ................................. SUCCESS [1.857s]
[INFO] IPP Binding ....................................... SUCCESS [0.385s]
[INFO] Keba Binding ...................................... SUCCESS [0.400s]
[INFO] MAX! Binding ...................................... SUCCESS [0.587s]
[INFO] MAX! Binding Tests ................................ SUCCESS [9.670s]
[INFO] Network Binding ................................... SUCCESS [0.318s]
[INFO] openHAB I/O Components ............................ SUCCESS [0.009s]
[INFO] openHAB Serial Transport .......................... SUCCESS [0.065s]
[INFO] PioneerAvr Binding ................................ SUCCESS [0.465s]
[INFO] Pulseaudio Binding ................................ SUCCESS [0.513s]
[INFO] Sonos Binding ..................................... SUCCESS [0.627s]
[INFO] SqueezeBox Binding ................................ SUCCESS [0.470s]
[INFO] Tesla Binding ..................................... SUCCESS [0.770s]
[INFO] Vitotronic Binding ................................ SUCCESS [0.381s]
[INFO] openHAB Core ...................................... SUCCESS [0.345s]
[INFO] openHAB I/O Add-Ons ............................... SUCCESS [0.008s]
[INFO] my.openHAB Connection Service ..................... SUCCESS [0.412s]
[INFO] openHAB UI Components ............................. SUCCESS [0.013s]
[INFO] openHAB Dashboard UI .............................. SUCCESS [0.276s]
[INFO] openHAB UI Add-Ons ................................ SUCCESS [0.009s]
[INFO] openHAB Classic UI Dashboard Integration .......... SUCCESS [0.239s]
[INFO] openHAB Paper UI Theme Fragment ................... SUCCESS [0.247s]
[INFO] openHAB Initializer ............................... SUCCESS [0.216s]
[INFO] openHAB Core 1.x Compatibility Layer Tests ........ SUCCESS [8.753s]
[INFO] openHAB Jetty ..................................... SUCCESS [0.048s]
[INFO] openHAB REST API Documentation .................... SUCCESS [0.364s]
[INFO] openHAB Classic Iconset ........................... SUCCESS [0.622s]
[INFO] openHAB Features .................................. SUCCESS [0.008s]
[INFO] openHAB Dependencies .............................. SUCCESS [0.397s]
[INFO] openHAB Runtime ................................... SUCCESS [0.130s]
[INFO] openHAB Products .................................. SUCCESS [0.009s]
[INFO] openHAB Runtime Application ....................... SUCCESS [16.931s]
[INFO] openHAB P2 Repository ............................. SUCCESS [5.339s]
[INFO] openHAB Target Platform ........................... SUCCESS [0.104s]
[INFO] openHAB Distribution .............................. SUCCESS [12.926s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2:08.071s
[INFO] Finished at: Wed Sep 23 15:09:53 UTC 2015
[INFO] Final Memory: 77M/199M
[INFO] ------------------------------------------------------------------------
Cleaning up unclosed ZipFile for archive /root/openhab2/products/org.openhab.product.runtime/target/products/org.openhab.product.runtime-win32.win32.x86.zip
Cleaning up unclosed ZipFile for archive /root/openhab2/products/org.openhab.product.runtime/target/products/org.openhab.product.runtime-win32.win32.x86.zip
Cleaning up unclosed ZipFile for archive /root/openhab2/products/org.openhab.product.runtime/target/products/org.openhab.product.runtime-win32.win32.x86.zip

...snip...

unzip distribution-2.0.0-SNAPSHOT-runtime.zip
unzip distribution-2.0.0-SNAPSHOT-addons.zip
...snip...

cd addons/
root@raspberrypi:/opt/openhab2/addons# ls
org.eclipse.smarthome.binding.hue-0.8.0-20150922.221826-288.jar
org.eclipse.smarthome.binding.lifx-0.8.0-20150922.221921-218.jar
org.eclipse.smarthome.binding.wemo-0.8.0-20150922.221916-251.jar
org.eclipse.smarthome.binding.yahooweather-0.8.0-20150922.221912-286.jar
org.openhab.action.mail-1.8.0-20150922.010008-81.jar
org.openhab.action.pushover-1.8.0-20150922.010008-81.jar
org.openhab.action.xbmc-1.8.0-20150922.010008-81.jar
org.openhab.action.xmpp-1.8.0-20150922.010008-81.jar
org.openhab.binding.anel-1.8.0-20150922.010008-79.jar
org.openhab.binding.astro-2.0.0-SNAPSHOT.jar
org.openhab.binding.autelis-2.0.0-SNAPSHOT.jar
org.openhab.binding.avmfritz-2.0.0-SNAPSHOT.jar
org.openhab.binding.denon-1.8.0-20150922.010008-79.jar
org.openhab.binding.energenie-1.8.0-20150922.010008-79.jar
org.openhab.binding.enocean-1.8.0-20150922.010008-80.jar
org.openhab.binding.epsonprojector-1.8.0-20150922.010008-80.jar
org.openhab.binding.exec-1.8.0-20150922.010008-81.jar
org.openhab.binding.freebox-2.0.0-SNAPSHOT.jar
org.openhab.binding.freeswitch-1.8.0-20150922.010008-79.jar
org.openhab.binding.fs20-1.8.0-20150922.010008-79.jar
org.openhab.binding.hdanywhere-2.0.0-SNAPSHOT.jar
org.openhab.binding.heatmiser-1.8.0-20150922.010008-80.jar
org.openhab.binding.homematic-2.0.0-SNAPSHOT.jar
org.openhab.binding.http-1.8.0-20150922.010008-80.jar
org.openhab.binding.ihc-1.8.0-20150922.010008-80.jar
org.openhab.binding.insteonplm-1.8.0-20150922.010008-79.jar
org.openhab.binding.ipp-2.0.0-SNAPSHOT.jar
org.openhab.binding.keba-2.0.0-SNAPSHOT.jar
org.openhab.binding.knx-1.8.0-20150922.010008-81.jar
org.openhab.binding.max-2.0.0-SNAPSHOT.jar
org.openhab.binding.milight-1.8.0-20150922.010008-80.jar
org.openhab.binding.modbus-1.8.0-20150922.010008-80.jar
org.openhab.binding.network-2.0.0-SNAPSHOT.jar
org.openhab.binding.nibeheatpump-1.8.0-20150922.010008-80.jar
org.openhab.binding.ntp-1.8.0-20150922.010008-80.jar
org.openhab.binding.onewire-1.8.0-20150922.010008-81.jar
org.openhab.binding.onkyo-1.8.0-20150922.010008-80.jar
org.openhab.binding.openenergymonitor-1.8.0-20150922.010008-79.jar
org.openhab.binding.owserver-1.8.0-20150922.010008-80.jar
org.openhab.binding.pioneeravr-2.0.0-SNAPSHOT.jar
org.openhab.binding.pulseaudio-2.0.0-SNAPSHOT.jar
org.openhab.binding.rfxcom-1.8.0-20150922.010008-80.jar
org.openhab.binding.samsungac-1.8.0-20150922.010008-80.jar
org.openhab.binding.snmp-1.8.0-20150922.010008-80.jar
org.openhab.binding.sonos-2.0.0-SNAPSHOT.jar
org.openhab.binding.squeezebox-2.0.0-SNAPSHOT.jar
org.openhab.binding.swegonventilation-1.8.0-20150922.010008-80.jar
org.openhab.binding.systeminfo-1.8.0-20150922.010008-80.jar
org.openhab.binding.tellstick-1.8.0-20150922.010008-79.jar
org.openhab.binding.tesla-2.0.0-SNAPSHOT.jar
org.openhab.binding.tinkerforge-1.8.0-20150922.010008-81.jar
org.openhab.binding.vitotronic-2.0.0-SNAPSHOT.jar
org.openhab.binding.weather-1.8.0-20150922.010008-81.jar
org.openhab.binding.zwave-1.8.0-20150922.010008-80.jar
org.openhab.io.multimedia.tts.marytts-1.8.0-20150922.010008-79.jar
org.openhab.io.myopenhab-2.0.0-SNAPSHOT.jar
org.openhab.persistence.jpa-1.8.0-20150922.010008-79.jar
org.openhab.persistence.logging-1.8.0-20150922.010008-79.jar
org.openhab.persistence.mysql-1.8.0-20150922.010008-79.jar
org.openhab.persistence.rrd4j-1.8.0-20150922.010008-79.jar
root@raspberrypi:/opt/openhab2/addons#
patrickse commented 8 years ago

Maybe you missed the checkout homematiccommand.

belmondo2001 commented 8 years ago

I tried the binding and it looks good. But for some Datapoints i got an Exception

(HM-TC-IT-WM-W-EU)

java.io.IOException: -1 Failure (sending getParamset() LEQ1214017:2 VALUES) at org.openhab.binding.homematic.internal.communicator.parser.RpcResponseParser.parse(RpcResponseParser.java:41) ~[bundleFile:na] at org.openhab.binding.homematic.internal.communicator.client.RpcClient.sendMessage(RpcClient.java:272) ~[bundleFile:na] at org.openhab.binding.homematic.internal.communicator.client.RpcClient.setChannelDatapointValues(RpcClient.java:146) ~[bundleFile:na] at org.openhab.binding.homematic.internal.communicator.AbstractHomematicGateway.loadChannelValues(AbstractHomematicGateway.java:409) [bundleFile:na] at org.openhab.binding.homematic.handler.HomematicThingHandler.updateChannelState(HomematicThingHandler.java:188) ~[bundleFile:na] at org.openhab.binding.homematic.handler.HomematicThingHandler.updateChannelState(HomematicThingHandler.java:166) ~[bundleFile:na] at org.openhab.binding.homematic.handler.HomematicBridgeHandler.onStateUpdated(HomematicBridgeHandler.java:231) [bundleFile:na] at org.openhab.binding.homematic.internal.communicator.AbstractHomematicGateway.eventReceived(AbstractHomematicGateway.java:545) [bundleFile:na] at org.openhab.binding.homematic.internal.communicator.server.RpcCallbackHandler.handleEvent(RpcCallbackHandler.java:130) [bundleFile:na] at org.openhab.binding.homematic.internal.communicator.server.RpcCallbackHandler.handleMethodCall(RpcCallbackHandler.java:85) [bundleFile:na] at org.openhab.binding.homematic.internal.communicator.server.RpcCallbackHandler.handleMethodCall(RpcCallbackHandler.java:99) [bundleFile:na] at org.openhab.binding.homematic.internal.communicator.server.RpcCallbackHandler.run(RpcCallbackHandler.java:63) [bundleFile:na] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_60] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_60] at java.lang.Thread.run(Thread.java:745) [na:1.8.0_60]

(HM-ES-TX-WM)

MEQ0381392:1 VALUES) java.io.IOException: -1 Failure (sending getParamset() MEQ0381392:1 VALUES) at org.openhab.binding.homematic.internal.communicator.parser.RpcResponseParser.parse(RpcResponseParser.java:41) ~[bundleFile:na] at org.openhab.binding.homematic.internal.communicator.client.RpcClient.sendMessage(RpcClient.java:272) ~[bundleFile:na] at org.openhab.binding.homematic.internal.communicator.client.RpcClient.setChannelDatapointValues(RpcClient.java:146) ~[bundleFile:na] at org.openhab.binding.homematic.internal.communicator.AbstractHomematicGateway.loadChannelValues(AbstractHomematicGateway.java:409) [bundleFile:na] at org.openhab.binding.homematic.handler.HomematicThingHandler.updateChannelState(HomematicThingHandler.java:188) ~[bundleFile:na] at org.openhab.binding.homematic.handler.HomematicThingHandler.updateChannelState(HomematicThingHandler.java:166) ~[bundleFile:na] at org.openhab.binding.homematic.handler.HomematicBridgeHandler.onStateUpdated(HomematicBridgeHandler.java:231) [bundleFile:na] at org.openhab.binding.homematic.internal.communicator.AbstractHomematicGateway.eventReceived(AbstractHomematicGateway.java:545) [bundleFile:na] at org.openhab.binding.homematic.internal.communicator.server.RpcCallbackHandler.handleEvent(RpcCallbackHandler.java:130) [bundleFile:na] at org.openhab.binding.homematic.internal.communicator.server.RpcCallbackHandler.handleMethodCall(RpcCallbackHandler.java:85) [bundleFile:na] at org.openhab.binding.homematic.internal.communicator.server.RpcCallbackHandler.handleMethodCall(RpcCallbackHandler.java:99) [bundleFile:na] at org.openhab.binding.homematic.internal.communicator.server.RpcCallbackHandler.run(RpcCallbackHandler.java:63) [bundleFile:na] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_60] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_60] at java.lang.Thread.run(Thread.java:745) [na:1.8.0_60]

Do someone know what's wrong ?

gerrieg commented 8 years ago

That's difficult to say ... a -1 Failure is like a 'catch all unknown errors'. It happens, when the channel is accessed for the first time and all channel values are loaded.

  • Are the devices working properly with the CCU?
  • Are the exceptions always or only sometimes when the channel is accessed?
  • Can you please switch the binding to trace mode (see readme) and send me the logfile?

I had the same error with a dimmer some time ago, i removed it from the CCU and installed it again and since then it works. With Homegear i never had this problem.

belmondo2001 commented 8 years ago

Hello,

here are the logfile

I hope you can find the problem.

In the ccu2 are no problems.

In the events.log I found followings entries

2015-09-26 22:19:46 - Thing 'homematic:HM-ES-TX-WM:29a37f28:MEQ0381392' has been added.

2015-09-26 22:19:46 - homematic:HM-ES-TX-WM:29a37f28:MEQ0381392' updated: INITIALIZING

2015-09-26 22:19:46 - homematic:HM-ES-TX-WM:29a37f28:MEQ0381392' updated: OFFLINE (HANDLER_MISSING_ERROR)

2015-09-26 22:20:02 - homematic:HM-ES-TX-WM:29a37f28:MEQ0381392' updated: ONLINE

2015-09-26 22:20:10 - homematic:HM-ES-TX-WM:29a37f28:MEQ0381392' updated: OFFLINE (COMMUNICATION_ERROR): -1 Failure (sending getParamset()

2015-09-26 22:20:28 - homematic:HM-ES-TX-WM:29a37f28:MEQ0381392' updated: ONLINE

2015-09-26 22:27:48 - Thing 'homematic:HM-ES-TX-WM:29a37f28:MEQ0381392' has been added.

2015-09-26 22:27:48 - homematic:HM-ES-TX-WM:29a37f28:MEQ0381392' updated: INITIALIZING

2015-09-26 22:27:48 - homematic:HM-ES-TX-WM:29a37f28:MEQ0381392' updated: OFFLINE (HANDLER_MISSING_ERROR)

2015-09-26 22:28:00 - homematic:HM-ES-TX-WM:29a37f28:MEQ0381392' updated: ONLINE

2015-09-26 22:28:07 - homematic:HM-ES-TX-WM:29a37f28:MEQ0381392' updated: OFFLINE (COMMUNICATION_ERROR): -1 Failure (sending getParamset()

2015-09-26 22:28:13 - homematic:HM-ES-TX-WM:29a37f28:MEQ0381392' updated: ONLINE

Von: Gerhard R. [mailto:notifications@github.com] Gesendet: Samstag, 26. September 2015 19:48 An: openhab/openhab2 Cc: belmondo2001 Betreff: Re: [openhab2] HomeMatic Binding (#88)

That's difficult to say ... a -1 Failure is like a 'catch all unknown errors'. It happens, when the channel is accessed for the first time and all channel values are loaded.

  • Are the devices working properly with the CCU?
  • Are the exceptions always or only sometimes when the channel is accessed?
  • Can you please switch the binding to trace mode (see readme) and send me the logfile?

I had the same error with a dimmer some time ago, i removed it from the CCU and installed it again and since then it works. With Homegear i never had this problem.

— Reply to this email directly or view it on GitHub https://github.com/openhab/openhab2/issues/88#issuecomment-143475354 .Das Bild wurde vom Absender entfernt.

belmondo2001 commented 8 years ago

I removed the :HM-ES-TX-WM from ccu2 und install it again. Same Error

gerrieg commented 8 years ago

Thank you for the info.

Your log is not a trace log, there should be are much more informations in the logfile. Please open the logback.xml file and add:

<logger name="org.openhab.binding.homematic" level="TRACE" />

Start openHAB and let it run until the exception occurs. Then zip the logfile and send it to me.

belmondo2001 commented 8 years ago

I hope this output helps.

I don’t know how to send you an zip file.

2015-09-26 22:22:43.818 [TRACE] [o.b.h.i.c.s.RpcCallbackHandler] - Event BinRpcMessage: system.multicall()

[

{

methodName=event

params=

[

  RF-29a37f28

  MEQ0381392:1

  BOOT

  false

]

}

{

methodName=event

params=

[

  RF-29a37f28

  MEQ0381392:1

  ENERGY_COUNTER

  342687.5

]

}

{

methodName=event

params=

[

  RF-29a37f28

  MEQ0381392:1

  POWER

  536.0

]

}

]

2015-09-26 22:22:43.820 [DEBUG] [o.o.b.h.i.c.HomematicGateway ] - Received new (Boolean) value 'false' for 'MEQ0381392:V_1_BOOT' from gateway with id '29a37f28'

2015-09-26 22:22:43.823 [DEBUG] [o.o.b.h.i.c.HomematicGateway ] - Received new (Double) value '342687.5' for 'MEQ0381392:V_1_ENERGY_COUNTER' from gateway with id '29a37f28'

2015-09-26 22:22:43.826 [TRACE] [o.o.b.h.i.c.HomematicGateway ] - Loading values for channel HmChannel[number=1,type=POWERMETER_IGL,initialized=false] of device 'MEQ0381392'

2015-09-26 22:22:43.827 [TRACE] [o.o.b.h.i.c.client.RpcClient ] - Client request BinRpcMessage getParamset()

MEQ0381392:1

MASTER

2015-09-26 22:22:43.828 [TRACE] [o.b.h.i.c.client.SocketHandler] - Returning socket for port 2001

2015-09-26 22:22:43.832 [TRACE] [o.o.b.h.i.c.client.RpcClient ] - Client response BinRpcMessage: {

AES_ACTIVE=false

METER_CONSTANT_GAS=0.01

METER_CONSTANT_IR=96

METER_CONSTANT_LED=10000

METER_SENSIBILITY_IR=0

METER_TYPE=1

}

2015-09-26 22:22:43.833 [TRACE] [o.o.b.h.i.c.client.RpcClient ] - Client request BinRpcMessage getParamset()

MEQ0381392:1

VALUES

2015-09-26 22:22:43.834 [TRACE] [o.b.h.i.c.client.SocketHandler] - Returning socket for port 2001

2015-09-26 22:22:43.838 [TRACE] [o.o.b.h.i.c.client.RpcClient ] - Client response BinRpcMessage: {

faultCode=-1

faultString=Failure

}

2015-09-26 22:22:43.839 [TRACE] [o.o.b.h.i.c.client.RpcClient ] - Error sending request: getParamset()

MEQ0381392:1

VALUES

2015-09-26 22:22:43.841 [ERROR] [.o.b.h.h.HomematicThingHandler] - -1 Failure (sending getParamset()

MEQ0381392:1

VALUES)

java.io.IOException: -1 Failure (sending getParamset()

MEQ0381392:1

VALUES)

            at org.openhab.binding.homematic.internal.communicator.parser.RpcResponseParser.parse(RpcResponseParser.java:41) ~[bundleFile:na]

            at org.openhab.binding.homematic.internal.communicator.client.RpcClient.sendMessage(RpcClient.java:272) ~[bundleFile:na]

            at org.openhab.binding.homematic.internal.communicator.client.RpcClient.setChannelDatapointValues(RpcClient.java:146) ~[bundleFile:na]

            at org.openhab.binding.homematic.internal.communicator.AbstractHomematicGateway.loadChannelValues(AbstractHomematicGateway.java:409) [bundleFile:na]

            at org.openhab.binding.homematic.handler.HomematicThingHandler.updateChannelState(HomematicThingHandler.java:188) ~[bundleFile:na]

            at org.openhab.binding.homematic.handler.HomematicThingHandler.updateChannelState(HomematicThingHandler.java:166) ~[bundleFile:na]

            at org.openhab.binding.homematic.handler.HomematicBridgeHandler.onStateUpdated(HomematicBridgeHandler.java:231) [bundleFile:na]

            at org.openhab.binding.homematic.internal.communicator.AbstractHomematicGateway.eventReceived(AbstractHomematicGateway.java:545) [bundleFile:na]

            at org.openhab.binding.homematic.internal.communicator.server.RpcCallbackHandler.handleEvent(RpcCallbackHandler.java:130) [bundleFile:na]

            at org.openhab.binding.homematic.internal.communicator.server.RpcCallbackHandler.handleMethodCall(RpcCallbackHandler.java:85) [bundleFile:na]

            at org.openhab.binding.homematic.internal.communicator.server.RpcCallbackHandler.handleMethodCall(RpcCallbackHandler.java:99) [bundleFile:na]

            at org.openhab.binding.homematic.internal.communicator.server.RpcCallbackHandler.run(RpcCallbackHandler.java:63) [bundleFile:na]

            at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_60]

            at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_60]

            at java.lang.Thread.run(Thread.java:745) [na:1.8.0_60]

2015-09-26 22:22:43.843 [DEBUG] [o.o.b.h.i.c.HomematicGateway ] - Received new (Double) value '536.0' for 'MEQ0381392:V_1_POWER' from gateway with id '29a37f28'

2015-09-26 22:22:43.846 [TRACE] [o.o.b.h.i.c.HomematicGateway ] - Loading values for channel HmChannel[number=1,type=POWERMETER_IGL,initialized=false] of device 'MEQ0381392'

2015-09-26 22:22:43.847 [TRACE] [o.o.b.h.i.c.client.RpcClient ] - Client request BinRpcMessage getParamset()

MEQ0381392:1

MASTER

2015-09-26 22:22:43.848 [TRACE] [o.b.h.i.c.client.SocketHandler] - Returning socket for port 2001

2015-09-26 22:22:43.852 [TRACE] [o.o.b.h.i.c.client.RpcClient ] - Client response BinRpcMessage: {

AES_ACTIVE=false

METER_CONSTANT_GAS=0.01

METER_CONSTANT_IR=96

METER_CONSTANT_LED=10000

METER_SENSIBILITY_IR=0

METER_TYPE=1

}

2015-09-26 22:22:43.853 [TRACE] [o.o.b.h.i.c.client.RpcClient ] - Client request BinRpcMessage getParamset()

MEQ0381392:1

VALUES

2015-09-26 22:22:43.854 [TRACE] [o.b.h.i.c.client.SocketHandler] - Returning socket for port 2001

2015-09-26 22:22:43.858 [TRACE] [o.o.b.h.i.c.client.RpcClient ] - Client response BinRpcMessage: {

faultCode=-1

faultString=Failure

}

2015-09-26 22:22:43.859 [TRACE] [o.o.b.h.i.c.client.RpcClient ] - Error sending request: getParamset()

MEQ0381392:1

VALUES

2015-09-26 22:22:43.861 [ERROR] [.o.b.h.h.HomematicThingHandler] - -1 Failure (sending getParamset()

MEQ0381392:1

VALUES)

java.io.IOException: -1 Failure (sending getParamset()

MEQ0381392:1

VALUES)

            at org.openhab.binding.homematic.internal.communicator.parser.RpcResponseParser.parse(RpcResponseParser.java:41) ~[bundleFile:na]

            at org.openhab.binding.homematic.internal.communicator.client.RpcClient.sendMessage(RpcClient.java:272) ~[bundleFile:na]

            at org.openhab.binding.homematic.internal.communicator.client.RpcClient.setChannelDatapointValues(RpcClient.java:146) ~[bundleFile:na]

            at org.openhab.binding.homematic.internal.communicator.AbstractHomematicGateway.loadChannelValues(AbstractHomematicGateway.java:409) [bundleFile:na]

            at org.openhab.binding.homematic.handler.HomematicThingHandler.updateChannelState(HomematicThingHandler.java:188) ~[bundleFile:na]

            at org.openhab.binding.homematic.handler.HomematicThingHandler.updateChannelState(HomematicThingHandler.java:166) ~[bundleFile:na]

            at org.openhab.binding.homematic.handler.HomematicBridgeHandler.onStateUpdated(HomematicBridgeHandler.java:231) [bundleFile:na]

            at org.openhab.binding.homematic.internal.communicator.AbstractHomematicGateway.eventReceived(AbstractHomematicGateway.java:545) [bundleFile:na]

            at org.openhab.binding.homematic.internal.communicator.server.RpcCallbackHandler.handleEvent(RpcCallbackHandler.java:130) [bundleFile:na]

            at org.openhab.binding.homematic.internal.communicator.server.RpcCallbackHandler.handleMethodCall(RpcCallbackHandler.java:85) [bundleFile:na]

            at org.openhab.binding.homematic.internal.communicator.server.RpcCallbackHandler.handleMethodCall(RpcCallbackHandler.java:99) [bundleFile:na]

            at org.openhab.binding.homematic.internal.communicator.server.RpcCallbackHandler.run(RpcCallbackHandler.java:63) [bundleFile:na]

            at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_60]

            at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_60]

            at java.lang.Thread.run(Thread.java:745) [na:1.8.0_60]

Von: Gerhard R. [mailto:notifications@github.com] Gesendet: Sonntag, 27. September 2015 09:12 An: openhab/openhab2 Cc: belmondo2001 Betreff: Re: [openhab2] HomeMatic Binding (#88)

Thank you for the info.

Your log is not a trace log, there should be are much more informations in the logfile. Please open the logback.xml file and add:

Start openHAB and let it run until the exception occurs. Then zip the logfile and send it to me.

— Reply to this email directly or view it on GitHub https://github.com/openhab/openhab2/issues/88#issuecomment-143526220 .Das Bild wurde vom Absender entfernt.

gerrieg commented 8 years ago

just click on my name and you will see my email address.

I really think it's a CCU problem, but to be sure, i just ordered a HM-ES-TX-WM from ELV. I'll let you know when it was delivered.

belmondo2001 commented 8 years ago

In the log of the ccu2

Sep 27 11:17:03 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=PARTY_MODE_SUBMIT failed getting physical value.

Sep 27 11:17:03 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=PARTY_MODE_SUBMIT failed getting physical value.

Sep 27 11:17:41 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=GAS_ENERGY_COUNTER failed getting physical value.

Sep 27 11:17:41 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=GAS_ENERGY_COUNTER failed getting physical value.

Sep 27 11:18:09 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=PARTY_MODE_SUBMIT failed getting physical value.

Sep 27 11:18:09 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=PARTY_MODE_SUBMIT failed getting physical value.

Sep 27 11:18:09 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=PARTY_MODE_SUBMIT failed getting physical value.

Sep 27 11:18:09 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=PARTY_MODE_SUBMIT failed getting physical value.

Sep 27 11:18:09 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=PARTY_MODE_SUBMIT failed getting physical value.

Sep 27 11:18:09 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=PARTY_MODE_SUBMIT failed getting physical value.

Sep 27 11:19:01 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=PARTY_MODE_SUBMIT failed getting physical value.

Sep 27 11:19:01 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=PARTY_MODE_SUBMIT failed getting physical value.

Sep 27 11:19:01 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=PARTY_MODE_SUBMIT failed getting physical value.

Sep 27 11:19:11 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=PARTY_MODE_SUBMIT failed getting physical value.

Sep 27 11:19:11 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=PARTY_MODE_SUBMIT failed getting physical value.

Sep 27 11:19:20 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=PARTY_MODE_SUBMIT failed getting physical value.

Sep 27 11:19:20 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=PARTY_MODE_SUBMIT failed getting physical value.

Sep 27 11:19:20 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=PARTY_MODE_SUBMIT failed getting physical value.

Von: Gerhard R. [mailto:notifications@github.com] Gesendet: Sonntag, 27. September 2015 10:07 An: openhab/openhab2 Cc: belmondo2001 Betreff: Re: [openhab2] HomeMatic Binding (#88)

just click on my name and you will see my email address.

I really think it's a CCU problem, but to be sure, i just ordered a HM-ES-TX-WM from ELV. I'll let you know when it was delivered.

— Reply to this email directly or view it on GitHub https://github.com/openhab/openhab2/issues/88#issuecomment-143528196 .Das Bild wurde vom Absender entfernt.

belmondo2001 commented 8 years ago

In the homematic Forum

A guy had the same problem, I believe

http://homematic-forum.de/forum/viewtopic.php?f=34&t=8967

Von: Gerhard R. [mailto:notifications@github.com] Gesendet: Sonntag, 27. September 2015 10:07 An: openhab/openhab2 Cc: belmondo2001 Betreff: Re: [openhab2] HomeMatic Binding (#88)

just click on my name and you will see my email address.

I really think it's a CCU problem, but to be sure, i just ordered a HM-ES-TX-WM from ELV. I'll let you know when it was delivered.

— Reply to this email directly or view it on GitHub https://github.com/openhab/openhab2/issues/88#issuecomment-143528196 .Das Bild wurde vom Absender entfernt.

belmondo2001 commented 8 years ago

I test it now with Openhab2 and homematic-1.8 binding. There are no problems. All works well

gerrieg commented 8 years ago

The 1.x binding uses a self made TclRega script to fetch the values from the CCU. The downside is, that not all values can be fetched with this method and the gateway must support TclRega scripts.

The 2.0 binding uses only the RPC-API and optional (only for CCU) TclRega scripts for scripts and variables support. This has the advantage, that the binding works with each gateway which supports at least an rfd daemon.

Until now i can not reproduce the problem with my CCU :-( It would be very helpful, if you can send me the FULL trace log by mail. Do you have any CCU addons installed? Can you enable the RSSI_DEVICE and RSSI_PEER datapoints and post the values?

belmondo2001 commented 8 years ago

Installed CCU Addons (xml Api 1.10) If you like, i can give you access to my ccu2. also i can start a java program in eclipse, if you have some javacode to test the problem.

gerrieg commented 8 years ago

Ha! I can reproduce the failure now with the rf daemon from OCCU, a HM-CFG-LAN and a HM-ES-PMSw1-Pl. Strange, sometimes the API call works, sometimes not.

Thank you for your offer to access your CCU, but it is no longer necessary.

gerrieg commented 8 years ago

@belmondo2001 can you please try the new compiled binding or build it from my repository

belmondo2001 commented 8 years ago

The problem still occurs.

2015-10-02 19:57:07.609 [ERROR] [.o.b.h.h.HomematicThingHandler] - -1 Failure (sending getParamset()

MEQ0381392:1

VALUES)

org.openhab.binding.homematic.internal.communicator.client.UnknownRpcFailureException: -1 Failure (sending getParamset()

MEQ0381392:1

VALUES)

    at org.openhab.binding.homematic.internal.communicator.parser.RpcResponseParser.parse(RpcResponseParser.java:44) ~[bundleFile:na]

    at org.openhab.binding.homematic.internal.communicator.client.RpcClient.sendSocketMessage(RpcClient.java:283) ~[bundleFile:na]

    at org.openhab.binding.homematic.internal.communicator.client.RpcClient.sendSocketMessage(RpcClient.java:296) ~[bundleFile:na]

    at org.openhab.binding.homematic.internal.communicator.client.RpcClient.sendSocketMessage(RpcClient.java:296) ~[bundleFile:na]

    at org.openhab.binding.homematic.internal.communicator.client.RpcClient.sendMessage(RpcClient.java:270) ~[bundleFile:na]

    at org.openhab.binding.homematic.internal.communicator.client.RpcClient.setChannelDatapointValues(RpcClient.java:149) ~[bundleFile:na]

    at org.openhab.binding.homematic.internal.communicator.AbstractHomematicGateway.loadChannelValues(AbstractHomematicGateway.java:406) [bundleFile:na]

    at org.openhab.binding.homematic.handler.HomematicThingHandler.updateChannelState(HomematicThingHandler.java:194) ~[bundleFile:na]

    at org.openhab.binding.homematic.handler.HomematicThingHandler.updateChannelState(HomematicThingHandler.java:172) ~[bundleFile:na]

    at org.openhab.binding.homematic.handler.HomematicBridgeHandler.onStateUpdated(HomematicBridgeHandler.java:223) [bundleFile:na]

    at org.openhab.binding.homematic.internal.communicator.AbstractHomematicGateway.eventReceived(AbstractHomematicGateway.java:526) [bundleFile:na]

    at org.openhab.binding.homematic.internal.communicator.server.RpcCallbackHandler.handleEvent(RpcCallbackHandler.java:129) [bundleFile:na]

    at org.openhab.binding.homematic.internal.communicator.server.RpcCallbackHandler.handleMethodCall(RpcCallbackHandler.java:84) [bundleFile:na]

    at org.openhab.binding.homematic.internal.communicator.server.RpcCallbackHandler.handleMethodCall(RpcCallbackHandler.java:98) [bundleFile:na]

    at org.openhab.binding.homematic.internal.communicator.server.RpcCallbackHandler.run(RpcCallbackHandler.java:62) [bundleFile:na]

Von: Gerhard R. [mailto:notifications@github.com] Gesendet: Mittwoch, 30. September 2015 22:28 An: openhab/openhab2 Cc: belmondo2001 Betreff: Re: [openhab2] HomeMatic Binding (#88)

@belmondo2001 https://github.com/belmondo2001
can you please try the new compiled binding https://drive.google.com/open?id=0Bw7zjCgsXYnHUUc2R3ZnMURibEE or build it from my repository

— Reply to this email directly or view it on GitHub https://github.com/openhab/openhab2/issues/88#issuecomment-144532075 .Das Bild wurde vom Absender entfernt.

gerrieg commented 8 years ago

really strange ... either it's a bug in the firmware or a undocumented 'feature'.

Based on my tests i think the gateway communicates with the device when i call the method from the API. If the communication fails, i get the -1 failure. I've tested with different distances between the device and gateway. If the device is within ~50cm, i get the failure very often. If i put the device furter away, the failure does not occur.

In the last binding version i've posted, i've implemented a workaround (beside other changes). If the gateway returns this failure, the call will be executed again 3x with 500ms delay. This always works in my tests, if the first call fails, the second works flawlessly (and the third is for safety).

But i think i have to implement another workaround to fallback to a TclRega script if the gateway is a CCU :confused:

gerrieg commented 8 years ago

I found another way to extract the datapoint values with the API if there is a -1 Failure. This is my last attempt before i implement the TclRega script workaround.

Again, either compile it from my repo or dowload a compiled version You need to update OH2 too because of the these changes: https://github.com/eclipse/smarthome/commit/6342457c64d008e48bcba859cbc848a51876be1f

Thanks for testing!

belmondo2001 commented 8 years ago

Now the missing Datapoints are found. I can see the missing in the events.log.

But I must back to my old Version, because openhab2 don’t show me any things in the Paper UI (Config/things) after I start the homematic binding.

I had update the runtime to the last version.

I don’t know whats my mistake in my Configuration.

Von: Gerhard R. [mailto:notifications@github.com] Gesendet: Sonntag, 4. Oktober 2015 14:20 An: openhab/openhab2 Cc: belmondo2001 Betreff: Re: [openhab2] HomeMatic Binding (#88)

I found another way to extract the datapoint values with the API if there is a -1 Failure. This is my last attempt before i implement the TclRega script workaround.

Again, either compile it from my repo or dowload a compiled version https://drive.google.com/file/d/0Bw7zjCgsXYnHMXliMFM2RWllb0k/view?usp=sharing You need to update OH2 too because of the these changes: eclipse/smarthome@ https://github.com/eclipse/smarthome/commit/6342457c64d008e48bcba859cbc848a51876be1f 6342457

Thanks for testing!

— Reply to this email directly or view it on GitHub https://github.com/openhab/openhab2/issues/88#issuecomment-145343534 .Das Bild wurde vom Absender entfernt.

gerrieg commented 8 years ago

great news! With the workaround i'm still 100% API compliant!

You can try to delete all three storage.* files in the folder $CONFIG_ROOT/userdata/mapdb/. This is the folder where PaperUI saves it's config.

belmondo2001 commented 8 years ago

Yes.

The Values are transmitted, but

In the event.log I see many changes von online to offline.

2015-10-07 18:05:24 - homematic_HM_TC_IT_WM_W_EU_47ff326c_LEQ1214011_V_1_HUMIDITY updated to 66

2015-10-07 18:05:24 - 'homematic:HM-TC-IT-WM-W-EU:47ff326c:LEQ1214011' updated: OFFLINE (COMMUNICATION_ERROR): -1 Failure (sending getValue()

LEQ1214011:2

PARTY_MODE_SUBMIT)

2015-10-07 18:05:24 - 'homematic:HM-TC-IT-WM-W-EU:47ff326c:LEQ1214011' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): -1 Failure (sending getValue()

LEQ1214011:2

PARTY_MODE_SUBMIT)

2015-10-07 18:05:24 - homematic_HM_TC_IT_WM_W_EU_47ff326c_LEQ1214011_V_0_RELOAD_FROM_GATEWAY updated to OFF

2015-10-07 18:05:24 - 'homematic:HM-TC-IT-WM-W-EU:47ff326c:LEQ1214011' updated: ONLINE

2015-10-07 18:05:24 - 'homematic:HM-TC-IT-WM-W-EU:47ff326c:LEQ1214011' changed from OFFLINE (COMMUNICATION_ERROR): -1 Failure (sending getValue()

LEQ1214011:2

PARTY_MODE_SUBMIT) to ONLINE

2015-10-07 18:05:24 - homematic_HM_TC_IT_WM_W_EU_47ff326c_LEQ1214011_V_0_RELOAD_FROM_GATEWAY updated to OFF

2015-10-07 18:05:24 - homematic_HM_TC_IT_WM_W_EU_47ff326c_LEQ1214011_V_1_TEMPERATURE updated to 19.90

2015-10-07 18:05:24 - homematic_HM_TC_IT_WM_W_EU_47ff326c_LEQ1214011_V_1_HUMIDITY updated to 66

2015-10-07 18:05:24 - 'homematic:HM-TC-IT-WM-W-EU:47ff326c:LEQ1214011' updated: OFFLINE (COMMUNICATION_ERROR): -1 Failure (sending getValue()

LEQ1214011:2

PARTY_MODE_SUBMIT)

2015-10-07 18:05:24 - 'homematic:HM-TC-IT-WM-W-EU:47ff326c:LEQ1214011' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): -1 Failure (sending getValue()

LEQ1214011:2

PARTY_MODE_SUBMIT)

2015-10-07 18:05:24 - 'homematic:HM-TC-IT-WM-W-EU:47ff326c:LEQ1214011' updated: ONLINE

2015-10-07 18:05:24 - 'homematic:HM-TC-IT-WM-W-EU:47ff326c:LEQ1214011' changed from OFFLINE (COMMUNICATION_ERROR): -1 Failure (sending getValue()

LEQ1214011:2

PARTY_MODE_SUBMIT) to ONLINE

2015-10-07 18:05:24 - homematic_HM_TC_IT_WM_W_EU_47ff326c_LEQ1214011_V_0_RELOAD_FROM_GATEWAY updated to OFF

2015-10-07 18:05:24 - homematic_HM_TC_IT_WM_W_EU_47ff326c_LEQ1214011_V_1_TEMPERATURE updated to 19.90

2015-10-07 18:05:24 - homematic_HM_TC_IT_WM_W_EU_47ff326c_LEQ1214011_V_1_HUMIDITY updated to 66

2015-10-07 18:05:24 - 'homematic:HM-TC-IT-WM-W-EU:47ff326c:LEQ1214011' updated: OFFLINE (COMMUNICATION_ERROR): -1 Failure (sending getValue()

LEQ1214011:2

PARTY_MODE_SUBMIT)

2015-10-07 18:05:24 - 'homematic:HM-TC-IT-WM-W-EU:47ff326c:LEQ1214011' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): -1 Failure (sending getValue()

LEQ1214011:2

PARTY_MODE_SUBMIT)

2015-10-07 18:05:24 - 'homematic:HM-TC-IT-WM-W-EU:47ff326c:LEQ1214011' updated: ONLINE

2015-10-07 18:05:24 - 'homematic:HM-TC-IT-WM-W-EU:47ff326c:LEQ1214011' changed from OFFLINE (COMMUNICATION_ERROR): -1 Failure (sending getValue()

LEQ1214011:2

PARTY_MODE_SUBMIT) to ONLINE

2015-10-07 18:05:24 - homematic_HM_TC_IT_WM_W_EU_47ff326c_LEQ1214011_V_0_RELOAD_FROM_GATEWAY updated to OFF

2015-10-07 18:05:24 - homematic_HM_TC_IT_WM_W_EU_47ff326c_LEQ1214011_V_1_TEMPERATURE updated to 19.90

2015-10-07 18:05:24 - homematic_HM_TC_IT_WM_W_EU_47ff326c_LEQ1214011_V_1_HUMIDITY updated to 66

2015-10-07 18:05:24 - 'homematic:HM-TC-IT-WM-W-EU:47ff326c:LEQ1214011' updated: OFFLINE (COMMUNICATION_ERROR): -1 Failure (sending getValue()

LEQ1214011:2

PARTY_MODE_SUBMIT)

Von: Gerhard R. [mailto:notifications@github.com] Gesendet: Mittwoch, 7. Oktober 2015 16:34 An: openhab/openhab2 Cc: belmondo2001 Betreff: Re: [openhab2] HomeMatic Binding (#88)

great news! With the workaround i'm still 100% API compliant!

You can try to delete all three storage.* files in the folder $CONFIG_ROOT/userdata/mapdb/. This is the folder where PaperUI saves it's config.

— Reply to this email directly or view it on GitHub https://github.com/openhab/openhab2/issues/88#issuecomment-146212499 .Das Bild wurde vom Absender entfernt.

gerrieg commented 8 years ago

I played with my new HM-ES-TX-WM, but there is no chance to fetch the datapoint values with a API method. I'm pretty sure this is a firmware bug.

So i implemented another workaround to fetch the values with a TclRega script if the gateway is a CCU.

Works for me now: Download

sja commented 8 years ago

I've got performance problems on my Raspberry.

My Szenario: RPi 1B: "rfpi" with homegear latest stable and a CUL Stick and a SCC board for MAX and Homematic RPi 2B: "openhab" with your binding

At first I tried to just add the homegear bridge and let device discovery do the rest. That was a bad idea, because the last logs I saw from rfpi was homegear's 50 threads limit reached ... and the pi never came back. (I let it work over night, but no chance to even ssh into it) Then I re-installed the rfpi with latest raspbian, latest (stable) homegear and added just one wall thermostat. So the amount of calls was less, but even that killed the homegear process.

In your code I saw a throtteling of some milliseconds. I increased that on my dev machine to about 700ms and started openHAB from there, but there still seem to be a problem. The load is immense.

Do you think, I would have a better chance if I migrate homegear to the openhab board? Then there will be localhost calls. But I'm scared of what happen, if I add the rest of about 20 Homematic and MAX devices.

gerrieg commented 8 years ago

My homegear test environment is a Debian VM with homegear 0.6 and 30 devices (not connected, only in the DB). Homgear has always 14 threads. Maybe this is a 0.5 and/or a PI issue. Which version of the binding are you using? Can you try the latest from my github repo? There were many changes since October.

I don't think that it makes any difference, if the http calls are on localhost or over a network in this case. My Homematic devices are all in use now (christmas lights). But as soon as my wife has released one device, I will test it with my PI :blush:

sja commented 8 years ago

Maybe its the Version. I have problems to install the deb packages on the latest raspbian version so I use 0.5. For the Binding I merge your repo locally to my one. So the latest and greatest is running ;-)

Am Samstag, 2. Januar 2016 schrieb Gerhard R. :

My homegear test environment is a Debian VM with homegear 0.6 and 30 devices (not connected, only in the DB). Homgear has always 14 threads. Maybe this is a 0.5 and/or a PI issue. Which version of the binding are you using? Can you try the latest from my github repo? There were many changes since October.

I don't think that it makes any difference, if the http calls are on localhost or over a network in this case. My Homematic devices are all in use now (christmas lights). But as soon as my wife has released one device, I will test it with my PI [image: :blush:]

— Reply to this email directly or view it on GitHub https://github.com/openhab/openhab2/issues/88#issuecomment-168383694.

Viburnum commented 8 years ago

Hi I just added the jar @gerrieg has provided and added the Homematic Bridge. While initializing the bridge, I get the following exception. Any idea? Openhab 2 Beta on OpenJDK Runtime Environment (IcedTea 2.6.3) (7u91-2.6.3-0ubuntu0.15.10.1)

2016-01-28 19:17:47.682 [ERROR] [ome.core.thing.internal.ThingManager] - Exception occured while calling thing handler factory 'org.openhab.binding.homematic.handler.HomematicThingHandlerFactory@3e38a280': javax/xml/bind/JAXBException java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException at org.openhab.binding.homematic.internal.communicator.HomematicGatewayFactory.createGateway(HomematicGatewayFactory.java:30) at org.openhab.binding.homematic.handler.HomematicBridgeHandler.initialize(HomematicBridgeHandler.java:70) at org.eclipse.smarthome.core.thing.binding.BaseThingHandlerFactory.registerHandler(BaseThingHandlerFactory.java:130) at org.eclipse.smarthome.core.thing.internal.ThingManager$6.call(ThingManager.java:507) at org.eclipse.smarthome.core.thing.internal.ThingManager$6.call(ThingManager.java:1) at java.util.concurrent.FutureTask.run(FutureTask.java:262)[:1.7.0_91] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)[:1.7.0_91] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)[:1.7.0_91] at java.lang.Thread.run(Thread.java:745)[:1.7.0_91] Caused by: java.lang.ClassNotFoundException: javax.xml.bind.JAXBException cannot be found by org.openhab.binding.homematic_2.0.0.201510041213 at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:432)[org.eclipse.osgi-3.10.2.v20150203-1939.jar:] at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:345)[org.eclipse.osgi-3.10.2.v20150203-1939.jar:] at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:337)[org.eclipse.osgi-3.10.2.v20150203-1939.jar:] at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160)[org.eclipse.osgi-3.10.2.v20150203-1939.jar:] at java.lang.ClassLoader.loadClass(ClassLoader.java:358)[:1.7.0_91] ... 9 more

kaikreuzer commented 8 years ago

Well, it sounds as if the manifest of the binding is lacking a package-import for javax/xml/bind...

Viburnum commented 8 years ago

Pull Request https://github.com/gerrieg/openhab2-addons/pull/1 adds javax/xml/bind to the manifest file

  • © Githubissues.
  • Githubissues is a development platform for aggregating issues.