Hi,
I just would like to mention that I have exact the same warnings in my logs since I have updated to the stable version of OH 2.1:
2017-08-04 19:50:49.062 [WARN ] [ematic.handler.HomematicThingHandler] - Channel not found for datapoint āLEQ1189529:0#RSSIā
2017-08-04 19:50:49.064 [WARN ] [ematic.handler.HomematicThingHandler] - Channel not found for datapoint āLEQ1189529:0#SIGNAL_STRENGTHā
My system:
A Pi3 with homegear and OP 2.1 stable and with mainly Homematic-devices
My systems seems to work though without any problems, so this is no blocking issue, still I would be glad to correct it and get rid of these warnings.
However, to be honest - at the moment I do not dare to remove the thing for the following reasons:
it happened already twice that - when I tried to remove things or items via PaperUi - that I could not fully remove them, and they remained sometimes as a kind of āghostedā (grey) item, which caused a ā404 not found errorā whenever I tried to remove it.
and the mentioned item is part of a group, I have tagged it with some ImperiHome-tags and I have mentioned in in some rules -> so I do not kn ow what will have if I try to remove it
-> for the moment I do not dare to try to remove it.
Nevertheless - thank you for the advice. I guess I will try it after I have made a full backup - and I will post then if it has worked.
Yesterday I updated to 2.1 stable (as previously I used some old snapshot of a pre-2.1 release) and this same problem occured again.
I have everything configured in *.things and *.items files and removed all Homematic-specific items and things, restarted it once without all items, stopped it, added the configuration files again and restarted OpenHAB and now it works again.
I have found a solution, or better the root of the problem. At least in my special case.
I had several rules, which were iterating through groups checking states, sending messages, playing sounds, etc. Due to my lazyness, i triggered the on the āchangeā of the group state, which triggered the rules also on startup, when the item states where restored. Due to the group state most likely several times.
I changed the trigger to prevent the rules from being executed on startup and afterwards the problem of the missinng channels is gone.
Stressing openHAB during startup may also be a good idea to reproduce the problem.
@gerrieg, do you need more info to reproduce the problem to find a solution? I was almost always unable to restart openHAB correctly due to that problem.
Thank you for the info! This of course explains the behavior, the error message is correct but very misleading. Iāll try to reproduce it and find a solution.
Hello, Iām also having a similar problem with the homematic binding (2.1.0) after updating to homegear 0.7.10 today. I have two window contacts but only one of them is getting updates (the problematic one has no āchannelsā data in the REST interface, the good one has). Everything is configured in files in my openHAB2 installation. Going back to homegear 0.7.9 didnāt solve the issue so Iām not sure whether this was only coincidence.
I can temporarily fix the problem by commenting out the problematic Thing and then commenting it in again. However after restarting the system the problem is back again. By setting the TRACE log level on the homematic binding I can see that homegear is actually sending the new state of the sensor but there appears no INFO nor ERROR message in the log.
After the regular RPC restart messages in the openHAB2 log I also see that only the good sensor is being updated.
Is there anything I can do? Do you need some additional information?
Hmm. Problem is back again (most likely never was gone completely :().
Not as severe as it was, but sometimes some devices donāt have all datapoints.
The devices in question are always HM-TC-IT-WM-W-EU or HM-CC-RT-DN (in my case the homegear variants of them).
If this is indeed a problematic to solve timing issue, wouldnāt it be a solution to (re)create the channels whenever that error occurs?
2017-10-24 08:56:08.512 [WARN ] [ematic.handler.HomematicThingHandler] - Channel not found for datapoint 'OEQ0300665:0#RSSI_DEVICE'
2017-10-24 08:56:08.518 [WARN ] [ematic.handler.HomematicThingHandler] - Channel not found for datapoint 'OEQ0300665:0#RSSI'
2017-10-24 08:56:08.520 [WARN ] [ematic.handler.HomematicThingHandler] - Channel not found for datapoint 'OEQ0300665:0#SIGNAL_STRENGTH'
2017-10-24 08:56:08.550 [WARN ] [ematic.handler.HomematicThingHandler] - Channel not found for datapoint 'OEQ0300665:2#ACTUAL_HUMIDITY'
2017-10-24 08:56:08.564 [WARN ] [ematic.handler.HomematicThingHandler] - Channel not found for datapoint 'OEQ0300665:2#ACTUAL_TEMPERATURE'
2017-10-24 08:56:08.565 [WARN ] [ematic.handler.HomematicThingHandler] - Channel not found for datapoint 'OEQ0300665:2#SET_TEMPERATURE'
Iām happy to provide any help to solve this issue, just ask what you need.
I tested today with some rules and events during startup, itās impossible for me to reproduce. But i found a small issue at startup, that MAY cause the warning. But i donāt know if this is exactly your problem.
So i want to ask you, if you can try the latest snapshot once this PR has been merged. If the warning still occurs, please send me a trace log again.
Sorry for this beginner question but how can I install the snapshot build of the homematic binding? I followed the instructions in the FAQs, however after restarting openHAB the old version 2.1.0 seems to be pulled in as well (it was āUninstalledā before restarting openHAB!):
My openHAB installation is still at version 2.1.0 (stable release), I only wanted to update the Homematic binding. Isnāt this possible? Would I mandatorily have to update openHAB as well? Thanks in advance.
I am not sure, but i donāt think it works. It can, but usually from release to release something changes.
Thatās exactly the reason why i migrated everything to config files (things and items). I can easily change the openHAB release. I just need to copy my files and i am done.
Currently i am waiting on the new build including the fix (merge is done, but no new build yet).
I have the āChannel not found for datapointā issue as well. I am using Homegear 0.7.12 and openhab 2.2 stable. At every other restart of openhab one or more devices have this issue. I stop homegear and openhab, restart both and it will probably be another device which will have this issue now or if Iām lucky, every device will work perfectly. Can I send any related logfiles to debug this.
There were some changes regarding data points in version 2.2 of the binding. The changes donāt affect all HM devices, but I do not remember what they were. There was a similar post here in the discussion forum with the same problem.
In Paper UI the only solution is to remove the items and add then rediscover them again.
I have all my HM devices in things files and I have reinstalled from scratch a few times lately. I donāt think that a rediscover will help, but I can try to recreate all things.
And since it will probably change on restart, I think that it is some sort of timing or whatever issue. The device which has the problem at one time will work again after a restart without any issue.