I incorporated some EnOcean window handles via Homegear/HomeMatic binding into openHAB 2. Up to a certain point, this worked flawlessly, as you can read here . However, I am struggling a bit with the items definition. The issue is that the raw states for the window handles, which are coming from Home…

@george.erhan I didn’t exactly followed your idea regarding a switch, but you pushed me in the right direction. I now defined the real and the virtual device as string. I then mapped the “incorrect” raw states of the real device via rule to the “correct” ones, i.e. Undefined → CLOSED Closed → OPE…

All right, so maybe I need to go the MQTT route. Homegear is supposed to publish all states of all its connected devices to MQTT. I could then subscribe to them and see what will be published. I might do it at a later point, definitely not tonight :wink: Thanks for sharing your thoughts. It’s defin…

@MHerbst Do you mind looking at the discussion above and share your opinion whether the HomeMatic binding might be the cause of these incorrect raw states? Thanks!

Hi Andreas, I can try to help but I have no experience with Homegear. So I have to guess. As far as I understood Homegear supports Enocean devices and these devices will be handled in the same way as Homematic devices. The Homematic binding gets information about the connected devices (their types …

[image] MHerbst: In order to find out what really happens, you can enable the trace for the Homematic binding and then restart openHAB. From the trace output, we can probably see what information Homegear sends to the binding. I am not really familiar with the Karaf console and debugging. I a…

It is quite easy. You have to log on to karaf console (via ssh) oder you can use the Karaf client program: client. In the Karaf console you then enter the following command: log:set TRACE org.openhab.homematic.binding

@MHerbst I think I can’t follow you completely. Here’s what I did and I think I missed something. Log into Karaf via sudo ssh -p 8101 openhab@localhost log:set TRACE org.openhab.homematic.binding logout from Karaf and restarted OH2 via sudo service openhab2 restart logged into Karaf, again I the…

Ouch, my fault. The correct statement is log:set TRACE org.openhab.binding.homematic You can disable the trace and restore the default logging with: log:set INFO org.openhab.binding.homematic

@MHerbst OK, that seems to be working :wink: Now, here’s the output from the log when I turned my window handle full circle. 2017-09-25 20:26:27.983 [TRACE] [nicator.server.BinRpcResponseHandler] - Event BinRpcMessage: system.multicall() [ { methodName=event params= [ RF-6e230a45 EOD…

The trace shows that the value received from Homegear for the STATE is of type “Integer” and it can have 3 different values (0, 1, 2). This does not work for item type CONTACT is an enum with two different values. You can try to define the item as “Number” and try to map the numeric values.

[image] MHerbst: You can try to define the item as “Number” and try to map the numeric values. Well, now I am back again at my original question: How can I perform a raw state transformation??? I don’t understand this. Clearly, when using a “Number” item or a “Contact” item without raw state…

[SOLVED] Raw state transformation

Setup, Configuration and Use Items & Sitemaps

george.erhan (George Erhan) September 27, 2017, 7:49pm 22

It’s the proxy item design pattern! Rich’s based on Bob’s one: