Hello everybody.
I still use the eBus binding in the old OpenHAB version.
I am currently switching to OH3 ( openHAB 3.0.1 ).
When I copy the “org.openhab.binding.ebus-3.0.11.kar” into the “openHAB-addons” folder and restart, I cannot find that under binding add-ons to install.
Am I doing something wrong?
Is the binding working after that error? Do you have used a FTDI buffer setting under Linux that is now not set anymore?
The slave answer you receive (9bytes) is much longer than in your config (2bytes). So this command is not correct for your device.
Do you really used the Kar file? Please check “bundle:list” and “feature:list”
Thanks for the fast information. I acted too stupid.
I found the mistake.
The beindingt doesn’t work after the error and i don’t use FTDI buffer settings, but i switched from the default driver to jserialcomm and it seems to work.
Thanks for answer! I’m trying to migrate from 1.x version, where it was unimportant. Find how to fix it in your configuration files.
Another question: In 1.x binding version we can provide different method for get and set:
{ ebus="id:circuits.getParameters.dayTemp, dst:50, set:circuits.set_DayTemp.value" }
Can we do something like this in new binding? I have a method, that provide a lot information about circuit:
{
"label": "Get circuit parameters",
"id": "mc.get_parameters",
"command": "B5 04",
"get": {
"master": [
{"type": "static", "default": "09"}
],
"slave": [
{"name": "day_temp", "type":"uchar", "label": "Day temperature"},
{"name": "night_temp", "type": "uchar", "label": "Night temperature"},
{"name": "heating_curve", "type": "uint", "label": "Heating curve", "factor": 0.01, "min": 0.1, "max": 4.0},
{"name": "circuit_type", "type": "uchar", "label": "Circuit type", "mapping": {"128": "Disabled", "129": "Mixing circuit", "130": "Fixed value", "131": "Cylinder circuit", "132": "Increase in return flow", "133": "Direct circuit"}},
{"name": "ot_shutdown_limit", "type": "uchar", "label": "Max limit outs. temp"},
{"name": "pump_delay", "type": "uchar", "label": "Pump delay time"},
{"name": "min_temp", "type": "uchar", "label": "Minimum temp"},
{"name": "max_temp", "type": "uchar", "label": "Maximum temp"},
{"name": "_unknown2", "type": "bytes", "length": "1"}
]
}
}
But for setting every parameter I need to use separate methods:
{
"label": "Circuit heating curve",
"id": "mc.heating_curve",
"command": "B5 09",
"template": [
{"name": "heating_curve", "type": "uchar", "label": "Heating Curve"}
],
"get": {
"master": [
{"type": "static", "default": "0D 35 00"}
],
"slave": [
{"type": "template-block"}
]
},
"set": {
"master": [
{"type": "static", "default": "0E 35 00"},
{"type": "template-block"}
]
}
}
etc....
Hello!
First of all, thanks a lot for all the efforts to make the new binding work!
Do you have any idea why this works (‘resolved’ file):
2021-02-23 20:54:00;"FF";"50";"B5 13";"03 04 22 00 F4 00 0A 22 00 32 00 00 00 00 00 00 00 97 00 AA";GET > custom-50.custom.podlogowe_zadana
with the config:
{
"label": "Temperatura podlogowego zadana",
"id": "custom.podlogowe_zadana",
"command": "B5 13",
"get": {
"master": [
{"name":"block_number", "type": "static", "default": "04 22 00"}
],
"slave": [
{"name":"dummy1", "type": "byte"},
{"name":"dummy2", "type": "byte"},
{"name":"podlogowe_obecna", "type": "data1c", "label": "Podlogowe zadana (°C)", "min":0, "max":100, "format":"%.1f°C"},
{"name":"dummy3", "type": "bytes", "length": 7}
]
}
},
… but this doesn’t (‘unresolved’ file)?
2021-02-23 20:52:14;"FF";"50";"B5 13";"03 04 15 00 55 00 0A 15 00 19 00 0A 00 90 01 78 00 C7 00 AA";
with the config:
{
"label": "Podlogowe krzywa grzewcza",
"id": "custom.podlogowe_krzywa",
"command": "B5 13",
"get": {
"master": [
{"name":"block_number", "type": "static", "default": "04 15 00"}
],
"slave": [
{"name":"dummy1", "type": "byte"},
{"name":"dummy2", "type": "byte"},
{"name":"podlogowe_krzywa", "type": "data1b", "label": "Krzywa grzewcza podlogowego", "factor" : 0.01},
{"name":"dummy3", "type": "bytes", "length": 7}
]
}
}
TRACE says:
2021-02-23 20:52:12.594 [TRACE] [ng.ebus.internal.handler.EBusHandler] - Poll command "ebus:custom-50:e7be1e28dd:b023838bf2:custom-50_custom_podlogowe-krzywa#podlogowe-krzywa" with "FF 50 B5 13 03 04 15 00 55" ...
2021-02-23 20:52:12.760 [TRACE] [s.internal.handler.EBusBridgeHandler] - Unknown telegram FF 50 B5 13 03 04 15 00 55 00 0A 15 00 19 00 0A 00 90 01 78 00 C7 00 AA
Mh, it looks good so far. No idea without checking the sources. Do you have some duplicates with the same id in your config?
@csowada I’ve changed all the IDs inside the Thing configuration - the result is the same.
BTW: the 2 Vaillant things provided with the binding throw an **HANDLER_INITIALIZING_ERROR** can't parse argument number: error that I was not able to debug either. Not sure if that can affect other Things, anyway disabling them doesn’t help with the original issue.
Hi! I need help to get it working with the following set-up:
openHAB 2.5.10 (openhabian) on raspberry pi
eBUS-Adapter 3 (from FHEM forum) connected to same raspberry pi via USB
eBUS Binding 2.50.11
ebusd installed and working.
ebusd starting parameters:
EBUSD_OPTS="--scanconfig --accesslevel=* --latency=20000 -d enh:/dev/ttyUSB-eBus --loglevel=info --address=ff --enablehex -p 8888"
“ebusctl info” says:
version: ebusd 21.2.v21.2
access: *
signal: acquired
symbol rate: 23
max symbol rate: 119
min arbitration micros: 381
max arbitration micros: 758
min symbol latency: 11
max symbol latency: 22
reconnects: 0
masters: 4
messages: 604
conditional: 49
poll: 0
update: 10
address 03: master #11
address 04: slave #25, ebusd
address 08: slave #11, scanned "MF=Vaillant;ID=HMU00;SW=0305;HW=0403", loaded "vaillant/08.hmu.csv"
address 10: master #2
address 15: slave #2, scanned "MF=Vaillant;ID=70000;SW=0209;HW=4103", loaded "vaillant/15.700.csv"
address 71: master #9
address 76: slave #9, scanned "MF=Vaillant;ID=VWZ00;SW=0305;HW=0403"
address e0: slave, scanned "MF=Vaillant;ID=OMU00;SW=0131;HW=5202", loaded "vaillant/e0.omu.csv"
address ff: master #25, ebusd
As you can see, ebusd is working and scanned the bus-devices. I am able to read and write values via ebusctl. The Problem starts, when I add a eBus Bridge in openhab. After that ebusctl is getting unresponsive. ebusctl info, find is not reacting anymore. At reads and writes I get no answer or errors. The eBus Bridge itselfs gets the state “online”. But I am not able to discover any eBus devices via PaperUI
In the log I found things like:
2021-03-12 19:50:43.888 [WARN ] [ev.ebus.core.EBusReceiveStateMachine] - Input buffer full, reset!
2021-03-12 19:50:43.894 [DEBUG] [s.internal.handler.EBusBridgeHandler] - eBUS telegram error; Input buffer full, reset! [ERROR: BUFFER_FULL, DATA: 10 75 00 C6 C6 10 07 04 00 C6 C6 C6 C6 10 C6 01 C6 09 40 4E C7 00 C6 C6 C6 C6 76 01 09 40 4E 68 C6 C6 C6 76 03 01 07 00 11 00 C6 C6 C6 08 09 00 C7 07]
2021-03-12 19:50:50.331 [DEBUG] [s.internal.handler.EBusBridgeHandler] - eBUS telegram error; Telegram starts with an invalid source address! C6 [ERROR: INVALID_SOURCE_ADDRESS, DATA: 10 75 00 C6 C6 10 07 04 00 C6 C6 C6 C6 10 C6 01 C6 09 40 4E C7 00 C6 C6 C6 C6 76 01 09 40 4E 68 C6 C6 C6 76 03 01 07 00 11 00 C6 C6 C6 08 09 00 C7 07]
2021-03-12 14:51:07.797 [DEBUG] [s.internal.handler.EBusBridgeHandler] - eBUS telegram error; Master CRC invalid! IS:84 SHOULD:00 [ERROR: MASTER_CRC_INVALID, DATA: 10 C6 C6 03 03 00 C6 04 00]
Can Anybody Help
I found out what is the problem: The new ebus adapter 3 supports an enhanced and a standard protocol. Default is “enhanced”. I now changed this to standard (via jumper) and openhab is now communicating with my ebus und device discovery is working.
Hello csowada and openhab ebus profis,
I’m playing now for days to get openhab working with my Vaillant heat pump (geoTHERM VWS 141/2). Main goal is to monitor and visualize several heating parameters of my house.
My setup:
ebus Adapter: “eBUS Adapter 3” from the ebusd team (many thanks to them) with Wifi Wemo
Rasp with newest version of openhab 2.5
On this rasp there is also ebusd running and this is working so far.
ebusd start parameter:
EBUSD_OPTS=“-d enh:10.0.0.184:9999 --scanconfig”
Here the ebusd info printout:
version: ebusd 21.2.v21.2
update check: OK
signal: acquired
symbol rate: 52
max symbol rate: 437
min arbitration micros: 4
max arbitration micros: 6437
min symbol latency: 0
max symbol latency: 54
reconnects: 0
masters: 4
messages: 529
conditional: 168
poll: 2
update: 59
address 03: master #11
address 08: slave #11, scanned "MF=Vaillant;ID=EHP00;SW=0344;HW=7201", loaded "vaillant/08.ehp.csv"
address 10: master #2
address 15: slave #2, scanned "MF=Vaillant;ID=UIH00;SW=0226;HW=6901", loaded "vaillant/15.uih.csv"
address 23: slave, scanned "MF=Vaillant;ID=EHP00;SW=0344;HW=7201", loaded "vaillant/23.ehp.cc.csv"
address 25: slave, scanned "MF=Vaillant;ID=EHP00;SW=0344;HW=7201", loaded "vaillant/25.ehp.hwc.csv"
address 31: master #8, ebusd
address 36: slave #8, ebusd
address 50: slave, scanned "MF=Vaillant;ID=EHP00;SW=0344;HW=7201"
address 70: master #4
address 75: slave #4, scanned "MF=Vaillant;ID=RC C ;SW=0321;HW=6201", loaded "vaillant/75.rcc.csv"
Openhab ebus binding 2.50.11
eBUS Bridge with ebusd as driver and local IP address and port 8888 to connect to ebusd. Bridge is online.
So good so far 
Now I have the first problem: in the PaperUI Inbox many “eBUS Standard” devices are appearing, but these I can’t use.
Okay, after this I started playing with config files and tried a very simple case. I want to decode the “status” message.
I created a file named “ehp.json” with following content and entered it in configurationUrl of binding config:
{
"id": "ehp",
"vendor": "Vaillant",
"label": "Vaillant Heat pump AMU",
"description": "Vaillant Heat pump",
"authors": [
"Ebusd File Converter"
],
"commands": [
{
"label": "Status",
"id": "status",
"command": "B5 11",
"get": {
"master": [
{"type":"static","default":"03"}
],
"slave": [
{"name":"temp","type":"data2b","label":"Temp"},
{"name":"press1","type":"data2b","label":"Press1"},
{"name":"press2","type":"data2b","label":"Press2"},
{"name":"hcmode2","type":"data2b","label":"hcmode2"},
{"name":"HEX","type":"byte","label":"HEX"}
]
}
}
]
}
after this I could manually add a thing of type “Vaillant Heat pump AMU” with slave address “08”, linked all channels to items but nothing happened.
I can see my status message in the “ebus-unresolved.csv”:
2021-03-17 16:36:34;“10”;“08”;“B5 11”;“01 03 8B 00 0A 8B 01 90 05 52 05 03 08 00 00 4C 00 AA”;
but I don’t know why, why is this message not resolving?
Any ideas what’s running wrong in my setup?
Or, are there any configs available which are working with my Vaillant heat pump?
Many, many thx
Joachim
I could be wrong, but the slave response is 10 bytes (0A) and you define 9 bytes: 4x data2b type and one byte type. Possibly it works if you define the last byte, which could be done by adding a
{"type":"byte"}
to the slave response in your json.
Hi all,
MANY THANKS to all for making this happen!!!
Currently upgrading from OH2 to OH3 and hence getting rid of six OH1 bindings, ebus1 being one of them. Can anybody tell when this binding will be officially released for OH3. Normally not shy to test beta releases, but I have enough problems currently with other stuff (like ekey and KNX).
Many thanks and best regards
Achim
Thx Chiuaua79, you are right that was the problem.
Hello,
thanks for the great work on this binding. It works quiet well.
One issue is left for me: I want to display the current error of my Vaillant heating. I get the value from ebusd
2021-03-21 10:52:45.197 [update notice] sent poll-read bai currenterror QQ=ff: -;-;-;-;-
but there is no item available which could store the value. Is there any fix available?
Yesterday I tried to install this binding. I put the 2.50.11 kar file in /usr/share/openhab2/addons/. Restarted OH 2.5.12, watched the logs and nothing happened. In PaperUI there is no sign of the addon (I can only install the old 1.14 version from the repository). When I’m on the console list -s |grep ebus displays nothing. When I run kar:list:
openhab> kar:list
KAR Name
────────────────────────────────
openhab-addons-2.5.12
org.openhab.binding.ebus-2.50.11
I’ve tried this on a Rpi model 1B (armhf, tried openHABian and raspbian) (Yeah I know, too old/slow, RPi4 is ordered) and virtual in my main OH lxd container (amd64). Both the same results.
I have a Esera USB coupler connected to the Rpi, not yet connected to the eBus. And in my container nothing connected. But I think the binding should be there even if I have nothing connected? Am I missing something?
feature:list shows:
x-openhab-binding-ebus │ 2.50.11 │ │ Uninstalled │ org.openhab.binding.ebus-2.50.11 │ eBUS Binding
UPDATE: After I cleaned the cache the binding is installed:
2021-03-28 11:58:27.143 [WARN ] [internal.things.EBusTypeProviderImpl] - eBUS command boiler.control.setopdata only contains a setter channel!
2021-03-28 11:58:27.162 [INFO ] [ing.ebus.internal.EBusHandlerFactory] - Use eBUS binding 2.50.11 [eBUS core: 1.1.5, eBUS configuration: 1.1.4]
2021-03-28 11:58:27.162 [INFO ] [ing.ebus.internal.EBusHandlerFactory] - eBUS core -> timestamp 202101311144, commit: #79c19b7, build-no: #null
2021-03-28 11:58:27.162 [INFO ] [ing.ebus.internal.EBusHandlerFactory] - eBUS configuration -> timestamp 202012271447, commit: #101042c, build-no: #null
Now waiting for my Rpi 4 to continue the journey.
Hi @csowada,
i just updated my openhab to version 3.1.0.M3. And now have the problem that the ebus binding can no longer be installed.
When I try it via the console I get the following error:
openhab> Feature:install x-openhab-binding-ebus
Error executing command: Unable to resolve root: missing requirement [root] osgi.identity; osgi.identity=x-openhab-biype=karaf.feature; version="[3.0.12.SNAPSHOT,3.0.12.SNAPSHOT]"; filter:="(&(osgi.identity=x-openhab-binding-ebus)(typre)(version>=3.0.12.SNAPSHOT)(version<=3.0.12.SNAPSHOT))" [caused by: Unable to resolve x-openhab-binding-ebus/3.0.12ssing requirement [x-openhab-binding-ebus/3.0.12.SNAPSHOT] osgi.identity; osgi.identity=org.openhab.binding.ebus; typ; version="[3.0.12.202102061921,3.0.12.202102061921]"; resolution:=mandatory [caused by: Unable to resolve org.openhas/3.0.12.202102061921: missing requirement [org.openhab.binding.ebus/3.0.12.202102061921] osgi.wiring.package; filterring.package=de.csdev.ebus.client)(version>=1.1.0)(!(version>=2.0.0)))" [caused by: Unable to resolve de.cs-dev.ebus…6: missing requirement [de.cs-dev.ebus.ebus-core/1.1.6] osgi.wiring.package; filter:="(&(osgi.wiring.package=org.apaang)(version>=2.6.0)(!(version>=3.0.0)))"]]]
I did the same steps as @stfn82 and got the same results. Except that the binding is no longer runs.
Do you happen to have any idea what the problem could be?
OK, so I’ve received my Pi4 and installed everything. Seems like everything is working, binding is finding a lot of things, but almost all without values. Only outside temp and date are displayed.
ebusctl i
version: ebusd 21.2.v21.2
update check: OK, broadcast.csv: different version available, memory.csv: different version available, vaillant/15.700.csv: different version available, vaillant/broadcast.csv: different version available, vaillant/errors.inc: different version available, vaillant/general.csv: different version available, vaillant/hcmode.inc: different version available
signal: acquired
symbol rate: 57
max symbol rate: 146
min arbitration micros: 648
max arbitration micros: 2718
min symbol latency: 4
max symbol latency: 9
reconnects: 0
masters: 4
messages: 558
conditional: 0
poll: 1
update: 10
address 03: master #11
address 08: slave #11, scanned "MF=Vaillant;ID=HMU00;SW=0313;HW=0403", loaded "vaillant/08.hmu.csv"
address 10: master #2
address 15: slave #2, scanned "MF=Vaillant;ID=70000;SW=0614;HW=6903", loaded "vaillant/15.700.csv"
address 31: master #8, ebusd
address 36: slave #8, ebusd
address 71: master #9
address 76: slave #9, scanned "MF=Vaillant;ID=VWZIO;SW=0111;HW=0103"
address ec: slave, scanned "MF=Vaillant;ID=SOL00;SW=0614;HW=6903", loaded "vaillant/ec.sol.sc.csv"
ebusctl scan result
08;Vaillant;HMU00;0313;0403;21;19;39;0010022462;0001;005140;N6
15;Vaillant;70000;0614;6903;21;20;17;0020171315;0082;011100;N9
76;Vaillant;VWZIO;0111;0103;21;20;09;0020117049;0082;005805;N7
ec;Vaillant;SOL00;0614;6903;21;20;17;0020171315;0082;011100;N9
sudo /usr/bin/ebusd --pidfile /var/run/ebusd.pid -d /dev/ttyUSB0 --enablehex --scanconfig=full -f -p 8888 --latency=100 -c /home/esera/ebusd-configuration/latest/en -l /var/log/ebusd.log
2021-04-03 15:26:46.471 [main notice] ebusd 21.2.v21.2 started with full scan on device /dev/ttyUSB0
2021-04-03 15:26:46.484 [bus notice] bus started with own address 31/36
2021-04-03 15:26:46.496 [bus notice] signal acquired
2021-04-03 15:26:46.521 [bus notice] new master 10, master count 2
2021-04-03 15:26:46.829 [bus notice] new master 03, master count 3
2021-04-03 15:26:46.829 [update notice] received unknown MS cmd: 1008b510090003ffff6eff070001 / 0101
2021-04-03 15:26:47.091 [bus notice] new master 71, master count 4
2021-04-03 15:26:47.091 [update notice] received unknown MS cmd: 1076b51009000000ffffff010000 / 0101
2021-04-03 15:26:51.566 [update notice] received unknown MS cmd: 7108b5110107 / 06643800038153
2021-04-03 15:26:52.563 [update notice] received unknown MS cmd: 7108b507030bffff / 0101
2021-04-03 15:26:53.696 [main notice] starting initial full scan
2021-04-03 15:26:57.717 [bus notice] scan 08: ;Vaillant;HMU00;0313;0403
2021-04-03 15:26:57.717 [update notice] store 08 ident: done
2021-04-03 15:26:57.717 [update notice] sent scan-read scan.08 QQ=31: Vaillant;HMU00;0313;0403
2021-04-03 15:26:57.717 [bus notice] scan 08: ;Vaillant;HMU00;0313;0403
2021-04-03 15:26:59.715 [main notice] read common config file vaillant/scan.csv
2021-04-03 15:26:59.715 [main notice] read common config file vaillant/general.csv
2021-04-03 15:26:59.717 [main notice] read common config file vaillant/broadcast.csv
2021-04-03 15:26:59.724 [main notice] read scan config file vaillant/08.hmu.csv for ID "hmu00", SW0313, HW0403
2021-04-03 15:26:59.727 [main notice] found messages: 61 (0 conditional on 0 conditions, 0 poll, 10 update)
2021-04-03 15:27:00.626 [update notice] sent unknown MS cmd: 3108b5090124 / 09003231313933393030
2021-04-03 15:27:01.337 [update notice] sent scan-read scan.08 id QQ=31:
2021-04-03 15:27:02.104 [update notice] sent scan-read scan.08 id QQ=31:
2021-04-03 15:27:05.475 [bus notice] scan 15: ;Vaillant;70000;0614;6903
2021-04-03 15:27:05.476 [update notice] store 15 ident: done
2021-04-03 15:27:05.477 [update notice] sent scan-read scan.15 QQ=31: Vaillant;70000;0614;6903
2021-04-03 15:27:05.477 [bus notice] scan 15: ;Vaillant;70000;0614;6903
2021-04-03 15:27:05.698 [update notice] sent scan-read scan.08 id QQ=31: 21;19;39;0010022462;0001;005140;N6
2021-04-03 15:27:05.699 [bus notice] scan 08: ;21;19;39;0010022462;0001;005140;N6
2021-04-03 15:27:07.018 [update notice] received unknown MS cmd: 1076b5110101 / 09ffff0080ff59000065
2021-04-03 15:27:08.237 [update notice] sent unknown MS cmd: 3115b5090124 / 09003231323031373030
2021-04-03 15:27:08.915 [update notice] sent scan-read scan.15 id QQ=31:
2021-04-03 15:27:09.695 [update notice] received read hmu State QQ=71: 100;56;3;heating_water
2021-04-03 15:27:10.364 [update notice] sent scan-read scan.15 id QQ=31:
2021-04-03 15:27:11.602 [update notice] received unknown BC cmd: 10feb505025c00
2021-04-03 15:27:12.269 [update notice] sent scan-read scan.15 id QQ=31: 21;20;17;0020171315;0082;011100;N9
2021-04-03 15:27:12.270 [bus notice] scan 15: ;21;20;17;0020171315;0082;011100;N9
2021-04-03 15:27:12.338 [main notice] read scan config file vaillant/15.700.csv for ID "70000", SW0614, HW6903
2021-04-03 15:27:12.339 [main notice] found messages: 481 (0 conditional on 0 conditions, 0 poll, 10 update)
2021-04-03 15:27:12.967 [update notice] received update-write hmu SetMode QQ=10: 3;-;-;110;1;1;1;1;0;0
2021-04-03 15:27:15.294 [bus notice] scan 76: ;Vaillant;VWZIO;0111;0103
2021-04-03 15:27:15.294 [update notice] store 76 ident: done
2021-04-03 15:27:15.295 [update notice] sent scan-read scan.76 QQ=31: Vaillant;VWZIO;0111;0103
2021-04-03 15:27:15.295 [bus notice] scan 76: ;Vaillant;VWZIO;0111;0103
2021-04-03 15:27:19.128 [main error] scan config 76: ERR: arbitration lost
2021-04-03 15:27:20.369 [update notice] received read hmu DateTime QQ=10: nosignal;-:-:-;-.-.-;13.062
2021-04-03 15:27:23.290 [update notice] received unknown MS cmd: 1008b507020900 / 025b03
2021-04-03 15:27:30.721 [main error] scan config 76: ERR: arbitration lost
2021-04-03 15:27:31.999 [update notice] received unknown MS cmd: 7108b507030bffff / 0101
2021-04-03 15:27:33.789 [update notice] received read hmu Status01 QQ=10: 52.0;49.5;13.062;-;-;hwc
2021-04-03 15:27:37.749 [update notice] received unknown MS cmd: 1076b5110101 / 09ffff0080ff5a000066
2021-04-03 15:27:42.547 [main error] scan config 76: ERR: arbitration lost
2021-04-03 15:27:43.693 [update notice] received unknown MS cmd: 1008b5110100 / 0945031c6400190001c8
2021-04-03 15:27:46.547 [update notice] received unknown MS cmd: 1076b512030f0202 / 07d002003003ff01
2021-04-03 15:27:51.431 [update notice] received update-write hmu SetMode QQ=10: 3;-;-;110;1;1;1;1;0;0
2021-04-03 15:27:52.089 [update notice] sent unknown MS cmd: 3176b5090124 / 09003231323030393030
2021-04-03 15:27:52.873 [update notice] sent scan-read scan.76 id QQ=31:
2021-04-03 15:27:55.778 [update notice] received read hmu State QQ=71: 100;57;3;heating_water
2021-04-03 15:27:56.335 [main error] scan config 76: ERR: arbitration lost
2021-04-03 15:28:02.557 [update notice] received read hmu Status01 QQ=10: 52.0;49.5;13.062;-;-;hwc
2021-04-03 15:28:05.330 [update notice] sent scan-read scan.76 id QQ=31:
2021-04-03 15:28:06.078 [update notice] sent scan-read scan.76 id QQ=31:
2021-04-03 15:28:07.907 [update notice] sent scan-read scan.76 id QQ=31:
2021-04-03 15:28:08.682 [update notice] sent scan-read scan.76 id QQ=31: 21;20;09;0020117049;0082;005805;N7
2021-04-03 15:28:08.683 [bus notice] scan 76: ;21;20;09;0020117049;0082;005805;N7
2021-04-03 15:28:08.686 [main error] unable to load scan config 76: no file from vaillant with prefix 76 found
2021-04-03 15:28:08.686 [main error] scan config 76: ERR: element not found
2021-04-03 15:28:13.112 [update notice] received read hmu State QQ=71: 100;57;3;heating_water
2021-04-03 15:28:24.429 [update notice] received read hmu State QQ=71: 100;57;3;heating_water
2021-04-03 15:28:26.172 [update notice] received update-write hmu SetMode QQ=10: 3;-;-;110;1;1;1;1;0;0
2021-04-03 15:28:33.215 [update notice] sent scan-read scan.76 QQ=31: Vaillant;VWZIO;0111;0103
2021-04-03 15:28:33.215 [bus notice] scan 76: ;Vaillant;VWZIO;0111;0103
2021-04-03 15:28:49.027 [update notice] received read hmu DateTime QQ=10: nosignal;-:-:-;-.-.-;13.062
2021-04-03 15:28:55.837 [update notice] received read hmu State QQ=71: 100;57;3;heating_water
2021-04-03 15:28:57.641 [update notice] received read hmu State QQ=71: 100;57;3;heating_water
2021-04-03 15:29:01.614 [update notice] received update-read broadcast vdatetime QQ=10: 15:29:33;03.04.2021
2021-04-03 15:29:04.472 [update notice] received read hmu Status01 QQ=10: 52.5;49.5;13.062;-;-;hwc
2021-04-03 15:29:14.962 [update notice] received read hmu State QQ=71: 100;57;3;heating_water
2021-04-03 15:29:17.285 [update notice] received read hmu State QQ=71: 100;57;3;heating_water
2021-04-03 15:29:26.004 [update notice] received read hmu State QQ=71: 100;57;3;heating_water
2021-04-03 15:29:33.689 [update notice] received update-write hmu SetMode QQ=10: 3;-;-;110;1;1;1;1;0;0
2021-04-03 15:29:36.491 [update notice] received read hmu State QQ=71: 100;57;3;heating_water
2021-04-03 15:29:42.154 [update notice] received read hmu State QQ=71: 100;57;3;heating_water
2021-04-03 15:29:44.932 [update notice] received unknown MS cmd: 1008b507020900 / 025a03
2021-04-03 15:29:47.795 [update notice] received read hmu DateTime QQ=10: nosignal;-:-:-;-.-.-;13.062
2021-04-03 15:29:51.622 [update notice] received read hmu Status01 QQ=10: 52.5;50.0;13.062;-;-;hwc
2021-04-03 15:29:59.813 [update notice] received unknown MS cmd: 1076b5110101 / 09ffff0080ff5a000066
2021-04-03 15:30:04.146 [update notice] received unknown MS cmd: 1008b5110100 / 094c031c6400190001c8
2021-04-03 15:30:09.167 [update notice] received unknown MS cmd: 1076b512030f0202 / 07d402003703ff01
2021-04-03 15:30:09.255 [update notice] received read hmu State QQ=71: 100;58;3;heating_water
2021-04-03 15:30:10.862 [main notice] update check: OK, broadcast.csv: different version available, memory.csv: different version available, vaillant/15.700.csv: different version available, vaillant/broadcast.csv: different version available, vaillant/errors.inc: different version available, vaillant/general.csv: different version available, vaillant/hcmode.inc: different version available
2021-04-03 15:30:12.058 [update notice] received update-write hmu SetMode QQ=10: 3;-;-;110;1;1;1;1;0;0
2021-04-03 15:30:21.782 [update notice] received read hmu State QQ=71: 100;58;3;heating_water
2021-04-03 15:30:21.896 [bus notice] scan ec: ;Vaillant;SOL00;0614;6903
2021-04-03 15:30:21.896 [update notice] store ec ident: done
2021-04-03 15:30:21.897 [update notice] sent scan-read scan.ec QQ=31: Vaillant;SOL00;0614;6903
2021-04-03 15:30:21.897 [bus notice] scan ec: ;Vaillant;SOL00;0614;6903
2021-04-03 15:30:26.404 [update notice] sent unknown MS cmd: 31ecb5090124 / 09003231323031373030
2021-04-03 15:30:30.239 [main error] scan config ec: ERR: arbitration lost
2021-04-03 15:30:35.732 [update notice] received unknown MS cmd: 1076b51303040d00 / 0a0d000100000003000300
2021-04-03 15:30:35.863 [update notice] received read hmu State QQ=71: 100;58;3;heating_water
2021-04-03 15:30:36.041 [update notice] received read hmu Status01 QQ=10: 52.5;50.0;13.062;-;-;hwc
2021-04-03 15:30:36.169 [update notice] received read hmu State QQ=71: 100;58;3;heating_water
2021-04-03 15:30:36.348 [update notice] received unknown MS cmd: 1076b5110101 / 09ffff0080ff5a000067
2021-04-03 15:30:36.476 [update notice] received read hmu State QQ=71: 100;58;3;heating_water
2021-04-03 15:30:36.660 [update notice] received read hmu DateTime QQ=10: nosignal;-:-:-;-.-.-;13.062
2021-04-03 15:30:36.787 [update notice] received read hmu State QQ=71: 100;58;3;heating_water
2021-04-03 15:30:36.980 [update notice] received unknown MS cmd: 1076b51303040d00 / 0a0d000100000003000300
2021-04-03 15:30:37.027 [bus notice] max. symbols per second: 141
2021-04-03 15:30:37.261 [update notice] received update-read broadcast vdatetime QQ=10: 15:30:34;03.04.2021
2021-04-03 15:30:37.376 [update notice] received unknown MS cmd: 7108b507030bffff / 0101
2021-04-03 15:30:37.555 [update notice] received unknown MS cmd: 1076b512030f0202 / 07d402003803ff01
2021-04-03 15:30:37.685 [update notice] received read hmu State QQ=71: 100;58;3;heating_water
2021-04-03 15:30:37.868 [update notice] received update-write hmu SetMode QQ=10: 3;-;-;110;1;1;1;1;0;0
2021-04-03 15:30:37.997 [update notice] received read hmu State QQ=71: 100;58;3;heating_water
2021-04-03 15:30:38.126 [update notice] received update-read broadcast outsidetemp QQ=10: 13.062
2021-04-03 15:30:38.256 [update notice] received read hmu State QQ=71: 100;58;3;heating_water
2021-04-03 15:30:38.375 [update notice] sent scan-read scan.ec id QQ=31:
2021-04-03 15:30:38.631 [update notice] sent scan-read scan.ec id QQ=31:
2021-04-03 15:30:38.838 [update notice] sent scan-read scan.ec id QQ=31:
2021-04-03 15:30:38.983 [update notice] received read hmu Status01 QQ=10: 52.5;50.0;13.062;-;-;hwc
2021-04-03 15:30:39.000 [bus notice] max. symbols per second: 158
2021-04-03 15:30:39.101 [update notice] sent scan-read scan.ec id QQ=31: 21;20;17;0020171315;0082;011100;N9
2021-04-03 15:30:39.101 [bus notice] scan ec: ;21;20;17;0020171315;0082;011100;N9
2021-04-03 15:30:39.114 [main notice] read scan config file vaillant/ec.sol.sc.csv for ID "sol00", SW0614, HW6903
2021-04-03 15:30:39.116 [main notice] found messages: 558 (0 conditional on 0 conditions, 1 poll, 10 update)
2021-04-03 15:30:39.286 [update notice] sent poll-read sc YieldThisYear QQ=31:
2021-04-03 15:30:39.943 [update notice] sent poll-read sc YieldThisYear QQ=31:
2021-04-03 15:30:40.626 [update notice] sent poll-read sc YieldThisYear QQ=31:
2021-04-03 15:30:40.810 [update notice] sent poll-read sc YieldThisYear QQ=31:
2021-04-03 15:30:41.579 [update notice] sent poll-read sc YieldThisYear QQ=31:
2021-04-03 15:30:41.769 [update notice] sent poll-read sc YieldThisYear QQ=31:
2021-04-03 15:30:41.942 [update notice] sent poll-read sc YieldThisYear QQ=31:
2021-04-03 15:30:42.599 [update notice] sent poll-read sc YieldThisYear QQ=31:
2021-04-03 15:30:43.388 [update notice] sent poll-read sc YieldThisYear QQ=31:
2021-04-03 15:30:43.528 [update notice] sent poll-read sc YieldThisYear QQ=31:
2021-04-03 15:30:43.718 [update notice] sent poll-read sc YieldThisYear QQ=31:
2021-04-03 15:30:43.838 [update notice] received unknown MS cmd: 1008b507020900 / 025a03
2021-04-03 15:30:43.936 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f58 / 00: ERR: invalid position
2021-04-03 15:30:44.211 [update notice] received update-write hmu SetMode QQ=10: off;0.0;-;-;0;1;1;1;0;0
2021-04-03 15:30:44.340 [update notice] received read hmu State QQ=71: 100;58;3;heating_water
2021-04-03 15:30:44.530 [update notice] received unknown MS cmd: 1076b51303040d00 / 0a0d000100000003000300
2021-04-03 15:30:44.659 [update notice] received read hmu State QQ=71: 100;58;3;heating_water
2021-04-03 15:30:44.804 [update notice] received update-write hmu StatusCirPump QQ=10: on
2021-04-03 15:30:44.933 [update notice] received read hmu State QQ=71: 100;58;3;heating_water
2021-04-03 15:30:45.083 [update notice] received unknown MS cmd: 1008b5120204ff / 0101
2021-04-03 15:30:45.182 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f00 / 00: ERR: invalid position
2021-04-03 15:30:45.370 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f08 / 00: ERR: invalid position
2021-04-03 15:30:46.027 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f10 / 00: ERR: invalid position
2021-04-03 15:30:46.706 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f18 / 00: ERR: invalid position
2021-04-03 15:30:46.894 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f20 / 00: ERR: invalid position
2021-04-03 15:30:47.036 [update notice] received read hmu Status01 QQ=10: 52.5;50.0;13.062;-;-;off
2021-04-03 15:30:47.308 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f28 / 00: ERR: invalid position
2021-04-03 15:30:47.454 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f30 / 00: ERR: invalid position
2021-04-03 15:30:48.162 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f38 / 00: ERR: invalid position
2021-04-03 15:30:48.351 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f40 / 00: ERR: invalid position
2021-04-03 15:30:49.008 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f48 / 00: ERR: invalid position
2021-04-03 15:30:49.711 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f50 / 00: ERR: invalid position
2021-04-03 15:30:49.898 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f58 / 00: ERR: invalid position
2021-04-03 15:30:49.983 [update notice] received unknown BC cmd: 10feb510020600
2021-04-03 15:30:50.112 [update notice] received read hmu State QQ=71: 0;58;on;heating_water
2021-04-03 15:30:50.295 [update notice] received update-write hmu SetMode QQ=10: off;0.0;-;-;0;1;1;1;0;0
2021-04-03 15:30:50.424 [update notice] received read hmu State QQ=71: 0;58;on;heating_water
2021-04-03 15:30:50.600 [update notice] received unknown MS cmd: 1076b51009000000ffffff010000 / 0101
2021-04-03 15:30:50.727 [update notice] received read hmu State QQ=71: 0;58;on;heating_water
2021-04-03 15:30:51.010 [update notice] received read hmu State QQ=71: 0;58;on;heating_water
2021-04-03 15:30:51.107 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f00 / 00: ERR: invalid position
2021-04-03 15:30:51.764 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f08 / 00: ERR: invalid position
2021-04-03 15:30:52.448 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f10 / 00: ERR: invalid position
2021-04-03 15:30:52.634 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f18 / 00: ERR: invalid position
2021-04-03 15:30:53.291 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f20 / 00: ERR: invalid position
2021-04-03 15:30:53.973 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f28 / 00: ERR: invalid position
2021-04-03 15:30:54.158 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f30 / 00: ERR: invalid position
2021-04-03 15:30:54.927 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f38 / 00: ERR: invalid position
2021-04-03 15:30:55.115 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f40 / 00: ERR: invalid position
2021-04-03 15:30:55.288 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f48 / 00: ERR: invalid position
2021-04-03 15:30:55.945 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f50 / 00: ERR: invalid position
2021-04-03 15:30:56.644 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f58 / 00: ERR: invalid position
2021-04-03 15:30:56.890 [update notice] received read hmu State QQ=71: 0;58;on;ready
2021-04-03 15:30:57.030 [update notice] received read hmu Status01 QQ=10: 52.5;50.0;13.062;-;-;off
2021-04-03 15:30:57.126 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f00 / 00: ERR: invalid position
2021-04-03 15:30:57.783 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f08 / 00: ERR: invalid position
2021-04-03 15:30:58.502 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f10 / 00: ERR: invalid position
2021-04-03 15:30:58.646 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f18 / 00: ERR: invalid position
2021-04-03 15:30:58.830 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f20 / 00: ERR: invalid position
2021-04-03 15:30:59.026 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f28 / 00: ERR: invalid position
2021-04-03 15:30:59.684 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f30 / 00: ERR: invalid position
2021-04-03 15:31:00.384 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f38 / 00: ERR: invalid position
2021-04-03 15:31:00.578 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f40 / 00: ERR: invalid position
2021-04-03 15:31:01.236 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f48 / 00: ERR: invalid position
2021-04-03 15:31:01.506 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f50 / 00: ERR: invalid position
2021-04-03 15:31:02.163 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f58 / 00: ERR: invalid position
2021-04-03 15:31:02.392 [update notice] received read hmu State QQ=71: 0;58;on;ready
2021-04-03 15:31:02.568 [update notice] received unknown MS cmd: 1076b51009000000ffffff010000 / 0101
2021-04-03 15:31:02.696 [update notice] received read hmu State QQ=71: 0;58;on;ready
2021-04-03 15:31:02.880 [update notice] received read hmu DateTime QQ=10: nosignal;-:-:-;-.-.-;13.062
2021-04-03 15:31:02.996 [update notice] received unknown MS cmd: 7108b507030bffff / 0101
2021-04-03 15:31:03.139 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f00 / 00: ERR: invalid position
2021-04-03 15:31:03.312 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f08 / 00: ERR: invalid position
2021-04-03 15:31:03.496 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f10 / 00: ERR: invalid position
2021-04-03 15:31:04.243 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f18 / 00: ERR: invalid position
2021-04-03 15:31:04.408 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f20 / 00: ERR: invalid position
2021-04-03 15:31:04.594 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f28 / 00: ERR: invalid position
2021-04-03 15:31:04.736 [update notice] received unknown MS cmd: 1008b5110100 / 0936031c000008000100
2021-04-03 15:31:04.834 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f30 / 00: ERR: invalid position
2021-04-03 15:31:04.980 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f38 / 00: ERR: invalid position
2021-04-03 15:31:05.637 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f40 / 00: ERR: invalid position
2021-04-03 15:31:05.846 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f48 / 00: ERR: invalid position
2021-04-03 15:31:05.992 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f50 / 00: ERR: invalid position
2021-04-03 15:31:06.224 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f58 / 00: ERR: invalid position
2021-04-03 15:31:06.409 [update notice] received read hmu Status01 QQ=10: 49.5;40.5;13.062;-;-;off
2021-04-03 15:31:06.673 [update notice] received unknown MS cmd: 1076b5110101 / 09ffff0080ff5a000066
2021-04-03 15:31:06.938 [update notice] received unknown MS cmd: 1076b512030f0201 / 07d502003003ff01
2021-04-03 15:31:07.932 [update notice] received update-write hmu SetMode QQ=10: off;0.0;-;-;0;1;1;1;0;0
2021-04-03 15:31:08.101 [update notice] received read hmu State QQ=71: 0;58;on;ready
2021-04-03 15:31:08.233 [update notice] received unknown MS cmd: 1076b51009000000ffffff010000 / 0101
2021-04-03 15:31:09.148 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f00 / 00: ERR: invalid position
2021-04-03 15:31:09.294 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f08 / 00: ERR: invalid position
2021-04-03 15:31:09.439 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f10 / 00: ERR: invalid position
2021-04-03 15:31:09.585 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f18 / 00: ERR: invalid position
2021-04-03 15:31:09.731 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f20 / 00: ERR: invalid position
2021-04-03 15:31:09.877 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f28 / 00: ERR: invalid position
2021-04-03 15:31:10.023 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f30 / 00: ERR: invalid position
2021-04-03 15:31:10.169 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f38 / 00: ERR: invalid position
2021-04-03 15:31:10.315 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f40 / 00: ERR: invalid position
2021-04-03 15:31:10.461 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f48 / 00: ERR: invalid position
2021-04-03 15:31:10.607 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f50 / 00: ERR: invalid position
2021-04-03 15:31:10.751 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f58 / 00: ERR: invalid position
2021-04-03 15:31:15.175 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f00 / 00: ERR: invalid position
2021-04-03 15:31:15.321 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f08 / 00: ERR: invalid position
2021-04-03 15:31:15.468 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f10 / 00: ERR: invalid position
2021-04-03 15:31:15.613 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f18 / 00: ERR: invalid position
2021-04-03 15:31:15.757 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f20 / 00: ERR: invalid position
2021-04-03 15:31:15.902 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f28 / 00: ERR: invalid position
2021-04-03 15:31:16.047 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f30 / 00: ERR: invalid position
2021-04-03 15:31:16.703 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f38 / 00: ERR: invalid position
2021-04-03 15:31:17.410 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f40 / 00: ERR: invalid position
2021-04-03 15:31:17.600 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f48 / 00: ERR: invalid position
2021-04-03 15:31:18.257 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f50 / 00: ERR: invalid position
2021-04-03 15:31:18.453 [update error] unable to parse poll-read sc YieldThisYear from 31ecb509030d3f58 / 00: ERR: invalid position
2021-04-03 15:31:18.679 [update notice] received unknown MS cmd: 1076b512030f0201 / 07d50200e002ff01
2021-04-03 15:31:19.210 [update notice] received unknown MS cmd: 1076b51009000000ffffff010000 / 0101
2021-04-03 15:31:20.871 [update notice] received unknown MS cmd: 7108b507030bffff / 0101
Where [main error] unable to load scan config 76: no file from vaillant with prefix 76 found probably indicates I should write my own config file.
After reading some issues on the ebus github I came up with this script to read all known values:
#!/bin/bash
echo "Reading all known eBUS values."
for i in $( /usr/bin/ebusctl f -F name ); do
echo "Reading value for:" $i
/usr/bin/ebusctl r $i
done
echo "Finished reading values."
Now I atleast see some of the items I also see in my thermostat. Shouldn’t the binding read those values @csowada ?
Hardware:
geoTHERM 3 kW (VWS 36/4.1 230V) heatpump connected to a Volthera PVT system.
VWZ MEH60 6kW post heater (400V)
VRC700
Esera usb coupler on Rpi4
Binding (OH 2.5.12 with 2.50.11 binding) configured to connect to ebus daemon over the network. Ebus running with:
sudo /usr/bin/ebusd --pidfile /var/run/ebusd.pid -d /dev/ttyUSB0 --enablehex --scanconfig=full -f -p 8888 --latency=100 -c /home/esera/ebusd-configuration/latest/en -l /var/log/ebusd.log