OH2.2 issues with Homegear / Homematic

Hi all,

after updating to Openhab version 2.2 I’m having issues with Homegear and Homematic.
I’m using the HM-MOD-RPI-PCB adapter on my Raspberry Pi 3, on version 2.0 everything works fine.
In PaperUI every Homematic device is online, but when I switch a light in basic UI nothing happens.
For me it looks like that receiving data from the devices to Homegear is working…
But sending from Openhab to Homegear and then to the devices isn’t?!

I hope you guys can help me… tried to summarise some infos, hope this helps…
If you need more logfiles let me know.

Thanks
Matthias

Openhabian infos

  Release = Raspbian GNU/Linux 8 (jessie)
##       Kernel = Linux 4.9.35-v7+
##       Platform = Raspberry Pi 3 Model B Rev 1.2
##       openHAB 2.2.0-1 (Release Build)
IP address 10.10.203.2/24

Homegear Version

[16:57:31] openhabian@pi-openhab:~$ homegear -v
Homegear version 0.7.14-1563
Copyright (c) 2013-2017 Sathya Laufer

Git commit SHA of libhomegear-base: -
Git branch of libhomegear-base:     -
Git commit SHA of Homegear:         -
Git branch of Homegear:             -

PHP (License: PHP License):
This product includes PHP software, freely available from <http://www.php.net/so                                         ftware/>
Copyright (c) 1999-2017 The PHP Group. All rights reserved.

openhab.log

2018-01-24 17:32:43.809 [INFO ] [ternal.communicator.client.RpcClient] - Interface 'WIRED' on gateway '618eedaa' not available, disabling support
2018-01-24 17:32:43.818 [INFO ] [ternal.communicator.client.RpcClient] - Interface 'HMIP' on gateway '618eedaa' not available, disabling support
2018-01-24 17:32:43.832 [INFO ] [ternal.communicator.client.RpcClient] - Interface 'CUXD' on gateway '618eedaa' not available, disabling support
2018-01-24 17:32:43.842 [INFO ] [ternal.communicator.client.RpcClient] - Interface 'GROUP' on gateway '618eedaa' not available, disabling support
2018-01-24 17:32:44.061 [INFO ] [ommunicator.AbstractHomematicGateway] - HmGatewayInfo[id=HOMEGEAR,type=Homegear,firmware=0.7.14-1563,address=VBC1476541,wired=false,hmip=false,cuxd=false,group=false]

2018-01-24 17:33:00.838 [ERROR] [ematic.handler.HomematicThingHandler] - -100 No answer from device. (sending setValue()
OEQ0243032:4
MANU_MODE
15.0
)
java.io.IOException: -100 No answer from device. (sending setValue()
OEQ0243032:4
MANU_MODE
15.0
)
	at org.openhab.binding.homematic.internal.communicator.parser.RpcResponseParser.parse(RpcResponseParser.java:47) [251:org.openhab.binding.homematic:2.2.0]
	at org.openhab.binding.homematic.internal.communicator.client.BinRpcClient.sendMessage(BinRpcClient.java:78) [251:org.openhab.binding.homematic:2.2.0]
	at org.openhab.binding.homematic.internal.communicator.client.BinRpcClient.sendMessage(BinRpcClient.java:90) [251:org.openhab.binding.homematic:2.2.0]
	at org.openhab.binding.homematic.internal.communicator.client.BinRpcClient.sendMessage(BinRpcClient.java:66) [251:org.openhab.binding.homematic:2.2.0]
	at org.openhab.binding.homematic.internal.communicator.client.RpcClient.setDatapointValue(RpcClient.java:293) [251:org.openhab.binding.homematic:2.2.0]
	at org.openhab.binding.homematic.internal.communicator.AbstractHomematicGateway$1.execute(AbstractHomematicGateway.java:571) [251:org.openhab.binding.homematic:2.2.0]
	at org.openhab.binding.homematic.internal.misc.DelayedExecuter.start(DelayedExecuter.java:61) [251:org.openhab.binding.homematic:2.2.0]
	at org.openhab.binding.homematic.internal.communicator.AbstractHomematicGateway.sendDatapoint(AbstractHomematicGateway.java:550) [251:org.openhab.binding.homematic:2.2.0]
	at org.openhab.binding.homematic.internal.communicator.AbstractHomematicGateway.sendDatapoint(AbstractHomematicGateway.java:529) [251:org.openhab.binding.homematic:2.2.0]
	at org.openhab.binding.homematic.handler.HomematicThingHandler.handleCommand(HomematicThingHandler.java:175) [251:org.openhab.binding.homematic:2.2.0]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:?]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
	at java.lang.reflect.Method.invoke(Method.java:498) ~[?:?]
	at org.eclipse.smarthome.core.internal.common.AbstractInvocationHandler.invokeDirect(AbstractInvocationHandler.java:153) [109:org.eclipse.smarthome.core:0.10.0.b1]
	at org.eclipse.smarthome.core.internal.common.InvocationHandlerSync.invoke(InvocationHandlerSync.java:59) [109:org.eclipse.smarthome.core:0.10.0.b1]
	at com.sun.proxy.$Proxy159.handleCommand(Unknown Source) [251:org.openhab.binding.homematic:2.2.0]
	at org.eclipse.smarthome.core.thing.internal.profiles.ProfileCallbackImpl.handleCommand(ProfileCallbackImpl.java:72) [116:org.eclipse.smarthome.core.thing:0.10.0.b1]
	at org.eclipse.smarthome.core.thing.internal.profiles.SystemDefaultProfile.onCommandFromItem(SystemDefaultProfile.java:49) [116:org.eclipse.smarthome.core.thing:0.10.0.b1]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:?]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
	at java.lang.reflect.Method.invoke(Method.java:498) ~[?:?]
	at org.eclipse.smarthome.core.internal.common.AbstractInvocationHandler.invokeDirect(AbstractInvocationHandler.java:153) [109:org.eclipse.smarthome.core:0.10.0.b1]
	at org.eclipse.smarthome.core.internal.common.Invocation.call(Invocation.java:53) [109:org.eclipse.smarthome.core:0.10.0.b1]
	at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
	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) [?:?]

events.log while switching a homatic device in basicUI

2018-01-24 17:33:10.821 [hingStatusInfoChangedEvent] - 'homematic:HG-HM-CC-RT-DN:618eedaa:OEQ0243032' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR)
2018-01-24 17:33:11.794 [hingStatusInfoChangedEvent] - 'homematic:HG-HM-CC-RT-DN:618eedaa:OEQ0243032' changed from OFFLINE (COMMUNICATION_ERROR) to ONLINE
2018-01-24 17:33:12.031 [me.event.ThingUpdatedEvent] - Thing 'homematic:HG-HM-CC-RT-DN:618eedaa:OEQ0243032' has been updated.

homegear -r

[17:45:54] openhabian@pi-openhab:~$ homegear -r
Connected to Homegear (version 0.7.14-1563).
> families list
   ID │ Name
──────┼───────────────────────────────
    0 │ HomeMatic BidCoS
  254 │ Miscellaneous
──────┴───────────────────────────────
> families select 0
Device family "HomeMatic BidCoS" selected.
For information about the family's commands type: "help"
(Family)> ls
         ID │ Name                      │  Address │ Serial Number │ Type │ Type String               │ Firmware │ Config Pending │ Unreach │ Low Bat
────────────┼───────────────────────────┼──────────┼───────────────┼──────┼───────────────────────────┼──────────┼────────────────┼─────────┼────────
            │                           │          │               │      │                           │          │                │         │
          1 │ Dachgeschoss Büro         │   51A01D │    NEQ1489970 │ 0095 │ HM-CC-RT-DN               │      1.4 │             No │      No │      No
          2 │ Dachgeschoss Badezimmer   │   51A00C │    NEQ1489987 │ 0095 │ HM-CC-RT-DN               │      1.4 │             No │      No │      No
          3 │ Dachgeschoss Küche        │   51A018 │    NEQ1489977 │ 0095 │ HM-CC-RT-DN               │      1.4 │             No │      No │      No
          4 │ Dachgeschoss Schlafzimmer │   51A005 │    NEQ1489985 │ 0095 │ HM-CC-RT-DN               │      1.4 │             No │      No │      No
          5 │ Dachgeschoss Wohnzimme... │   51A985 │    NEQ1488399 │ 0095 │ HM-CC-RT-DN               │      1.4 │             No │      No │      No
          6 │ Dachgeschoss Wohnzimme... │   51A9B7 │    NEQ1488386 │ 0095 │ HM-CC-RT-DN               │      1.4 │             No │      No │      No
          7 │ Erdgeschoss Badezimmer    │   569AD2 │    OEQ0243032 │ 0095 │ HM-CC-RT-DN               │      1.4 │             No │      No │      No
          8 │ Erdgeschoss Wohnzimmer... │   567BFE │    OEQ0242336 │ 0095 │ HM-CC-RT-DN               │      1.4 │             No │      No │      No
          9 │ Erdgeschoss Wohnzimmer... │   567C00 │    OEQ0242338 │ 0095 │ HM-CC-RT-DN               │      1.4 │             No │      No │      No
         10 │ Erdgeschoss Wohnzimmer... │   567C01 │    OEQ0242339 │ 0095 │ HM-CC-RT-DN               │      1.4 │             No │      No │      No
         11 │ Erdgeschoss Hauswirtsc... │   567C04 │    OEQ0242342 │ 0095 │ HM-CC-RT-DN               │      1.4 │             No │      No │      No
         12 │ Kellergeschoss Fittnes... │   567C4A │    OEQ0242362 │ 0095 │ HM-CC-RT-DN               │      1.4 │             No │      No │      No
         13 │ Dachgeschoss Wohnzimme... │   5A0CF6 │    OEQ0473427 │ 0069 │ HM-LC-Sw1PBU-FM           │      2.8 │             No │      No │      No
         14 │ Dachgeschoss Esszimmer... │   4ADE1A │    NEQ0389308 │ 0068 │ HM-LC-Dim1TPBU-FM         │      2.9 │             No │      No │      No
────────────┴───────────────────────────┴──────────┴───────────────┴──────┴───────────────────────────┴──────────┴────────────────┴─────────┴────────
(Family)>

homegear.log

01/24/18 17:24:00.359 Starting Homegear...
01/24/18 17:24:00.359 Homegear version 0.7.14-1563
01/24/18 17:24:00.359 Git commit SHA of libhomegear-base: -
01/24/18 17:24:00.359 Git branch of libhomegear-base:     -
01/24/18 17:24:00.359 Git commit SHA of Homegear:         -
01/24/18 17:24:00.359 Git branch of Homegear:             -
01/24/18 17:24:00.361 Info: Setting allowed core file size to "4294967295" for user with id 0 and group with id 0.
01/24/18 17:24:00.361 Info: Core file size now is "4294967295".
01/24/18 17:24:00.361 Info: Setting maximum thread priority to "4294967295" for user with id 0 and group with id 0.
01/24/18 17:24:00.361 Info: Maximum thread priority now is "4294967295".
01/24/18 17:24:00.439 Info: Backing up database...
01/24/18 17:24:00.683 Initializing database...
01/24/18 17:24:00.687 Info: Loading family module mod_miscellaneous.so
01/24/18 17:24:00.691 /etc/homegear/families/miscellaneous.conf
01/24/18 17:24:00.691 Info: Loading family module mod_homematicbidcos.so
01/24/18 17:24:00.703 /etc/homegear/families/homematicbidcos.conf
01/24/18 17:24:00.705 Info: Loading family module mod_homematicwired.so
01/24/18 17:24:00.710 /etc/homegear/families/homematicwired.conf
01/24/18 17:24:00.711 Info: Setting up physical interfaces and GPIOs...
01/24/18 17:24:00.712 Info: Dropping privileges to user homegear (110) and group homegear (116)
01/24/18 17:24:00.713 Info: Homegear is (now) running as user with id 110 and group with id 116.
01/24/18 17:24:00.719 Starting script engine server...
01/24/18 17:24:00.727 Initializing licensing controller...
01/24/18 17:24:00.727 Loading licensing controller data...
01/24/18 17:24:00.727 Loading devices...
01/24/18 17:24:00.728 Loading XML RPC devices...
01/24/18 17:24:01.891 Loading device 2
01/24/18 17:24:01.891 Module HomeMatic BidCoS: Info: Central address set to 0xFD7392.
01/24/18 17:24:01.892 Module HomeMatic BidCoS: Loading peer 1
01/24/18 17:24:01.910 Module HomeMatic BidCoS: Loading peer 2
01/24/18 17:24:01.926 Module HomeMatic BidCoS: Loading peer 3
01/24/18 17:24:01.943 Module HomeMatic BidCoS: Loading peer 4
01/24/18 17:24:01.959 Module HomeMatic BidCoS: Loading peer 5
01/24/18 17:24:01.976 Module HomeMatic BidCoS: Loading peer 6
01/24/18 17:24:01.994 Module HomeMatic BidCoS: Loading peer 7
01/24/18 17:24:02.011 Module HomeMatic BidCoS: Loading peer 8
01/24/18 17:24:02.029 Module HomeMatic BidCoS: Loading peer 9
01/24/18 17:24:02.047 Module HomeMatic BidCoS: Loading peer 10
01/24/18 17:24:02.065 Module HomeMatic BidCoS: Loading peer 11
01/24/18 17:24:02.083 Module HomeMatic BidCoS: Loading peer 12
01/24/18 17:24:02.101 Module HomeMatic BidCoS: Loading peer 13
01/24/18 17:24:02.112 Module HomeMatic BidCoS: Loading peer 14
01/24/18 17:24:02.154 Info: Not initializing device family HomeMatic Wired, because no physical interface was found.
01/24/18 17:24:02.154 Info: Disposing family module mod_homematicwired.so
01/24/18 17:24:02.154 Loading XML RPC devices...
01/24/18 17:24:02.158 Loading device 1
01/24/18 17:24:02.158 Initializing RPC client...
01/24/18 17:24:02.158 Starting XML RPC server RPCServer1 listening on :::2001...
01/24/18 17:24:02.162 Starting XML RPC server RPCServer2 listening on :::2002, SSL enabled...
01/24/18 17:24:02.162 RPC Server (Port 2001): Info: RPC Server started listening on address :: and port 2001
01/24/18 17:24:02.195 Starting XML RPC server RPCServer3 listening on :::2003, SSL enabled, authentication enabled...
01/24/18 17:24:02.195 RPC Server (Port 2002): Info: RPC Server started listening on address :: and port 2002
01/24/18 17:24:02.227 Starting CLI server...
01/24/18 17:24:02.227 RPC Server (Port 2003): Info: RPC Server started listening on address :: and port 2003
01/24/18 17:24:02.227 Initializing event handler...
01/24/18 17:24:02.227 Loading events...
01/24/18 17:24:02.228 Starting flows server...
01/24/18 17:24:02.233 Starting IPC server...
01/24/18 17:24:02.238 Start listening for packets...
01/24/18 17:24:04.239 Startup complete. Waiting for physical interfaces to connect.
01/24/18 17:24:04.240 All physical interfaces are connected now.
01/24/18 17:24:04.240 Starting UPnP server...
01/24/18 17:24:04.242 Info: UPnP server: Binding to address: 10.10.203.2
01/24/18 17:24:04.242 UPnP Server: Info: Started listening.
01/24/18 17:24:06.681 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Info: Firmware version: 1.2.1
01/24/18 17:24:06.688 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Info: Serial number: NEQ1332224
01/24/18 17:24:06.704 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Info: Init queue completed. Sending peers...
01/24/18 17:24:07.067 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Info: Peer sending completed.
01/24/18 17:24:16.466 HomeMatic BidCoS packet received (My-HM-MOD-RPI-PCB, RSSI: -49 dBm): 0FD78610567BFE0000000A9CBB0B4100
01/24/18 17:24:16.467 Module HomeMatic BidCoS: Info: ACTUAL_TEMPERATURE on channel 4 of HomeMatic BidCoS peer 8 with serial number OEQ0242336 was set to 0x00BB.
01/24/18 17:24:16.468 Module HomeMatic BidCoS: Info: BATTERY_STATE on channel 4 of HomeMatic BidCoS peer 8 with serial number OEQ0242336 was set to 0x0B.
01/24/18 17:24:16.468 Module HomeMatic BidCoS: Info: BOOST_STATE on channel 4 of HomeMatic BidCoS peer 8 with serial number OEQ0242336 was set to 0x00.
01/24/18 17:24:16.468 Module HomeMatic BidCoS: Info: CONTROL_MODE on channel 4 of HomeMatic BidCoS peer 8 with serial number OEQ0242336 was set to 0x00.
01/24/18 17:24:16.468 Module HomeMatic BidCoS: Info: FAULT_REPORTING on channel 4 of HomeMatic BidCoS peer 8 with serial number OEQ0242336 was set to 0x00.
01/24/18 17:24:16.503 Module HomeMatic BidCoS: Info: PARTY_START_TIME on channel 4 of HomeMatic BidCoS peer 8 with serial number OEQ0242336 was set to 0x00.
01/24/18 17:24:16.503 Module HomeMatic BidCoS: Info: VALVE_STATE on channel 4 of HomeMatic BidCoS peer 8 with serial number OEQ0242336 was set to 0x41.
01/24/18 17:24:17.444 HomeMatic BidCoS packet received (My-HM-MOD-RPI-PCB, RSSI: -48 dBm): 0F2A861051A00C0000000A88B20A0040
01/24/18 17:24:17.445 Module HomeMatic BidCoS: Info: ACTUAL_TEMPERATURE on channel 4 of HomeMatic BidCoS peer 2 with serial number NEQ1489987 was set to 0x00B2.
01/24/18 17:24:17.445 Module HomeMatic BidCoS: Info: BATTERY_STATE on channel 4 of HomeMatic BidCoS peer 2 with serial number NEQ1489987 was set to 0x0A.
01/24/18 17:24:17.445 Module HomeMatic BidCoS: Info: BOOST_STATE on channel 4 of HomeMatic BidCoS peer 2 with serial number NEQ1489987 was set to 0x00.
01/24/18 17:24:17.445 Module HomeMatic BidCoS: Info: CONTROL_MODE on channel 4 of HomeMatic BidCoS peer 2 with serial number NEQ1489987 was set to 0x01.
01/24/18 17:24:17.445 Module HomeMatic BidCoS: Info: FAULT_REPORTING on channel 4 of HomeMatic BidCoS peer 2 with serial number NEQ1489987 was set to 0x00.
01/24/18 17:24:17.469 Module HomeMatic BidCoS: Info: PARTY_START_TIME on channel 4 of HomeMatic BidCoS peer 2 with serial number NEQ1489987 was set to 0x00.
01/24/18 17:24:17.469 Module HomeMatic BidCoS: Info: SET_TEMPERATURE on channel 4 of HomeMatic BidCoS peer 2 with serial number NEQ1489987 was set to 0x22.
01/24/18 17:24:17.469 Module HomeMatic BidCoS: Info: VALVE_STATE on channel 4 of HomeMatic BidCoS peer 2 with serial number NEQ1489987 was set to 0x00.
01/24/18 17:24:28.002 HomeMatic BidCoS packet received (My-HM-MOD-RPI-PCB, RSSI: -46 dBm): 0F1A861051A9B70000000A88A90D1740
...
..
.
01/24/18 17:32:26.421 Module HomeMatic BidCoS: Info: ACTUAL_TEMPERATURE on channel 4 of HomeMatic BidCoS peer 1 with serial number NEQ1489970 was set to 0x00AB.
01/24/18 17:32:26.421 Module HomeMatic BidCoS: Info: BATTERY_STATE on channel 4 of HomeMatic BidCoS peer 1 with serial number NEQ1489970 was set to 0x0A.
01/24/18 17:32:26.422 Module HomeMatic BidCoS: Info: BOOST_STATE on channel 4 of HomeMatic BidCoS peer 1 with serial number NEQ1489970 was set to 0x00.
01/24/18 17:32:26.422 Module HomeMatic BidCoS: Info: CONTROL_MODE on channel 4 of HomeMatic BidCoS peer 1 with serial number NEQ1489970 was set to 0x00.
01/24/18 17:32:26.422 Module HomeMatic BidCoS: Info: FAULT_REPORTING on channel 4 of HomeMatic BidCoS peer 1 with serial number NEQ1489970 was set to 0x00.
01/24/18 17:32:26.422 Module HomeMatic BidCoS: Info: PARTY_START_TIME on channel 4 of HomeMatic BidCoS peer 1 with serial number NEQ1489970 was set to 0x00.
01/24/18 17:32:26.422 Module HomeMatic BidCoS: Info: SET_TEMPERATURE on channel 4 of HomeMatic BidCoS peer 1 with serial number NEQ1489970 was set to 0x22.
01/24/18 17:32:26.422 Module HomeMatic BidCoS: Info: VALVE_STATE on channel 4 of HomeMatic BidCoS peer 1 with serial number NEQ1489970 was set to 0x07.
01/24/18 17:32:43.693 RPC Server (Port 2001): Info: Connection from ::ffff:127.0.0.1:50956 accepted. Client number: 13
01/24/18 17:32:43.693 RPC Server (Port 2001): Info: RPC server client id for client number 13 is: 0
01/24/18 17:32:43.695 RPC Server (Port 2001): Info: Client number 13 is calling RPC method: getDeviceDescription (1) Parameters:
(String) BidCoS-RF
01/24/18 17:32:43.760 RPC Server (Port 2001): Info: Connection from ::ffff:127.0.0.1:50960 accepted. Client number: 14
01/24/18 17:32:43.761 RPC Server (Port 2001): Info: RPC server client id for client number 14 is: 1
01/24/18 17:32:43.765 RPC Server (Port 2001): Info: Client number 14 is calling RPC method: listBidcosInterfaces (1) Parameters:
01/24/18 17:32:44.092 RPC Server (Port 2001): Info: Connection from ::ffff:127.0.0.1:50982 accepted. Client number: 15
01/24/18 17:32:44.092 RPC Server (Port 2001): Info: RPC server client id for client number 15 is: 2
01/24/18 17:32:44.094 RPC Server (Port 2001): Info: Client number 15 is calling RPC method: init (2) Parameters:
(String) binary://10.10.203.2:9126
(String) RF-618eedaa
01/24/18 17:32:44.094 Info: Client with IP ::ffff:127.0.0.1 is calling "init".
01/24/18 17:32:44.095 Info: Adding server "binary://10.10.203.2".
01/24/18 17:32:44.095 Info: Calling init methods on server "binary://10.10.203.2".
01/24/18 17:32:44.107 RPC Server (Port 2001): Info: Connection from ::ffff:127.0.0.1:50984 accepted. Client number: 16
01/24/18 17:32:44.107 RPC Server (Port 2001): Info: RPC server client id for client number 16 is: 3
01/24/18 17:32:44.108 RPC Server (Port 2001): Info: Client number 16 is calling RPC method: listDevices (2) Parameters:
01/24/18 17:32:44.235 RPC Server (Port 2001): Info: Client number 16 is calling RPC method: getDeviceInfo (2) Parameters:
01/24/18 17:32:44.299 RPC Server (Port 2001): Info: Client number 16 is calling RPC method: getParamsetDescription (2) Parameters:
(String) NEQ0389308:0
(String) MASTER
01/24/18 17:32:44.314 RPC Server (Port 2001): Info: Client number 16 is calling RPC method: getParamsetDescription (2) Parameters:
(String) NEQ0389308:0
(String) VALUES
01/24/18 17:32:44.320 RPC Server (Port 2001): Info: Client number 16 is calling RPC method: getParamsetDescription (2) Parameters:
(String) NEQ0389308:1
(String) MASTER
...
..
.
01/24/18 17:32:45.283 RPC Server (Port 2001): Info: Client number 16 is calling RPC method: getParamsetDescription (2) Parameters:
(String) OEQ0473427:1
(String) VALUES
01/24/18 17:32:45.299 RPC Server (Port 2001): Info: Client number 16 is calling RPC method: getAllSystemVariables (2) Parameters:
01/24/18 17:32:45.314 RPC Server (Port 2001): Info: Client number 16 is calling RPC method: getAllScripts (2) Parameters:
01/24/18 17:32:45.457 RPC Server (Port 2001): Info: Client number 16 is calling RPC method: getParamset (2) Parameters:
(String) OEQ0242339:0
(String) MASTER
01/24/18 17:32:45.483 RPC Server (Port 2001): Info: Client number 16 is calling RPC method: getParamset (2) Parameters:
(String) OEQ0242336:0
(String) MASTER
01/24/18 17:32:45.491 RPC Server (Port 2001): Info: Client number 16 is calling RPC method: getParamset (2) Parameters:
(String) NEQ0389308:0
(String) MASTER
01/24/18 17:32:45.495 RPC Server (Port 2001): Info: Client number 16 is calling RPC method: getParamset (2) Parameters:
...
..
.
01/24/18 17:32:47.051 RPC Server (Port 2001): Info: Client number 16 is calling RPC method: getParamset (2) Parameters:
(String) NEQ1489977:0
(String) VALUES
01/24/18 17:32:47.075 HomeMatic BidCoS packet received (My-HM-MOD-RPI-PCB, RSSI: -48 dBm): 0F4C861051A9850000000A88AB0D0640
01/24/18 17:32:47.076 Module HomeMatic BidCoS: Info: ACTUAL_TEMPERATURE on channel 4 of HomeMatic BidCoS peer 5 with serial number NEQ1488399 was set to 0x00AB.
01/24/18 17:32:47.077 Module HomeMatic BidCoS: Info: BATTERY_STATE on channel 4 of HomeMatic BidCoS peer 5 with serial number NEQ1488399 was set to 0x0D.
01/24/18 17:32:47.077 Module HomeMatic BidCoS: Info: BOOST_STATE on channel 4 of HomeMatic BidCoS peer 5 with serial number NEQ1488399 was set to 0x00.
01/24/18 17:32:47.077 Module HomeMatic BidCoS: Info: CONTROL_MODE on channel 4 of HomeMatic BidCoS peer 5 with serial number NEQ1488399 was set to 0x01.
01/24/18 17:32:47.077 Module HomeMatic BidCoS: Info: FAULT_REPORTING on channel 4 of HomeMatic BidCoS peer 5 with serial number NEQ1488399 was set to 0x00.
01/24/18 17:32:47.077 Module HomeMatic BidCoS: Info: PARTY_START_TIME on channel 4 of HomeMatic BidCoS peer 5 with serial number NEQ1488399 was set to 0x00.
01/24/18 17:32:47.077 Module HomeMatic BidCoS: Info: SET_TEMPERATURE on channel 4 of HomeMatic BidCoS peer 5 with serial number NEQ1488399 was set to 0x22.
01/24/18 17:32:47.077 Module HomeMatic BidCoS: Info: VALVE_STATE on channel 4 of HomeMatic BidCoS peer 5 with serial number NEQ1488399 was set to 0x06.
01/24/18 17:32:47.096 RPC Server (Port 2001): Info: Client number 16 is calling RPC method: getParamset (2) Parameters:
(String) NEQ1489977:1
(String) MASTER
01/24/18 17:32:47.099 RPC Server (Port 2001): Info: Client number 16 is calling RPC method: getParamset (2) Parameters:
(String) NEQ1489977:1
(String) VALUES
01/24/18 17:32:47.103 RPC Server (Port 2001): Info: Client number 16 is calling RPC method: getParamset (2) Parameters:
(String) NEQ1489977:2
(String) MASTER
...
..
.
01/24/18 17:32:49.511 RPC Server (Port 2001): Info: Client number 16 is calling RPC method: getParamset (2) Parameters:
(String) NEQ1489987:6
(String) MASTER
01/24/18 17:32:49.515 RPC Server (Port 2001): Info: Client number 16 is calling RPC method: getParamset (2) Parameters:
(String) NEQ1489987:6
(String) VALUES
01/24/18 17:32:55.679 RPC Server (Port 2001): Info: Client number 16 is calling RPC method: setValue (2) Parameters:
(String) OEQ0243032:4
(String) MANU_MODE
(Float) 15
01/24/18 17:32:57.032 HomeMatic BidCoS packet received (My-HM-MOD-RPI-PCB, RSSI: -63 dBm): 0FE98610567C040000000A90AD0B2000
01/24/18 17:32:57.033 Module HomeMatic BidCoS: Info: ACTUAL_TEMPERATURE on channel 4 of HomeMatic BidCoS peer 11 with serial number OEQ0242342 was set to 0x00AD.
01/24/18 17:32:57.033 Module HomeMatic BidCoS: Info: BATTERY_STATE on channel 4 of HomeMatic BidCoS peer 11 with serial number OEQ0242342 was set to 0x0B.
01/24/18 17:32:57.033 Module HomeMatic BidCoS: Info: BOOST_STATE on channel 4 of HomeMatic BidCoS peer 11 with serial number OEQ0242342 was set to 0x00.
01/24/18 17:32:57.033 Module HomeMatic BidCoS: Info: CONTROL_MODE on channel 4 of HomeMatic BidCoS peer 11 with serial number OEQ0242342 was set to 0x00.
01/24/18 17:32:57.033 Module HomeMatic BidCoS: Info: FAULT_REPORTING on channel 4 of HomeMatic BidCoS peer 11 with serial number OEQ0242342 was set to 0x00.
01/24/18 17:32:57.034 Module HomeMatic BidCoS: Info: PARTY_START_TIME on channel 4 of HomeMatic BidCoS peer 11 with serial number OEQ0242342 was set to 0x00.
01/24/18 17:32:57.034 Module HomeMatic BidCoS: Info: VALVE_STATE on channel 4 of HomeMatic BidCoS peer 11 with serial number OEQ0242342 was set to 0x20.
01/24/18 17:32:58.255 RPC Server (Port 2001): Info: Connection from ::ffff:127.0.0.1:51240 accepted. Client number: 25
01/24/18 17:32:58.255 RPC Server (Port 2001): Info: RPC server client id for client number 25 is: 4
01/24/18 17:32:58.256 RPC Server (Port 2001): Info: Client number 25 is calling RPC method: setValue (2) Parameters:
(String) OEQ0243032:4
(String) MANU_MODE
(Float) 15
01/24/18 17:33:00.843 RPC Server (Port 2001): Info: Client number 25 is calling RPC method: setValue (2) Parameters:
(String) OEQ0242336:4
(String) MANU_MODE
(Float) 15
01/24/18 17:33:01.392 Module HomeMatic BidCoS: Info: Setting peer to unreachable, because the queue processing was interrupted.
01/24/18 17:33:01.392 Module HomeMatic BidCoS: Info: Queue is not finished (peer: 7). Retrying...
01/24/18 17:33:03.414 RPC Server (Port 2001): Info: Connection from ::ffff:127.0.0.1:51290 accepted. Client number: 26
01/24/18 17:33:03.414 RPC Server (Port 2001): Info: RPC server client id for client number 26 is: 5
01/24/18 17:33:03.415 RPC Server (Port 2001): Info: Client number 26 is calling RPC method: setValue (2) Parameters:
(String) OEQ0242336:4
(String) MANU_MODE
(Float) 15
01/24/18 17:33:04.399 Module HomeMatic BidCoS: Info: Setting peer to unreachable, because the queue processing was interrupted.
01/24/18 17:33:04.399 Module HomeMatic BidCoS: Info: Queue is not finished (peer: 7). Retrying...
01/24/18 17:33:05.988 RPC Server (Port 2001): Info: Client number 26 is calling RPC method: setValue (2) Parameters:
(String) OEQ0242338:4
(String) MANU_MODE
(Float) 15
01/24/18 17:33:06.503 Module HomeMatic BidCoS: Info: Setting peer to unreachable, because the queue processing was interrupted.
01/24/18 17:33:06.504 Module HomeMatic BidCoS: Info: Queue is not finished (peer: 8). Retrying...
01/24/18 17:33:07.606 Module HomeMatic BidCoS: Info: Setting peer to unreachable, because the queue processing was interrupted.
01/24/18 17:33:07.606 Module HomeMatic BidCoS: Info: Queue is not finished (peer: 7). Retrying...
01/24/18 17:33:08.553 RPC Server (Port 2001): Info: Connection from ::ffff:127.0.0.1:51340 accepted. Client number: 27
01/24/18 17:33:08.554 RPC Server (Port 2001): Info: RPC server client id for client number 27 is: 6
01/24/18 17:33:08.554 RPC Server (Port 2001): Info: Client number 27 is calling RPC method: setValue (2) Parameters:
(String) OEQ0242338:4
(String) MANU_MODE
(Float) 15
...
..
.

Is homegear and openhab running on the same machine?

Try to shotddown homegear and openhab and the start homegear and the openhab

Yes, Homegear and OpenHAB (Openhabian) is running on the same machine.

Tried everything, rebooting the entire machine, stop/start Homegear and OpenHAB.

Enter the correct Network Callback Address in the Homematic Bridge.

If you are not sure which one, show the output of ifconfig. 127.0.0.1 may work, but i am not sure, if openHAB is listening on loopback.

Hi,

From the beginning I had set the Gateway Address for the Homatic Bridge Binding in PaperUI to “localhost”.
I also set the IP to 127.0.0.1 and changed the Gateway type from Auto to CCU (read this in a different post) but with no luck.

ifconfig

[19:24:39] openhabian@pi-openhab:~$ ifconfig
eth0      Link encap:Ethernet  HWaddr b8:27:eb:14:47:13
          inet addr:10.10.203.2  Bcast:10.10.203.255  Mask:255.255.255.0
          inet6 addr: fe80::2fad:d738:ee06:5e2c/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:381750 errors:0 dropped:2478 overruns:0 frame:0
          TX packets:360759 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:64005239 (61.0 MiB)  TX bytes:90588949 (86.3 MiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:41648 errors:0 dropped:0 overruns:0 frame:0
          TX packets:41648 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1
          RX bytes:4549277 (4.3 MiB)  TX bytes:4549277 (4.3 MiB)

Try 10.10.203.2

Same thing, no luck…

The weird thing is if I change something on the aktor on the radiator lowering or raising for example the temperature.
Its visible in the basicUI… But for some reason the other way around isn’t working.

2018-01-24 20:05:09.944 [vent.ItemStateChangedEvent] - DG_Heizung_Buero_Empfang changed from -53 to -54
2018-01-24 20:05:10.021 [vent.ItemStateChangedEvent] - DG_Heizung_Buero_SollTemperatur changed from 18.50 to 17.00
2018-01-24 20:05:23.028 [vent.ItemStateChangedEvent] - DG_Heizung_Buero_SollTemperatur changed from 17.00 to 18.50

I changed from the HM-MOD-RPI-PCB about 6 weeks ago, so my memory may be wrong, but i remember running firmware 1.4.x, not 1.2.1 like you do. I upgraded the firmware like described here.

I found a better link, the important part is not buried:

Hi Matthias,

I had exactly the same issue. Homegear and openHAB seem to be fine.

The problem is:

java.io.IOException: -100 No answer from device. (sending setValue()
OEQ0243032:4
MANU_MODE
15.0

So this means the RSSI is very very bad and therefor the commands will not passed to the device.
After adjusting the position of the PI with the HM-MOD-RPI-PCB…everything is fine.

1 Like

HI Oliver,

think it’s not related to the RSSI. I have multiple Homematic devices within the same room with the Raspberry.
Besides this Homegear showing unreach NO and changes on the devices itself are visible in Openhab.
I get the error MSG when I want to control devices via Openhab.

And in the past everything works very well, the only thing what I changed is the Version from Openhab & Homegear (updated via the openHABian Configuration Tool)

@job Do I need to save anything before updating the HM-MOD-RPI-PCB FW?
I’m using my own rfKey, which is saved anyway…

Thanks all for investigating!
Matthias

@elteide, i have no idea. I did the upgrade before i set the stuff up.

But i would guess no, because the devices are connected to homegear, not to the HM-MOD-RPI-PCB. (I switched from that HM-MOD-RPI-PCB away a few weeks ago, and did not pair anything again.)

Hi Matthias,

for me it was also after upgrading homegear and openHAB.
I had also multiple devices in the same room. One of them logs this java.io.IOException. all other where fine.
Also homegear says it´s “online”. Homegear received data information from the device, but was not able to send commands to the device until the mesage -100 No answer from device. (sending setValue() was gone.
For this i´m nearly 100% sure thats is related to higher than -100 RSSI, sending commands to the device.

Hi all,

I updated to the 1.4.1 FW on the HM-MOD-RPI-PCB.
But still get the java.io.Excepion when I want to control via OpenHAB.
When you look into my events.log you see that the devices are in range lower than -100 RSSI.
(Raspberry is located in DG Wohnzimmer)
But on the same time in the openhab.log you see the errors No answer from device.

What else could it be and what would you try next?

homegear.log

01/25/18 13:22:32.754 Startup complete. Waiting for physical interfaces to connect.
01/25/18 13:22:32.754 All physical interfaces are connected now.
01/25/18 13:22:32.754 Starting UPnP server...
01/25/18 13:22:32.755 Info: UPnP server: Binding to address: 10.10.203.2
01/25/18 13:22:32.756 UPnP Server: Info: Started listening.
01/25/18 13:22:35.196 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Info: Firmware version: 1.4.1
01/25/18 13:22:35.202 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Info: Serial number: NEQ1332224
01/25/18 13:22:35.217 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Info: Init queue completed. Sending peers...
01/25/18 13:22:35.584 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Info: Peer sending completed.
01/25/18 13:22:37.293 HomeMatic BidCoS packet received (My-HM-MOD-RPI-PCB, RSSI: -52 dBm): 0FB08610567BFE0000000A88AF0B0000
01/25/18 13:22:37.294 Module HomeMatic BidCoS: Info: ACTUAL_TEMPERATURE on channel 4 of HomeMatic BidCoS peer 8 with serial number OEQ0242336 was set to 0x00AF.
01/25/18 13:22:37.294 Module HomeMatic BidCoS: Info: BATTERY_STATE on channel 4 of HomeMatic BidCoS peer 8 with serial number OEQ0242336 was set to 0x0B.
01/25/18 13:22:37.294 Module HomeMatic BidCoS: Info: BOOST_STATE on channel 4 of HomeMatic BidCoS peer 8 with serial number OEQ0242336 was set to 0x00.
01/25/18 13:22:37.294 Module HomeMatic BidCoS: Info: CONTROL_MODE on channel 4 of HomeMatic BidCoS peer 8 with serial number OEQ0242336 was set to 0x00.
01/25/18 13:22:37.294 Module HomeMatic BidCoS: Info: FAULT_REPORTING on channel 4 of HomeMatic BidCoS peer 8 with serial number OEQ0242336 was set to 0x00.
01/25/18 13:22:37.294 Module HomeMatic BidCoS: Info: PARTY_START_TIME on channel 4 of HomeMatic BidCoS peer 8 with serial number OEQ0242336 was set to 0x00.
01/25/18 13:22:37.295 Module HomeMatic BidCoS: Info: VALVE_STATE on channel 4 of HomeMatic BidCoS peer 8 with serial number OEQ0242336 was set to 0x00.
01/25/18 13:22:42.227 HomeMatic BidCoS packet received (My-HM-MOD-RPI-PCB, RSSI: -47 dBm): 0FF6861051A9B70000000A88A90D1700

events.log

2018-01-25 13:42:10.868 [vent.ItemStateChangedEvent] - EG_Heizung_Wohnzimmer_Schreibtisch_Empfang changed from NULL to 0
2018-01-25 13:42:10.977 [vent.ItemStateChangedEvent] - KG_Heizung_Fittnessraum_Empfang changed from NULL to -62
2018-01-25 13:42:11.355 [vent.ItemStateChangedEvent] - EG_Heizung_Wohnzimmer_Esstisch_Empfang changed from NULL to -44
2018-01-25 13:42:11.462 [vent.ItemStateChangedEvent] - EG_Heizung_Wohnzimmer_Couch_Empfang changed from NULL to -45
2018-01-25 13:42:11.577 [vent.ItemStateChangedEvent] - EG_Heizung_HaWi_Empfang changed from NULL to -66
2018-01-25 13:42:12.577 [vent.ItemStateChangedEvent] - DG_Heizung_Buero_Empfang changed from NULL to -55
2018-01-25 13:42:12.585 [vent.ItemStateChangedEvent] - EG_Heizung_Bad_Empfang changed from NULL to -69
2018-01-25 13:42:12.815 [vent.ItemStateChangedEvent] - DG_Heizung_Bad_Empfang changed from NULL to 0
2018-01-25 13:42:14.512 [vent.ItemStateChangedEvent] - DG_Heizung_Wohnzimmer_Couch_Empfang changed from NULL to -48
2018-01-25 13:42:15.140 [vent.ItemStateChangedEvent] - DG_Heizung_Kueche_Empfang changed from NULL to -55
2018-01-25 13:42:15.159 [vent.ItemStateChangedEvent] - DG_Heizung_Schlafzimmer_Empfang changed from NULL to 0
2018-01-25 13:42:15.799 [vent.ItemStateChangedEvent] - DG_Heizung_Wohnzimmer_DachF_Empfang changed from NULL to 0
2018-01-25 13:42:43.077 [vent.ItemStateChangedEvent] - EG_Heizung_Wohnzimmer_Schreibtisch_Empfang changed from 0 to -51
2018-01-25 13:42:56.244 [vent.ItemStateChangedEvent] - DG_Heizung_Schlafzimmer_Empfang changed from 0 to -72
2018-01-25 13:42:57.494 [vent.ItemStateChangedEvent] - DG_Heizung_Bad_Empfang changed from 0 to -47
2018-01-25 13:43:03.606 [vent.ItemStateChangedEvent] - DG_Heizung_Wohnzimmer_DachF_Empfang changed from 0 to -49
2018-01-25 13:43:07.497 [vent.ItemStateChangedEvent] - EG_Heizung_HaWi_Empfang changed from -66 to -65
2018-01-25 13:44:17.757 [vent.ItemStateChangedEvent] - DG_Heizung_Buero_Empfang changed from -55 to -56
2018-01-25 13:44:17.957 [vent.ItemStateChangedEvent] - EG_Heizung_Wohnzimmer_Esstisch_Empfang changed from -44 to -45
2018-01-25 13:44:19.445 [vent.ItemStateChangedEvent] - DG_Heizung_Kueche_Empfang changed from -55 to -56
2018-01-25 13:44:28.720 [vent.ItemStateChangedEvent] - KG_Heizung_Fittnessraum_Empfang changed from -62 to -60
2018-01-25 13:45:04.009 [vent.ItemStateChangedEvent] - DG_Heizung_Wohnzimmer_Couch_Empfang changed from -48 to -47
2018-01-25 13:45:28.839 [vent.ItemStateChangedEvent] - EG_Heizung_Wohnzimmer_Schreibtisch_Empfang changed from -51 to -50
2018-01-25 13:45:45.241 [vent.ItemStateChangedEvent] - DG_Heizung_Schlafzimmer_Empfang changed from -72 to -71
2018-01-25 13:46:08.254 [vent.ItemStateChangedEvent] - EG_Heizung_HaWi_Empfang changed from -65 to -66
2018-01-25 13:46:25.450 [vent.ItemStateChangedEvent] - DG_Heizung_Kueche_Empfang changed from -56 to -55

When I switch Boost mode on (DG_Heizung_Buero_Mode_Boost)

2018-01-25 14:00:25.664 [ome.event.ItemCommandEvent] - Item 'DG_Heizung_Buero_Mode_Boost' received command ON
2018-01-25 14:00:25.696 [GroupItemStateChangedEvent] - DG_Heizung_Mode_Boost changed from OFF to ON through DG_Heizung_Buero_Mode_Boost
2018-01-25 14:00:25.703 [vent.ItemStateChangedEvent] - DG_Heizung_Buero_Mode_Boost changed from NULL to ON
==> /var/log/openhab2/openhab.log <==
2018-01-25 14:00:30.859 [ERROR] [ematic.handler.HomematicThingHandler] - -100 No answer from device. (sending setValue()
NEQ1489970:4
BOOST_MODE
true
)
java.io.IOException: -100 No answer from device. (sending setValue()
NEQ1489970:4
BOOST_MODE
true
)
	at org.openhab.binding.homematic.internal.communicator.parser.RpcResponseParser.parse(RpcResponseParser.java:47) [251:org.openhab.binding.homematic:2.2.0]
	at org.openhab.binding.homematic.internal.communicator.client.BinRpcClient.sendMessage(BinRpcClient.java:78) [251:org.openhab.binding.homematic:2.2.0]
	at org.openhab.binding.homematic.internal.communicator.client.BinRpcClient.sendMessage(BinRpcClient.java:90) [251:org.openhab.binding.homematic:2.2.0]
	at org.openhab.binding.homematic.internal.communicator.client.BinRpcClient.sendMessage(BinRpcClient.java:66) [251:org.openhab.binding.homematic:2.2.0]
	at org.openhab.binding.homematic.internal.communicator.client.RpcClient.setDatapointValue(RpcClient.java:293) [251:org.openhab.binding.homematic:2.2.0]
	at org.openhab.binding.homematic.internal.communicator.AbstractHomematicGateway$1.execute(AbstractHomematicGateway.java:571) [251:org.openhab.binding.homematic:2.2.0]
	at org.openhab.binding.homematic.internal.misc.DelayedExecuter.start(DelayedExecuter.java:61) [251:org.openhab.binding.homematic:2.2.0]
	at org.openhab.binding.homematic.internal.communicator.AbstractHomematicGateway.sendDatapoint(AbstractHomematicGateway.java:550) [251:org.openhab.binding.homematic:2.2.0]
	at org.openhab.binding.homematic.internal.communicator.AbstractHomematicGateway.sendDatapoint(AbstractHomematicGateway.java:529) [251:org.openhab.binding.homematic:2.2.0]
	at org.openhab.binding.homematic.handler.HomematicThingHandler.handleCommand(HomematicThingHandler.java:175) [251:org.openhab.binding.homematic:2.2.0]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:?]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
	at java.lang.reflect.Method.invoke(Method.java:498) ~[?:?]
	at org.eclipse.smarthome.core.internal.common.AbstractInvocationHandler.invokeDirect(AbstractInvocationHandler.java:153) [109:org.eclipse.smarthome.core:0.10.0.b1]
	at org.eclipse.smarthome.core.internal.common.InvocationHandlerSync.invoke(InvocationHandlerSync.java:59) [109:org.eclipse.smarthome.core:0.10.0.b1]
	at com.sun.proxy.$Proxy154.handleCommand(Unknown Source) [251:org.openhab.binding.homematic:2.2.0]
	at org.eclipse.smarthome.core.thing.internal.profiles.ProfileCallbackImpl.handleCommand(ProfileCallbackImpl.java:72) [116:org.eclipse.smarthome.core.thing:0.10.0.b1]
	at org.eclipse.smarthome.core.thing.internal.profiles.SystemDefaultProfile.onCommandFromItem(SystemDefaultProfile.java:49) [116:org.eclipse.smarthome.core.thing:0.10.0.b1]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:?]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
	at java.lang.reflect.Method.invoke(Method.java:498) ~[?:?]
	at org.eclipse.smarthome.core.internal.common.AbstractInvocationHandler.invokeDirect(AbstractInvocationHandler.java:153) [109:org.eclipse.smarthome.core:0.10.0.b1]
	at org.eclipse.smarthome.core.internal.common.Invocation.call(Invocation.java:53) [109:org.eclipse.smarthome.core:0.10.0.b1]
	at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
	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) [?:?]
==> /var/log/openhab2/events.log <==
2018-01-25 14:00:40.674 [hingStatusInfoChangedEvent] - 'homematic:HG-HM-CC-RT-DN:618eedaa:NEQ1489970' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR)
2018-01-25 14:00:40.695 [vent.ItemStateChangedEvent] - DG_Heizung_Buero_keinEmpfang changed from 0 to 1
2018-01-25 14:00:40.699 [GroupItemStateChangedEvent] - Homematic_Unreached changed from 0 to 1 through DG_Heizung_Buero_keinEmpfang
2018-01-25 14:00:43.445 [GroupItemStateChangedEvent] - Homematic_Unreached changed from 1 to 0 through DG_Heizung_Buero_keinEmpfang
2018-01-25 14:00:43.451 [vent.ItemStateChangedEvent] - DG_Heizung_Buero_keinEmpfang changed from 1 to 0
2018-01-25 14:00:43.579 [me.event.ThingUpdatedEvent] - Thing 'homematic:HG-HM-CC-RT-DN:618eedaa:NEQ1489970' has been updated.
2018-01-25 14:00:43.587 [ome.event.ItemCommandEvent] - Item 'DG_Heizung_Buero_Mode_Boost' received command OFF
==> /var/log/openhab2/openhab.log <==
2018-01-25 14:00:43.592 [WARN ] [ommunicator.AbstractHomematicGateway] - Datapoint of type ACTION cannot be set to false, it is not published to the gateway with id '618eedaa': 'NEQ1489970:4#BOOST_MODE'
==> /var/log/openhab2/events.log <==
2018-01-25 14:00:43.597 [vent.ItemStateChangedEvent] - DG_Heizung_Buero_Mode_Boost changed from ON to OFF
2018-01-25 14:00:43.601 [GroupItemStateChangedEvent] - DG_Heizung_Mode_Boost changed from ON to OFF through DG_Heizung_Buero_Mode_Boost

Maybe it is also this:

Will be fixed in the next hours.

1 Like

Hi all,

thanks all for your support, the issue is fixed after upgrading Homegear ot version 0.7.15-1575.

Thanks,

Matthias