FHT Binding: Can't get my devices controlled via openhab

Hi,

i am struggling to pair my FHT Devices with openhab. Following i will list my configs, items and log information. Maybe someone can help me find my errors.

My setup:
addons:
org.openhab.binding.fht-1.11.0-SNAPSHOT.jar* org.openhab.io.transport.cul-1.7.0-SNAPSHOT.jar

configs:
fht.cfg
fht:device=serial:/dev/ttyACM0

fs20.cfg
fs20:device=serial:/dev/ttyACM0

Working fs20 Item:
Switch PowerSocket "Steckdose" ["Lighting"] {fs20="C85205"}

Not working fht items:
Number fhtSchlafzimmerDesired "Desired-Temp. [%.1f °C]" { fht="housecode=2457;datapoint=DESIRED_TEMP" } //Number fhtRoom1Desired "Desired-Temp. [%.1f °C]" { cul="TW5C2A" } Number fhtSchlafzimmerMeasured "Measured Temp. [%.1f °C]" { fht="housecode=2457;datapoint=MEASURED_TEMP" } //Number fhtRoom1Measured "Measured Temp. [%.1f °C]" { cul="TR5C2A" } Number fhtSchlafzimmerValve "Valve [%.1f %%]" { fht="housecode=2457;address=01;datapoint=VALVE" } Switch fhtSchlafzimmerBattery "Battery [%s]" { fht="housecode=2457;datapoint=BATTERY" } Contact fhtRoom1Window "Window [MAP(en.map):%s]" { fht="housecode=5C2A;address=7B;datapoint=WINDOW" }

Number test "abc" {fht="399705"}

Debug Messages:

2017-07-27 13:53:30.743 [DEBUG] [nhab.binding.fht.internal.FHTBinding] - We received probably a FHT 8b frame 2017-07-27 13:53:30.744 [DEBUG] [nhab.binding.fht.internal.FHTBinding] - Received FHT8b state for unknown device with address FD199B 2017-07-27 13:53:33.266 [DEBUG] [nhab.binding.fht.internal.FHTBinding] - Processing 0 waiting FHT temperature commands 2017-07-27 13:53:42.551 [DEBUG] [nhab.binding.fht.internal.FHTBinding] - Received FHT message 2017-07-27 13:53:42.552 [DEBUG] [nhab.binding.fht.internal.FHTBinding] - We received probably a FHT 8b frame 2017-07-27 13:53:42.553 [DEBUG] [nhab.binding.fht.internal.FHTBinding] - Received FHT8b state for unknown device with address 399705 2017-07-27 13:54:32.172 [DEBUG] [nhab.binding.fht.internal.FHTBinding] - Received FHT message 2017-07-27 13:54:32.177 [DEBUG] [nhab.binding.fht.internal.FHTBinding] - We received probably a FHT 8b frame 2017-07-27 13:54:32.178 [DEBUG] [nhab.binding.fht.internal.FHTBinding] - Received FHT8b state for unknown device with address D04989 2017-07-27 13:54:32.667 [DEBUG] [nhab.binding.fht.internal.FHTBinding] - Received FHT message 2017-07-27 13:54:32.668 [DEBUG] [nhab.binding.fht.internal.FHTBinding] - We received probably a FHT 8b frame 2017-07-27 13:54:32.669 [DEBUG] [nhab.binding.fht.internal.FHTBinding] - Received FHT8b state for unknown device with address D04989 2017-07-27 13:54:33.268 [DEBUG] [nhab.binding.fht.internal.FHTBinding] - Processing 0 waiting FHT temperature commands 2017-07-27 13:54:39.021 [DEBUG] [nhab.binding.fht.internal.FHTBinding] - Received FHT message 2017-07-27 13:54:39.023 [DEBUG] [nhab.binding.fht.internal.FHTBinding] - Received FHT report 2017-07-27 13:54:39.024 [DEBUG] [nhab.binding.fht.internal.FHTBinding] - Received valve opening of unknown actuator with address 245700

Hey,

I also have problems with FHT but you already receive something. What Kind of Cul are you using? I have a nanocul at USB port in /dev/ttyUSB0.

Second question : why Do you Add this transport addon additionally?

Regards
Marcus

Hi Marcus,

saw your thread out there already.
I guess there aren’t many of us left out there which are using fht. Atleast most of the solutions are definetly outdated and from version 1.x.

I’m using a busware v3.4 cul. I can also control my fs20 devices without a problem. I can also send messages to my fht devices, but within the next cycle the changes get reverted.

I added this addon, because i were desperate :smiley: I don’t know if you need it or not.