my Homematic items used to be connected to Openhab through Homegear. Lately I bought a real CCU2 and started to transfer the devices to the CCU which I also configured as a bridge in OH (homegear is still in use for some items). But now I have the problem that some, but not all of my Thermostats(connected to CCU) cannot be controlled by Openhab. But from the CCU’s command interface all Thermostats work fine and can be completely controlled. After pairing the Thermostats immediately show up in Openhab’s inbox. After configuration the thing is visible in the devices list, but an error(404) occurs and no channels are visible. The log output shows the following error (please see full trace output below):
e.g.: Channel not found for datapoint 'NEQ1230845:4#ACTUAL_TEMPERATURE’
I need to point out that for one Thermostat everything works fine. I checked the complete config of the Items in CCU2 and Openhab for any meaningful difference. Nothing. I also removed all items and links using the karaf console. I removed the thing from openhab, unpaired it from the CCU and paired it again. I also restarted the OH service after every change. Nothing. I am running OH version 2.1.0-1. Other things like rollershutter work fine. Those were never connected to OH though homegear.
Could the problem be related to the fact, that the Thermostats were already paired and connected to OH through homegear?
Does anyone have an idea what could be the problem?
Thanks in advance for your support!
23:18:23.553 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Double) value ‘23.3’ for ‘NEQ1230845:4#ACTUAL_TEMPERATURE’ from gateway with id '0b259674’
23:18:23.555 [WARN ] [ematic.handler.HomematicThingHandler] - Channel not found for datapoint 'NEQ1230845:4#ACTUAL_TEMPERATURE’
23:18:23.559 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Double) value ‘2.6’ for ‘NEQ1230845:4#BATTERY_STATE’ from gateway with id '0b259674’
23:18:23.562 [WARN ] [ematic.handler.HomematicThingHandler] - Channel not found for datapoint 'NEQ1230845:4#BATTERY_STATE’
23:18:23.564 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Integer) value ‘0’ for ‘NEQ1230845:4#BOOST_STATE’ from gateway with id '0b259674’
23:18:23.567 [WARN ] [ematic.handler.HomematicThingHandler] - Channel not found for datapoint 'NEQ1230845:4#BOOST_STATE’
23:18:23.569 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Integer) value ‘1’ for ‘NEQ1230845:4#CONTROL_MODE’ from gateway with id '0b259674’
23:18:23.573 [WARN ] [ematic.handler.HomematicThingHandler] - Channel not found for datapoint 'NEQ1230845:4#CONTROL_MODE’
23:18:23.575 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Integer) value ‘0’ for ‘NEQ1230845:4#FAULT_REPORTING’ from gateway with id '0b259674’
23:18:23.578 [WARN ] [ematic.handler.HomematicThingHandler] - Channel not found for datapoint 'NEQ1230845:4#FAULT_REPORTING’
23:18:23.580 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Integer) value ‘0’ for ‘NEQ1230845:4#PARTY_START_TIME’ from gateway with id '0b259674’
23:18:23.582 [WARN ] [ematic.handler.HomematicThingHandler] - Channel not found for datapoint 'NEQ1230845:4#PARTY_START_TIME’
23:18:23.584 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Double) value ‘4.5’ for ‘NEQ1230845:4#SET_TEMPERATURE’ from gateway with id '0b259674’
23:18:23.586 [WARN ] [ematic.handler.HomematicThingHandler] - Channel not found for datapoint 'NEQ1230845:4#SET_TEMPERATURE’
23:18:23.588 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Integer) value ‘0’ for ‘NEQ1230845:4#VALVE_STATE’ from gateway with id '0b259674’
23:18:23.590 [WARN ] [ematic.handler.HomematicThingHandler] - Channel not found for datapoint 'NEQ1230845:4#VALVE_STATE’
23:18:25.666 [TRACE] [nal.communicator.client.BinRpcClient] - Client BinRpcRequest:
Unfortunately no solution from me. Just wanted to weigh in saying that I have the same issue. Paired with Homegear my devices worked fine, via CCU2 the devices show up as Things but the items for the different channels are never updated and cannot be modified from OpenHAB.
If you haven’t done it yet you should update the CCU to the latest firmware. Then check the firewall settings in the CCU and disable the firewall.
If the machine where you are running OH has more than one IP address you should configure the correct IP address in the binding configuration in Paper UI. If you have used it with Homegear before you may also set the mode in the binding config explicitly to CCU.
You can also try to install a 2.2 snapshot, because there have been a lot of improvements since 2.1.
If nothing helps we will need a log output with trace mode enabled for the Homematic binding.
The CCU has running the latest firmware (2.29.23) and the firewall is set to “full access” for both “HomeMatic XML-RPC API” and “Remote HomeMatic-Script API”. As far as I can tell there is no option for actually disabling the firewall.
After moving the devices from Homegear to CCU2, I uninstalled and reinstalled the Homematic binding completely. CCU is set explicitly in the binding settings.
When installing the latest 2.2 snapshot from the APT repository (upgrading over the 2.1 release), OpenHAB refused to start. Without doing any further investigation, I reverted back to 2.1.
Could you give me a hint on which logs you need and how to gather them? I’d be happy to provide them.
Below is a screenshot of the error message I see in the Paper UI when accessing the Homematic Things:
If you see immediately the error 404 then maybe you stored configuration is damaged. But this means that openhab.log should already show some error message. Can you check it?
I don’t know exactly where the configuration information are stored when using installation via apt. There should be a directory named jsondb that contains the Paper UI config and also backups of the config.
To enable the trace mode for the Homematic binding you must log in to the Karaf console and then enter the following command: log:set DEBUG org.openhab.binding.homematic
Hi,
i have exactly the same problem. In json.db the channel “array” is empty. I update to 2.2, but nothing changed. openhab.log shows no errors or warnings regarding this problem.
Regards,
Seppy
Hey Gabriel, I can report that I solved my issue. It was related to the
fact that I am using homegear alongside homegear. Homegear is integrated
into openhab through a CCU emulation and it was using the same ports as my
real CCU2 to communicate with openhab. This produced a communication mess.
It was more or less random if a message was delivered correctly or not. So
it is very important if using homegear and a CCU at the same time to
configure them on different ports. This can be done in the homegear
configuration files and needs to be adapted accordingly in the advanced
bridge settings in OH. I am currently not at home so I can’t point you to
the exact files. Please let me know whether you succeeded.
Hi,
i activated tracelogging (after changed RF Port). I tried to add an new device from the occu. Here’s the output:
2017-11-30 21:18:42.875 [DEBUG] [ommunicator.AbstractHomematicGateway] - Loading values for channel HmChannel[number=0,type=MAINTENANCE,initialized=false] of device 'MEQ0676866'
MEQ0676866:0
MEQ0676866:0
2017-11-30 21:18:42.960 [DEBUG] [ematic.handler.HomematicThingHandler] - Initializing thing 'homematic:HM-LC-Bl1PBU-FM:86778610:MEQ0676866' from gateway '86778610'
2017-11-30 21:18:42.976 [DEBUG] [ommunicator.AbstractHomematicGateway] - Loading values for channel HmChannel[number=1,type=BLIND,initialized=false] of device 'MEQ0676866'
MEQ0676866:1
MEQ0676866:1
MEQ0676866:1
2017-11-30 21:18:43.177 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Double) value '0.0' for 'MEQ0676866:1#LEVEL' from gateway with id '86778610'
2017-11-30 21:18:43.183 [WARN ] [ematic.handler.HomematicThingHandler] - Channel not found for datapoint 'MEQ0676866:1#LEVEL'
MEQ0676866:1
MEQ0676866:1
2017-11-30 21:18:43.203 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Boolean) value 'false' for 'MEQ0676866:1#WORKING' from gateway with id '86778610'
2017-11-30 21:18:43.211 [WARN ] [ematic.handler.HomematicThingHandler] - Channel not found for datapoint 'MEQ0676866:1#WORKING'
2017-11-30 21:18:43.216 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Integer) value '0' for 'MEQ0676866:1#DIRECTION' from gateway with id '86778610'
2017-11-30 21:18:43.223 [WARN ] [ematic.handler.HomematicThingHandler] - Channel not found for datapoint 'MEQ0676866:1#DIRECTION'
Sorry for the late reply. The 404 error was fixed by an upgrade to OpenHAB
2.2. I have to admit that the other issue (inability to update channels)
was a layer 8 issue - when moving from HomeGear to CCU2 I missed the
changed channel nomenclature.
Thanks for your support and apologies for wasting your time
