It was my mistake, i haven’t mosquito installed, but the error ebusd: command not found persist
> ebusd --foreground --mqtthost=core-mosquitto --mqttport=1883 --mqttuser=addons --mqttpass=Ooch7oodae1ohthahboh0bahp0awieXiequ9wang4Shue1uboofiezu0Eeraijio --scanconfig --mqttjson --mqttint=/etc/ebusd/mqtt-hassio.cfg --mqtttopic=ebusd --device=udp:192.168.1.145:3333 --log=all:notice
Uninstall the addon and then reinstall. That should fix it
Nothing special
Blockquote
2022-11-17 07:17:00.321 [network info] [00584] client connection opened 172.30.32.2
2022-11-17 07:19:00.329 [network info] [00585] connection closed
i install the log is:
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[20:37:14] WARNING: USB and network device defined. Only one device can be used at a time.
[20:37:14] WARNING: Ignoring USB device…
ebusd --foreground --mqtthost=core-mosquitto --mqttport=1883 --mqttuser=addons --mqttpass=yur8Fu4ohceiva1aigoojung7ohg1yahceFado3oow4uzah6ahxee2eu7oobiejo --scanconfig --mqttjson --latency=10000 --mqttint=/etc/ebusd/mqtt-hassio.cfg --mqtttopic=ebusd --device=enh:192.168.0.54:3333 --log=all:notice
2022-11-17 20:37:19.497 [main notice] ebusd 22.4.v3.16.2-200-ga8ca21f541 started with auto scan on enhanced device 192.168.0.54:3333
2022-11-17 20:37:21.802 [bus notice] device status: resetting
2022-11-17 20:37:21.804 [bus notice] bus started with own address 31/36
2022-11-17 20:37:21.806 [bus notice] signal acquired
2022-11-17 20:37:21.823 [mqtt notice] connection established
2022-11-17 20:37:21.838 [bus error] device status: unexpected available enhanced following byte 1
2022-11-17 20:37:21.842 [bus error] device status: unexpected available enhanced following byte 1
2022-11-17 20:37:21.846 [bus error] device status: unexpected available enhanced following byte 1
2022-11-17 20:37:21.868 [bus error] device status: unexpected available enhanced following byte 1
2022-11-17 20:37:21.877 [bus error] device status: unexpected available enhanced byte 2
2022-11-17 20:37:21.906 [bus error] device status: unexpected available enhanced following byte 1
2022-11-17 20:37:21.913 [bus error] device status: unexpected available enhanced following byte 1
2022-11-17 20:37:21.916 [bus error] device status: unexpected available enhanced following byte 1
now work change 
change:
enh:[192.168.0.54:3333]
to:
[192.168.0.54:3333]
NOW CAN I FOUND CORRECT SENSOR?
I’ve installed this ‘Add-on’… All seems to be O.K.
Just one question - what is the meaning of error: ‘ERR: element not found’ ?
I have no idea…
2022-11-19 13:02:50.208 [main error] error reading templates in vaillant: ERR: element not found, last error: vaillant/_templates.csv:46: ERR: element not found, field type TEMP in field 0
2022-11-19 13:02:50.213 [main notice] read scan config file vaillant/08.bai.csv for ID "bai00", SW1410, HW6701
2022-11-19 13:02:50.216 [main error] error resolving conditions: ERR: element not found, last error: condition scan id: message not found, condition scan id: message not found, condition scan id: message not found, condition scan id: message not found, condition scan id: message not found, condition scan id: message not found, condition scan id: message not found, condition scan id: message not found, condition scan id: message not found, condition scan id: message not found, condition scan id: message not found, condition scan id: message not found, condition scan id: message not found, condition scan id: message not found, condition scan id: message not found, condition scan id: message not found, condition scan id: message not found
2022-11-19 13:02:50.223 [main error] error executing instructions: ERR: element not found, last error: error resolving condition for "08.bai": ERR: element not found condition scan id: message not founderror resolving condition for "08.bai": ERR: element not found condition scan id: message not founderror resolving condition for "08.bai": ERR: element not found condition scan id: message not founderror resolving condition for "08.bai": ERR: element not found condition scan id: message not founderror resolving condition for "08.bai": ERR: element not found condition scan id: message not founderror resolving condition for "08.bai": ERR: element not found condition scan id: message not founderror resolving condition for "08.bai": ERR: element not found condition scan id: message not founderror resolving condition for "08.bai": ERR: element not found condition scan id: message not founderror resolving condition for "08.bai": ERR: element not found condition scan id: message not founderror resolving condition for "08.bai": ERR: element not found condition scan id: message not founderror resolving condition for "08.bai": ERR: element not found condition scan id: message not founderror resolving condition for "08.bai": ERR: element not found condition scan id: message not founderror resolving condition for "08.bai": ERR: element not found condition scan id: message not founderror resolving condition for "08.bai": ERR: element not found condition scan id: message not founderror resolving condition for "08.bai": ERR: element not found condition scan id: message not founderror resolving condition for "08.bai": ERR: element not found condition scan id: message not found, error loading "vaillant/bai.0010003886.inc" for "08": ERR: element not found vaillant/bai.0010003886.inc:8: ERR: element not found, field type POWER in field 0, error including "vaillant/hcmode.inc" for "08": ERR: element not found vaillant/hcmode.inc:4: ERR: element not found, field type DCFSTATE in field 0
2022-11-19 13:02:50.225 [main notice] found messages: 1 (0 conditional on 26 conditions, 0 poll, 0 update)
2022-11-19 13:02:50.226 [main info] scan config 08 message received
Thanks a lot, now it works and i can read data from my Vaillant ecoTec heater
Seems to be a problem resolving / loading the configuration files.
If you have custom config files set up, check if the path is correct and the files are there
if you have not set up a custom config file location, they should be loaded from GitHub dynamically. in that case check the internet connection.
Hi
Anybody know how by this adapter activate on Vaillant QUICK MODE ? It is one load and water heating
And can anybody write manual how controll and change value by MQTT on autodiscovery ? Example when i want turn on or off water pump or change temp on room desired thermostat ?Please
hi @pepeEL,
what can be written to the ebus (changing temperature for example) is defined in the ebusd config files. By default a scan is done on the ebus to identify your hardware its software and their respective versions and revisions. then matching config files are loaded from GitHub - john30/ebusd-configuration: ebusd configuration files
Again, these config files define what can be read from and written to the ebus via ebusd.
you can also create your own config files and load them instead of using the default from GitHub, by setting custom config files path in add-on settings.
ok ebus scan my hardware and show me in integration MQTT in HA sevice name ebusd bai, or ebusd 700, ebusd broadcast and ebusd vr_71. WHen i go to ebai i see entities showing like temp and other parameters. But how i can control and setup temperature in room or change state example for zone 1 from auto to day or OFF ? In mqtt no found entities like thermostat.
See “set” in 3.3. MQTT client · john30/ebusd Wiki · GitHub on the specification for how to set values via ebusd
See MQTT - Home Assistant to see how to send values via mqtt from homeassistant
OK but for example in MQTT EXplorer show me more infor than in MQTT HA… Example MQTT explorer show me ebusd 700 - waterpressure but in HA on MQTT i dont see it.
Hi, i’m also struggling to get the climate card/sensor correct. I’m getting live data via the ebusd daemon. I see 5 devices and a lot of entities in the mqtt integration.
I can also display some entities from ebus and see them updating. So far, so good.
mqtt:
climate:
- name: CV keuken
max_temp: 25
min_temp: 15
precision: 0.1
temp_step: 0.5
modes:
- auto
- heat
- cool
- 'off'
mode_state_template: >-
{% set values = { 'auto':'auto', 'on':'heat', 'night':'cool', 'summer':'off'} %}
{{ values[value] if value in values.keys() else 'off' }}
mode_state_topic: "ebusd/470/Hc1OPMode"
mode_command_template: >-
{% set values = { 'auto':'auto', 'heat':'on', 'cool':'night', 'off':'summer'} %}
{{ values[value] if value in values.keys() else 'auto' }}
mode_command_topic: "ebusd/470/Hc1OPMode/set"
temperature_state_topic: "ebusd/470/DisplayedHc1RoomTempDesired"
temperature_low_state_topic: "ebusd/470/Hc1NightTemp"
temperature_high_state_topic: "ebusd/470/Hc1DayTemp"
temperature_low_command_topic: "ebusd/470/Hc1NightTemp/set"
temperature_high_command_topic: "ebusd/470/Hc1DayTemp/set"
current_temperature_topic: "ebusd/470/DisplayedRoomTemp"
Hi all, i need hel on VALLIANT ecoTEC pro 236 VMW.
Equipment:
0010021995 - Caldaia Vaillant EcoTEC Pro a condensazione VMW 236/5-3
0020260943 - Termostato Caldaia Vaillant sensoHOME 380
I install adaptor and config ebusd addon , they work it.
I found all sensor and i cant control system thermostat
example:
BUT I CANT keep temperature room and heat. I cant use thermostat in home assistant?
So wrong config to csv i have auto discover.
Help
The log to start up for my valliant :
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[12:37:27] WARNING: USB and network device defined. Only one device can be used at a time.
[12:37:27] WARNING: Ignoring USB device...
> ebusd --foreground --mqtthost=core-mosquitto --mqttport=1883 --mqttuser=addons --mqttpass=yur8Fu4ohceiva1aigoojung7ohg1yahceFado3oow4uzah6ahxee2eu7oobiejo --scanconfig --mqttjson --latency=10000 --mqttint=/etc/ebusd/mqtt-hassio.cfg --mqtttopic=ebusd --device=192.168.0.54:3333 --log=all:notice
2022-12-06 12:37:32.684 [main notice] ebusd 22.4.v3.16.2-200-ga8ca21f541 started with auto scan on device 192.168.0.54:3333
2022-12-06 12:37:35.768 [bus notice] bus started with own address 31/36
2022-12-06 12:37:35.778 [bus notice] signal acquired
2022-12-06 12:37:39.131 [bus notice] new master 10, master count 2
2022-12-06 12:37:39.191 [bus notice] new master 03, master count 3
2022-12-06 12:37:39.191 [update notice] received unknown MS cmd: 1008b5110101 / 0917170080ff150000ff
2022-12-06 12:37:39.458 [update notice] received unknown MS cmd: 1008b51009000000ffffff050000 / 0101
2022-12-06 12:37:42.676 [mqtt notice] connection established
2022-12-06 12:37:46.740 [bus notice] scan 08: ;Vaillant;BAI00;0404;9602
2022-12-06 12:37:46.740 [update notice] store 08 ident: done
2022-12-06 12:37:46.740 [update notice] sent scan-read scan.08 QQ=31: Vaillant;BAI00;0404;9602
2022-12-06 12:37:46.740 [bus notice] scan 08: ;Vaillant;BAI00;0404;9602
2022-12-06 12:37:48.756 [main notice] read common config file vaillant/broadcast.csv
2022-12-06 12:37:49.209 [update notice] received unknown MS cmd: 1008b5110101 / 0917170080ff150000ff
2022-12-06 12:37:49.216 [main notice] read common config file vaillant/scan.csv
2022-12-06 12:37:49.476 [update notice] received unknown MS cmd: 1008b51009000000ffffff050000 / 0101
2022-12-06 12:37:49.712 [update notice] received update-read broadcast vdatetime QQ=10: 04:41:19;26.11.2022
2022-12-06 12:37:49.749 [main notice] read common config file vaillant/general.csv
2022-12-06 12:37:49.968 [update notice] received unknown MS cmd: 1008b5110102 / 06013c96468264
2022-12-06 12:37:50.233 [update notice] received unknown MS cmd: 1008b5110100 / 08ba000e001f000000
2022-12-06 12:37:50.238 [main notice] read scan config file vaillant/08.bai.csv for ID "bai00", SW0404, HW9602
2022-12-06 12:37:50.436 [update notice] sent scan-read scan.08 id QQ=31:
2022-12-06 12:37:50.527 [update notice] received update-read broadcast outsidetemp QQ=10: -40.000
2022-12-06 12:37:50.647 [update notice] sent scan-read scan.08 id QQ=31:
2022-12-06 12:37:50.812 [update notice] sent scan-read scan.08 id QQ=31:
2022-12-06 12:37:50.976 [update notice] sent scan-read scan.08 id QQ=31: 21;22;42;0010021995;0001;021739;N9
[bus notice] scan 08: ;Vaillant;BAI00;0404;9602
[update notice] store 08 ident: done
[update notice] sent scan-read scan.08 QQ=31: Vaillant;BAI00;0404;9602
[bus notice] scan 08: ;Vaillant;BAI00;0404;9602
[main notice] read common config file vaillant/broadcast.csv
[update notice] received unknown MS cmd: 1008b5110101 / 0917170080ff150000ff
[main notice] read common config file vaillant/scan.csv
[update notice] received unknown MS cmd: 1008b51009000000ffffff050000 / 0101
[update notice] received update-read broadcast vdatetime QQ=10: 04:41:19;26.11.2022
[main notice] read common config file vaillant/general.csv
[update notice] received unknown MS cmd: 1008b5110102 / 06013c96468264
[update notice] received unknown MS cmd: 1008b5110100 / 08ba000e001f000000
[main notice] read scan config file vaillant/08.bai.csv for ID "bai00", SW0404, HW9602
Autoscan to recognize :
vaillant/08.bai.csv for ID “bai00”, SW0404, HW9602
BUT I CANT keep temperature room and heat.
I cant use thermostat in home assistant?
I see only sensor
So wrong config to csv i have auto discover.
Help
I’m sorry many of you are having trouble integrating ebusd and Home Assistant beyond reading out data. For what it’s worth, I am also having similar problems.
This Add-on is primarily a docker container to get http://ebusd.eu running on the same computer as HA OS. Running ebusd appears to work for @Achille_Sano, @woutike, @pepeEL and others.
The remaining problems"can be categorized in one of two categories:
1: getting the correct data read from or written to eBus (heating system)
Here the ebusd config files are your best approach. The biggest problem being that there is no official documentation of proprietary ebus messages. Although there is a community of hobbyists trying to reverse engineer them.
2: Interfacing from Home Assistant with ebusd using MQTT. In this case you can take a look at MQTT integration · john30/ebusd Wiki · GitHub
Again, I’m sorry to say this these two categories of problems are inherent to ebusd or mqtt respectivly and thus out of scope for getting ebusd to run on home assistant os.
That being said, and while I’m working on making some aspects easier through this add-on, feel free to discuss these categories but please consider if this thread would be the best place to do so given the categorization above as there may be better focused resources with more people that can help.
Hi, I just wanted to let you all know that I’ll be stepping away from this project. I received a wireless adapter 3 this week so will run ebusd from a separate RPi running Debian rather than my Hass OS Pi.
It seems my ebusd interface now works, but how can I check the correct data interpretation?
I use a heatpump Ochsner GMSW 12 plus
Screenshot from MQTT Explorer:
eBUSd log:
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
> ebusd --foreground --mqtthost=core-mosquitto --mqttport=1883 --mqttuser=addons --mqttpass=jie5thooDaipai0koo8thol6osohTh6Aishor1loosheet2oomoo4OataingaChi --scanconfig --configpath=/config/ebusd-configuration/latest/en/ --latency=10000 --mqttint=/etc/ebusd/mqtt-hassio.cfg --mqtttopic=ebusd --device=192.168.200.238:5000 --log=all:error
2023-02-01 19:58:53.860 [main error] unable to load scan config 06: list files in tem ERR: element not found
2023-02-01 19:58:53.863 [main error] scan config 06: ERR: element not found
2023-02-01 19:58:55.996 [main error] unable to load scan config 08: list files in tem ERR: element not found
2023-02-01 19:58:55.996 [main error] scan config 08: ERR: element not found
2023-02-01 19:58:58.201 [main error] unable to load scan config 15: list files in tem ERR: element not found
2023-02-01 19:58:58.201 [main error] scan config 15: ERR: element not found
2023-02-01 19:59:41.271 [bus error] poll 21576 mode.heating failed: ERR: read timeout
2023-02-01 20:07:41.275 [bus error] poll 21576 status.heating failed: ERR: read timeout
