That fixed it @watou, InsteonPLM with a PLM works
What needs to change with the binding so this doesnât need be ran from the prompt?
That fixed it @watou, InsteonPLM with a PLM works
What needs to change with the binding so this doesnât need be ran from the prompt?
Regarding the netatmo binding, I noticed a minor bug. When I start openHAB2, I got this error:
15:47:12.895 [INFO ] [ding.netatmo.internal.NetatmoBinding] - The following Netatmo measurements are not yet configured:
xx:xx:xx:xx:xx:xx#Temperature (Indoor)
xx:xx:xx:xx:xx:xx#Noise (Indoor)
xx:xx:xx:xx:xx:xx#CO2 (Indoor)
xx:xx:xx:xx:xx:xx#Humidity (Indoor)
xx:xx:xx:xx:xx:xx#Pressure (Indoor)
xx:xx:xx:xx:xx:xx#yy:yy:yy:yy:yy:yy#Temperature (Module extérieur)
xx:xx:xx:xx:xx:xx#yy:yy:yy:yy:yy:yy#Humidity (Module extérieur)
When comes the next refresh cycle (5 minutes later), everything is then OK.
As a result, you have first values only 5 minutes after starting openHAB2.
I have not checked if the behaviour is the same in openHAB 1.8.
Could you create a PR similar to this one, but that depends on the openhab-transport-serial feature? That way the binding can be installed from the Paper UI, and installs dependent features at the same time.
Separately, the aspect of the InsteonPLM binding that depends on the org.apache.http bundle will still fail, so Iâm assuming you tested a different aspect of the binding?
@watou, Iâve already did that. https://github.com/openhab/openhab/commit/2cd8362a26555f21d0c742fa04311fd5d131b7d4#diff-9a92cb6081222067edd1cc1e2ada4c76.
I manually copied a snapshot build if insteonplm to the addonâs directory, along with the config file. I assume thatâs why things werenât plumbed correctly?
Yes, I used a PLM via a USB (serial) port vs the hub that uses http. So as long as somebody uses either a USB or serial PLM, it should work.
Yeah, a distro defining the dependent features is needed for the dependent features to be installed via Paper UI. So make a PR like you did for netatmo and I will review and merge.
It was done awhile ago by @Kai :
- <feature name="openhab-binding-expire1" description="Expire Binding" version="${project.version}">
- <feature>openhab-runtime-base</feature>
- <feature>openhab-runtime-compat1x</feature>
- <bundle start-level="80">mvn:org.openhab.binding/org.openhab.binding.expire/${project.version}</bundle>
- </feature>
- <feature name="openhab-binding-fatekplc1" description="Fatek PLC Binding" version="${project.version}">
- <feature>openhab-runtime-base</feature>
- <feature>openhab-runtime-compat1x</feature>
- <feature>openhab-transport-serial</feature>
- <bundle start-level="80">mvn:org.simplify4u/jfatek/3.0.0</bundle>
- <bundle start-level="80">mvn:org.openhab.binding/org.openhab.binding.fatekplc/${project.version}</bundle>
- <configfile finalname="${openhab.conf}/services/fatekplc.cfg" override="false">mvn:${project.groupId}/openhab-addons-external/${project.version}/cfg/fatekplc</configfile>
- </feature>
- <feature name="openhab-binding-freeswitch1" description="Freeswitch Binding" version="${project.version}">
- <feature>openhab-runtime-base</feature>
- <feature>openhab-runtime-compat1x</feature>
- <bundle start-level="80">mvn:org.openhab.binding/org.openhab.binding.freeswitch/${project.version}</bundle>
- <configfile finalname="${openhab.conf}/services/freeswitch.cfg" override="false">mvn:${project.groupId}/openhab-addons-external/${project.version}/cfg/freeswitch</configfile>
- </feature>
- <artifact><file>src/main/resources/conf/comfoair.cfg</file><type>cfg</type><classifier>comfoair</classifier></artifact>
- <artifact><file>src/main/resources/conf/culintertechno.cfg</file><type>cfg</type><classifier>culintertechno</classifier></artifact>
- <artifact><file>src/main/resources/conf/denon.cfg</file><type>cfg</type><classifier>denon</classifier></artifact>
- <artifact><file>src/main/resources/conf/dmx.cfg</file><type>cfg</type><classifier>dmx</classifier></artifact>
- <artifact><file>src/main/resources/conf/dsmr.cfg</file><type>cfg</type><classifier>dsmr</classifier></artifact>
- <artifact><file>src/main/resources/conf/dynamodb.cfg</file><type>cfg</type><classifier>dynamodb</classifier></artifact>
- <artifact><file>src/main/resources/conf/ebus.cfg</file><type>cfg</type><classifier>ebus</classifier></artifact>
- <artifact><file>src/main/resources/conf/ecobee.cfg</file><type>cfg</type><classifier>ecobee</classifier></artifact>
- <artifact><file>src/main/resources/conf/ecotouch.cfg</file><type>cfg</type><classifier>ecotouch</classifier></artifact>
- <artifact><file>src/main/resources/conf/ekey.cfg</file><type>cfg</type><classifier>ekey</classifier></artifact>
- <artifact><file>src/main/resources/conf/enphaseenergy.cfg</file><type>cfg</type><classifier>enphaseenergy</classifier></artifact>
- <artifact><file>src/main/resources/conf/enocean.cfg</file><type>cfg</type><classifier>enocean</classifier></artifact>
- <artifact><file>src/main/resources/conf/epsonprojector.cfg</file><type>cfg</type><classifier>epsonprojector</classifier></artifact>
- <artifact><file>src/main/resources/conf/fatekplc.cfg</file><type>cfg</type><classifier>fatekplc</classifier></artifact>
- <artifact><file>src/main/resources/conf/freeswitch.cfg</file><type>cfg</type><classifier>freeswitch</classifier></artifact>
- <artifact><file>src/main/resources/conf/fritzbox.cfg</file><type>cfg</type><classifier>fritzbox</classifier></artifact>
- <artifact><file>src/main/resources/conf/fritzboxtr064.cfg</file><type>cfg</type><classifier>fritzboxtr064</classifier></artifact>
- <artifact><file>src/main/resources/conf/garadget.cfg</file><type>cfg</type><classifier>garadget</classifier></artifact>
- <artifact><file>src/main/resources/conf/gc100ir.cfg</file><type>cfg</type><classifier>gc100ir</classifier></artifact>
- <artifact><file>src/main/resources/conf/gcal.cfg</file><type>cfg</type><classifier>gcal</classifier></artifact>
- <artifact><file>src/main/resources/conf/gcal-persistence.cfg</file><type>cfg</type><classifier>gcal-persistence</classifier></artifact>
# The insteon PLM controller port, one for each modem or hub.
# You can have multiple ports, but that has never been tested, use at your own peril.
#
# examples of valid port configurations for serial or usb modems:
#
# port_0=/dev/insteon (Linux, with serial port symlinked to /dev/insteon)
# port_0=/dev/ttyS0 (Linux, with plain old serial modem)
# port_0=/dev/ttyUSB0 (Linux, with usb based PLM modem)
# port_0=COM1 (Windows, with serial/usb modem on COM1)
#
# to connect to an Insteon Hub2 (the 2014 version) on port 25105, with
# a poll interval of 1000ms = 1sec:
#
# port_0=/hub2/my_user_name:my_password@myinsteonhub.mydomain:25105,poll_time=1000
#
# to connect to the raw tcp feed on an older Insteon Hub (pre 2014 version) on port 9761
#
# port_0=/hub/localhost:9761
This file has been truncated. show original
What is missing is the ability for OH2 to detect OH1 addons in the /addons directory and install the oh1 compatibility layer. Otherwise, this will continually come up.
What is missing is the ability for OH2 to detect OH1 addons in the /addons directory and install the oh1 compatibility layer. Otherwise, this will continually come up.
I think an issue against one of the other repos would help, unless itâs already documented somewhere that manually installing dependent features is required if you drop an addon JAR in the addons directory.
What is missing is the ability for OH2 to detect OH1 addons in the /addons directory and install the oh1 compatibility layer. Otherwise, this will continually come up.
I think an issue against one of the other repos would help, unless itâs already documented somewhere that manually installing dependent features is required if you drop an addon JAR in the addons directory.
@kai, which repo is the correct place to create an issue for this?
Rob
In the future, users could develop and put personal 2.x bindings in the addons subdirectory. So the compatibility layer must not be installed because a jar is present in this directory.
unless itâs already documented somewhere that manually installing dependent features is required if you drop an addon JAR in the addons directory.
It is documented here. We might also add a note to the README file within the addons folder - feel free to create an according PR for https://github.com/openhab/openhab-distro/blob/master/distributions/distribution-resources/src/main/resources/addons/README.
Btw, @watou and @Lolodomo, you are doing an amazing job on getting 1.x add-ons working again - THANKS!
@Kai, OH2 should be smart enough to detect a OH1 binding and make sure this step has been completed:
Install the 1.x compatibility layer by running feature:install openhab-runtime-compat1x in the openHAB console
Not everybody reads the documentation especially with how simple it was to do this with OH1.
I agree with you. Even me who knows this constraint, I sometimes forget to do it. It should be done automatically, if technically possible.
It should be done automatically, if technically possible.
I doubt that it is. Anyhow, we will soon have all that is working included as installable features, so you wonât need the addon folder anymore, only for rare exceptional cases.
The only thing I could imagine is to introduce another package besides âstandardâ, e.g. something like âoh1compatâ. But this again could be misleading since people might think that you cannot use any 1.x add-ons on the âstandardâ package.
It is documented here. We might also add a note to the README file within the addons folder - feel free to create an according PR for https://github.com/openhab/openhab-distro/blob/master/distributions/distribution-resources/src/main/resources/addons/README.
@ranielsen, would you do that?
you are doing an amazing job on getting 1.x add-ons working again - THANKS!
You and your crew are doing brilliant work, so thank you, too!
Btw, @watou and @Lolodomo, you are doing an amazing job on getting 1.x add-ons working again - THANKS!
Note that I have tested only 6 1.x bindings and 5 2.0 bindings.
I remember you wrote we have 160 1.x bindings. That would mean my own tests only cover around 4% of all 1.x bindings. Very low in fact.
Remains to be tested by myself (1.x bindings): MQTTitude, rrd4j, RFXCOM (waiting for a fix in the 2.0 binding) and my powermax binding.
MQTT and weather 1.x bindings correctly packaged and working well in OH2 snapshot 111.
Unfortunately the netatmo binding is broken in this last snapshot. I will open an issue. I get a JSON parsing error.
Issue opened: https://github.com/openhab/openhab/issues/3937
I probably missed the PR but the snapshot 111 fixed my issue with Astro 2.0 and incorrect date format for display of astro dates in UI. Thank you.
I will try again RFXCOM 2.0 and Freebox 2.0 in case there was a general fix for display of items in UI.
Updated status with OH2 snapshot #111.
Features OK, considering my personal (and so partial) usage:
Features KO (not working at all):
Features working but with bugs: