Pauli Anttila

@Jakob Hauerslev, most probably you are using old version of the binding where ihc controller address is not "hostname" but "ip".
 
Newer binding version
ihc:controller:1 [ hostname="192.168.1.10"... Older version:
ihc:controller:1 [ ip="192.168.1.10"...

@Nicholai85, did you add new channel or tried to edit automatically created channel? I just tested PaperUI and added new channel with pulse width parameter + new item + linked channel to item fully via PaperUI without problem.

Update 12.3.2019:
Binding has been merged to openHAB main repository and will available in 2.5 version. Before that, new version can be found from official openHAB snapshot builds.
Before official add-on documentation page is updated, binding documentation can found here.
 
NOTE. If you have used older beta versions of the binding, beware that there has been some breaking changes lately:
Controller address parameter is not anymore ip, but hostname "-channel" suffix is removed from channel types. E.g. switch-channel is just switch.  
###########################################################################################################################
 
Even openHAB 1 IHC binding has been rock solid for many years, I finally decided to port the binding to support openHAB 2 features.
Latest version: https://openhab.jfrog.io/openhab/libs-pullrequest-local/org/openhab/binding/org.openhab.binding.ihc/2.4.0-SNAPSHOT/
Documentation link
Some improvements / features:
By default, binding create channels automatically from project file (currently all dataline_inputs, dataline_outputs, airlink_inputs, airlink_outputs and resource_temperature). Auto creation can be disabled, and channels can be created manually (then all resource id's are supported). Support both Paper UI and thing files configuration. Channels for basic controller information (state, SW and HW version, controller uptime, etc). Trigger channels support (button short press, long press and extra long press). Support multiple controllers (those who have e.g. two controllers environment).  

 

@Kandersen, from here you can find first test version for configurable ON level. It should work with dimmer channels and you need to add onLevel channel parameter (e.g. onLevel=70). I don't have IHC dimmers so I didn't test it well.

@h.hojgaard, @Kandersen, thats great 
I encourage all others test the lates version as well, so that I can fix all problem hopefully before openHAB 2.5 release.

Binding has been merged to openHAB main repository and will available in 2.5 version. Before that, new version can be found starting at tomorrow from official openHAB snapshot builds.
Before official add-on documentation page is updated, binding documentation can found here.
 
NOTE. If you have used older beta versions of the binding, beware that there has been some breaking changes lately:
Controller address parameter is not anymore ip, but hostname "-channel" suffix is removed from channel types. E.g. switch-channel is just switch.

@Gert Kjerslev, @veng, @Nicki Z. I updated apache http client. Could one of you run ones again following version with default 5000ms timeout (with IHC binding trace level debugs)?
https://www.dropbox.com/s/kaebm8nve8y84c7/org.openhab.binding.ihc_2.4.0.201901091843.jar?dl=0
If you still meet timeout problem, please enable http client debugs by following command from karaf console and run test again.
log:set DEBUG org.apache.http You can disable http client debugs by 
log:set DEFAULT org.apache.http Please, send me the log as well.

@veng and @Nicki Z., I'm using Apache http client library to communicate to the IHC controller. Some reason in windows platform, timeout doesn't work like library API defines, so I guess it's a bug on library side. On Mac (OS X) and Linux it works correctly.

@candstand, Could you try this version https://www.dropbox.com/s/dz0diiiw0jcd6mh/org.openhab.binding.ihc_2.4.0.201812151728.jar?dl=0
Production date variable data type has been changed from dateTime to String in v3 software. I tried to fix that. Could you still keep trace level logs and send them to me as I very interested to see if there are any other changes.

Some reason Google translator translate pretty "bad" english, so it's pretty hard to fully understand what you try to reach on your example.
Anyhow, following configuration is read only from openHAB perpective, meaning that only timer value change in IHC is updated to openHAB item.
Number U_TimerVand                        "Timerværdi for vanding [%.0f]"                            <time>            {ihc="<0x1102410"} So if you change the U_TimerVand item value, it will not be updated to IHC. When every timer value is changed in IHC side (timer is running or you change it via service view), value is updated to openHAB item.
Timers are in millisecond resolution in IHC, so I guess that, if timer is running, you will get a lot of updates. Maybe not every millisecond, but very often. 
So most probably it's not wise to sync timer value between openHAB and IHC. If you just want to change the timer value from openHAB to IHC, you could make it write only (>). If you want to know when timer is expired (counted to 0), your most probably should change the IHC code so that when timer is expired some kind of flag is set, which change is then syncronized to openHAB.
 
Syntax explanation:
Syncronization in both directions (IHC <-> openHAB):
Number U_TimerVand   "Timerværdi for vanding [%.0f]"   <time>  {ihc="0x1102410"} Read only (IHC -> openHAB):
Number U_TimerVand   "Timerværdi for vanding [%.0f]"   <time>  {ihc="<0x1102410"} Write only (openHAB -> IHC):
Number U_TimerVand   "Timerværdi for vanding [%.0f]"   <time>  {ihc=">0x1102410"}  

Update 12.3.2019:
Binding has been merged to openHAB main repository and will available in 2.5 version. Before that, new version can be found from official openHAB snapshot builds.
Before official add-on documentation page is updated, binding documentation can found here.
 
NOTE. If you have used older beta versions of the binding, beware that there has been some breaking changes lately:
Controller address parameter is not anymore ip, but hostname "-channel" suffix is removed from channel types. E.g. switch-channel is just switch.  
###########################################################################################################################
 
Even openHAB 1 IHC binding has been rock solid for many years, I finally decided to port the binding to support openHAB 2 features.
Latest version: https://openhab.jfrog.io/openhab/libs-pullrequest-local/org/openhab/binding/org.openhab.binding.ihc/2.4.0-SNAPSHOT/
Documentation link
Some improvements / features:
By default, binding create channels automatically from project file (currently all dataline_inputs, dataline_outputs, airlink_inputs, airlink_outputs and resource_temperature). Auto creation can be disabled, and channels can be created manually (then all resource id's are supported). Support both Paper UI and thing files configuration. Channels for basic controller information (state, SW and HW version, controller uptime, etc). Trigger channels support (button short press, long press and extra long press). Support multiple controllers (those who have e.g. two controllers environment).  

 

Update 12.3.2019:
Binding has been merged to openHAB main repository and will available in 2.5 version. Before that, new version can be found from official openHAB snapshot builds.
Before official add-on documentation page is updated, binding documentation can found here.
 
NOTE. If you have used older beta versions of the binding, beware that there has been some breaking changes lately:
Controller address parameter is not anymore ip, but hostname "-channel" suffix is removed from channel types. E.g. switch-channel is just switch.  
###########################################################################################################################
 
Even openHAB 1 IHC binding has been rock solid for many years, I finally decided to port the binding to support openHAB 2 features.
Latest version: https://openhab.jfrog.io/openhab/libs-pullrequest-local/org/openhab/binding/org.openhab.binding.ihc/2.4.0-SNAPSHOT/
Documentation link
Some improvements / features:
By default, binding create channels automatically from project file (currently all dataline_inputs, dataline_outputs, airlink_inputs, airlink_outputs and resource_temperature). Auto creation can be disabled, and channels can be created manually (then all resource id's are supported). Support both Paper UI and thing files configuration. Channels for basic controller information (state, SW and HW version, controller uptime, etc). Trigger channels support (button short press, long press and extra long press). Support multiple controllers (those who have e.g. two controllers environment).  

 

Update 12.3.2019:
Binding has been merged to openHAB main repository and will available in 2.5 version. Before that, new version can be found from official openHAB snapshot builds.
Before official add-on documentation page is updated, binding documentation can found here.
 
NOTE. If you have used older beta versions of the binding, beware that there has been some breaking changes lately:
Controller address parameter is not anymore ip, but hostname "-channel" suffix is removed from channel types. E.g. switch-channel is just switch.  
###########################################################################################################################
 
Even openHAB 1 IHC binding has been rock solid for many years, I finally decided to port the binding to support openHAB 2 features.
Latest version: https://openhab.jfrog.io/openhab/libs-pullrequest-local/org/openhab/binding/org.openhab.binding.ihc/2.4.0-SNAPSHOT/
Documentation link
Some improvements / features:
By default, binding create channels automatically from project file (currently all dataline_inputs, dataline_outputs, airlink_inputs, airlink_outputs and resource_temperature). Auto creation can be disabled, and channels can be created manually (then all resource id's are supported). Support both Paper UI and thing files configuration. Channels for basic controller information (state, SW and HW version, controller uptime, etc). Trigger channels support (button short press, long press and extra long press). Support multiple controllers (those who have e.g. two controllers environment).