New binding for 1Wire, FHT and Evo Home radio signals

Thanks for the info, I’ll try setting the cron pattern device ping setting.

I’ve never used the “CeNT” option on the FHT80B before and I’ve just checked it in the room I’m in now and I think it was already set to On. I say that because when I selected the “CeNT” option On was the option that was immediately displayed so I assume that was the current option. I don’t have an FHZ1000 central controller, I have an FHT80B thermostat and an FHT8V radiator valve controller in each room.

In case it is useful to anyone the documentation for the “Cent” option is as follows:

9.8.Connecting to the home radio central unit (‘CEnt’)
You only require this special function, if you want the heating control to work
with a new FHZ1000 central unit or no central unit at all, in other words, you
wish to unregister the heating control from the central unit.
Radio communication between the heating control and the central unit is also
protected by the heating control’s security code. For this purpose the
respective heating control is ‘registered’ with the central unit.
To ensure that the heating control only works with your central unit and not
with your neighbor's central unit, for example, the heating control can only be
registered with one central unit.
If you want to register the heating control with another central unit, then you
must first to re- enable the heating control. 3 different settings are possible:
‘On’: Heating control is registered with the central unit
‘Off’: No radio communication with the central unit. Registration is not
 possible.
‘nA’: Heating control is enabled for registration with the central unit
To set, proceed as follows:
• Press the ‘PROG’ button until ‘Sond’ appears on the LCD.
• Use the scroller to select the special ‘CEnt’ function.
• To confirm your selection, briefly press the ‘PROG’ button.
• The LCD displays the current setting (‘On’, ‘Off’, ‘nA’).
• Use the scroller to select the setting you require (‘On’, ‘Off’, ‘nA’) and
confirm your selection by pressing the ‘PROG’ button.
The heating control then returns to the normal operating mode.

Found here.

I currently use the fht (which is actually for openHAB 1.x) addon in an openHAB 2.4 system and use the remoteopenhab addon to send the values to and from the 2.4 system and the “live” 3.4 system. The fht addon can read the measured temperature and set the desired temperature. In the fht log I see a measured temperature update approximately every 1-3 minutes.

I’ll set the cron pattern and see what happens. Many thanks again :slight_smile:

I just set the cron pattern device ping to 0 15 16 ? * WED * for the FHT80B with housecode 1010 and saw this in the log:

@2023-07-12T15:14:36.103661Z    CH      return read:    "T010100AA0017\r\n"     duration: PT8.503504S
@2023-07-12T15:14:36.103952Z    ExR     "FHT Message: {protocol : FHT, housecode : 101, command : VALVE, description : 0xaa, mode : LIME_CYCLE, repeated : true, position : 0.0, allowLowBatteryBeep : false}, signal strength: -62.500000"
@2023-07-12T15:14:36.104144Z    CH      call read
@2023-07-12T15:14:36.944159Z    CH      return read:    "T080800AA00F7\r\n"     duration: PT0.840015S
@2023-07-12T15:14:36.944429Z    ExR     "FHT Message: {protocol : FHT, housecode : 808, command : VALVE, description : 0xaa, mode : LIME_CYCLE, repeated : true, position : 0.0, allowLowBatteryBeep : false}, signal strength: -78.500000"
@2023-07-12T15:14:36.944648Z    CH      call read
@2023-07-12T15:14:56.102362Z    CH      return read:    "T060600AA0007\r\n"     duration: PT19.157714S
@2023-07-12T15:14:56.102637Z    ExR     "FHT Message: {protocol : FHT, housecode : 606, command : VALVE, description : 0xaa, mode : LIME_CYCLE, repeated : true, position : 0.0, allowLowBatteryBeep : false}, signal strength: -70.500000"
@2023-07-12T15:14:56.102836Z    CH      call read
@2023-07-12T15:15:00.635817Z    CH      call write:     "X\r\nT02\r\nT03\r\n"
@2023-07-12T15:15:00.636004Z    CH      return write    duration: PT0.000187S
@2023-07-12T15:15:00.637091Z    CH      call write:     "T0A0A60176107620C6310640F\n"
@2023-07-12T15:15:00.637280Z    CH      return write    duration: PT0.000189S
@2023-07-12T15:15:00.637343Z    CH      call write:     "X\r\nT02\r\nT03\r\n"
@2023-07-12T15:15:00.637443Z    CH      return write    duration: PT0.0001S
@2023-07-12T15:15:00.637503Z    CH      call write:     "X\r\nT02\r\nT03\r\n"
@2023-07-12T15:15:00.637602Z    CH      return write    duration: PT0.000099S
@2023-07-12T15:15:00.637694Z    CH      call write:     "T0A0A65FF66FF\n"
@2023-07-12T15:15:00.637863Z    CH      return write    duration: PT0.000169S
@2023-07-12T15:15:00.637925Z    CH      call write:     "X\r\nT02\r\nT03\r\n"
@2023-07-12T15:15:00.638076Z    CH      return write    duration: PT0.000151S
@2023-07-12T15:15:00.643969Z    CH      return read:    "21  900\r\nN/A\r\nAE\r\n21  900\r\n0A0A:6017,6107,620C,6310,640F\r\nA1\r\n21"  duration: PT4.541133S
@2023-07-12T15:15:00.648011Z    CH      call read
@2023-07-12T15:15:00.648066Z    CH      return read:    "  900\r\n0A0A:6017,6107,620C,6310,640F\r\nA1\r\n21  900\r\n0A0A:6017,610"      duration: PT0.000055S
@2023-07-12T15:15:00.648362Z    CH      call read
@2023-07-12T15:15:00.748529Z    CH      return read:    "7,620C,6310,640F 0A0A:65FF,66FF\r\n9A\r\n"     duration: PT0.100167S
@2023-07-12T15:15:00.749063Z    CH      call read
@2023-07-12T15:15:19.857312Z    CH      return read:    "T040400AA0019\r\n"     duration: PT19.108249S
@2023-07-12T15:15:19.857778Z    ExR     "FHT Message: {protocol : FHT, housecode : 404, command : VALVE, description : 0xaa, mode : LIME_CYCLE, repeated : true, position : 0.0, allowLowBatteryBeep : false}, signal strength: -61.500000"
@2023-07-12T15:15:19.857967Z    CH      call read
@2023-07-12T15:15:45.174774Z    CH      return read:    "T090900AA00FB\r\n"     duration: PT25.316807S
@2023-07-12T15:15:45.175005Z    ExR     "FHT Message: {protocol : FHT, housecode : 909, command : VALVE, description : 0xaa, mode : LIME_CYCLE, repeated : true, position : 0.0, allowLowBatteryBeep : false}, signal strength: -76.500000"
@2023-07-12T15:15:45.175195Z    CH      call read
@2023-07-12T15:15:56.268494Z    CH      return read:    "T020200AA0061\r\n"     duration: PT11.093299S
@2023-07-12T15:15:56.268722Z    ExR     "FHT Message: {protocol : FHT, housecode : 202, command : VALVE, description : 0xaa, mode : LIME_CYCLE, repeated : true, position : 0.0, allowLowBatteryBeep : false}, signal strength: -25.500000"
@2023-07-12T15:15:56.268962Z    CH      call read
@2023-07-12T15:15:58.738897Z    CH      return read:    "T0A0A00A600EC\r\n"     duration: PT2.469935S
@2023-07-12T15:15:58.739141Z    ExR     "FHT Message: {protocol : FHT, housecode : 1010, command : VALVE, description : 0xa6, mode : POSITION, repeated : true, position : 0.0, allowLowBatteryBeep : false}, signal strength: -84.000000"
@2023-07-12T15:15:58.739366Z    CH      call read
@2023-07-12T15:16:04.395173Z    CH      return read:    "T050500AA0005\r\n"     duration: PT5.655807S
@2023-07-12T15:16:04.395384Z    ExR     "FHT Message: {protocol : FHT, housecode : 505, command : VALVE, description : 0xaa, mode : LIME_CYCLE, repeated : true, position : 0.0, allowLowBatteryBeep : false}, signal strength: -71.500000"
@2023-07-12T15:16:04.395602Z    CH      call read

Is this what you’d expect to see? The item linked to the temperatureMeasured channel for that FHT80B has stayed NULL.

Hi Arne,

do you think the 3.2.0 build also works with openHAB 4.0 or do we need an updated build?

Best Regards
Pit

Hi Pit,

I will test it the next days…
Did you still need assistance with the registering issue?

Arne

Hi Arne,

thank you, I don’t need further assistance.

Best Regards
PIt

@aploese Hi Arne,
Hi all,

first of all I wish you a Merry Christmas!

This is an an older thread but I give it a try. I want to use my FHT-80b device (with the CUL stick)

I am running OpenHAB 4.1.0 and tried to install the 3.2.0 bindings (oh-ibapl-kar-3.2.0-20220120.135418-1.kar), but I am still facing issues:

 org.apache.felix.resolver.reason.ReasonException: Unable to resolve root: missing requirement [root] osgi.identity; osgi.identity=openhab-onewire4j-binding; type=karaf.feature; version="[3.2.0.SNAPSHOT,3.2.0.SNAPSHOT]"; filter:="(&(osgi.identity=openhab-onewire4j-binding)(type=karaf.feature)(version>=3.2.0.SNAPSHOT)(version<=3.2.0.SNAPSHOT))" [caused by: Unable to resolve openhab-onewire4j-binding/3.2.0.SNAPSHOT: missing requirement [openhab-onewire4j-binding/3.2.0.SNAPSHOT] osgi.identity; osgi.identity=de.ibapl.openhab.onewire4j; type=osgi.bundle; version="[3.2.0.202201201354,3.2.0.202201201354]"; resolution:=mandatory [caused by: Unable to resolve de.ibapl.openhab.onewire4j/3.2.0.202201201354: missing requirement [de.ibapl.openhab.onewire4j/3.2.0.202201201354] osgi.wiring.package; filter:="(&(osgi.wiring.package=org.openhab.core.config.core)(version>=3.2.0)(!(version>=4.0.0)))"]]

Is there any possible to run the binding under 4.1.0 or have I to downgrade my version? How can I resolve the missing requirements?
Or is there any other library or tool I can use? (I read something about homegear…)

Sorry for asking these stupid questions. I am a newbie according to openhab. I need some hints.

Thanks in advance!

Best regards
Andi

I found the 4.0.0 snapshot and installed it (also the features.xml and .pom)
https://oss.sonatype.org/content/repositories/snapshots/de/ibapl/openhab/oh-ibapl-kar/4.0.0-SNAPSHOT/

There was no error in the log but I cant find the Bindinge/the the things in the UI.

I saw in the feature list that the features are listed but some of them were not startet. So I installed it manually in the console. Now they are started:

openhab> feature:list -s --repository oh-ibapl-features-4.0.0-SNAPSHOT
Name                       │ Version        │ Required │ State   │ Repository                       │ Description
───────────────────────────┼────────────────┼──────────┼─────────┼──────────────────────────────────┼──────────────────────────────
de.ibapl.jnhw.jnhw         │ 3.0.0          │ x        │ Started │ oh-ibapl-features-4.0.0-SNAPSHOT │ JNHW
de.ibapl.spsw.jniprovider  │ 3.1.0          │ x        │ Started │ oh-ibapl-features-4.0.0-SNAPSHOT │ JNI provider for serial port
de.ibapl.spsw.jnhwprovider │ 3.1.0          │ x        │ Started │ oh-ibapl-features-4.0.0-SNAPSHOT │ JNHW provider for serial port
openhab-fhz4j-binding      │ 4.0.0.SNAPSHOT │ x        │ Started │ oh-ibapl-features-4.0.0-SNAPSHOT │ Fhz4J OH Binding
openhab-onewire4j-binding  │ 4.0.0.SNAPSHOT │ x        │ Started │ oh-ibapl-features-4.0.0-SNAPSHOT │ OneWire4J OH Binding

But still I can’t add things for FHT. How can I access them in the UI?

Hi,

under OpenHAB 3.X the binding just show up - I will have to look into this. Maybe there must be Installed under OpenHAB 4.X?.

Arne

Hi Arne,

thanks for your answer.

Is there any difference between the 4.0.0 and the 4.0.2 snapshot? On the sonataype server I found the 4.0.0. snapshot. I tried to build the 4.0.2 snapshot, but maybe I have overseen a goal in the pom.xml for just building the snapshot without deploying it (but my developer skills for adapting the pom are not good enough :wink: )

Is the 4.0.0-snapshot. already implemented for Openhab 4 or is it more intended for Openhab3?

Andi

I changed the numbering,
now: 4.1.0.3-SNAPSHOT,
so the first 3 digits are that of OH the last is a running number each time starting with 0, if a new OH version is out.
I asked in the developer forum for help - keep fingers crossed.

Arne

1 Like

Hi Arne,

I’ve tried the new builds oh-ibapl-kar-4.1.0.3-20231227.133539-1.kar and oh-ibapl-kar-4.1.0.3-20231228.164608-2.kar. Both of them continously create error messages:

2023-12-29 16:29:06.520 [WARN ] [d.i.e.f.h.SpswBridgeHandler         ] - Got IOE in CUL Adapter
de.ibapl.spsw.api.TimeoutIOException: null
	at de.ibapl.spsw.jnhwprovider.PosixSerialPortSocket.read(PosixSerialPortSocket.java:912) ~[?:?]
	at de.ibapl.fhz4j.cul.CulAdapter$StreamListener.run(CulAdapter.java:70) [bundleFile:?]
	at java.lang.Thread.run(Thread.java:840) [?:?]
2023-12-29 16:29:07.564 [WARN ] [d.i.e.f.h.SpswBridgeHandler         ] - Got IOE in CUL Adapter
de.ibapl.spsw.api.TimeoutIOException: null
	at de.ibapl.spsw.jnhwprovider.PosixSerialPortSocket.read(PosixSerialPortSocket.java:912) ~[?:?]
	at de.ibapl.fhz4j.cul.CulAdapter$StreamListener.run(CulAdapter.java:70) [bundleFile:?]
	at java.lang.Thread.run(Thread.java:840) [?:?]
2023-12-29 16:29:08.602 [WARN ] [d.i.e.f.h.SpswBridgeHandler         ] - Got IOE in CUL Adapter
de.ibapl.spsw.api.TimeoutIOException: null
	at de.ibapl.spsw.jnhwprovider.PosixSerialPortSocket.read(PosixSerialPortSocket.java:912) ~[?:?]
	at de.ibapl.fhz4j.cul.CulAdapter$StreamListener.run(CulAdapter.java:70) [bundleFile:?]
	at java.lang.Thread.run(Thread.java:840) [?:?]

Best Regards,
Pit

A new version is out and should fix nearly everything :wink:
https://oss.sonatype.org/content/repositories/snapshots/de/ibapl/openhab/oh-ibapl-kar/4.0.0-SNAPSHOT/

The features are renamed to openhab-binding-fhz4j and openhab-binding-onewire4j so they will be picked up by OH as add-on.
Currenty they appear under Openhabs own add-ons and get uninstalled (and disappear in the web UI) if one installs or uninstalls an add-on - Make sure to reinstall the feature (binding) in the console again.
Once I consider the package is ready for marketplace these issues will go away.

Hi Arne,

trhanks for releasing a new version. I tried oh-ibapl-kar-4.1.0.3-20240103.110905-6.kar

On the UI now the Bridge is visible. But I got read timeouts. I am using a “nanocul”. Can this occur because the nanocul is working withe the setting 38400 baud? Is it possible to configure the speed (e.g. that there is a input field for setting the speed)?

@2024-01-03T20:18:02.272520171Z SP      call opend:     "/dev/ttyUSB0" (speed=_38400_BPS, dataBits=DB_8, stopBits=SB_1, partity=NONE, flowControl=[])
@2024-01-03T20:18:02.273159986Z SP      call setSpeed:  _9600_BPS
@2024-01-03T20:18:02.275004819Z SP      return setSpeed
@2024-01-03T20:18:02.275232893Z SP      call setDataBits:       DB_8
@2024-01-03T20:18:02.277670356Z SP      return setDataBits
@2024-01-03T20:18:02.277887782Z SP      call setParity: NONE
@2024-01-03T20:18:02.279999449Z SP      return setParity
@2024-01-03T20:18:02.280230579Z SP      call setStopBits:       SB_1
@2024-01-03T20:18:02.282495819Z SP      return setStopBits
@2024-01-03T20:18:02.282732282Z SP      call setFlowControl:    []
@2024-01-03T20:18:02.285050023Z SP      return setFlowControl
@2024-01-03T20:18:02.285265856Z SP      call setTimeouts:       (interByteReadTimeout=100, overallReadTimeout=60000, overallWriteTimeout=1000)
@2024-01-03T20:18:02.285455764Z SP      return setTimeouts
@2024-01-03T20:18:02.359611653Z CH      call write:     "\r\n"
@2024-01-03T20:18:02.360002949Z CH      return write    duration: PT0.000391296S
@2024-01-03T20:18:02.360270579Z CH      call write:     "vd\r\n"
@2024-01-03T20:18:02.360513153Z CH      return write    duration: PT0.000242574S
@2024-01-03T20:18:02.361551282Z CH      call read
@2024-01-03T20:19:02.453316580Z CH      return read-timeout: buff.position=0, buff.remaining=64 "       duration: PT1M0.091765298S
@2024-01-03T20:19:02.454186728Z CH      call read

Andre

The communication is modeled after:
Home of culfw.
If you can connect via the screen command it should work culfw reference - See “X<RR>” to enable radio reception.
If you have any problems, just ask ;.)

Arne

Hi Arne,

Wirh the screen command it is working and I can see the messages from my FHT80b devoces.

But he connect is only possible with the speed on the serial port of 38400 bits per second (nanocul sticks are workin on this speed). The nano cul stick works in other aspects like the cul stick.

In the log file I can see that the binding tries to connect with 9600 bits per second. I assume that the setspeed commando is aetting the speed for the usb serial device to this speed. But this is not suitabe for the stick so I assume that the read timeouts are because of this.

So do you have any ideas how I can solve this?

Andre

You can try the latest → And set the speed in the config.

Hi Arne,

thanks for the new version (https://oss.sonatype.org/content/repositories/snapshots/de/ibapl/openhab/oh-ibapl-kar/4.1.0.3-SNAPSHOT/oh-ibapl-kar-4.1.0.3-20240104.114733-7.kar) and for the feauture to set the speed on the serial connection

The first try was not successfull. The second try was successfull - after the first connection with screen (send the command X61 in screen and waiting for the first message and after that closing the screen session) , and then adding the Bridge. Maybe also in combination with the scan for devices. - see also the beginning of the log files of the 2nd try

But after I restarted openhab I have to reinstall the binding in the console, to deactivate the bridge, to repeat the procedure with the screen session and to activate the bridge again.

I don’t know what leads to this behavior.

Also I have some questions about the binding:

  • The measured temperature is somtimes not updated although the temperature changes. It seems that the FHT80b device sends the updates not regularly although the devices are paired (and also repeated the pairing). Sometimes the updates appearing regularly. Do you have any idea why this happens?
    Update: Currently the first device is sending updates regularly

  • What I have to configure Cron Pattern Device ping? How often and when the device have to be pinged?

  • I see some runtime exceptions in the log file from the parser. Maybe this can be also a result of sending too many commands that are not send out. I have two devices and the 2nd device was sometimes not reacting and didn’t send any measured temperature updates.See also below. the log file snippet of the runtime exception

Andre

First Try

@2024-01-04T14:23:37.771544477Z SP      call opend:     "/dev/ttyUSB0" (speed=38400 bps, dataBits=DB_8, stopBits=1 sb, partity=NONE, flowControl=[])
@2024-01-04T14:23:37.772499440Z SP      call setSpeed:  38400 bps
@2024-01-04T14:23:37.773478829Z SP      return setSpeed
@2024-01-04T14:23:37.773767570Z SP      call setDataBits:       DB_8
@2024-01-04T14:23:37.775957292Z SP      return setDataBits
@2024-01-04T14:23:37.776246644Z SP      call setParity: NONE
@2024-01-04T14:23:37.778454940Z SP      return setParity
@2024-01-04T14:23:37.778690125Z SP      call setStopBits:       1 sb
@2024-01-04T14:23:37.780887403Z SP      return setStopBits
@2024-01-04T14:23:37.780997644Z SP      call setFlowControl:    []
@2024-01-04T14:23:37.783419681Z SP      return setFlowControl
@2024-01-04T14:23:37.783515347Z SP      call setTimeouts:       (interByteReadTimeout=100, overallReadTimeout=60000, overallWriteTimeout=1000)
@2024-01-04T14:23:37.783711366Z SP      return setTimeouts
@2024-01-04T14:23:37.784975033Z @2024-01-04T14:23:37.785159310Z CH      call read
CH      call write:     ""
@2024-01-04T14:23:37.785533273Z CH      return write    duration: PT0.000373963S
@2024-01-04T14:23:37.786216977Z CH      call write:     "X61\r\n"
@2024-01-04T14:23:37.786596662Z CH      return write    duration: PT0.000379685S
@2024-01-04T14:23:37.887049903Z CH      call write:     "T011101\r\n"
@2024-01-04T14:23:37.887426477Z CH      return write    duration: PT0.000376574S
@2024-01-04T14:24:37.842669404Z CH      return read-timeout: buff.position=0, buff.remaining=64 "       duration: PT1M0.057694371S
@2024-01-04T14:24:37.843278367Z CH      call read
@2024-01-04T14:25:37.896967202Z CH      return read-timeout: buff.position=0, buff.remaining=64 "       duration: PT1M0.053688835S
@2024-01-04T14:25:37.897389276Z CH      call read
@2024-01-04T14:26:37.930159481Z CH      return read-timeout: buff.position=0, buff.remaining=64 "       duration: PT1M0.032770205S
@2024-01-04T14:26:37.930589833Z CH      call read
@2024-01-04T14:27:37.986312593Z CH      return read-timeout: buff.position=0, buff.remaining=64 "       duration: PT1M0.05572276S
@2024-01-04T14:27:37.986753926Z CH      call read
@2024-01-04T14:28:38.041435706Z CH      return read-timeout: buff.position=0, buff.remaining=64 "       duration: P

Beginning of the 2nd try

@2024-01-04T14:59:22.175845532Z SP      call opend:     "/dev/ttyUSB0" (speed=38400 bps, dataBits=DB_8, stopBits=1 sb, partity=NONE, flowControl=[])
@2024-01-04T14:59:22.176239643Z SP      call setSpeed:  38400 bps
@2024-01-04T14:59:22.178029773Z SP      return setSpeed
@2024-01-04T14:59:22.178123032Z SP      call setDataBits:       DB_8
@2024-01-04T14:59:22.180513921Z SP      return setDataBits
@2024-01-04T14:59:22.180947495Z SP      call setParity: NONE
@2024-01-04T14:59:22.183257254Z SP      return setParity
@2024-01-04T14:59:22.183766088Z SP      call setStopBits:       1 sb
@2024-01-04T14:59:22.185642440Z SP      return setStopBits
@2024-01-04T14:59:22.185899403Z SP      call setFlowControl:    []
@2024-01-04T14:59:22.188148847Z SP      return setFlowControl
@2024-01-04T14:59:22.188491588Z SP      call setTimeouts:       (interByteReadTimeout=100, overallReadTimeout=60000, overallWriteTimeout=1000)
@2024-01-04T14:59:22.188701088Z SP      return setTimeouts
@2024-01-04T14:59:22.189508106Z CH      call write:     ""
@2024-01-04T14:59:22.189466551Z CH      call read
@2024-01-04T14:59:22.189804551Z CH      return write    duration: PT0.000296445S
@2024-01-04T14:59:22.190262754Z CH      call write:     "X61\r\n"
@2024-01-04T14:59:22.190580125Z CH      return write    duration: PT0.000317371S
@2024-01-04T14:59:22.213198699Z CH      return read:    "? (^?^?X61 is unknown) Use one of A B C E e F f G h i K k l M m R "    duration: PT0.023732148S
@2024-01-04T14:59:22.214387903Z CH      call read
@2024-01-04T14:59:22.291196495Z CH      call write:     "T011101\r\n"
@2024-01-04T14:59:22.291774366Z CH      return write    duration: PT0.000577871S
@2024-01-04T14:59:22.329362217Z CH      return read:    "T t U V W X x Y Z z\r\n"       duration: PT0.114974314S
@2024-01-04T14:59:22.330096495Z CH      call read
@2024-01-04T14:59:44.113851908Z CH      return read:    "T111000A63017\r\n"     duration: PT21.783755413S
@2024-01-04T14:59:44.114838001Z ExR     "FHT Message: {protocol : FHT, housecode : 1716, command : VALVE, description : 0xa6, mode : POSITION, repeated : true, position : 18.82353, allowLowBatteryBeep : false}, signal strength: -62,5000>
@2024-01-04T14:59:44.120106538Z CH      call read

snippet of the runtime exception

@2024-01-04T15:40:18.921879475Z CH      call write:     "X\r\nT02\r\nT03\r\n"
@2024-01-04T15:40:18.922228401Z CH      return write    duration: PT0.000348926S
@2024-01-04T15:40:18.922364438Z CH      call write:     "T1E604122\n"
@2024-01-04T15:40:18.922542290Z CH      return write    duration: PT0.000177852S
@2024-01-04T15:40:18.922647772Z CH      call write:     "X\r\nT02\r\nT03\r\n"
@2024-01-04T15:40:18.922852660Z CH      return write    duration: PT0.000204888S
@2024-01-04T15:40:18.955338586Z CH      return read:    "61  872\r\n1110:412F 1110:412E 1110:412D 1110:412C 1110:412F 1110:"    duration: PT0.117497333S
@2024-01-04T15:40:18.958390994Z CH      call read
@2024-01-04T15:40:18.971360994Z CH      return read:    "412E 1110:412D 1110:412C 1110:412B 1110:412A 1110:4129 1110:4128"      duration: PT0.01297S
@2024-01-04T15:40:18.972028235Z CH      call read
@2024-01-04T15:40:19.072257142Z CH      return read:    " 1E60:413C 1E34151:E 246\r\n\r\n\r\r:1 224406112314:E\r\n\r\n" duration: PT0.100228907S
@2024-01-04T15:40:19.074565957Z ExR     java.lang.RuntimeException: State: COLLECT_TYPE last byte 0x24
        at de.ibapl.fhz4j.parser.em.EmParser.parse(EmParser.java:126)
        at de.ibapl.fhz4j.parser.cul.CulParser.parse(CulParser.java:307)
        at de.ibapl.fhz4j.cul.CulAdapter$StreamListener.run(CulAdapter.java:75)
        at java.base/java.lang.Thread.run(Thread.java:840)
Caused by: java.lang.RuntimeException: Wrong Type
        at de.ibapl.fhz4j.parser.em.EmParser.parse(EmParser.java:90)
        ... 3 more

Hi Arne,

the build oh-ibapl-kar-4.1.0.3-20240104.114733-7 works fine for me. I also can see the addons in the Web UI.
For optical reasons you might want to reduce the log level of the FHT80 TF messages:

2024-01-07 10:37:12.357 [ERROR] [d.i.e.f.h.Fht80TfHandler            ] - update FHT80 TF {protocol : FHT_TF, address : 0x0db526, value : WINDOW_INTERNAL_CLOSED, lowBattery : false} channel: {fhz4j:fht80-tf:829c126606:dca2bea8e4}

Thank you & Best Regards,
Pit

For the measured temp etc…
You must bring the device in function (Manual 3.9.9 “CEnt” to “On” or “nA” off will disable the communication with a “Zentrale” ;-).
Here comes the “CronPattern” into play once a week it will send each FHT80b (FHT80 cant connect to a “Zentrale”) the fht reporting command, so it will send the changes I ask for (currently all).
It seems that once a week is OK - if you do it more frequently you may exhaust you sent time slots of the CUL.
The Binding should come up without any interfering.
You should be able to pause the binding, unplug the CUL, pug the CUL in. and then just start it.
If the binding receives no data, pleas send the com logging, so I can check.

A new version is out - it should fix some low level problems if the running CUL/Onewire adapter get unplugged (native EHUP error).

And the FHT-Tf log are less.

1 Like