[SOLVED] Datapoint xxx not found on gateway yyy

Hi!

The weekend has left me completely puzzled and also frustrated.

From what I can see in my logfiles, it all started late saturday night. I had seen in my Homegear logfile, that I should not listen on my internal IP, but rather on localhost or enable SSL and authentication. Since I didn’t want to change too much, I chose the first one. Unfortunately I entered ::1, not localhost or 127.0.0.1. At that point, OH could not connect to Homegear anymore, since OH does not seem to support IPv6 at that location (or so, didn’t debug that further). I fiddled around, restarted OH and Homegear several times changing configs and stuff and got it back to work - or so I thought. Switching my light off worked just fine, so I went to bed.
In the morning I noticed, the light switch in a different room was not working. I checked OpenHAB and indeed something was wrong. I restarted everything and started checking logfiles. I saw, I had not fixed OH, because over night the log had been filling up with messages like these

2019-03-16 23:56:22.586 [INFO ] [ternal.communicator.client.RpcClient] - Interface 'HMIP' on gateway '885e9eab' not available, disabling support
2019-03-16 23:56:22.593 [INFO ] [ternal.communicator.client.RpcClient] - Interface 'CUXD' on gateway '885e9eab' not available, disabling support
2019-03-16 23:56:22.601 [INFO ] [ternal.communicator.client.RpcClient] - Interface 'GROUP' on gateway '885e9eab' not available, disabling support
2019-03-16 23:56:22.604 [INFO ] [ommunicator.AbstractHomematicGateway] - HmGatewayInfo[id=HOMEGEAR,type=Homegear,firmware=0.7.38-2757,address=VBC5976700,rf=true,wired=true,hmip=false,cuxd=false,group=false]
2019-03-16 23:56:27.763 [WARN ] [ommunicator.AbstractHomematicGateway] - Connection lost on gateway '885e9eab', cause: "No Pong received!"
2019-03-16 23:56:27.798 [INFO ] [ommunicator.AbstractHomematicGateway] - Connection resumed on gateway '885e9eab'
2019-03-16 23:56:27.825 [WARN ] [matic.handler.HomematicBridgeHandler] - Device with address 'NEQ0433748' not found on gateway '885e9eab'
2019-03-16 23:56:27.832 [WARN ] [matic.handler.HomematicBridgeHandler] - Device with address 'PEQ1189342' not found on gateway '885e9eab'

(and so forth, listing all things connected to this gateway)
I restarted Homegear and OH. This resulted in the following messages, which are the cause of my frustration

2019-03-17 06:10:48.407 [WARN ] [ematic.handler.HomematicThingHandler] - Datapoint 'PEQ1189342:4#LOWERING_MODE' not found on gateway '885e9eab'
2019-03-17 06:10:49.730 [WARN ] [ematic.handler.HomematicThingHandler] - Datapoint 'PEQ1189342:4#MANU_MODE' not found on gateway '885e9eab'
2019-03-17 06:10:49.733 [WARN ] [ematic.handler.HomematicThingHandler] - Datapoint 'PEQ1189342:4#AUTO_MODE' not found on gateway '885e9eab'
2019-03-17 06:10:49.769 [WARN ] [ematic.handler.HomematicThingHandler] - Datapoint 'PEQ1189342:4#BOOST_MODE' not found on gateway '885e9eab'
2019-03-17 06:10:49.773 [WARN ] [ematic.handler.HomematicThingHandler] - Datapoint 'PEQ1189342:4#COMFORT_MODE' not found on gateway '885e9eab'

Even tho I reverted all configuration changes I had made step by step, the message was not going away. I checked Homegear (as far as I could) and the Datapoints still exist. I tried to fix my installation for several hours, trying different ways to reset and empty caches and other things that could’ve gotten mixed up during that night - with no luck. I even unpaired all HM devices from Homegear and removed them from OH, removed the bridge, downgraded Homegear by a few versions, re-paired one of the thermostats and the datapoints are still missing. So I thought, okay, it must be a problem in my OH setup. I took a different, (almost) freshly installed Pi, installed OH 2.4.0 (the version I’ve been using since months), installed the homematic binding, added my Homegear bridge, paired the thermostat and what do I see: the same list of datapoints, that is missing half of what should be there.

Here’s where I’m puzzled. I completely wiped homegear with all files and everything (removed /etc/homegear, /var/lib/homegear /var/log/homegear), did a fresh install of OH - what else could possibly even be the cause? I am out of ideas.

What else have I tried:

  • installing all available updates
  • switching between 127.0.0.1 and a local IP for the bridge connection (which both end in the same result, so both ways kinda work at the moment)
  • checking for remains of my homematic devices in /var/lib/openhab2 after removing them in Paper UI
  • restarting the entire Pi
  • openhab-cli clean-cache
  • log:set DEBUG org.eclipse.smarthome.binding.homematic
    log:set TRACE org.eclipse.smarthome.binding.homematic.internal.communicator.AbstractHomematicGateway

As I said, I am out of ideas and I usually don’t give up easily. If there’s anything you can think of what I could look at, all ideas are welcome!

Greetings
n

I have the same issue here.
Since the last update of the homegear, the HM-CC-RT-DN does not update any longer.

Re-adding them to Paper-UI does not solve the issue (this was, what helped when updating from OH2.3 to 2.4 with the same issue).

This issue has been solved.
Some channels were not properly announced by homegear.

If you did rediscover your things with the problematic version you need to rediscover again, to get the channels. Otherwise it will magically work after installing the current version. (stable, testing and nightly have been fixed afaik.)

1 Like

Thanks for the pointer! I will check that out as soon as I get home. Since I had unpaired all devices from homegear (in preparation for a complete reinstall of everything on a different machine), unfortunately nothing will magically reappear in my setup. :wink: