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: JFrog
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?
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
In the past I used to install it via Marketplace, but that’s not possible anymore, is it?
I tried to install the above version (copy it to the addon directory) but I get an error message:
2020-12-02 15:33:34.675 [WARN ] [org.apache.felix.fileinstall ] - Error while starting bundle: file:/usr/share/openhab/addons/org.openhab.binding.vallox-2.5.5-SNAPSHOT.jar
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.vallox [257]
Unresolved requirement: Import-Package: org.eclipse.smarthome.core.common
at org.eclipse.osgi.container.Module.start(Module.java:444) ~[org.eclipse.osgi-3.12.100.jar:?]
at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:383) ~[org.eclipse.osgi-3.12.100.jar:?]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundle(DirectoryWatcher.java:1260) [bundleFile:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundles(DirectoryWatcher.java:1233) [bundleFile:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:520) [bundleFile:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:365) [bundleFile:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:316) [bundleFile:3.6.4]
In OH3 I only find the ValloxMV binding. This is for newer systems that are accessible via Ethernet. I need the Vallox SE binding which can be accessed via the serial interface.
@gitMiguel Hi Miika have you been able to make it work with OH3?
I would be willing to test it (I noticed you asked for someone at times) but have a couple hardware beginner questions first.
I have a MV model available for testing (also controlled via the valloxmv binding). It has a connection box like below
I also have an USB RS485 adapter that I believe (but do not know for sure, never used it) I can connect there.
It has two wires only and identifies as a Bus 001 Device 005: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter
I connected the right hand side RS_A and RS_B to the adapter (it has 2 wire inputs labelled A and B).
OH and binding are configure and the thing is up but nothing works.
When I do smarthome:send FanSpeed 2 to the FanSpeed channel for a test I get
2021-03-01 13:48:29.572 [DEBUG] [al.se.connection.ValloxBaseConnector] - Wrote 01-21-11-29-03-5F
2021-03-01 13:48:30.075 [DEBUG] [al.se.connection.ValloxBaseConnector] - Wrote 01-21-11-29-03-5F
2021-03-01 13:48:30.578 [DEBUG] [al.se.connection.ValloxBaseConnector] - Wrote 01-21-11-29-03-5F
2021-03-01 13:48:31.080 [DEBUG] [al.se.connection.ValloxBaseConnector] - Wrote 01-21-11-29-03-5F
2021-03-01 13:48:31.583 [DEBUG] [al.se.connection.ValloxBaseConnector] - Wrote 01-21-11-29-03-5F
2021-03-01 13:48:32.086 [DEBUG] [.internal.se.handler.ValloxSEHandler] - Reconnecting after error: Ack byte not received for telegram: 01-21-11-29-03-5F
and the thing drops offline and reconnects.
At times (some interval presumably) I’m seeing
2021-03-01 13:49:39.101 [DEBUG] [.internal.se.handler.ValloxSEHandler] - Refreshing channels:
[FAN_SPEED, FAN_SPEED_MAX, FAN_SPEED_MIN, SELECT, PROGRAM_2, HUMIDITY, FLAGS_4]
2021-03-01 13:49:39.162 [DEBUG] [al.se.connection.ValloxBaseConnector] - Wrote 01-21-11-00-29-5C
2021-03-01 13:49:39.665 [DEBUG] [al.se.connection.ValloxBaseConnector] - Wrote 01-21-11-00-A5-D8
2021-03-01 13:49:40.168 [DEBUG] [al.se.connection.ValloxBaseConnector] - Wrote 01-21-11-00-A9-DC
2021-03-01 13:49:40.671 [DEBUG] [al.se.connection.ValloxBaseConnector] - Wrote 01-21-11-00-A3-D6
2021-03-01 13:49:41.174 [DEBUG] [al.se.connection.ValloxBaseConnector] - Wrote 01-21-11-00-B5-E8
2021-03-01 13:49:41.677 [DEBUG] [al.se.connection.ValloxBaseConnector] - Wrote 01-21-11-00-2A-5D
2021-03-01 13:49:42.180 [DEBUG] [al.se.connection.ValloxBaseConnector] - Wrote 01-21-11-00-6F-A2
I assume the serial connection is not properly working yet.
On a sidenote: I ultimately will want to control 3 units.
Does anyone know if I can daisy chain the RS_A and RS_B ports ? If so, how do I set the RS485 addresses of a unit ?
Could anyone to read this thread please tell me how to debug serial communication ?
I noticed I didn’t/ didn’t have to set serial parameters such as baud rate.
Also, to restate, this is a MV unit which is already accessible via modbus/TCP and I’m trying to
connect via serial in addition to this.
Does the binding support this (there was a mention of MV support being dropped) ?
On my box, I have not seen any configuration option about RS485 I would need to enable or set.
What did I miss ?
