New Vallox Binding

Tags: #<Tag:0x00007f616dd7b150> #<Tag:0x00007f616dd7b038>

Hi all,

I’ve been developing a binding for older Vallox SE model air ventilation units. To be exact, I continued @SuperOok’s work. Now I made PR #6459 to get it someday merged in to the official release. The main goal would be to combine this and @bjoernbrings 's
Vallox MV binding and release a binding that handles all types and models of Vallox.

You can download the bundle from jFrog: org.openhab.binding.vallox-2.5.5-SNAPSHOT.jar or install in straight from Eclipse Marketplace. For now this binding supports only SE models. Not the newer MV.

Here’s also a link to my github repo containing the source code. Have a look and tell me if you find anything to fix.

Edit #1
2.5.1-SNAPSHOT version is available

3 Likes

Hello,

Serial connection testers are needed. :wave: New build is on it’s way. If encounter any errors or triubles, send me trace logs and comment into github if it’s something specific.

Thanks,
Miika

Edit #1:
Looks like the build is still queued. And I found some bugs that most likely prevents the serial part working so no hurry in testing.

Edit #2:
New build is now available.

Hi,

Newest build now contains some new internal functionality that should be tested by more people than me. For example ValloxMV binding is now combined in it. Could some of you Vallox MV (org.openhab.binding.valloxmv) users test and confirm that everything works as expected? Serial connection is finalized and tested but only in my dev environment. So if there’s a volunteer with for example openHAB -> usb -> rs485 connection testing is needed.

Works like a charm with the MV350.
I’ve only tested / looked at changing states & fan speed (only for at home profile), showing outside temperature, humidty & next filter change date. All of these work

Thanks!

1 Like

Hi,

For not braking backward compatibility and ease of review, we decided to drop MV model support from this binding. The plan is then to combine these two after we move to 3.0.0 release.

Hi, I connected 2 Vallox systems (80SE & 90SE) with OpenHAB via the binding. I have two questions.

  1. What update rate is set in the binding? How often are the values updated? I have the impression that not all values are updated correctly. Especially when I restart the ventilation systems.

  2. I need the status whether the bypass valve is open or not. Can you add this value?

Hello, Sebastian!

  1. Refresh happens every 5 minutes. If you think something is not working, please enable DEBUG or TRACE logging to see what really happens.

  2. Switch channel vallox:se-tcp:vallox:status#damperMotorPosition shows you the if the heat recovery cell is bypassed, aka if it’s in summer position. Is this what you need?

I want to connect two Vallox SE (80SE & 90SE) devices with the binding. Every single device works, but not both at the same time. I get the following error message in Openhab (version 2.5.1) when I changed for example the fanspeed:

2020-03-05 18:55:22.079 [ome.event.ItemCommandEvent] - Item 'FanSpeed2' received command 4

2020-03-05 18:55:22.117 [nt.ItemStatePredictedEvent] - FanSpeed2 predicted to become 4

2020-03-05 18:55:22.142 [vent.ItemStateChangedEvent] - FanSpeed2 changed from 3 to 4

==> /var/log/openhab2/openhab.log <==

2020-03-05 18:55:22.151 [DEBUG] [ernal.connection.ValloxBaseConnector] - Wrote 01-26-11-29-0F-70

2020-03-05 18:55:22.151 [DEBUG] [ernal.connection.ValloxBaseConnector] - Send queue handler started

2020-03-05 18:55:22.654 [DEBUG] [ernal.connection.ValloxBaseConnector] - Wrote 01-26-11-29-0F-70

2020-03-05 18:55:23.156 [DEBUG] [ernal.connection.ValloxBaseConnector] - Wrote 01-26-11-29-0F-70

2020-03-05 18:55:23.660 [DEBUG] [ernal.connection.ValloxBaseConnector] - Wrote 01-26-11-29-0F-70

2020-03-05 18:55:24.162 [DEBUG] [ernal.connection.ValloxBaseConnector] - Wrote 01-26-11-29-0F-70

2020-03-05 18:55:24.665 [DEBUG] [lox.internal.handler.ValloxSEHandler] - Reconnecting after error: Ack byte not received for telegram: 01-26-11-29-0F-70

==> /var/log/openhab2/events.log <==

2020-03-05 18:55:24.668 [hingStatusInfoChangedEvent] - 'vallox:se-serial:downstairs' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Ack byte not received for telegram: 01-26-11-29-0F-70

==> /var/log/openhab2/openhab.log <==

2020-03-05 18:55:25.156 [TRACE] [lox.internal.handler.ValloxSEHandler] - Telegram received OK 01-11-21-71-00-A4

2020-03-05 18:55:25.158 [DEBUG] [ng.vallox.internal.telegram.Telegram] - Channels parsed from telegram {status#firePlaceBoosterOn=OFF, setting#activateFirePlaceBooster=OFF, status#remoteControlOn=OFF}

2020-03-05 18:55:25.162 [TRACE] [lox.internal.handler.ValloxSEHandler] - Telegram not for us 01-21-11-00-A3-D6

2020-03-05 18:55:25.290 [TRACE] [lox.internal.handler.ValloxSEHandler] - Telegram received OK 01-11-21-A3-01-D7

2020-03-05 18:55:25.292 [DEBUG] [ng.vallox.internal.telegram.Telegram] - Channels parsed from telegram {status#postHeatingIndicator=OFF, setting#humidityAdjustState=OFF, setting#co2AdjustState=OFF, setting#powerState=ON, setting#postHeatingState=OFF, maintenance#filterGuardIndicator=OFF, alarm#faultIndicator=OFF, maintenance#serviceReminderIndicator=OFF}

2020-03-05 18:55:25.303 [TRACE] [lox.internal.handler.ValloxSEHandler] - Telegram not for us 01-21-11-00-29-5C

2020-03-05 18:55:25.306 [TRACE] [lox.internal.handler.ValloxSEHandler] - Telegram received OK 01-11-21-29-0F-6B

2020-03-05 18:55:25.309 [DEBUG] [ng.vallox.internal.telegram.Telegram] - Channels parsed from telegram {fanControl#fanSpeed=4}

2020-03-05 18:55:25.313 [TRACE] [lox.internal.handler.ValloxSEHandler] - Telegram not for us 01-21-11-00-35-68

2020-03-05 18:55:25.317 [TRACE] [lox.internal.handler.ValloxSEHandler] - Telegram received OK 01-11-21-35-96-FE

2020-03-05 18:55:25.320 [DEBUG] [ng.vallox.internal.telegram.Telegram] - Channels parsed from telegram {efficiency#averageEfficiency=77, efficiency#inEfficiency=77, efficiency#outEfficiency=77, temperature#tempIncoming=16}

2020-03-05 18:55:25.324 [TRACE] [lox.internal.handler.ValloxSEHandler] - Telegram not for us 01-21-11-00-A3-D6

2020-03-05 18:55:25.328 [TRACE] [lox.internal.handler.ValloxSEHandler] - Telegram received OK 01-11-21-A3-01-D7

2020-03-05 18:55:25.331 [DEBUG] [ng.vallox.internal.telegram.Telegram] - Channels parsed from telegram {status#postHeatingIndicator=OFF, setting#humidityAdjustState=OFF, setting#co2AdjustState=OFF, setting#powerState=ON, setting#postHeatingState=OFF, maintenance#filterGuardIndicator=OFF, alarm#faultIndicator=OFF, maintenance#serviceReminderIndicator=OFF}

2020-03-05 18:55:25.340 [TRACE] [lox.internal.handler.ValloxSEHandler] - Telegram not for us 01-21-11-00-71-A4

==> /var/log/openhab2/events.log <==

2020-03-05 18:55:26.155 [vent.ItemStateChangedEvent] - Grohe_Leistung changed from 75 to 73

==> /var/log/openhab2/openhab.log <==

2020-03-05 18:55:27.238 [TRACE] [lox.internal.handler.ValloxSEHandler] - Telegram received OK 01-11-21-71-00-A4

2020-03-05 18:55:27.239 [DEBUG] [ng.vallox.internal.telegram.Telegram] - Channels parsed from telegram {status#firePlaceBoosterOn=OFF, setting#activateFirePlaceBooster=OFF, status#remoteControlOn=OFF}

2020-03-05 18:55:27.363 [TRACE] [lox.internal.handler.ValloxSEHandler] - Telegram received OK 01-11-20-2B-00-5D

2020-03-05 18:55:27.365 [DEBUG] [ng.vallox.internal.telegram.Telegram] - Channels parsed from telegram {status#co2=0}

2020-03-05 18:55:27.490 [TRACE] [lox.internal.handler.ValloxSEHandler] - Telegram received OK 01-11-20-2C-00-5E

2020-03-05 18:55:27.492 [DEBUG] [ng.vallox.internal.telegram.Telegram] - Channels parsed from telegram {status#co2=0}

2020-03-05 18:55:27.626 [TRACE] [lox.internal.handler.ValloxSEHandler] - Telegram received OK 01-11-20-35-96-FD

2020-03-05 18:55:27.631 [DEBUG] [ng.vallox.internal.telegram.Telegram] - Channels parsed from telegram {efficiency#averageEfficiency=77, efficiency#inEfficiency=77, efficiency#outEfficiency=77, temperature#tempIncoming=16}

2020-03-05 18:55:27.760 [TRACE] [lox.internal.handler.ValloxSEHandler] - Telegram received OK 01-11-20-34-9A-00

2020-03-05 18:55:27.765 [DEBUG] [ng.vallox.internal.telegram.Telegram] - Channels parsed from telegram {efficiency#averageEfficiency=77, efficiency#inEfficiency=77, efficiency#outEfficiency=77, temperature#tempInside=18}

2020-03-05 18:55:27.895 [TRACE] [lox.internal.handler.ValloxSEHandler] - Telegram received OK 01-11-20-32-81-E5

2020-03-05 18:55:27.900 [DEBUG] [ng.vallox.internal.telegram.Telegram] - Channels parsed from telegram {temperature#tempOutside=9, efficiency#averageEfficiency=77, efficiency#inEfficiency=77, efficiency#outEfficiency=77}

2020-03-05 18:55:27.910 [TRACE] [lox.internal.handler.ValloxSEHandler] - Telegram received OK 01-11-20-33-87-EC

2020-03-05 18:55:27.915 [DEBUG] [ng.vallox.internal.telegram.Telegram] - Channels parsed from telegram {efficiency#averageEfficiency=77, temperature#tempExhaust=11, efficiency#inEfficiency=77, efficiency#outEfficiency=77}

2020-03-05 18:55:28.218 [DEBUG] [lox.internal.handler.ValloxSEHandler] - Closing connection

2020-03-05 18:55:28.230 [DEBUG] [ernal.connection.ValloxBaseConnector] - Listener removed: org.openhab.binding.vallox.internal.handler.ValloxSEHandler@1c61aa7

2020-03-05 18:55:28.232 [DEBUG] [ernal.connection.ValloxBaseConnector] - Send queue handler stopped

2020-03-05 18:55:28.253 [DEBUG] [nal.connection.ValloxSerialConnector] - Serial connection closed

2020-03-05 18:55:28.256 [DEBUG] [ernal.connection.ValloxBaseConnector] - Listener registered: org.openhab.binding.vallox.internal.handler.ValloxSEHandler@1c61aa7

2020-03-05 18:55:28.258 [DEBUG] [nal.connection.ValloxSerialConnector] - Connecting to /dev/ttyUSB1

2020-03-05 18:55:28.269 [DEBUG] [nal.connection.ValloxSerialConnector] - Connected to /dev/ttyUSB1

==> /var/log/openhab2/events.log <==

2020-03-05 18:55:28.274 [hingStatusInfoChangedEvent] - 'vallox:se-serial:downstairs' changed from OFFLINE (COMMUNICATION_ERROR): Ack byte not received for telegram: 01-26-11-29-0F-70 to ONLINE

==> /var/log/openhab2/openhab.log <==

2020-03-05 18:55:28.574 [TRACE] [lox.internal.handler.ValloxSEHandler] - Connection already open

==> /var/log/openhab2/events.log <==

2020-03-05 18:55:29.743 [vent.ItemStateChangedEvent] - Current_DateTime changed from 2020-03-05T18:54:29.731+0100 to 2020-03-05T18:55:29.734+0100

==> /var/log/openhab2/openhab.log <==

2020-03-05 18:55:30.315 [TRACE] [lox.internal.handler.ValloxSEHandler] - Telegram received OK 01-11-20-2A-2A-86

2020-03-05 18:55:30.319 [DEBUG] [ng.vallox.internal.telegram.Telegram] - Channels parsed from telegram {status#humidity=-4.411764705882353}

2020-03-05 18:55:30.327 [TRACE] [lox.internal.handler.ValloxSEHandler] - Telegram not for us 01-21-11-00-A3-D6

2020-03-05 18:55:30.461 [TRACE] [lox.internal.handler.ValloxSEHandler] - Telegram received OK 01-11-21-A3-01-D7

2020-03-05 18:55:30.464 [DEBUG] [ng.vallox.internal.telegram.Telegram] - Channels parsed from telegram {status#postHeatingIndicator=OFF, setting#humidityAdjustState=OFF, setting#co2AdjustState=OFF, setting#powerState=ON, setting#postHeatingState=OFF, maintenance#filterGuardIndicator=OFF, alarm#faultIndicator=OFF, maintenance#serviceReminderIndicator=OFF}

2020-03-05 18:55:30.471 [TRACE] [lox.internal.handler.ValloxSEHandler] - Telegram not for us 01-21-11-00-29-5C

2020-03-05 18:55:30.473 [TRACE] [lox.internal.handler.ValloxSEHandler] - Telegram received OK 01-11-21-29-0F-6B

2020-03-05 18:55:30.480 [DEBUG] [ng.vallox.internal.telegram.Telegram] - Channels parsed from telegram {fanControl#fanSpeed=4}

2020-03-05 18:55:30.485 [TRACE] [lox.internal.handler.ValloxSEHandler] - Telegram not for us 01-21-11-00-35-68

2020-03-05 18:55:30.487 [TRACE] [lox.internal.handler.ValloxSEHandler] - Telegram received OK 01-11-21-35-96-FE

2020-03-05 18:55:30.490 [DEBUG] [ng.vallox.internal.telegram.Telegram] - Channels parsed from telegram {efficiency#averageEfficiency=77, efficiency#inEfficiency=77, efficiency#outEfficiency=77, temperature#tempIncoming=16}

2020-03-05 18:55:30.494 [TRACE] [lox.internal.handler.ValloxSEHandler] - Telegram not for us 01-21-11-00-A3-D6

2020-03-05 18:55:30.497 [TRACE] [lox.internal.handler.ValloxSEHandler] - Telegram received OK 01-11-21-A3-01-D7

2020-03-05 18:55:30.500 [DEBUG] [ng.vallox.internal.telegram.Telegram] - Channels parsed from telegram {status#postHeatingIndicator=OFF, setting#humidityAdjustState=OFF, setting#co2AdjustState=OFF, setting#powerState=ON, setting#postHeatingState=OFF, maintenance#filterGuardIndicator=OFF, alarm#faultIndicator=OFF, maintenance#serviceReminderIndicator=OFF}

2020-03-05 18:55:30.507 [TRACE] [lox.internal.handler.ValloxSEHandler] - Telegram not for us 01-21-11-00-71-A4

2020-03-05 18:55:35.475 [TRACE] [lox.internal.handler.ValloxSEHandler] - Telegram received OK 01-11-21-71-00-A4

2020-03-05 18:55:35.479 [DEBUG] [ng.vallox.internal.telegram.Telegram] - Channels parsed from telegram {status#firePlaceBoosterOn=OFF, setting#activateFirePlaceBooster=OFF, status#remoteControlOn=OFF}

2020-03-05 18:55:35.482 [TRACE] [lox.internal.handler.ValloxSEHandler] - Telegram not for us 01-21-11-00-A3-D6

2020-03-05 18:55:35.610 [TRACE] [lox.internal.handler.ValloxSEHandler] - Telegram received OK 01-11-21-A3-01-D7

2020-03-05 18:55:35.612 [DEBUG] [ng.vallox.internal.telegram.Telegram] - Channels parsed from telegram {status#postHeatingIndicator=OFF, setting#humidityAdjustState=OFF, setting#co2AdjustState=OFF, setting#powerState=ON, setting#postHeatingState=OFF, maintenance#filterGuardIndicator=OFF, alarm#faultIndicator=OFF, maintenance#serviceReminderIndicator=OFF}

2020-03-05 18:55:35.620 [TRACE] [lox.internal.handler.ValloxSEHandler] - Telegram not for us 01-21-11-00-29-5C

2020-03-05 18:55:35.623 [TRACE] [lox.internal.handler.ValloxSEHandler] - Telegram received OK 01-11-21-29-0F-6B

2020-03-05 18:55:35.625 [DEBUG] [ng.vallox.internal.telegram.Telegram] - Channels parsed from telegram {fanControl#fanSpeed=4}

2020-03-05 18:55:35.629 [TRACE] [lox.internal.handler.ValloxSEHandler] - Telegram not for us 01-21-11-00-35-68

2020-03-05 18:55:35.632 [TRACE] [lox.internal.handler.ValloxSEHandler] - Telegram received OK 01-11-21-35-96-FE

2020-03-05 18:55:35.634 [DEBUG] [ng.vallox.internal.telegram.Telegram] - Channels parsed from telegram {efficiency#averageEfficiency=77, efficiency#inEfficiency=77, efficiency#outEfficiency=77, temperature#tempIncoming=16}

2020-03-05 18:55:35.641 [TRACE] [lox.internal.handler.ValloxSEHandler] - Telegram not for us 01-21-11-00-A3-D6

2020-03-05 18:55:35.643 [TRACE] [lox.internal.handler.ValloxSEHandler] - Telegram received OK 01-11-21-A3-01-D7

2020-03-05 18:55:35.646 [DEBUG] [ng.vallox.internal.telegram.Telegram] - Channels parsed from telegram {status#postHeatingIndicator=OFF, setting#humidityAdjustState=OFF, setting#co2AdjustState=OFF, setting#powerState=ON, setting#postHeatingState=OFF, maintenance#filterGuardIndicator=OFF, alarm#faultIndicator=OFF, maintenance#serviceReminderIndicator=OFF}

2020-03-05 18:55:35.659 [TRACE] [lox.internal.handler.ValloxSEHandler] - Telegram not for us 01-21-11-00-71-A4

When I remove one of the systems from the configuration, then I can change the fanspeed without any error messages. I opend an issue on github for that.

Thank you for the additional info. Let’s continue this over github. :+1:

With the update to OpenHAB 2.5.4 I can no longer adjust values. I get the following error message from the binding:

2020-04-23 08:01:32.620 [ome.event.ItemCommandEvent] - Item 'FanSpeed2' received command 3
2020-04-23 08:01:32.651 [nt.ItemStatePredictedEvent] - FanSpeed2 predicted to become 3
2020-04-23 08:01:32.671 [vent.ItemStateChangedEvent] - FanSpeed2 changed from 2 to 3
2020-04-23 08:01:32.683 [DEBUG] [.internal.se.handler.ValloxSEHandler] - Unsupported command '3'
2020-04-23 08:01:33.513 [TRACE] [.internal.se.handler.ValloxSEHandler] - Telegram not for us 01-21-11-00-A3-D6

What does Unsupported command mean?

I have two things in my home currently:

  • Vallox 350 SE-E ventilation system
  • OpenHAB 2.5.4 running on a host with close physical proximity to the Vallox main unit

Now I want to connect both using the binding. Is there any kind of documentation on the physical link that needs to be established? A little bit of a ‘Getting started’ document would help to flatten my learning curve. Therefore any hints are appreciated.

It means that my UoM implementattion didn’t go as planned :D,
and DecimalType commands aren’t accepted. I’ll fix it but before that you can downgrade if 2.5.3-SNAPSHOT was working better: https://openhab.jfrog.io/openhab/libs-pullrequest-local/org/openhab/addons/bundles/org.openhab.binding.vallox/2.5.3-SNAPSHOT/

Hi @martingruening, first thing you need is a RS485 adapter for the physical connection. For now I’m using USB to RS485 converter. Connection diagrams can be found in your machines manual. You can start by familiarize yourself with RS485.

Thanks for letting me know. I just ordered a RS485 USB adapter and a USB extension cable. A wall mounted control unit from Vallox (FBD 382 LCD) is connected to the central unit and I want to keep that one. Can I add the new RS485 connection in parallel?

Yes. I have the exact same setup with my 110 SE R unit.

@Sebastian_Neu please try the newest build org.openhab.binding.vallox-2.5.5-SNAPSHOT.jar

With the newest version for me it’s possible to set the fan speed for one time. After the second try the following error message appears:

2020-04-28 13:57:53.208 [ome.event.ItemCommandEvent] - Item 'FanSpeed' received command 4

2020-04-28 13:57:53.230 [nt.ItemStatePredictedEvent] - FanSpeed predicted to become 5

2020-04-28 13:57:53.471 [TRACE] [.internal.se.handler.ValloxSEHandler] - Telegram not for us 01-21-11-00-A3-D6

2020-04-28 13:57:53.474 [TRACE] [.internal.se.handler.ValloxSEHandler] - Telegram received OK 01-11-21-A3-01-D7

2020-04-28 13:57:53.476 [TRACE] [vallox.internal.se.telegram.Telegram] - Channels parsed from telegram {status#postHeatingIndicator=OFF, setting#humidityAdjustState=OFF, setting#co2AdjustState=OFF, setting#powerState=ON, setting#postHeatingState=OFF, maintenance#filterGuardIndicator=OFF, alarm#faultIndicator=OFF, maintenance#serviceReminderIndicator=OFF}

2020-04-28 13:57:53.481 [DEBUG] [al.se.connection.ValloxBaseConnector] - Wrote 01-25-11-00-AF-E6

2020-04-28 13:57:53.492 [TRACE] [.internal.se.handler.ValloxSEHandler] - Telegram not for us 01-21-11-00-29-5C

2020-04-28 13:57:53.732 [TRACE] [.internal.se.handler.ValloxSEHandler] - CRC checksum failed 01-11-E9-B5-7F-01

2020-04-28 13:57:53.735 [TRACE] [.internal.se.handler.ValloxSEHandler] - Telegram received OK 01-11-21-29-0F-6B

2020-04-28 13:57:53.737 [TRACE] [vallox.internal.se.telegram.Telegram] - Channels parsed from telegram {fanControl#fanSpeed=4}

2020-04-28 13:57:53.754 [TRACE] [.internal.se.handler.ValloxSEHandler] - Telegram not for us 01-21-11-00-35-68

2020-04-28 13:57:53.757 [TRACE] [.internal.se.handler.ValloxSEHandler] - Telegram received OK 01-11-21-35-9B-03

2020-04-28 13:57:53.760 [TRACE] [vallox.internal.se.telegram.Telegram] - Channels parsed from telegram {temperature#tempIncoming=18 °C}

2020-04-28 13:57:53.775 [TRACE] [.internal.se.handler.ValloxSEHandler] - Telegram not for us 01-21-11-00-A3-D6

2020-04-28 13:57:53.778 [TRACE] [.internal.se.handler.ValloxSEHandler] - Telegram received OK 01-11-21-A3-01-D7

2020-04-28 13:57:53.780 [TRACE] [vallox.internal.se.telegram.Telegram] - Channels parsed from telegram {status#postHeatingIndicator=OFF, setting#humidityAdjustState=OFF, setting#co2AdjustState=OFF, setting#powerState=ON, setting#postHeatingState=OFF, maintenance#filterGuardIndicator=OFF, alarm#faultIndicator=OFF, maintenance#serviceReminderIndicator=OFF}

2020-04-28 13:57:53.797 [TRACE] [.internal.se.handler.ValloxSEHandler] - Telegram not for us 01-21-11-00-71-A4

2020-04-28 13:57:53.799 [TRACE] [.internal.se.handler.ValloxSEHandler] - Telegram received OK 01-11-21-71-00-A4

2020-04-28 13:57:53.802 [TRACE] [vallox.internal.se.telegram.Telegram] - Channels parsed from telegram {status#firePlaceBoosterOn=OFF, setting#activateFirePlaceBooster=OFF, status#remoteControlOn=OFF}

2020-04-28 13:57:53.986 [DEBUG] [al.se.connection.ValloxBaseConnector] - Wrote 01-25-11-00-08-3F

2020-04-28 13:57:54.002 [TRACE] [.internal.se.handler.ValloxSEHandler] - Telegram received OK 01-11-25-08-03-42

2020-04-28 13:57:54.005 [TRACE] [vallox.internal.se.telegram.Telegram] - Channels parsed from telegram {fanControl#exhaustFanOff=OFF, status#damperMotorPosition=ON, fanControl#supplyFanOff=OFF, status#preHeatingOn=OFF, alarm#faultSignalRelayClosed=OFF, status#firePlaceBoosterSwitch=OFF}    
2020-04-28 13:57:55.415 [DEBUG] [.internal.se.handler.ValloxSEHandler] - Connection failed 

java.io.IOException: Port in use

at org.openhab.binding.vallox.internal.se.connection.ValloxSerialConnector.connect(ValloxSerialConnector.java:90) ~[?:?]

at org.openhab.binding.vallox.internal.se.handler.ValloxSEHandler.connect(ValloxSEHandler.java:102) ~[?:?]

at org.openhab.binding.vallox.internal.se.handler.ValloxSEHandler.checkConnection(ValloxSEHandler.java:378) ~[?:?]

at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_222]

at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [?:1.8.0_222]

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [?:1.8.0_222]

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [?:1.8.0_222]

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_222]

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_222]

at java.lang.Thread.run(Thread.java:748) [?:1.8.0_222]

Caused by: org.eclipse.smarthome.io.transport.serial.PortInUseException

at org.eclipse.smarthome.io.transport.serial.internal.SerialPortIdentifierImpl.open(SerialPortIdentifierImpl.java:61) ~[?:?]

at org.openhab.binding.vallox.internal.se.connection.ValloxSerialConnector.connect(ValloxSerialConnector.java:65) ~[?:?]

... 9 more

2020-04-28 13:57:55.447 [hingStatusInfoChangedEvent] - 'vallox:se-serial:upstairs' changed from OFFLINE (COMMUNICATION_ERROR): Ack byte not received for telegram: 01-25-11-29-1F-7F to OFFLINE (COMMUNICATION_ERROR): Port in use

@Sebastian_Neu I pushed two separate fixes. As soon as the build finishes you can download the new version from the link above.

So far it seems to be working now.

1 Like