OpenHAB 1.5 HomeMatic Binding does not want to connect to HomeGear

[Darko Križić]

Hi,

I updated from OpenHAB 1.4.0 (actually a 2 months old 1.5.0-SNAPSHOT) to OpenHAB 1.5.0 and have problems, that the (new) HomeMatic Binding does not want to connect to Homegear (unchanged from OpenHAB 1.4.0, an Open Source CCU XML RPC Server that actually wraps the CLU). I get the following exception

17:46:50.307 INFO  o.o.b.h.i.c.CcuCommunicator[:62]- Starting CCU communicator

17:46:50.348 INFO  o.o.b.h.i.c.c.TclRegaScriptClient[:79]- Starting TclRegaScriptClient

17:46:51.579 INFO  o.o.b.h.i.c.CcuStateHolder[:81]- Loading CCU datapoints

17:46:52.255 INFO  o.o.c.s.AbstractActiveService[:169]- Exec Refresh Service has been started

17:46:52.339 INFO  o.o.m.script.AlertNumberUpdate[:53]- AlertNumber 0

17:46:52.829 INFO  o.o.c.s.AbstractActiveService[:169]- HTTP Refresh Service has been started

17:46:53.710 ERROR o.o.b.h.i.c.CcuCommunicator[:84]- Could not start CCU communicator: Connection refused

org.openhab.binding.homematic.internal.communicator.client.CcuClientException: Connection refused

at org.openhab.binding.homematic.internal.communicator.client.TclRegaScriptClient.sendScript(TclRegaScriptClient.java:240)

at org.openhab.binding.homematic.internal.communicator.client.TclRegaScriptClient.sendScriptByName(TclRegaScriptClient.java:191)

at org.openhab.binding.homematic.internal.communicator.client.TclRegaScriptClient.iterateAllDatapoints(TclRegaScriptClient.java:113)

at org.openhab.binding.homematic.internal.communicator.CcuStateHolder.loadDatapoints(CcuStateHolder.java:83)

at org.openhab.binding.homematic.internal.communicator.CcuCommunicator.start(CcuCommunicator.java:69)

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

Caused by: java.net.ConnectException: Connection refused

at java.net.PlainSocketImpl.socketConnect(Native Method)

at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)

at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)

at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)

at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)

at java.net.Socket.connect(Socket.java:579)

17:46:53.771 INFO  o.o.b.h.i.c.CcuCommunicator[:111]- Shutting down CCU communicator

17:46:53.854 INFO  o.o.c.s.AbstractActiveService[:169]- CCU keep alive thread has been started

HomeGear runs on the right ports:

root@openhab:/home/pi# netstat -anp | grep homegear

tcp        0      0 0.0.0.0:2001            0.0.0.0:*               LISTEN      24043/homegear  

tcp        0      0 0.0.0.0:2002            0.0.0.0:*               LISTEN      24043/homegear  

tcp        0      0 0.0.0.0:2003            0.0.0.0:*               LISTEN      24043/homegear  

Looking at the source I can see that the port 2001 is used, so the configuration looks correct. Here are the lines in openhab.cfg

root@openhab:/opt/openhab/configurations# cat openhab.cfg | grep homematic | grep -v "^#" | grep -v "^$"

homematic:host=127.0.0.1

homematic:rpc=bin

homematic:callback.host=127.0.0.1

homematic:callback.port=9123

homematic:alive.interval=300

I am clueless. Can anybody help me?

Regards,

Darko

[gerrieg]

Hi Darko!

Does Homegear support TclRega Scripts like a real CCU? These scripts are necessary for the features the new binding offers.

The TclRegaScriptClient connects to port 8181 and you get a Connection refused. I think these scripts are not supported.

If you don’t have a real CCU, you can try the lxccu project:

http://www.lxccu.com/

http://homematic-forum.de/forum/viewtopic.php?f=26&t=18359

BR

Gerhard

[Darko Križić]

Hi Gerhard,

I don’t know what TclRega Script are, but this sound like the reason for the problem, because Homegear does not open a port 8181. Ok, I will try lxccu. Thanks for the explanation, because I started getting mad, because I thought that the Homematic binding had a problem accessing the normal ports 2001…

I HOPE I don’t have to re-pair all my HomeMatic devices :-( 

Regards,

Darko

--
You received this message because you are subscribed to the Google Groups "openhab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openhab+u...@googlegroups.com.
To post to this group, send email to ope...@googlegroups.com.
Visit this group at http://groups.google.com/group/openhab.
For more options, visit https://groups.google.com/d/optout.

[Darko Križić]

Hi Gerhard,

yesterday I spent several hours to re-activate my HomeMatic stuff after update from OpenHAB 1.4 to 1.5. Before I was using

  OpenHAB -> HomeMatic Binding -> HomeGear -> CUL

HomeGear supports XMLRPC, but not the TclRega Scripts. It can be easily configured and is very very fast with a small footprint. Which alternatives do I have?

  OpenHAB -> CUL Binding -> CUL      <- Needs testing, but the documentation does not mention HomeMatic

  OpenHAB -> HomeMatic Binding -> LxCCU -> CUxD -> CUL

I managed to install LxCCU, but it has no native support for CUL, so I need CUxD. I never had a CCU and never planned to have one. I did not manage to configure any device with LxCCU/CUxD. The configuration is very cumbersome and running OpenHAB and LxCCU on a single Raspberry Pi kills the whole machine.

So I am stuck now. I was not expecting that I will have that many problems with the new HomeMatic Binding which is NOT a drop in replacement. In the evening I will consider using

  OpenHAB -> HomeMatic Binding (1.4) -> HomeGear -> CUL    <- I don't know if the old version runs with the new HomeMatic

Another option would be to use

  OpenHAB -> HomeMatic Binding -> LxCCU -> LAN Gateway

But this will cost money and nothing beats the wireless performance of the CUL stick with the external antenna. 

Regards,

Darko

[Gerhard R.]

Hi Darko!

I really recommend buying a CCU. It's not that expensive. The big advantage is, you don't have to fiddle around for hours with selfmade solutions. It's also future proof if new devices comes out.

The OH 1.5 homematic binding MAY be a dropin replacement if you own a CCU. For all other solutions, if they don't support TclRega Scripts it does not work. 

You have three options:

1.) Buy a CCU (recommended)

2.) Use LxCCU with a LAN Gateway on a Cubietruck (PI is to slow as you already mention). But a CCU is cheaper.

3.) still use the 1.4 binding

Regards

Gerhard

[Yves M]

Hi Gerhard,

I don't think that "throw away your old stuff and buy new stuff" is a good solution for something that worked quite well before. Using OH with a CUL is not a "selfmade solution", it's something that has been done in the purest spirit of creating something that worked without having to throw lots of money at companies with proprietary solutions that might be obsolete next month and something people have invested a lot time in. Hasn't OH been started in the same spirit?
Using the 1.4 binding isn't a solution either, because it had bugs that caused it to be instable. A good solution would be to provide a binding that's backward compatible or at least write something about breaking compatibility in the release notes BEFORE people install OH 1.5. Even the wiki pages mentioned Homegear before OH 1.5, so removing compatibility without even mentioning it is kinda dickish against those users that use a CUL with Homematic devices, and I'm pretty sure that Darko and I are not the only people with that setup. And I'd rather remove OH than buy an unnecessary CCU.

Regards,
Yves 

[Gerhard R.]

Hi Yves!

Some functions would not be possible if i made it 100% backward compatible or i would have had to do many things twice even with different strategies behind. At the end i would have two bindings in one.

Also i think it's the other way around when it comes to Homematic. A CCU is the default way to connect to Homematic devices and a CUL is the proprietary solution.

I think the majority of users have a CCU. Because of the many possibilities to connect to Homematic devices, perhaps it would be better to have multiple bindings (homematic.ccu, homematic.cul, ...). So each binding can exploit the possibilities of the 'connection device'

We should ask the OH Team about their opinion or we should make a vote to know how many people are using alternatives.

Regards,

Gerhard

[Yves M]

Hi Gerhard,

I agree that 100% backward compatibility often is neither possible nor desired. Breaking compatibility is a normal process in development, and usually is not a big problem.

I'm arguing that at least clearly announcing it would have been nice. I wouldn't mind too much beeing stuck with the OH 1.4 binding if at least the bugs would have been fixed, that caused the most problems (the connection refresh bug [ccu connection refresh fails because "address is already in use"] and the data converter bug where double values are used as opposed to floats that are expected by the HM datapoints).

The idea of having a homematic.cul binding sounds good (especially as there already is a cul binding anyway), but I guess you'd have to integrate a lot of stuff that already has been done in Homegear. Maybe it could be a homematic.homegear binding instead that basically is a 1.4 HM binding with bugfixes, as you wouldn't have to care about whether a CUL is used or any other transceiver hardware supported by Homegear.
On the other hand I wouldn't be surprised if sathya (the Homegear developer) would implement the necessary changes to support the tclRega scripts introduced with OH 1.5 if he just got the necessary information about how the communication with the CCU is handled by the HM binding....

Regards,
Yves

[Gerhard R.]

Hi Yves!

Maybe I should have a better description in the wiki, OK.

I looked at the Homegear homepage today. I knew the project, but i have never looked at it more closely. I think the integration with my binding is not very complicated. The only thing i need from the Homegear developer is a method, where i can fetch the metadata and states of all devices. If he implements such a method, i can modify my binding so that it also works with Homegear.

I'll contact the Homegear developer and ask him. 

Regards,

Gerhard

[Darko Križić]

Hi,

• The old HomeMatic Binding 1.4 works perfectly with HomeGear and offers all I want. Am am able to control my HomeMatic devices and I see that states.
• The new HomeMatic Binding 1.5 does require a CCU, because it requires a TclRega Service Running on Port 8181.

To me it is not clear what advantages TclRega does offer. I looks like I can execute some scripts, but I personally like the idea of having my logic centralized in OpenHAB and let HomeMatic dumb.

I fully agree with the idea of having a HomeMatic Binding that is able to NOT offer TclRega, configurable. What is the design reason, that this is not possible?

Regards,

Darko

[Darko Križić]

Hi Gerhard,

I wrote my last comment before you wrote this. I agree with that.  Thanks.

Regards,

Darko

[Gerhard R.]

Hi Darko!

That is my approach too, let Homematic dumb and the complete logic in openHab. 

fyi: The scripts are used to get/set CCU Variables, execute CCU programs, sending commands to a remote control and (re-)loading metadata and states for all devices. The variables and programs are not necesarry in Homegear, so the only thing i need is a possibility to (re-)load these metadata and states. It's not necesarry for Homegear to support the complete TclRega Scripts, i only need a method to get the data.

If the Homegear developer is willing to implement this, i see no problem to support Homegear too.

The only limitation would be the commands to a remote control, but that is not so important. Maybe the Homegear developer implements a method i can call to support this too.

I'll keep you up to date in this thread.

Regards,

Gerhard

[evgeni....@gmail.com]

Guys,

I can only agree with Darko and Yves. I am having HM-CFG-LAN that is perfectly working with FHEM. Since I like more the OH graphical interface and flexibility I have decided to try to migrate from FHEM to OH. Well, to be honest I needed about two weeks (partualy because I was too busy) until I managed to figure out how to have a working environment with OH. The same I did with FHEM in one night... I don't underestimate the complexity of the development (I am a former software developer, now Project Manager) but I must definitely say that the learning curve of OH is quite steep.

Now back to the subject - I would argue that everybody having Homematic as a platform would have CCU. I decided to spare it because per design I wanted to have a home automation solution based on a PC (either RPi, or Windows) and to integrate several platforms which could be done so fare by OH and FHEM. Thus I also prefer to have a "dumb" device to communicate with my Homematic architecture and to let PC-based scripts handle everything else...

Regards/MfG

Evgeni Nikolov

[Gerhard R.]

Hi!

I can't get in contact with Syntha from Homegear. The forum activation e-mail never arrives (and it's not in spam). Can someone who is already registered please tell Syntha, that he should send the activation e-mail to me? Username gerrieg

Thanks!

BR

Gerhard

[Darko Križić]

Hi Gerhard,

I wrote a message to Sathya in the Homegear forum.

Regards,

Darko 

[Gerhard R.]

Thanks Darko

Sathya not Syntha of course, damn auto correction :-)

[hfe...@gmail.com]

Hey,

it should be easy, to get the new HomeMatic Binding work with Homegear again. I won't implement TclRega scripts though, as I think, it is a huge security risk to execute dynamically posted scripts - especially over an unencrypted connection and without authentication of any kind (and Homegear already supports the execution of local scripts through "runScript"). They are used as a workaround anyway, because it is impossible to modify the CCU's RPC functions.

@Gerhard: Just tell me, what you need and I will implement it immediately.

Cheers,

Sathya

[Gerhard R.]

Hi Homegear Guys!

Just for your info ... Sathya and i are now working together. He already implemented a RPC method i need, so i can start adding support for Homegear in the binding.

If a beta is ready, i will post it here.

Regards,

Gerhard

[Thomas E.-E.]

Hi Evgeni,

what exactly were the problems when migrating to openHAB? In general it should be the other way round :-)

It would be really great to learn from your experience and enhance the existing documentation (probably you could help with that?)

Best is to start a new thread for that topic.

Regards,

Thomas E.-E.

[Gerhard R.]

Hi!

So here is the first public build of the Homematic binding with Homegear support.

Important: You need at least Homegear 0.5.2! A first version is already downloadable.

Release Notes: https://github.com/openhab/openhab/wiki/Homematic-Binding

If you encounter any problems, just contact me or Sathya.

Best,

Gerhard

[Jens Kluge]

Hi Gerhard,

Wow! Sounds really interesting.

So just a basic question.

Can I install homegear on rpi and use it with RF wireless LAN gateway and have same (or even more) functionality as with CCU software on rpi

Great work!

Best,
Jens

[Darko Križić]

Hi Jens,

no, Homegear is “only” a bridge, that offers a RPCXML interface (mostly compatible with CCU) and controls a CUL. So it is an alternative to a CCU. But important: It is dumb. It is used for pairing the devices. In combination with OpenHAB this is the preferred device, because it is really fast.

Regards,

Darko

--
You received this message because you are subscribed to a topic in the Google Groups "openhab" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/openhab/DIK9wb0lTi4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to openhab+u...@googlegroups.com.

[hfe...@gmail.com]

Hey Jens,

actually Homegear is not as dumb as Darko suggests. Currently it's just not very comfortable to use, as there is no configuration interface (we are working on that ;-) - you can use the HomeMatic configurator in the mean time). But apart from that, you can do everything, you can do with the CCU, with Homegear, too. Homegear is also fully scriptable in any programming language of your liking using RPC - so you can do pretty much everything imagineable with your HomeMatic devices.

Cheers,

Sathya

[Yves M]

Thank you! Great work! :)

[Darko Križić]

Hi Sathya,

excuse my wording. I just wanted to state that i LOVE HomeGear and prefer it much more than any CCU, because of it’s clean design and simple interface (I am a CLI guy). What I meant with „dumb“ is, that HomeGear does not contains any logic that runs inside HomeGear, like „if switch sends on, send signal to actor“. This must happen outside. And this is what makes the combination of OpenHAB/HomeGear so powerful. So I agree with you!

Regards,

Darko

[hfe...@gmail.com]

Hey Darko,

I think the problem is, there is still a lot of documentation missing... ;-). And if there would be a web interface, the possibilities would be more clear...

> if switch sends on, send signal to actor

That is possible, see here. Simple events like "turn this actor on if a switch is pressed" can be processed directly in Homegear. For more complex stuff Homegear can execute a script in /var/lib/homegear/scripts on for example pressing a button (or any other event, see here and here). I think, Gerhard also implemented the possibilty to execute a Homegear script from openHAB (I'm not 100% sure though).

Cheers,

Sathya

[Darko Križić]

Hi Sathya,

cool, I did not know that. I use Homegear for a while, but I was not aware that it does offer the possibility run have logic in HomeGear. I agree with you, that the following would be nice:

• A complete documentation
• A web frontend for configuring the devices, including custom names and doing some basic configuration (e.g. run times for the roller shutter actor). Currently I need to run this stupid HomeMatic software in a Windows 7 VMWare VM

On the other hand, I prefer centralizing the complete logic into one single place, and that would be OpenHAB in my case, because OpenHAB integrates much more technologies. Therefore I am very happy, that the current version of OpenHAB HomeMatic Binding and HomeGear harmonize well, despite I did not test it on my own (currently no time).

Regards,

Darko

[Gerhard R.]

Hi!

Yes, executing scripts is implemented. But currently without parameters. If there is a need for script parameters in item binding, i can add it.

Regards,

Gerhard

[Darko Križić]

Hi Gerhard and Sathya,

I just wanted to confirm that the combination:

• Homegear 0.5.2-1 and
• Openhab Binding 1.6.0-SNAPSHOT

work. Thank you very much for not needing to buy a CCU :-)

Regards,

Darko

[Darko Križić]

Hi Gerhard,

after some testing I saw, that updates from Homematic are not recognized by OpenHAB. On initial startup of OpenHAB all values are fetched correctly from Homegear, but after I change a state in HomeMatic (e.g. open Windows, toggle the light), I don't see any change in OpenHAB. That worked perfectly with Binding 1.5.0. In the Homegear log I can see that the packet is received and I can see that the state is ok, but OpenHAB has no clue about this change.

Did I miss something? Shouldn't that work?

Regards,

Darko

[Gerhard R.]

Hi Darko!

Every update or just a few?

Can you please switch the binding to DEBUG mode, so you can see every event Homegear is sending to the binding. 

logback.xml:

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

You have to find out, if Homegear does not send the event or the Binding has a problem receiving the events.

Regards,

Gerhard

[Darko Križić]

Hi Gerhard,

I configured the logger and I can see, that there are no log entries, when I open/close a door. The initial loading of the values work:

11:57:22.162 DEBUG o.o.b.h.i.b.HomematicActivator[:33]- Homematic binding has been started.

11:57:23.128 DEBUG o.o.b.h.i.b.HomematicGenericBindingProvider[:63]- Adding item KG_Water with DatapointConfig[address=LEQ0100873,channel=1,parameter=STATE]

11:57:23.159 DEBUG o.o.b.h.i.b.HomematicGenericBindingProvider[:63]- Adding item KG_Window_Wasch with DatapointConfig[address=KEQ0847233,channel=1,parameter=STATE]

11:57:23.205 DEBUG o.o.b.h.i.b.HomematicGenericBindingProvider[:63]- Adding item KG_Window_Sport with DatapointConfig[address=KEQ0847360,channel=1,parameter=STATE]

11:57:23.386 DEBUG o.o.b.h.i.b.HomematicGenericBindingProvider[:63]- Adding item EG_Blind_Toilet with DatapointConfig[address=LEQ0071320,channel=1,parameter=LEVEL]

11:57:37.610 INFO  o.o.b.h.i.bus.HomematicBinding[:92]- HomematicConfig[host=127.0.0.1,callbackHost=127.0.0.1,callbackPort=9123,aliveInterval=300,rpc=bin]

11:57:37.638 INFO  o.o.b.h.i.c.HomematicCommunicator[:68]- Starting Homematic communicator

11:57:37.685 DEBUG o.o.b.h.i.c.ItemDisabler[:53]- Starting ItemDisabler

11:57:39.977 INFO  o.o.b.h.i.c.HomematicCommunicator[:80]- Homematic ServerId[name=Homegear,version=0.5.2]

11:57:40.063 INFO  o.o.b.h.i.c.c.HomegearClient[:54]- Starting HomegearClient

11:57:40.077 DEBUG o.o.b.h.i.c.c.BinRpcClient[:43]- Starting BinRpcClient

11:57:40.108 INFO  o.o.b.h.i.c.StateHolder[:81]- Loading Homematic datapoints

11:57:40.957 DEBUG o.o.b.h.i.c.c.BaseHomematicClient[:113]- Adding battery type to device HM-Sec-RHS: 2x LR44

11:57:41.035 DEBUG o.o.b.h.i.c.c.BaseHomematicClient[:113]- Adding battery type to device HM-Sec-SC: 2x LR44

11:57:41.083 DEBUG o.o.b.h.i.c.c.BaseHomematicClient[:113]- Adding battery type to device HM-Sec-SC: 2x LR44

11:57:41.133 DEBUG o.o.b.h.i.c.c.BaseHomematicClient[:113]- Adding battery type to device HM-Sec-RHS: 2x LR44

11:57:41.790 INFO  o.o.b.h.i.c.StateHolder[:89]- Finished loading 297 Homematic datapoints

11:57:41.804 INFO  o.o.b.h.i.c.StateHolder[:143]- Loading Homematic Server variables

11:57:41.848 INFO  o.o.b.h.i.c.StateHolder[:152]- Finished loading 0 Homematic server variables

11:57:41.860 INFO  o.o.b.h.i.c.s.BinRpcCallbackServer[:44]- Starting BinRpcCallbackServer at port 9123

11:57:41.924 INFO  o.o.b.h.i.c.HomematicCommunicator[:106]- Scheduling one datapoint reload job in 60 seconds

11:57:41.959 INFO  o.o.c.s.AbstractActiveService[:169]- Homematic server keep alive thread has been started

When opening a door I see the following in Homegear log:

07/20/14 10:00:17.807 HomeMatic BidCoS packet received (My-CUL, RSSI: 0x55): 0C01A64152CFE8FD142201F000

07/20/14 10:00:17.812 Module HomeMatic BidCoS: Info: LOWBAT of HomeMatic BidCoS peer 2 with serial number LEQ0034871:1 was set to 0x00.

07/20/14 10:00:17.816 Module HomeMatic BidCoS: Info: STATE of HomeMatic BidCoS peer 2 with serial number LEQ0034871:1 was set to 0x00.

07/20/14 10:00:17.902 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0A018002FD142252CFE80

But no reaction in OpenHAB. So either Homegear is not sending or OpenHAB not receiving. 

[Gerhard R.]

Hi Darko!

> HomematicConfig[host=127.0.0.1,callbackHost=127.0.0.1,callbackPort=9123,aliveInterval=300,rpc=bin]

Can you please try to configure the real IP Address instead of 127.0.0.1. Maybe this is the problem.

The binding writes every received event immediately to the log in debug mode, so i think Homegear is not sending something.

Regards,

Gerhard

 

[Darko Križić]

Hi,

I changed from 127.0.0.1 to my real IP (10.10.0.22), but no change. I just saw, that Port 9123 is listening on IPv6 only:

root@openhab:/opt/openhab# netstat -an | grep 9123

tcp6       0      0 :::9123                 :::*                    LISTEN     

tcp6       0      0 10.10.0.22:9123         10.10.0.22:46225        TIME_WAIT  

But this does not seem to be the problem. I looks like that HomeGear does not connect to OpenHAB Port 9123 and does not keep the connection open, but I cannot find any useful information in the HomeGear log.

Is there anybody out there using OpenHAB with Homegear and can report if it works or not...

Darko Križić
da...@krizic.net

This mail is signed with a digital certificate. You can verify my real name and you can encrypt your answer to me. Please support this technology, by using digital certificates.

[Darko Križić]

Hi Gerhard,

but there is some communication:

07/20/14 10:53:41.033 Info: Connecting to host 10.10.0.22 on port 9123...

07/20/14 10:53:41.035 Info: Connected to host 10.10.0.22 on port 9123. Client number is: 13

07/20/14 10:53:41.035 Sending packet: 42696E000000002A0000001273797374656D2E6C6973744D6574686F6473000000010000000300000008486F6D6567656172

07/20/14 10:53:41.040 RPC client receiving binary rpc packet with size: 40. Payload size is: 32

07/20/14 10:53:41.043 Debug: Received packet from server 10.10.0.22 on port 9123: 42696E01000000200000010000000001000000030000001073797374656D2E6D756C746963616C6C00

07/20/14 10:53:41.044 Response was:

(Array length=1)

{

  (String) system.multicall

}

But the connection is quickly dropped:

tcp6       0      0 :::9123                 :::*                    LISTEN     

tcp6       0      0 10.10.0.22:9123         10.10.0.22:46225        TIME_WAIT  

I don’t see any reason. For my understanding, Homegear should keep the connection open to OpenHAB, but either OpenHAB or Homegear drop it. I cannot find any according log entries.

:-(

Regards,

Darko

On 2014-07-20, at 12:14, Gerhard R. <gerhard...@gmail.com> wrote:

[Gerhard R.]

Hi Darko!

The communication seems to be ok, this request/response is one of the first after startup ... but no events are sent.

@Sathya

Can you reproduce it? Any ideas?

Regards,

Gerhard

[hfe...@gmail.com]

Hey,

I will look into it later this evening... It should work. It looks like the response from openHAB to "listMethods" is missing "event".

Cheers,
Sathya

[Gerhard R.]

Hi Darko!

Added event to listMethods, can you try this build please?

BR,

Gerhard

[Darko Križić]

Hi Gerhard,

yes, that did it!!! Now it works! When toggling my terrace I see the following in my log:

15:05:54.866 DEBUG o.o.b.h.i.c.HomematicCommunicator[:166]- Received new (Integer) value '-84' for DatapointConfig[address=LEQ0034871,channel=0,parameter=RSSI_DEVICE]

15:05:54.958 DEBUG o.o.b.h.i.c.HomematicCommunicator[:166]- Received new (Boolean) value 'false' for DatapointConfig[address=LEQ0034871,channel=1,parameter=LOWBAT]

15:05:54.966 DEBUG o.o.b.h.i.c.HomematicCommunicator[:166]- Received new (Boolean) value 'false' for DatapointConfig[address=LEQ0034871,channel=1,parameter=STATE]

15:05:54.972 DEBUG o.o.b.h.i.c.s.AbstractTypeConverter[:105]- Converting (Boolean) value 'false' with OpenClosedTypeConverter for HmDatapoint[address=LEQ0034871,channel=1,parameter=STATE]

The only thing that I did recognize is that the iOS client does not update this value automatically, only after a refresh. But the Web UI does change the value instantly. I presume this problem is somewhere else.

Darko Križić
da...@krizic.net

This mail is signed with a digital certificate. You can verify my real name and you can encrypt your answer to me. Please support this technology, by using digital certificates.

You guys are fabulous.

Regards,

Darko

--
You received this message because you are subscribed to a topic in the Google Groups "openhab" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/openhab/DIK9wb0lTi4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to openhab+u...@googlegroups.com.
To post to this group, send email to ope...@googlegroups.com.
Visit this group at http://groups.google.com/group/openhab.
For more options, visit https://groups.google.com/d/optout.

<org.openhab.binding.homematic-1.6.0-SNAPSHOT-pb05.jar>

[Gerhard R.]

Hi Darko!

Great! Seems the version from the homepage differs at this point with the last version i've got from Sathya. I've downloaded the homepage version now ;-)

Yes, the IOS App has nothing to do with the binding itself. 

Will make a pull-request ...

BR,

Gerhard

[hfe...@gmail.com]

Hey Gerhard,

thanks for fixing this so quickly ;-).

Sathya