Hi timstanley1985,
I also use MQTT and it works good.
Greetings Tobias
New release 
0.85
- IMPROVE: Automatically configure MQTT
- IMPROVE: Add MQTT log configuration option
- IMPROVE: Use precompiled eBUSd
I think we are getting pretty close to a 1.0 release. Are there any features missing or any bugs that need fixing?
Hi. I try it but when click UPDATE and check Create Backup, it create backup very very very long and then start update. I think that it is very long time…
Hi, moved from manually created ebusd docker to this addon without an issue. Everything working fine for both reading and writing to ebus. Thanks a lot!
But tell me how works MQTT automatically ? WHere we can put login and pass and addres IP ?
I do not need to put user/password.
If you are using MQTT broker addon from HA, ebusd addon use HA user/password probably.
To put IP:port for network ebusd adapter you need to switch " Show unused optional configuration options" on configuration page.
Local MQTT server is discovered automaticaly I assume.
For me its no working… no send data to mqtt…
Yes i have broker on as addon in HA but user and pass for my MQTT is othr then user for HA. For me no working… no connect with adapter…also when use old config yaml from 0.84
This is log:
[s6-init] making user provided files available at /var/run/s6/etc…exited 0.
[s6-init] ensuring user provided files have correct perms…exited 0.
[fix-attrs.d] applying ownership & permissions fixes…
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts…
[cont-init.d] done.
[services.d] starting services
[services.d] done.
ebusd --foreground --mqtthost=core-mosquitto --mqttuser=addons --mqttpass=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx --mqttport=1883 --scanconfig --latency=40 --device=enh:192.168.4.39:9999 --log=all:notice --log=mqtt:notice
ebusd: invalid log: areas
Tryebusd --help' orebusd --usage’ for more information.
[cmd] /run.sh exited 64
[cont-finish.d] executing container finish scripts…
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
When use new config without user and pass only read data from ebus but nothing send to HA mqtt
In this situation i must go back to working 0.84
2022-01-19 12:37:51.031 [main notice] found messages: 621 (2 conditional on 25 conditions, 0 poll, 10 update)
2022-01-19 12:37:53.237 [bus notice] scan 26: ;Vaillant;VR_71;0104;0503
2022-01-19 12:37:53.237 [update notice] store 26 ident: done
2022-01-19 12:37:53.237 [update notice] sent scan-read scan.26 QQ=31: Vaillant;VR_71;0104;0503
2022-01-19 12:37:53.237 [bus notice] scan 26: ;Vaillant;VR_71;0104;0503
2022-01-19 12:37:53.409 [main error] scan config 26: ERR: SYN received
2022-01-19 12:37:53.851 [update notice] received unknown MS cmd: 1026b5230106 / 10e4019f01af01aa01008000800080003d
2022-01-19 12:37:54.489 [update notice] received update-write bai SetMode QQ=10: auto;29.0;-;-;0;0;1;0;0;0
2022-01-19 12:37:54.702 [update notice] received unknown MS cmd: 1026b5230f05ffffff000000ffffffffffff0000 / 0101
2022-01-19 12:37:54.982 [update notice] received unknown MS cmd: 1026b5230402000000 / 02019c
2022-01-19 12:37:55.199 [update notice] received unknown MS cmd: 1026b5230402010134 / 0201fb
2022-01-19 12:37:55.441 [update notice] received unknown MS cmd: 1026b5230402020134 / 0201fb
2022-01-19 12:37:55.669 [bus notice] new master 00, master count 4
2022-01-19 12:37:55.730 [update notice] received read 700 z3Name1 QQ=00: PIETR
2022-01-19 12:37:56.019 [update notice] received read 700 z3Name2 QQ=00: 0
2022-01-19 12:37:56.294 [update notice] received read 700 z3OpMode QQ=00: auto
2022-01-19 12:37:56.524 [update notice] received unknown MS cmd: 0015b52406020003021b00 / 0601031b000000
2022-01-19 12:37:56.762 [update notice] received read 700 z3ActualRoomTempDesired QQ=00: 22
2022-01-19 12:37:56.983 [update notice] received unknown MS cmd: 0015b52406020003021900 / 050103190001
2022-01-19 12:37:57.031 [bus notice] max. symbols per second: 113
2022-01-19 12:37:57.297 [update notice] received unknown MS cmd: 0015b52406020003021c00 / 0501031c0002
2022-01-19 12:37:57.520 [update notice] received unknown MS cmd: 0015b52406020003021100 / 050303110001
2022-01-19 12:37:57.896 [update notice] received read 700 z3QuickVetoTemp QQ=00: 21
2022-01-19 12:37:58.076 [update notice] received read 700 z3DayTemp QQ=00: 22
2022-01-19 12:37:58.312 [update notice] received unknown MS cmd: 0015b52406020003020200 / 08020302000000c041
2022-01-19 12:37:58.549 [update notice] received read 700 z3RoomTemp QQ=00: 22.1875
2022-01-19 12:37:58.777 [update notice] received unknown MS cmd: 0015b52406020003020100 / 06020301000100
2022-01-19 12:37:59.007 [bus notice] max. symbols per second: 122
2022-01-19 12:37:59.008 [update notice] received read 700 z3SFMode QQ=00: auto
2022-01-19 12:37:59.236 [update notice] received read 700 z3NightTemp QQ=00: 22
2022-01-19 12:38:04.046 [update notice] received read bai Status01 QQ=10: 32.5;28.5;2.750;30.0;49.0;on
2022-01-19 12:38:04.345 [update notice] received unknown MS cmd: 1026b5230106 / 10e6019f01af01aa01008000800080003d
2022-01-19 12:38:04.632 [update notice] received unknown MS cmd: 1026b5230107 / 0f008000800080008000008000805705
2022-01-19 12:38:04.888 [update notice] received read bai Status02 QQ=10: auto;60;75.0;70;65.0
2022-01-19 12:38:05.160 [update notice] received update-write bai SetMode QQ=10: auto;29.5;-;-;0;0;1;0;0;0
2022-01-19 12:38:05.427 [update notice] received read bai DateTime QQ=10: valid;12:38:03;19.01.2022;2.750
2022-01-19 12:38:05.636 [bus notice] scan 05: ;Vaillant;VR920;2402;5703
2022-01-19 12:38:05.636 [update notice] store 05 ident: done
2022-01-19 12:38:05.636 [update notice] sent scan-read scan.05 QQ=31: Vaillant;VR920;2402;5703
2022-01-19 12:38:05.636 [bus notice] scan 05: ;Vaillant;VR920;2402;5703
2022-01-19 12:38:05.746 [main error] scan config 05: ERR: SYN received
2022-01-19 12:38:05.980 [update notice] received update-read broadcast vdatetime QQ=10: 12:38:01;19.01.2022
2022-01-19 12:38:06.243 [update notice] received unknown MS cmd: 1008b5110100 / 080d020d20040f0001
2022-01-19 12:38:06.534 [update notice] received unknown MS cmd: 1026b5230f05ffffff000000ffffffffffff0000 / 0101
2022-01-19 12:38:06.800 [update notice] received unknown MS cmd: 1026b5230402000000 / 02019c
2022-01-19 12:38:07.026 [update notice] received unknown MS cmd: 1026b5230402010134 / 0201fb
2022-01-19 12:38:07.241 [update notice] received update-read broadcast outsidetemp QQ=10: 2.250
2022-01-19 12:38:07.487 [update notice] received unknown MS cmd: 1026b5230402020134 / 0201fb
2022-01-19 12:38:07.732 [update notice] received unknown MS cmd: 1008b5100305ff01 / 0101
2022-01-19 12:38:08.035 [update notice] sent unknown MS cmd: 3126b5090124 / 09003231313931333030
2022-01-19 12:38:08.152 [update notice] received update-write bai StatusCirPump QQ=10: off
2022-01-19 12:38:08.391 [update notice] sent scan-read scan.26 id QQ=31:
2022-01-19 12:38:08.632 [update notice] sent scan-read scan.26 id QQ=31:
2022-01-19 12:38:08.878 [update notice] sent scan-read scan.26 id QQ=31: 21;19;13;0020184847;0082;006352;N4
2022-01-19 12:38:08.878 [bus notice] scan 26: ;21;19;13;0020184847;0082;006352;N4
2022-01-19 12:38:09.083 [update notice] received unknown MS cmd: 1008b513020508 / 00
2022-01-19 12:38:09.119 [main notice] read scan config file vaillant/26.vr_71.csv for ID "vr_71", SW0104, HW0503
2022-01-19 12:38:09.242 [main notice] found messages: 633 (2 conditional on 25 conditions, 0 poll, 10 update)
2022-01-19 12:38:09.297 [update notice] received unknown BC cmd: 10feb510020601
2022-01-19 12:38:09.571 [update notice] received unknown MS cmd: 1026b5030c0700ffffffffffffffffffff / 0101
2022-01-19 12:38:13.495 [update notice] received read bai Status01 QQ=10: 32.5;28.5;2.750;30.0;49.0;on
2022-01-19 12:38:13.805 [update notice] received read vr_71 SensorData1 QQ=10: 30.44;25.94;27.00;26.62;-;-;-;00 3d
2022-01-19 12:38:14.093 [update notice] received read vr_71 SensorData2 QQ=10: -;-;-;-;0.00;8.00;80 57 05
2022-01-19 12:38:15.091 [update notice] received update-write bai SetMode QQ=10: auto;29.0;-;-;0;0;1;0;0;0
2022-01-19 12:38:15.379 [update notice] received write vr_71 SetActorState QQ=10: -;-;-;off;off;off;-;-;-;-;-;-;00 00
2022-01-19 12:38:15.630 [update notice] received write vr_71 Mc1FlowTempDesired QQ=10: off;0.0;on;-100
2022-01-19 12:38:16.604 [update notice] received write vr_71 Mc2FlowTempDesired QQ=10: on;26.0;on;-5
2022-01-19 12:38:16.856 [update notice] received write vr_71 Mc3FlowTempDesired QQ=10: on;26.0;on;-5
2022-01-19 12:38:21.379 [main error] scan config 05: ERR: wrong symbol received
2022-01-19 12:38:23.557 [update notice] received read bai Status01 QQ=10: 32.5;28.5;2.750;30.0;49.0;on
2022-01-19 12:38:23.859 [update notice] received read vr_71 SensorData1 QQ=10: 30.50;26.00;27.00;26.56;-;-;-;00 3d
2022-01-19 12:38:24.153 [update notice] received read vr_71 SensorData2 QQ=10: -;-;-;-;0.00;8.00;80 57 05
2022-01-19 12:38:25.276 [update notice] received update-write bai SetMode QQ=10: auto;29.0;-;-;0;0;1;0;0;0
2022-01-19 12:38:25.444 [update notice] received write vr_71 SetActorState QQ=10: -;-;-;off;off;off;-;-;-;-;-;-;00 00
2022-01-19 12:38:25.689 [update notice] received write vr_71 Mc1FlowTempDesired QQ=10: off;0.0;on;-100
2022-01-19 12:38:26.665 [update notice] received write vr_71 Mc2FlowTempDesired QQ=10: on;26.0;on;-5
2022-01-19 12:38:26.913 [update notice] received write vr_71 Mc3FlowTempDesired QQ=10: on;26.0;on;-5
2022-01-19 12:38:33.354 [update notice] received read bai Status01 QQ=10: 32.5;28.5;2.750;30.0;49.0;on
2022-01-19 12:38:33.617 [update notice] sent unknown MS cmd: 3105b5090124 / 09003231323031343030
2022-01-19 12:38:33.805 [update notice] received read vr_71 SensorData1 QQ=10: 30.56;26.00;27.00;26.56;-;-;-;00 3d
2022-01-19 12:38:34.008 [update notice] sent scan-read scan.05 id QQ=31:
2022-01-19 12:38:34.225 [update notice] sent scan-read scan.05 id QQ=31:
2022-01-19 12:38:34.563 [update notice] sent scan-read scan.05 id QQ=31: 21;20;14;0020252922;0938;012306;N6
2022-01-19 12:38:34.563 [bus notice] scan 05: ;21;20;14;0020252922;0938;012306;N6
2022-01-19 12:38:34.714 [main error] unable to load scan config 05: no file from vaillant with prefix 05 matches ID "vr920", SW2402, HW5703
2022-01-19 12:38:34.714 [main error] scan config 05: ERR: element not found
2022-01-19 12:38:34.789 [update notice] received read bai Status02 QQ=10: auto;60;75.0;70;65.0
2022-01-19 12:38:35.058 [update notice] received update-write bai SetMode QQ=10: auto;29.0;-;-;0;0;1;0;0;0
2022-01-19 12:38:35.442 [update notice] received write vr_71 SetActorState QQ=10: -;-;-;off;off;off;-;-;-;-;-;-;00 00
2022-01-19 12:38:35.678 [update notice] received write vr_71 Mc1FlowTempDesired QQ=10: off;0.0;on;-100
2022-01-19 12:38:35.925 [update notice] received write vr_71 Mc2FlowTempDesired QQ=10: on;26.0;on;-5
2022-01-19 12:38:36.171 [update notice] received write vr_71 Mc3FlowTempDesired QQ=10: on;26.0;on;-5
2022-01-19 12:38:43.396 [update notice] received read bai Status01 QQ=10: 32.5;29.0;2.750;30.0;49.0;on
2022-01-19 12:38:43.722 [update notice] received read vr_71 SensorData1 QQ=10: 30.62;26.00;27.00;26.56;-;-;-;00 3d
2022-01-19 12:38:43.995 [update notice] received read vr_71 SensorData2 QQ=10: -;-;-;-;0.00;8.00;80 57 05
2022-01-19 12:38:44.259 [update notice] received update-write bai SetMode QQ=10: auto;29.0;-;-;0;0;1;0;0;0
2022-01-19 12:38:44.547 [update notice] received write vr_71 SetActorState QQ=10: -;-;-;off;off;off;-;-;-;-;-;-;00 00
2022-01-19 12:38:44.831 [update notice] received write vr_71 Mc1FlowTempDesired QQ=10: off;0.0;on;-100
2022-01-19 12:38:45.039 [update notice] received write vr_71 Mc2FlowTempDesired QQ=10: on;26.0;on;-5
2022-01-19 12:38:45.286 [update notice] received write vr_71 Mc3FlowTempDesired QQ=10: on;26.0;on;0
Now i also can not go back to version 0.84…
In this situation i go back to my docker on Synology NAS. It works ok. To time when connection MQTT with HA is now resolved i must user other docker… 
For me this is no good situation…
@pepeEL
try to turn off loggs for MQTT. You have log:areas error. See ebusd documentation
’
-
--log=AREAS:LEVEL
Only write log for matching AREA(S) below or equal to LEVEL [all:notice].
This is an alternative form to using --logareas/–loglevel and allows to specify an individual level for each area by using the option multiple times. E.g. for having only bus messages in info level and all other in error level, use--log=all:error --log=bus:info.
’
I set --log=AREAS:LEVEL
and no working… problem is probably that addon dont have access to send data by mqtt.
I have Log level for all messages : notice only selected.
see my logs on start of ebusd addon
[s6-init] making user provided files available at /var/run/s6/etc…exited 0.
[s6-init] ensuring user provided files have correct perms…exited 0.
[fix-attrs.d] applying ownership & permissions fixes…
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts…
[cont-init.d] done.
[services.d] starting services
[services.d] done.
ebusd --foreground --mqtthost=core-mosquitto --mqttuser=addons --mqttpass=xxxx --mqttport=1883 --scanconfig --latency=10000 --accesslevel=* --device=192.168.5.110:9999 --log=all:notice
on version 0.84 works ok.
But on 0.85 stil not working. This is my running:
> ebusd --foreground --mqtthost=core-mosquitto --mqttuser=addons --mqttpass=xxxxxxxxxxxxxxxxxxxxxxxxxxx --mqttport=1883 --scanconfig --latency=10000 --accesslevel=* --device=enh:192.168.4.39:9999 --log=all:notice
this is running for 0.84 and working:
> ebusd --foreground --scanconfig --latency=10000 --mqtthost=192.168.4.6 --mqttport=1883 --mqttuser=mqtt --mqttpass=xxxxxxx --accesslevel=* --device=enh:192.168.4.39:9999 --log=all:notice
try to delete “enh:” from --device=enh:192.168.4.39:9999 , think that this is not an issue but worth to try.
No my adapter and configuration must working with “enh” i try it in older version. Also on adapter is setup enhanced configuration.
I have network adapter connected (wemos mini) and it works without “enh:”.
I do not have more ideas what could be wrong, sorry.
I’ve got here the same issue, the wemos (from John30) can get the data from the ebusd, but it will not send to my MQTT broker
Hi!
I have problem connecting to ebusd via mqtt. I think the configuration (addons) is not getting correct mqtt user and password from mosquito. The copied log:
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
> ebusd --foreground --mqtthost=core-mosquitto --mqttuser=addons --mqttpass=mai5ariShaePae9queinieZoon2phaebei9Ge5baengimeiP3foipee5nooyahyu --mqttport=1883 --scanconfig --mqttretain --latency=10 --accesslevel=* --device=enh:192.168.31.144:8888 --log=all:debug --log=main:debug --log=bus:debug --log=update:debug --log=network:debug --log=mqtt:debug
ebusd: invalid log: areas
Try `ebusd --help' or `ebusd --usage' for more information.
[cmd] /run.sh exited 64
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
Any advice?
Thank you!
I have the same problem. Version 0.85 is not for use. I go back to 0.84 and works ok.
Thanks, but how can I install 0.84? 