Thanks, I used this before, but you need some logic in the background if you have a switch on=auto / off=off and another one with on / off.
I actually prefer a triple switch (string) with all three states auto / on / off
But I am still on 1.9 - so I did not test, if this worls with 2.1 as well.
Hello, Markus. I want to thank you for a well written library. But I have a question - How to determine the temperature inside room ? I have RC35 and it has a room temperature sensor. This temperature is visible in the branded mobile application - EasyControl . But I have not found such a specific variable in the file “heizung.item” and example’s
Take a look to the log file (like explained in the wiki). There is a list of all availible channels with actual values. Can you see it there? A channel with this temperature?
Same here. Seems that it installs the OH1.x version.
I started with manually installing the 2.x binding, things where discovered, items linked.
After the update the discovery is no longer working (binding itself starts and communicates with the interface as I see in the log) and the things all now show as “offline” in PaperUI. No control of items possible anymore.
Is there any “official” source that should be used ? That´s the latest version I found in this thread but it seems to be outdated (5.February 2017).
Karaf shows a 2.1-Version, so this should be fine:
206 | Active | 80 | 2.1.0.201702051357 | KM200 Binding
After this it discovers the gateway and I added the private key as required in the gateways thing settings
Some time later the things are being discovered
Strange things I see after this:
The Paper UI still shows the “old” binding to be installable in the add-ons section - this I think would kill the configuration. How to get rid of it ?
Snapshot version does not show up in the add-ons section.
Correction: (13:03) : Items now show up in the control section.
Http error 500, causes the binding to mailfunction after a few minutes. Would suggest to have a parameter “polling intervall” as I have the impression data is requeste to often, causing an overload on the gateway device.
My overall impression:
I´m doing something wrong
Currently it is a bit unclear how the process to get and install the latest snapshot version of the binding looks like so that it shows up correct in Paper UI.
@Markinus: Could you please give some small set of instructions on how to do this properly ?
Any progress on the HTTP error 500 ? For me the binding is not running stable, as I would have to restart the gateway from time to time. Switched to version 1.10 (latest snapshot release), but still no progress.
Did someone figure out a better workaround ?
I recently upgraded my openhabian system and use the km200 version 2.1.0.201702051357
After each upgrade I struggle with the thing generation (deleting all items / things and start with registering the gateway as described somewhere above.
Currently it’s obviously working again.
However, I found a log entry: [hab.binding.km200.internal.KM200Comm] - Fatal transport error: The server 192.168.178.49 failed to respond
The strange thing is that I configured the gateway on 192.168.178.43.
So I have no idea where the binding gets the .49 from and why it’s trying to contact the km on this IP adress.
Of course it’s not working, because it’s just a PoE switch on the .49
Someone an idea?
EDIT:
After a reboot I had to open the gateway and even if the private key and IP adress have been present, the gateway did not get connected.
After opening the gateway thing and closed it with ok (without changes) it was back online…
Strange or a known issue?
EDIT 4:
After a reboot the binding is not active: 269 | Resolved | 80 | 2.1.0.201702051357 | KM200 Binding | org.openhab.binding.km200
How can I ensure that the binding is loaded during startup?
It’s located in /usr/share/openhab2/addons (like always).
some bindings I have set in addons.cfg like
… harmonyhub,http1,mqtt1 (for those which are from OH1).
So do I need to specify the km200 here even though it is neither OH1 nor included in the addons.kar file?
Hi @NCO ,
my personal opinion is that the binding is far away from being stable in OH2.
Checking the openhab.log I see HTTP500 errors after running the binding for a few minutes requiring a reboot of the KM device (It seems that polling data takes place to often and the device is not capable of handling many requests at the same time) and the Thing / Item creation is not reliable (as you noticed).
Some things may be caused by the fact that OH2.1 is work in progress, where sometimes the new builds have issues that are being fixed again later.
In principle the decoding of the data coming from the KM device is working fine, but it needs fine tuning on the interfacing side as well as on the OH2 part.
I highly appreciate the work done by @Markinus, I seriously doubt if it could have been done by me any better, but I would not use this in a productive environment (yet).
Maybe Markus will find some time to address the open points, currently I assume he´s busy with something else.
Nevertheless if you have the skillset required and the time you could fork and improve it. Guess he would be glad to find someone helping him.
Regards,
Oggerschummer
thanks for your response.
I am very greateful that Markus is putting so much effort into this binding and I am actually pretty happy with it.
In my previous setup (openhabian with OH2 stable) the same binding file mentioned above was running flawlessly - so I assume it root cause is within OH2 (which is now the snapshot build),
Or it could be, that I still don’t get the point about using addons.cfg properly.
If my problem(s) mentioed above are not a known issue (or my fault of using it incorrectly) than I will probably switch back the the last sd-card image.
It took me a while to get the “illegal key size” error fixed on OpenHABian distro. If other have the same problems as me, here is what I did to get it fixed (I’m also putting this here for my own future reference )
The apt-get solution didn’t work for me, I got this error:
Unable to locate package "oracle-java8-unlimited-jce-policy"
today i test new openhabian with OH 2.1. Binding not working correctly. Search for things find gateway after configure gateway with IP and privat key find other things. After restart binding not start update. When i go again to Search for things in console show me ,[scovery.KM200GatewayDiscoveryService] - Gateway not configured, scanning postponed.,. Go to things and readd key. But some things show me ,UNINITIALIZED - BRIDGE_UNINITIALIZED,
Late reply, I know But thanks for this recommendation.
I actually experienced some issues using the Oracle files. From time to time, my Pi would freeze up, and I couldn’t find anything in the logging to cause this.
After I downloaded the files for Zulu, this problem went away. So I’m pretty sure this was the cause.
Good question. I have not heard from @Markinus for months, up to now it was not stable enough to rely on it in a productive OH2.x environment. My impression is, that he´s no longer maintaining it, which is really a pity as it is a very good approach. Maybe contact him directly to see what the current status is on his side. Judging from his Github account he is offline since early 2017, no contributions since then. But statistics on github seem to be wrong, last commit to OH2 was September 2017.
I’m still working on this binding. The last version is working very nice and it looks like it could be merged in next time. Here is the last version:
–link removed–