openHAB2 IHC binding

Pauli Anttila · May 19, 2018

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).

Pauli Anttila · April 4, 2019

35 minutes ago, Gilbert said:

i dont get that i need to make a rule or profile follow now

OH1 bindings support both item updates and commands. OH2 bindings supports only commans to channels. Your zwave sensor updates the item state, so update is not propagated to ihc item and therefore not to linked ihc channel. Thats why you need profiles or rule. Follow profile create command from item update, and that command is then send to ihc channel.

Gilbert · April 5, 2019

18 timer siden, Kandersen skrev:

I´m think about a way to reproduce/try this follow profile, but I´m not sure what exactly I have to change/insert into the Visual (IHC) program.. Would a LK temperture sensor do (not linked to any inputs ofcouse) ?

Yes that is What i have fugt/temp sensor no added input just a empty input

Kandersen · April 7, 2019

På 5.4.2019 at 17:10 , Gilbert skrev:

Yes that is What i have fugt/temp sensor no added input just a empty input

I´ll give it a try one of the upcoming days.

Gilbert · April 9, 2019

it seams that i only can use "swicth" command

i tryed to use contact, number and string.

and tryed it from openhab console client

Kandersen · April 9, 2019

58 minutter siden, Gilbert skrev:

it seams that i only can use "swicth" command

i tryed to use contact, number and string.

and tryed it from openhab console client

You seem to be correct. I just tried as well.. I dont get anything through the follow profile.. But I doubt it´s an IHC binding issue , cause it seems that I cant even get the openhab items to update from the follow profile.
This is my item:

Number test_temperatur  "Test temperatur fra zwave temp [%.1f °C] "    <cu_heating>    (Temperatur)      { channel="ihc:controller:elko:zwave_temp" [profile="follow", profile-parameterID="NetamoUdendoersTemperature"] }

The profile-parameterID="NetamoUdendoersTemperature" is my outdoor Netamo temperature sensor. It does update allright. But nothing gets through to the item test_temperatur, which in my opinion is wrong. It should follow the netamo sensor, even without IHC channel. And when the item doesnt update, neither does the IHC channel, ofcouse. At least this is how I understand the follow profile option.

I have seen at the community others are using Number items as well, so I wonder if this is an openhab 2.5 issue. I guess I´ll have to ask..

Kandersen · April 9, 2019

2 timer siden, Gilbert skrev:

it seams that i only can use "swicth" command

i tryed to use contact, number and string.

and tryed it from openhab console client

Got it working now..
Seems like the profile-parameterID has changed. It´s no longer needed. Insted use the channel of the thing you want the item to follow..
This item works great, and it sends the temperature to the IHC controller (temperature product) as well:

Number test_temperatur  "Test temperatur fra zwave temp [%.1f °C] "    <cu_heating>    (Temperatur)      { channel="netatmo:NAModule1:75e7162d:0200002741f4:Temperature", channel="ihc:controller:elko:zwave_temp" [profile="follow"] }

Kandersen · April 10, 2019

På 9.4.2019 at 18:22 , Gilbert skrev:

it seams that i only can use "swicth" command

i tryed to use contact, number and string.

and tryed it from openhab console client

Did you get your problem fixed, @Gilbert?

Gilbert · April 14, 2019

Ihc.things

ihc:controller:elko [ hostname="192.168.0.3", username="admin", password="kode", timeout=5009, loadProjectFile=true, createChannelsAutomatically=false ] {
Channels:
Type number : ihc_2935316 "My Test temp" [ resourceId=2935316, direction="WriteOnly" ]

}

Ihc.items

Number test_ihc "Test temperatur" (Temperatur) { channel="zwave:device:167941bc836:node21:sensor_temperature", channel="ihc:control ler:elko:ihc_2935316" [profile="follow"] }

skulle den så ikke virker ? Eller er mine øjne helt blanke

Kandersen · April 14, 2019

Tjek lige din items linje. Jeg tror du har en space i channel=":ihc:control ler:elko:ihc_2935316".. Hvis jeg kopiere den ind i et ramme, så ser den sådan her ud:

Number test_ihc  "Test temperatur"        (Temperatur) { channel="zwave:device:167941bc836:node21:sensor_temperature", channel="ihc:control ler:elko:ihc_2935316" [profile="follow"] }

Bemærk mellemrummet i ":control ler:"
Du burde dog få en fejl i openhab loggen..

Gilbert · April 14, 2019

2019-04-14 22:25:44.635 [WARN ] [el.core.internal.ModelRepositoryImpl] - Configuration model 'ihc.items' has errors, therefore ignoring it: [1,7]: extraneous input ' ' expecting RULE_ID
[1,176]: extraneous input ' ' expecting EOF

Gilbert · April 14, 2019

1 time siden, Gilbert skrev:

2019-04-14 22:25:44.635 [WARN ] [el.core.internal.ModelRepositoryImpl] - Configuration model 'ihc.items' has errors, therefore ignoring it: [1,7]: extraneous input ' ' expecting RULE_ID
[1,176]: extraneous input ' ' expecting EOF

Got it working now, there where some hidden characters, thanks and sorry the hazzle

Morten H · April 26, 2019

Hi there. Everytime I try to change a pulsewidth in paperui (Configuration/Things/Channels/Entré - Lys loft - Ringetryk - Indgang Generic switch channel) it says Channel updated down in the right corner, but if I go to log, it just keeps doing this in an endless cycle. I'm 100% percent sure that it starts after I change the pulsewidth. I tried reinstalling, and making all my toggle switches. Everything works fine, but when I change a pulsewidth anywhere in paperui I get that same endless circle in log.

Changing pulsewidth back to nothing does not fix it. Deleting the channel does not fix it. I need to remove the whole thing and then add it again to make the error stop.

2019-04-27 00:19:12.206 [hingStatusInfoChangedEvent] - 'ihc:controller:6b310126' changed from OFFLINE (BRIDGE_OFFLINE): Initializing communication to the IHC / ELKO controller to ONLINE

==> /var/log/openhab2/openhab.log <==

2019-04-27 00:19:21.352 [ERROR] [ab.binding.ihc.internal.ws.IhcClient] - New controller state change notification wait failed...

org.openhab.binding.ihc.internal.ws.exeptions.IhcExecption: org.apache.http.conn.ConnectTimeoutException: Connect to 192.168.1.151:443 [/192.168.1.151] failed: Read timed out

	at org.openhab.binding.ihc.internal.ws.http.IhcHttpsClient.sendQuery(IhcHttpsClient.java:110) ~[198:org.openhab.binding.ihc:2.4.0.201810011706]

	at org.openhab.binding.ihc.internal.ws.services.IhcBaseService.sendSoapQuery(IhcBaseService.java:45) ~[198:org.openhab.binding.ihc:2.4.0.201810011706]

	at org.openhab.binding.ihc.internal.ws.services.IhcControllerService.getControllerState(IhcControllerService.java:103) ~[198:org.openhab.binding.ihc:2.4.0.201810011706]

	at org.openhab.binding.ihc.internal.ws.IhcClient$IhcControllerStateListener.run(IhcClient.java:488) [198:org.openhab.binding.ihc:2.4.0.201810011706]

Caused by: org.apache.http.conn.ConnectTimeoutException: Connect to 192.168.1.151:443 [/192.168.1.151] failed: Read timed out

	at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:143) ~[?:?]

	at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:353) ~[?:?]

	at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:380) ~[?:?]

	at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236) ~[?:?]

	at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184) ~[?:?]

	at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88) ~[?:?]

	at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110) ~[?:?]

	at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184) ~[?:?]

	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82) ~[?:?]

	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55) ~[?:?]

	at org.openhab.binding.ihc.internal.ws.http.IhcHttpsClient.sendQ(IhcHttpsClient.java:134) ~[?:?]

	at org.openhab.binding.ihc.internal.ws.http.IhcHttpsClient.sendQuery(IhcHttpsClient.java:94) ~[?:?]

	... 3 more

Caused by: java.net.SocketTimeoutException: Read timed out

	at java.net.SocketInputStream.socketRead0(Native Method) ~[?:?]

	at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) ~[?:?]

	at java.net.SocketInputStream.read(SocketInputStream.java:171) ~[?:?]

	at java.net.SocketInputStream.read(SocketInputStream.java:141) ~[?:?]

	at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) ~[?:?]

	at sun.security.ssl.InputRecord.read(InputRecord.java:503) ~[?:?]

	at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:975) ~[?:?]

	at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1367) ~[?:?]

	at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1395) ~[?:?]

	at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1379) ~[?:?]

	at org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.java:394) ~[?:?]

	at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:353) ~[?:?]

	at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:134) ~[?:?]

	at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:353) ~[?:?]

	at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:380) ~[?:?]

	at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236) ~[?:?]

	at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184) ~[?:?]

	at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88) ~[?:?]

	at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110) ~[?:?]

	at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184) ~[?:?]

	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82) ~[?:?]

	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55) ~[?:?]

	at org.openhab.binding.ihc.internal.ws.http.IhcHttpsClient.sendQ(IhcHttpsClient.java:134) ~[?:?]

	at org.openhab.binding.ihc.internal.ws.http.IhcHttpsClient.sendQuery(IhcHttpsClient.java:94) ~[?:?]

	... 3 more

2019-04-27 00:19:21.493 [WARN ] [ding.ihc.internal.handler.IhcHandler] - Error occurred on communication to IHC controller: org.apache.http.conn.ConnectTimeoutException: Connect to 192.168.1.151:443 [/192.168.1.151] failed: Read timed out

==> /var/log/openhab2/events.log <==

2019-04-27 00:19:32.003 [hingStatusInfoChangedEvent] - 'ihc:controller:6b310126' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE): Initializing communication to the IHC / ELKO controller

2019-04-27 00:19:32.672 [me.event.ThingUpdatedEvent] - Thing 'ihc:controller:6b310126' has been updated.

2019-04-27 00:19:32.953 [hingStatusInfoChangedEvent] - 'ihc:controller:6b310126' changed from OFFLINE (BRIDGE_OFFLINE): Initializing communication to the IHC / ELKO controller to ONLINE

EjvindHald · April 27, 2019

I have tried to go with both the latest 2.4 and 2.5 bindings, but I cannot get the IHC Controller Thing online. I keep getting "Offline - Bridge Offline" or other error messages. I have tried both using a things file and having paperUI add a thing. Both gives errors.

The log shows this:

root@HaldNAS:~# tail -f /volume1/@appstore/openHAB/userdata/logs/openhab.log
at org.openhab.binding.ihc.internal.handler.IhcHandler.updateControllerProperties(IhcHandler.java:277) ~[?:?]
at org.openhab.binding.ihc.internal.handler.IhcHandler.connect(IhcHandler.java:497) ~[?:?]
at org.openhab.binding.ihc.internal.handler.IhcHandler.reconnectCheck(IhcHandler.java:767) ~[?:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[?:?]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) ~[?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) ~[?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
at java.lang.Thread.run(Thread.java:748) [?:?]

And from Karaf console:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<authenticate1 xmlns="utcs">
<password>secret</password>
<username>openhabSVC</username>
<application>treeview</application>
</authenticate1>
</soapenv:Body>
</soapenv:Envelope>
2019-04-27 07:58:50.921 [DEBUG] [ding.ihc.internal.handler.IhcHandler] - Can't open connection to controller
2019-04-27 07:58:51.923 [DEBUG] [ab.binding.ihc.internal.ws.IhcClient] - Closing connection
2019-04-27 07:58:51.924 [DEBUG] [ab.binding.ihc.internal.ws.IhcClient] - Connection closed
2019-04-27 07:58:51.924 [DEBUG] [ding.ihc.internal.handler.IhcHandler] - Connecting to IHC / ELKO LS controller [IP='null', username='openhabSVC'].
2019-04-27 07:58:51.925 [DEBUG] [ab.binding.ihc.internal.ws.IhcClient] - Opening connection
2019-04-27 07:58:51.926 [DEBUG] [c.internal.ws.http.IhcConnectionPool] - Initialize SSL context
2019-04-27 07:58:51.927 [DEBUG] [ws.services.IhcAuthenticationService] - Open connection
2019-04-27 07:58:51.927 [DEBUG] [.ihc.internal.ws.http.IhcHttpsClient] - Open connection to 'https://null/ws/AuthenticationService'
2019-04-27 07:58:51.929 [TRACE] [.ihc.internal.ws.http.IhcHttpsClient] - Send query (connectionPool=7035853, clientId=16128980 requestId=0, timeout=10000, headers=[content-type: text/xml]): <?xml version="1.0" encoding="UTF-8"?>

Please note it seems like the IP address seems to be 'null'

The header of my things.file look like this:

ihc:controller:haldIHC [ hostname="192.168.1.31:444", username="openhabSVC", password="g75Ja!qen", timeout=10000, loadProjectFile=true, createChannelsAutomatically=false ] {

so I using a custom port 444. Is that not supported by IHC binding 2 or openHAB 2.4 anymore?

I am using Java 8.161 and openHAB 2.4 installed on a Synology DiskStation. My IHC Controller is HW 7.

Pauli Anttila · April 27, 2019

@EjvindHald, ip parameter has been changed to hostname very lately. Version which you running still use ip parameter. This can be seen from the debug

2019-04-27 07:58:51.924 [DEBUG] [ding.ihc.internal.handler.IhcHandler] - Connecting to IHC / ELKO LS controller [IP='something', username='openhabSVC'].

Latest version should debug following

2019-04-27 07:58:51.924 [DEBUG] [ding.ihc.internal.handler.IhcHandler] - Connecting to IHC / ELKO LS controller [hostname='something', username='openhabSVC'].

EjvindHald · April 27, 2019

Thanks. This is very useful info.

However, I sm still not quite sure, what is wrong. I have tried completely without a things file and letting paperUI detect. This also gives an error.

I have tried copied both the recent 2.5 snapshot binding and the latest 2.4 version from your dropbox folder into Addons folder and restarted openHAB. I used the links from this thread. Both versions gives the error.

Could openHAB use another version of the binding copied previously to an internal destination somewhere?

Pauli Anttila · April 27, 2019

Quote

Could openHAB use another version of the binding copied previously to an internal destination somewhere?

Yes, openHAB (exactly speaking the Karaf) have cache folder which can contain old version of the binding. If you are using openhabian, cache folder is /var/lib/openhab2/cache/. Search openHAB forum more. From karat console you can see which version is running.

openhab> bundle:list org.openhab.binding.ihc
START LEVEL 100 , List Threshold: 50
 ID │ State  │ Lvl │ Version            │ Name
────┼────────┼─────┼────────────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
300 │ Active │  80 │ 2.4.0.201812182121 │ IHC / ELKO Binding

When handling bindings manually by adding and removing them from add-on folder, it's always wise to stop the current binding before remove it by command

bundle:stop org.openhab.binding.ihc

And check that bundle State is Resolved before remove it.

Kandersen · April 27, 2019

When I install a new version of the binding (manually). I always use Karaf to make sure, then old one is gone.. Normally it´s enough to just delete the old binding from the /addons/ folder, but I have experienced a few times, where it left the old one installed and running, and the new one was installed but no active. In this case, you can use Karaf to uninstall the old binding, and activate the new one. No need to clear cache and tmp then..
I only clear cashe and tmp if things are really screewed up, cause after a clear cache and tmp, it takes quite some time for my system to get back up running, and second, I have several problems with devices added to USB ports due they change port ID when rebooting and specially when i clear cache/tmp. I do use Symlinks, but for reason I cant seem to find, Symlinks doesn´t always work (for my RS485 USB dongle used for modbus connection to Nilan CTS602 interface).

To uninstall a binding from karaf:
bundle:uninstall <binding ID>

To start a binding from karaf:
bundle:start <binding ID>

Pauli Anttila · April 27, 2019

@Morten H, did you modify auto discovered channel or did you add new custom channel which you modified? I quickly tested with custom channel and pulse width editing works fine on my environment.

Morten H · April 27, 2019

3 timer siden, Pauli Anttila skrev:

@Morten H, did you modify auto discovered channel or did you add new custom channel which you modified? I quickly tested with custom channel and pulse width editing works fine on my environment.

I did it on an auto generated channel. So thats the problem?

Morten H · April 27, 2019

3 timer siden, Pauli Anttila skrev:

@Morten H, did you modify auto discovered channel or did you add new custom channel which you modified? I quickly tested with custom channel and pulse width editing works fine on my environment.

Hey Pauli. I tried deleting the switch channel that I wished to have pulsewidth, and I created it again with pulsewidth 200. This starts the error loop. Tried from scratch, and after the binding found all channels I disabled "Create Channels Automatically". Deletede the channel I want with pulsewidth. Made it again with pulsewidth, and it still resultet in that error loop..

2019-04-27 18:24:10.788 [me.event.ThingUpdatedEvent] - Thing 'ihc:controller:27bf5158' has been updated.

2019-04-27 18:24:15.862 [hingStatusInfoChangedEvent] - 'ihc:controller:27bf5158' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): org.apache.http.conn.ConnectTimeoutException: Connect to 192.168.1.151:443 [/192.168.1.151] failed: Read timed out

2019-04-27 18:24:46.389 [hingStatusInfoChangedEvent] - 'ihc:controller:27bf5158' changed from OFFLINE (COMMUNICATION_ERROR): org.apache.http.conn.ConnectTimeoutException: Connect to 192.168.1.151:443 [/192.168.1.151] failed: Read timed out to OFFLINE (BRIDGE_OFFLINE): Initializing communication to the IHC / ELKO controller

2019-04-27 18:24:47.072 [me.event.ThingUpdatedEvent] - Thing 'ihc:controller:27bf5158' has been updated.

2019-04-27 18:24:47.354 [hingStatusInfoChangedEvent] - 'ihc:controller:27bf5158' changed from OFFLINE (BRIDGE_OFFLINE): Initializing communication to the IHC / ELKO controller to ONLINE

2019-04-27 18:24:50.256 [.ItemChannelLinkAddedEvent] - Link 'IHCELKOController_Entre_kip-ihc:controller:27bf5158:entre_kip' has been added.

==> /var/log/openhab2/openhab.log <==

2019-04-27 18:24:52.494 [WARN ] [ab.binding.ihc.internal.ws.IhcClient] - New notifications wait failed...

org.openhab.binding.ihc.internal.ws.exeptions.IhcExecption: org.apache.http.conn.ConnectTimeoutException: Connect to 192.168.1.151:443 [/192.168.1.151] failed: Read timed out

	at org.openhab.binding.ihc.internal.ws.http.IhcHttpsClient.sendQuery(IhcHttpsClient.java:110) ~[198:org.openhab.binding.ihc:2.4.0.201810011706]

	at org.openhab.binding.ihc.internal.ws.services.IhcBaseService.sendSoapQuery(IhcBaseService.java:45) ~[198:org.openhab.binding.ihc:2.4.0.201810011706]

	at org.openhab.binding.ihc.internal.ws.services.IhcResourceInteractionService.waitResourceValueNotifications(IhcResourceInteractionService.java:572) ~[198:org.openhab.binding.ihc:2.4.0.201810011706]

	at org.openhab.binding.ihc.internal.ws.IhcClient.waitResourceValueNotifications(IhcClient.java:357) ~[198:org.openhab.binding.ihc:2.4.0.201810011706]

	at org.openhab.binding.ihc.internal.ws.IhcClient.access$1(IhcClient.java:355) ~[198:org.openhab.binding.ihc:2.4.0.201810011706]

	at org.openhab.binding.ihc.internal.ws.IhcClient$IhcResourceValueNotificationListener.waitResourceNotifications(IhcClient.java:439) [198:org.openhab.binding.ihc:2.4.0.201810011706]

	at org.openhab.binding.ihc.internal.ws.IhcClient$IhcResourceValueNotificationListener.run(IhcClient.java:431) [198:org.openhab.binding.ihc:2.4.0.201810011706]

Caused by: org.apache.http.conn.ConnectTimeoutException: Connect to 192.168.1.151:443 [/192.168.1.151] failed: Read timed out

	at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:143) ~[?:?]

	at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:353) ~[?:?]

	at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:380) ~[?:?]

	at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236) ~[?:?]

	at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184) ~[?:?]

	at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88) ~[?:?]

	at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110) ~[?:?]

	at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184) ~[?:?]

	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82) ~[?:?]

	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55) ~[?:?]

	at org.openhab.binding.ihc.internal.ws.http.IhcHttpsClient.sendQ(IhcHttpsClient.java:134) ~[?:?]

	at org.openhab.binding.ihc.internal.ws.http.IhcHttpsClient.sendQuery(IhcHttpsClient.java:94) ~[?:?]

	... 6 more

Caused by: java.net.SocketTimeoutException: Read timed out

	at java.net.SocketInputStream.socketRead0(Native Method) ~[?:?]

	at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) ~[?:?]

	at java.net.SocketInputStream.read(SocketInputStream.java:171) ~[?:?]

	at java.net.SocketInputStream.read(SocketInputStream.java:141) ~[?:?]

	at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) ~[?:?]

	at sun.security.ssl.InputRecord.read(InputRecord.java:503) ~[?:?]

	at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:975) ~[?:?]

	at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1367) ~[?:?]

	at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1395) ~[?:?]

	at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1379) ~[?:?]

	at org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.java:394) ~[?:?]

	at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:353) ~[?:?]

	at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:134) ~[?:?]

	at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:353) ~[?:?]

	at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:380) ~[?:?]

	at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236) ~[?:?]

	at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184) ~[?:?]

	at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88) ~[?:?]

	at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110) ~[?:?]

	at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184) ~[?:?]

	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82) ~[?:?]

	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55) ~[?:?]

	at org.openhab.binding.ihc.internal.ws.http.IhcHttpsClient.sendQ(IhcHttpsClient.java:134) ~[?:?]

	at org.openhab.binding.ihc.internal.ws.http.IhcHttpsClient.sendQuery(IhcHttpsClient.java:94) ~[?:?]

	... 6 more

2019-04-27 18:24:52.591 [WARN ] [ding.ihc.internal.handler.IhcHandler] - Error occurred on communication to IHC controller: org.apache.http.conn.ConnectTimeoutException: Connect to 192.168.1.151:443 [/192.168.1.151] failed: Read timed out

==> /var/log/openhab2/events.log <==

2019-04-27 18:25:02.599 [hingStatusInfoChangedEvent] - 'ihc:controller:27bf5158' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE): Initializing communication to the IHC / ELKO controller

EjvindHald · May 11, 2019

Hi @Pauli Anttila

I am in the process of convertering all my items from binding version 1 to version 2. This means I have both old and new binding enabled. It all goes fine until I keep getting an error, which I cannot solve.

Upon start of the binding, I get many of these, and I have only shown 3:

2019-05-11 11:42:12.619 [ERROR] [.thing.internal.GenericThingProvider] - Channel type ihc:switch could not be resolved.
2019-05-11 11:42:12.621 [ERROR] [.thing.internal.GenericThingProvider] - Channel type ihc:dimmer could not be resolved.
2019-05-11 11:42:12.623 [ERROR] [.thing.internal.GenericThingProvider] - Channel type ihc:switch could not be resolved.

and the first many Things works fine, but when I add one more, it throws this error:

2019-05-11 11:43:15.606 [ERROR] [ding.ihc.internal.handler.IhcHandler] - Can't update channel 'ihc:controller:haldIHC:ThStueplanStueTrykOverstVenstre' value, cause
org.openhab.binding.ihc.internal.ws.exeptions.IhcExecption: No resource id found
at org.openhab.binding.ihc.internal.ws.services.IhcResourceInteractionService.resourceQuery(IhcResourceInteractionService.java:81) ~[212:org.openhab.binding.ihc:2.5.0.201903151801]

The bold is mine. However, that resource id actually exist, and if I move some lines around in my Things file, then it is suddenly another one with that problem.

I do not know if this problem is related to the binding, openHAB or lack of CPU resources.

I am running openhab version 2.4.0 with your binding org.openhab.binding.ihc-2.5.0-SNAPSHOT on a Synology NAS server. I have attached my Things file.

If I open karaf console, I get a lot of rows.

Thanks.

ihc without pwd.things

Kandersen · May 11, 2019

Could it be some odd caracters somewhere in the file. This has fooled me a coupple of times give all sorts of strange errors.

EjvindHald · May 11, 2019

Also my idea, so I have tried searching for these, but was not able to locate any. Therefore, I uploaded my Things file, so maybe other can see if there any problems like this.

Kandersen · May 11, 2019

Just looked. Cant see anything wrong either..
Do you still use the old binding and it´s resource ID´s ?

Pauli Anttila · May 11, 2019

@EjvindHald, contact channels have direction which is not support as contact is nativily read only channel, but those shouldn't cause any problems. Otherwise I didn't spot any mistakes. Could you enable trace level logs and sent them as well?

Btw, you are not using latest version, but I can't remember if there has been any problems. Here is a link to latest version which I have copied to my dropbox: https://www.dropbox.com/s/xgfj233wdtezlje/org.openhab.binding.ihc-2.5.0.201904021823.jar?dl=0

Log ind

openHAB2 IHC binding

Spørgsmål

Link til kommentar

Del på andre sites

Top Posters For This Question

Popular Days

Top Posters For This Question

Popular Days

Popular Posts

Pauli Anttila

EjvindHald

Pauli Anttila

Posted Images

325 svar på dette spørgsmål

Recommended Posts

Link til kommentar

Del på andre sites

Link til kommentar

Del på andre sites

Link til kommentar

Del på andre sites

Link til kommentar

Del på andre sites

Link til kommentar

Del på andre sites

Link til kommentar

Del på andre sites

Link til kommentar

Del på andre sites

Link til kommentar

Del på andre sites

Link til kommentar

Del på andre sites

Link til kommentar

Del på andre sites

Link til kommentar

Del på andre sites

Link til kommentar

Del på andre sites

Link til kommentar

Del på andre sites

Link til kommentar

Del på andre sites

Link til kommentar

Del på andre sites

Link til kommentar

Del på andre sites

Link til kommentar

Del på andre sites

Link til kommentar

Del på andre sites

Link til kommentar

Del på andre sites

Link til kommentar

Del på andre sites

Link til kommentar

Del på andre sites

Link til kommentar

Del på andre sites

Link til kommentar

Del på andre sites

Link til kommentar

Del på andre sites

Link til kommentar

Del på andre sites

Join the conversation

Important Information