OpenHab2 and FHT

i have a raspberry with cul-stick and openhab2

i installed the cul and fht binding 1.11.0_snapshot

its not working… i get the following error

2017-10-11 18:57:10.548 [ERROR] [org.apache.felix.configadmin ] - [org.osgi.service.event.EventHandler, org.osgi.service.cm.ManagedService, id=286, bundle=187/file:/usr/share/openhab2/addons/org.openhab.binding.fht-1.11.0-SNAPSHOT.jar]: Updating property device of configuration org.openhab.fht caused a problem: The device name can’t be empty
org.osgi.service.cm.ConfigurationException: device : The device name can’t be empty
at org.openhab.io.transport.cul.CULLifecycleManager.config(CULLifecycleManager.java:57)[190:org.openhab.io.transport.cul:1.11.0.201710050110]
at org.openhab.binding.fht.internal.FHTBinding.updated(FHTBinding.java:297)[187:org.openhab.binding.fht:1.11.0.201710050110]
at org.apache.felix.cm.impl.helper.ManagedServiceTracker.updated(ManagedServiceTracker.java:189)[3:org.apache.felix.configadmin:1.8.12]
at org.apache.felix.cm.impl.helper.ManagedServiceTracker.updateService(ManagedServiceTracker.java:152)[3:org.apache.felix.configadmin:1.8.12]
at org.apache.felix.cm.impl.helper.ManagedServiceTracker.provideConfiguration(ManagedServiceTracker.java:85)[3:org.apache.felix.configadmin:1.8.12]
at org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceUpdate.provide(ConfigurationManager.java:1461)[3:org.apache.felix.configadmin:1.8.12]
at org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceUpdate.run(ConfigurationManager.java:1417)[3:org.apache.felix.configadmin:1.8.12]
at org.apache.felix.cm.impl.UpdateThread.run0(UpdateThread.java:141)[3:org.apache.felix.configadmin:1.8.12]
at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:109)[3:org.apache.felix.configadmin:1.8.12]

i dont understand this… The device name can’t be empty

my fht.cfg
device=serial:/dev/ttyUSB0
baudrate=38400
housecode=1E63

i created the fht.cfg in Folder /etc/openhab2/Services
hope that is right… but at the moment i suppose that that could be the wrong folder…

has anybody a idea?

THX
Marcel

Here is my fht.cfg in /etc/openhab2/services:

fht:housecode=1234
fht:device=serial:/dev/ttyUSBcul0
fht:baudrate=38400
fht:parity=NONE

fht:time.update=true             // update time ...
fht:time.update.cron=0 0 4 * * ? // ... at night

Any OpenHAB 1 bindings used in OpenHAB 2 require their parameters to be prefixed by the binding name, in this case “fht”.

1 Like

THX now i get the following error

0:23:17.548 [DEBUG] [org.openhab.binding.fht ] - ServiceEvent REGISTERED - {org.openhab.model.item.binding.BindingConfigReader, org.openhab.binding.fht.FHTBindingProvider}={component.name=org.openhab.binding.fht.genericbindingprovider, component.id=169, service.id=285, service.bundleid=187, service.scope=bundle} - org.openhab.binding.fht
10:23:17.668 [WARN ] [io.transport.cul.CULLifecycleManager] - CUL config is NULL, doing nothing
10:23:17.671 [DEBUG] [org.openhab.binding.fht ] - ServiceEvent REGISTERED - {org.osgi.service.event.EventHandler, org.osgi.service.cm.ManagedService}={event.topics=openhab/command/*, service.pid=org.openhab.fht, component.name=org.openhab.binding.fht.binding, component.id=168, service.id=287, service.bundleid=187, service.scope=bundle} - org.openhab.binding.fht
10:23:17.693 [INFO ] [ternal.serial.CULSerialConfigFactory] - Update config, baudrate = 38400
10:23:17.695 [INFO ] [ternal.serial.CULSerialConfigFactory] - Update config, parity = NONE (0)
10:23:17.870 [WARN ] [io.transport.cul.CULLifecycleManager] - Can’t open CUL
org.openhab.io.transport.cul.CULDeviceException: gnu.io.NoSuchPortException
at org.openhab.io.transport.cul.internal.serial.CULSerialHandlerImpl.openHardware(CULSerialHandlerImpl.java:110)[190:org.openhab.io.transport.cul:1.11.0.201710050110]
at org.openhab.io.transport.cul.internal.AbstractCULHandler.open(AbstractCULHandler.java:133)[190:org.openhab.io.transport.cul:1.11.0.201710050110]
at org.openhab.io.transport.cul.internal.CULManager.createNewHandler(CULManager.java:149)[190:org.openhab.io.transport.cul:1.11.0.201710050110]
at org.openhab.io.transport.cul.internal.CULManager.getOpenCULHandler(CULManager.java:84)[190:org.openhab.io.transport.cul:1.11.0.201710050110]
at org.openhab.io.transport.cul.CULLifecycleManager.open(CULLifecycleManager.java:86)[190:org.openhab.io.transport.cul:1.11.0.201710050110]
at org.openhab.io.transport.cul.CULLifecycleManager.config(CULLifecycleManager.java:74)[190:org.openhab.io.transport.cul:1.11.0.201710050110]
at org.openhab.binding.fht.internal.FHTBinding.updated(FHTBinding.java:297)[187:org.openhab.binding.fht:1.11.0.201710050110]
at org.apache.felix.cm.impl.helper.ManagedServiceTracker.updated(ManagedServiceTracker.java:189)[3:org.apache.felix.configadmin:1.8.12]
at org.apache.felix.cm.impl.helper.ManagedServiceTracker.updateService(ManagedServiceTracker.java:152)[3:org.apache.felix.configadmin:1.8.12]
at org.apache.felix.cm.impl.helper.ManagedServiceTracker.provideConfiguration(ManagedServiceTracker.java:85)[3:org.apache.felix.configadmin:1.8.12]
at org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceUpdate.provide(ConfigurationManager.java:1461)[3:org.apache.felix.configadmin:1.8.12]
at org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceUpdate.run(ConfigurationManager.java:1417)[3:org.apache.felix.configadmin:1.8.12]
at org.apache.felix.cm.impl.UpdateThread.run0(UpdateThread.java:141)[3:org.apache.felix.configadmin:1.8.12]
at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:109)[3:org.apache.felix.configadmin:1.8.12]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_65]
Caused by: gnu.io.NoSuchPortException
at gnu.io.CommPortIdentifier.getPortIdentifier(CommPortIdentifier.java:273)[188:com.neuronrobotics.nrjavaserial:3.12.0.OH]
at org.openhab.io.transport.cul.internal.serial.CULSerialHandlerImpl.openHardware(CULSerialHandlerImpl.java:86)[190:org.openhab.io.transport.cul:1.11.0.201710050110]
… 14 more
10:23:17.900 [ERROR] [org.apache.felix.configadmin ] - [org.osgi.service.event.EventHandler, org.osgi.service.cm.ManagedService, id=287, bundle=187/file:/usr/share/openhab2/addons/org.openhab.binding.fht-1.11.0-SNAPSHOT.jar]: Unexpected problem updating configuration org.openhab.fht
java.lang.NullPointerException
at org.openhab.binding.fht.internal.FHTBinding$1.open(FHTBinding.java:114)[187:org.openhab.binding.fht:1.11.0.201710050110]
at org.openhab.io.transport.cul.CULLifecycleManager.open(CULLifecycleManager.java:92)[190:org.openhab.io.transport.cul:1.11.0.201710050110]
at org.openhab.io.transport.cul.CULLifecycleManager.config(CULLifecycleManager.java:74)[190:org.openhab.io.transport.cul:1.11.0.201710050110]
at org.openhab.binding.fht.internal.FHTBinding.updated(FHTBinding.java:297)[187:org.openhab.binding.fht:1.11.0.201710050110]
at org.apache.felix.cm.impl.helper.ManagedServiceTracker.updated(ManagedServiceTracker.java:189)[3:org.apache.felix.configadmin:1.8.12]
at org.apache.felix.cm.impl.helper.ManagedServiceTracker.updateService(ManagedServiceTracker.java:152)[3:org.apache.felix.configadmin:1.8.12]
at org.apache.felix.cm.impl.helper.ManagedServiceTracker.provideConfiguration(ManagedServiceTracker.java:85)[3:org.apache.felix.configadmin:1.8.12]
at org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceUpdate.provide(ConfigurationManager.java:1461)[3:org.apache.felix.configadmin:1.8.12]
at org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceUpdate.run(ConfigurationManager.java:1417)[3:org.apache.felix.configadmin:1.8.12]
at org.apache.felix.cm.impl.UpdateThread.run0(UpdateThread.java:141)[3:org.apache.felix.configadmin:1.8.12]
at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:109)[3:org.apache.felix.configadmin:1.8.12]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_65]

Have you checked that the path to your CUL device is correct? Are you sure it’s /dev/ttyUSB0?

hi yes… i added the the openhab user to tty Group…
now i have no error
i tried to set the temperature but nothing happend to my fht80b

10:54:34.189 [INFO ] [marthome.event.ItemStateChangedEvent] - HeizungArbeitszimmerDesired changed from 7 to 7.5
10:54:34.350 [INFO ] [smarthome.event.ItemCommandEvent ] - Item ‘HeizungArbeitszimmerDesired’ received command 8
10:54:34.351 [DEBUG] [nhab.binding.fht.internal.FHTBinding] - internalReceiveCommand() is called!
10:54:34.352 [DEBUG] [nhab.binding.fht.internal.FHTBinding] - Queuing new desired temperature
10:54:34.352 [INFO ] [marthome.event.ItemStateChangedEvent] - HeizungArbeitszimmerDesired changed from 7.5 to 8
10:54:34.517 [INFO ] [smarthome.event.ItemCommandEvent ] - Item ‘HeizungArbeitszimmerDesired’ received command 8.5
10:54:34.519 [DEBUG] [nhab.binding.fht.internal.FHTBinding] - internalReceiveCommand() is called!
10:54:34.521 [DEBUG] [nhab.binding.fht.internal.FHTBinding] - Queuing new desired temperature
10:54:34.524 [INFO ] [marthome.event.ItemStateChangedEvent] - HeizungArbeitszimmerDesired changed from 8 to 8.5
10:54:35.826 [INFO ] [smarthome.event.ItemCommandEvent ] - Item ‘HeizungArbeitszimmerDesired’ received command 9
10:54:35.834 [DEBUG] [nhab.binding.fht.internal.FHTBinding] - internalReceiveCommand() is called!
10:54:35.834 [INFO ] [marthome.event.ItemStateChangedEvent] - HeizungArbeitszimmerDesired changed from 8.5 to 9
10:54:35.835 [DEBUG] [nhab.binding.fht.internal.FHTBinding] - Queuing new desired temperature
10:54:36.004 [INFO ] [smarthome.event.ItemCommandEvent ] - Item ‘HeizungArbeitszimmerDesired’ received command 9.5
10:54:36.015 [DEBUG] [nhab.binding.fht.internal.FHTBinding] - internalReceiveCommand() is called!
10:54:36.017 [DEBUG] [nhab.binding.fht.internal.FHTBinding] - Queuing new desired temperature
10:54:36.022 [INFO ] [marthome.event.ItemStateChangedEvent] - HeizungArbeitszimmerDesired changed from 9 to 9.5
10:54:36.152 [INFO ] [smarthome.event.ItemCommandEvent ] - Item ‘HeizungArbeitszimmerDesired’ received command 9.5
10:54:36.153 [DEBUG] [nhab.binding.fht.internal.FHTBinding] - internalReceiveCommand() is called!
10:54:36.154 [DEBUG] [nhab.binding.fht.internal.FHTBinding] - Queuing new desired temperature
10:54:43.205 [DEBUG] [nhab.binding.fht.internal.FHTBinding] - Processing 1 waiting FHT temperature commands
10:55:43.207 [DEBUG] [nhab.binding.fht.internal.FHTBinding] - Processing 0 waiting FHT temperature commands
10:56:43.209 [DEBUG] [nhab.binding.fht.internal.FHTBinding] - Processing 0 waiting FHT temperature commands

It takes a few minutes for the command to be sent to the thermostat. Be patient :slight_smile:

few minutes? 5 minutes or more?

because waiting since 7 or 8 Minutes and nothing happend

i think my device Code could be wrong…

device Code1: 030 Code2:004

my Items Looks like this

Number HeizungArbeitszimmerDesired “Arbeitszimmer Soll-Temp. [%.1f °C]” (Heating, logger) { fht=“housecode=1E04;datapoint=DESIRED_TEMP” }

Number HeizungArbeitszimmerMeasured “Arbeitszimmer Ist-Temp. [%.1f °C]” (Heating) { fht=“housecode=1E04;datapoint=MEASURED_TEMP” }

Number HeizungArbeitszimmerValve “Arbeitszimmer Ventil [%.1f %%]” (Heating) { fht=“housecode=1E04;address=00;datapoint=VALVE” }

Switch HeizungArbeitszimmerBattery “Arbeitszimmer Heizung Batterie [%s]” (Heating, Battery) { fht=“housecode=1E04;datapoint=BATTERY” }

is the housecode for this items wrong?

i activated cul log… and get the following message whenn i try to Change the temperature

11:46:25.154 [INFO ] [marthome.event.ItemStateChangedEvent] - HeizungArbeitszimmerDesired changed from 12 to 12.5
11:46:27.066 [DEBUG] [nhab.binding.fht.internal.FHTBinding] - Processing 1 waiting FHT temperature commands
11:46:27.093 [DEBUG] [port.cul.internal.AbstractCULHandler] - Requesting credit report
11:46:27.106 [DEBUG] [port.cul.internal.AbstractCULHandler] - Received raw message from CUL: ? (1E044119 is unknown) Use one of A B C E e F f G h i K k l M m R T t U V W X x Y Z z
11:46:27.116 [DEBUG] [port.cul.internal.AbstractCULHandler] - Requesting credit report
11:46:27.148 [DEBUG] [port.cul.internal.AbstractCULHandler] - Received raw message from CUL: 00 508
11:46:27.152 [DEBUG] [port.cul.internal.AbstractCULHandler] - credit10ms = 508
11:47:27.068 [DEBUG] [nhab.binding.fht.internal.FHTBinding] - Processing 0 waiting FHT temperature commands
11:48:27.070 [DEBUG] [nhab.binding.fht.internal.FHTBinding] - Processing 0 waiting FHT temperature commands

hope you can help me… i am frustrated

Here’s an example of one of my FHT items:

Number HeatingStudyDesired “Study Desired-Temp. [%.1f °C]” (Heating, logger) { fht=“housecode=3C5F;datapoint=DESIRED_TEMP” }

Looks like my items…

the the Cent at the fht musst be set to nA?

could the fhz1000 be the problem? actualy i used this for 3 fht… but for this fht which i try to config with openhab i deactivated the fhz1000

the the Cent at the fht musst be set to nA?

I don’t understand your question.

What type of CUL device are you using? Does it have the latest firmware?

cul… this one

with the newst Firmware 1.67

my fht80-b3 musst be paired with the cul? if yes how?

i dont understand this…
i set the temperate and i get the following log

13:41:02.712 [INFO ] [smarthome.event.ItemCommandEvent    ] - Item 'HeizungArbeitszimmerDesired' received command 21
13:41:02.723 [INFO ] [marthome.event.ItemStateChangedEvent] - HeizungArbeitszimmerDesired changed from 20.5 to 21
13:41:24.595 [DEBUG] [nhab.binding.fht.internal.FHTBinding] - Processing 1 waiting FHT temperature commands
13:41:24.618 [DEBUG] [port.cul.internal.AbstractCULHandler] - Requesting credit report
13:41:24.634 [DEBUG] [port.cul.internal.AbstractCULHandler] - Received raw message from CUL: 00  900
13:41:24.645 [DEBUG] [port.cul.internal.AbstractCULHandler] - credit10ms = 900

the Temperatur of the fht not changed…
what ist CUL: 00 900? what does it mean?

There is no need to pair the FHT with the CUL device, the only link between the FHT80b and OpenHAB is the config in the fht.items file.

If you change the set point (desired temperature) on the FHT80b manually, do you see the change appear in OpenHAB a few minutes later?

What is in your sitemap for the thermostat control in OpenHAB? Mine looks like this:

Text item=HeatingMainBedroomMeasured label="Room Temp [%.1f °C]"
Setpoint item=HeatingMainBedroomDesired label="Desired Room Temp [%.1f °C]" minValue=6 maxValue=30 step=0.5

my fht.cfg

fht:housecode=1234
fht:device=serial:/dev/ttyUSB0
fht:baudrate=38400
fht:parity=NONE

fht:time.update=true             // update time ...
fht:time.update.cron=0 0 4 * * ? // ... at night

my fht.items


/************************************************************************************/
/* 	FHT80B - Funk-Heizkörperthermostate												*/
/*	binding: fht="housecode=<housecode>;address=<optional>;datapoint=<optional>"	*/
/*	items: 	Switch, Number 															*/
/*	datapoint:DESIRED_TEMP, MEASURED_TEMP, VALVE, BATTERY							*/
/*	FHTState: BATTERY_LOW															*/
/************************************************************************************/

Number HeizungArbeitszimmerDesired "Arbeitszimmer Soll-Temp. [%.1f °C]" 	<temperature>	(Heating, logger)	{ fht="housecode=1E04;datapoint=DESIRED_TEMP" }

Number HeizungArbeitszimmerMeasured	"Arbeitszimmer Ist-Temp. [%.1f °C]"		<temperature> (Heating) 	{ fht="housecode=1E04;datapoint=MEASURED_TEMP" }

Number HeizungArbeitszimmerValve "Arbeitszimmer Ventil [%.1f %%]"			<heating>	(Heating)		{ fht="housecode=1E04;address=00;datapoint=VALVE" }

Switch HeizungArbeitszimmerBattery "Arbeitszimmer Heizung Batterie [%s]" 	<battery>	(Heating, Battery)	{ fht="housecode=1E04;datapoint=BATTERY" }


Number HeizungBadDesired "Bad Soll-Temp. [%.1f °C]" 	<temperature>	(Heating, logger)	{ fht="housecode=6215;datapoint=DESIRED_TEMP" }

Number HeizungBadMeasured	"Bad Ist-Temp. [%.1f °C]"		<temperature> (Heating) 	{ fht="housecode=6215;datapoint=MEASURED_TEMP" }

Number HeizungBadValve "Bad Ventil [%.1f %%]"			<heating>	(Heating)		{ fht="housecode=6215;address=00;datapoint=VALVE" }

Switch HeizungBadBattery "Bad Heizung Batterie [%s]" 	<battery>	(Heating, Battery)	{ fht="housecode=6215;datapoint=BATTERY" }

/************************************************************************************/
/* FHT 80TF-2 - Funk-Tür-Fenster-Melder	 											*/
/*	binding: fht="housecode=<housecode>;address=<optional>;datapoint=WINDOW"		*/
/*	items: 	Contact 																*/
/*	datapoint:WINDOW																*/
/*	FHTState: WINDOW_OPEN, WINDOW_CLOSED											*/
/************************************************************************************/

my sitemap

sitemap fht label="Hauptmenue"
{
	Frame {
		Text label="Arbeitszimmer [%.1f °C]" item=HeizungArbeitszimmerMeasured icon="heating" {
			Setpoint item=HeizungArbeitszimmerDesired minValue=6 maxValue=30 step=0.5 
			Text item=HeizungArbeitszimmerMeasured
			Text item=HeizungArbeitszimmerValve		
			Text item=HeizungArbeitszimmerBattery
		}
	}
	Frame {
		Text label="Bad [%.1f °C]" item=HeizungBadMeasured icon="heating" {
			Setpoint item=HeizungBadDesired minValue=6 maxValue=30 step=0.5 
			Text item=HeizungBadMeasured
			Text item=HeizungBadValve		
			Text item=HeizungBadBattery
		}
	}
}

if i Change Temperatur at the fht.sitemap (Website) i get the following log entries

17:23:20.205 [DEBUG] [nhab.binding.fht.internal.FHTBinding] - Queuing new desired temperature
17:23:20.236 [INFO ] [smarthome.event.ItemCommandEvent    ] - Item 'HeizungArbeitszimmerDesired' received command 12
17:23:20.247 [DEBUG] [nhab.binding.fht.internal.FHTBinding] - internalReceiveCommand() is called!
17:23:20.252 [DEBUG] [nhab.binding.fht.internal.FHTBinding] - Queuing new desired temperature
17:23:20.349 [INFO ] [smarthome.event.ItemCommandEvent    ] - Item 'HeizungArbeitszimmerDesired' received command 12.5
17:23:20.358 [INFO ] [marthome.event.ItemStateChangedEvent] - HeizungArbeitszimmerDesired changed from 12 to 12.5
17:23:20.359 [DEBUG] [nhab.binding.fht.internal.FHTBinding] - internalReceiveCommand() is called!
17:23:20.360 [DEBUG] [nhab.binding.fht.internal.FHTBinding] - Queuing new desired temperature
17:23:20.634 [INFO ] [smarthome.event.ItemCommandEvent    ] - Item 'HeizungArbeitszimmerDesired' received command 13
17:23:20.640 [DEBUG] [nhab.binding.fht.internal.FHTBinding] - internalReceiveCommand() is called!
17:23:20.641 [DEBUG] [nhab.binding.fht.internal.FHTBinding] - Queuing new desired temperature
17:23:20.648 [INFO ] [marthome.event.ItemStateChangedEvent] - HeizungArbeitszimmerDesired changed from 12.5 to 13
17:23:20.765 [INFO ] [smarthome.event.ItemCommandEvent    ] - Item 'HeizungArbeitszimmerDesired' received command 13
17:23:20.770 [DEBUG] [nhab.binding.fht.internal.FHTBinding] - internalReceiveCommand() is called!
17:23:20.771 [DEBUG] [nhab.binding.fht.internal.FHTBinding] - Queuing new desired temperature
17:23:20.987 [INFO ] [smarthome.event.ItemCommandEvent    ] - Item 'HeizungArbeitszimmerDesired' received command 13.5
17:23:21.001 [DEBUG] [nhab.binding.fht.internal.FHTBinding] - internalReceiveCommand() is called!
17:23:21.003 [DEBUG] [nhab.binding.fht.internal.FHTBinding] - Queuing new desired temperature
17:23:21.011 [INFO ] [marthome.event.ItemStateChangedEvent] - HeizungArbeitszimmerDesired changed from 13 to 13.5

seconds later i get the following log entries

17:23:58.068 [DEBUG] [nhab.binding.fht.internal.FHTBinding] - Processing 1 waiting FHT temperature commands
17:23:58.095 [DEBUG] [port.cul.internal.AbstractCULHandler] - Requesting credit report
17:23:58.122 [DEBUG] [port.cul.internal.AbstractCULHandler] - Received raw message from CUL: 00  900
17:23:58.130 [DEBUG] [port.cul.internal.AbstractCULHandler] - credit10ms = 900

if i Change the temperature manually at the fht80b i get no log entry :frowning:

yesterday i tried fhem… with fhem everything is working…

if i Change the Temperatur at openhab… i get a log in the fhem log with…

2017.10.13 08:44:34 3: CUL868: Unknown code ? (1e044112 is unknown) Use one of A B C E e F f G h i K k l M m R T t U V W X x Y Z z, help me!

in openhab log is no entry…

has anybody a idea?

Hallo mkraus81,

i have got the a similar problem. In my case the intertechno binding is in conflict.
This binding on a second (selfmade CUL -> nanoCUL), only for this usage,
prevents the correct handling of FHT messages. When i disconnect the intertechno CUL
(unplug USB from Pi), i get error message for this CUL, and just from this moment i get correct FHT messages (on the other CUL), and everything works as it should.
The really disappointing thing, if i disable (delete Intertechno.cfg )or unistall intertechno binding FHT is NOT working after a reboot. It is really a mess. Only fiddling after every reboot i get a working FHT.
My Setup 5 * FHT8b (earlier Version of FHT80b) and a FHZ 1000. From the ventil binded to FHZ 1000 i never get any message. The other ones are working fine. For me it was not neccessary to use the setting “cent to NA”.

Maybe someone has an idea to get a setup that is working without this anoying bug.

P.S. i use the bindings for (FHT, FS20 an Intertechno) in version 1.12. in the addon Folder in the latest stable OpneHAB 2.

Greets Jason0815

Hallo mein Geräte code ist 1.= 065 2.=077 wie errechnet sich der Hauscode?
Wo und wie kann ich die CUL Protokolierung aktiviern und wo einsehen?

Habt Ihr auch eine Config für die Übersicht der Räume und Temperatur einstellen asl Vorlage Muster für den Home Builder?

Besten Dank

Liebe Grüße Martin