I would log this as an issue on the ebusd github. You could try tweaking the section at line 230 of mqtt-hassio.cfg and making a pull request if you find something that works.
OK - I’ll log it after I’ve had another go at getting 22.1 to work for me.
Re: the tweaking of mqtt-gassio.cfg I’ll have to research what this entails before I embark on another ‘project’
I decided to give the edge variant a try.
After the first attempt crashing my pi I got it installed (probably low memory - pi 3).
It does not work for me at all
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 --mqttport=1883 --mqttuser=addons --mqttpass=xxxxxxxxxx --readonly --scanconfig --mqttjson --mqttlog --latency=0 --mqttint=/etc/ebusd/mqtt-hassio.cfg --mqtttopic=ebusd --device=/dev/ttyUSB0 --log=all:notice
2022-02-17 18:06:57.694 [main notice] ebusd 22.1.v22.1-32-gea60ef9 started read only with auto scan on device /dev/ttyUSB0
2022-02-17 18:06:58.980 [bus notice] bus started with own address 31/36
2022-02-17 18:06:58.988 [mqtt notice] connection established
2022-02-17 18:06:58.994 [bus notice] signal acquired
2022-02-17 18:07:01.695 [bus notice] new master 10, master count 1
2022-02-17 18:07:01.695 [update notice] received unknown BC cmd: 10feb5050427001f00
2022-02-17 18:07:02.129 [update notice] received unknown BC cmd: 10feb505034a0100
2022-02-17 18:07:03.966 [update notice] received unknown MS cmd: 1023b505072b001900000000 / 00
2022-02-17 18:07:04.205 [bus notice] new master 03, master count 2
2022-02-17 18:07:04.205 [update notice] received unknown MS cmd: 1008b511020300 / 0af901fe05b502032c0000
2022-02-17 18:07:04.365 [update notice] received unknown MS cmd: 1008b5110102 / 050000c800c8
2022-02-17 18:07:05.962 [update notice] received unknown MS cmd: 1008b509040ed10000 / 00
2022-02-17 18:07:06.474 [update notice] received unknown MS cmd: 1008b50903290100 / 050100d90100
2022-02-17 18:07:08.039 [update notice] received unknown BC cmd: 10feb516080000071917020422
2022-02-17 18:07:08.215 [update notice] received unknown BC cmd: 10feb51603018003
2022-02-17 18:07:08.727 [update notice] received update-read broadcast datetime QQ=10: 3.500;19:07:00;17.02.2022
2022-02-17 18:07:08.988 [main error] scan config 08: ERR: element not found
2022-02-17 18:07:09.206 [update notice] received unknown BC cmd: 10feb51603043005
2022-02-17 18:07:09.780 [update notice] received unknown MS cmd: 1008b50903290700 / 0507009d0100
2022-02-17 18:07:09.956 [update notice] received unknown MS cmd: 1050b5040101 / 09170400000081000100
2022-02-17 18:07:10.119 [update notice] received unknown MS cmd: 1050b504020d00 / 051900f00117
2022-02-17 18:07:10.307 [update notice] received unknown MS cmd: 1050b5040132 / 0a001a0603010130050100
2022-02-17 18:07:10.453 [update notice] received unknown MS cmd: 1050b5040131 / 020001
2022-02-17 18:07:10.989 [main error] scan config 15: ERR: element not found
2022-02-17 18:07:11.907 [update notice] received unknown BC cmd: 10feb5050427001f00
So I now have endless unknown xx cmd: and scan config errors.
No sensors are detected.
I know this an ebusd issue not the addon but the end result is I’m below square 1.
I’m out of my depth with this one so I’m going to think out which way I want to go.
Really pining for the executable in V0.87…
For the record which version of ebusd was in V0.87 - maybe I can squirt it into the container?
[edit]
I think it must be Quince (21.3)
Your config has read only set, is that why your write sensors weren’t working?
I would also try unsetting your latency, eBUSd should set this automatically
I want use Auto Discovery but for me now not working and i dont know why… also i dont have many know to resolved problem. I also send on github problem but with no answear
For those having issues try pushing rebuild on eBUSd Edge. John30 has just merged a commit which looks like it might resolve some issues
For information, I had the exact same problem.
After 2 days of research, I notice that HA is using a local DNS server running on my HA.
After modifying the DNS config of HA so that it uses the DNS server of my FIA box, the installation of the ebusd add-on goes correctly
Issue with unknown command I solved with --accesslevel=*
I have a question:
[mqtt debug] publish ebusd/global/updatecheck revision v22.1 available, broadcast.csv: different version available, memory.csv: different version available
What does different version available means? Where does it get info about different version?
I have copied CSV files to /config folder in HA… Does it check the “local” files to those on github?
Thanks!
Help on mqtt-hassio.cfg please.
I’m now using my own (in order to get all my sensors).
I’ve got my sensors covered in filter-name = and write access with filter-direction = r|u|^w
Is it possible to define an input_select for an ebus item which has a selection of string values?
Specifically ebusd/hwc/OperatingMode which is defined as hwcmodes which are on/off/auto
I see there is a section in the cfg file
type_switch-list =
binary_sensor,,measurement = onoff
sensor,, =
and I feel it should be possible to add it here but the documentation in the file has baffled me.
I’m guessing the line would be something like input_select,,measurement = hwcmodes but it will also need linking somehow to the ebus item…
Thanks
I’ve never worked out what that update warning means. I have always run the latest version of the config but always get that warning. I think you can just ignore it. Maybe ask here: https://github.com/john30/ebusd/discussions
1 Like
@sonosy if you look at the inline comments it looks like type_switch-list is for read only sensors-
# HA integration: the mapping list for rather binary sensor entities by field type, name, message, and unit.
type_switch-list =
binary_sensor,,measurement = onoff
sensor,, =
I would try changing type_switch-w-list but it does says in the comments that this is for potentially writable binary entities so may not work if what you need is an input select. If this doesn’t work I would suggest you ask a question on the eBUSd discussion page and report back with any solution please.
# HA integration: the mapping list for (potentially) writable binary switch entities by field type, name, message, and unit.
type_switch-w-list =
switch,, = onoff
Question:
Is the option from docs:
Git clone the ebusd-configuration files to your /config folder and edit the config files for your heating system. Add a number 1-9 (1 high priority, 9 low prioirty) after the r at the start of each line and eBUSd will poll that reading automatically.
also available for example broadcast.csv file in line 5:
b,,outsidetemp,outside temperature,,,,"01",,,temp2,,,,,,,,,,,,,,,
So f.e. to put b1 in front? Will it poll automaticly according to priority 1?
Thanks guys, have a nice day!
Hey Guys,
small noob question, I have trying to set my HWC to “off” but am unable to. This is what I am doing:
/ebusd/bai/Status02/set
With the following payload
{
"0": {
"name": "hwcmode",
"value": "off"
},
"1": {
"name": "temp0",
"value": 60
},
"2": {
"name": "temp1",
"value": 65
},
"3": {
"name": "temp0",
"value": 70
},
"4": {
"name": "temp1",
"value": 65
}
}
But nothing changes. I also add --mqttvar=filter-direction=r|u|^w as custom line.
Guillaume,
I am also looking for a solution to send JSON payload to set ebusd parameters like timers. It is only working for single values in my setup. However, in you case I assume that /ebusd/bai/Status02 is not a writable parameter. Please verify your ebusd config:
r,Status02,Betriebsart/Maximaltemperatur/ReglerCurrentTEMP/Maximaltemperatur/ReglerCurrentTemp,02,hwcmode;temp0;temp1;temp0;temp1,
1 Like
thanks that’s probably it!!
How can i find the CSV for my setup with the addon? as i have set to autoconfigure.
Only thing i was able to find is the following
: scan 08: ;Vaillant;BAI00;0311;9602
but can’t find this referenced in github.
Guys
I’ ve made a link with my ebus through a esera network gateway. I assume that the network settings are correct, because i see one outdoor temp. sensor updating with a value via ebusd broadcast device. But all the other sensor entities give a ‘unknown’ state… Is see in the log file that there are errors like ‘arbitration lost’ and ‘ERR, wrong symbol received’, have no clue what it means???
Do i need that use a custom csv file for my vaillant system?
Thanks in advance for any advice!
2022-04-26 15:04:21.741 [bus debug] start request 31
2022-04-26 15:04:21.741 [bus debug] arbitration start with 31
2022-04-26 15:04:21.826 [bus debug] arbitration lost
2022-04-26 15:04:21.826 [bus debug] ERR: arbitration lost during ready, retry
2022-04-26 15:04:21.892 [bus debug] ERR: read timeout during receive command, switching to skip
2022-04-26 15:04:21.892 [bus debug] start request 31
2022-04-26 15:04:21.892 [bus debug] arbitration start with 31
2022-04-26 15:04:22.641 [bus debug] arbitration won
2022-04-26 15:04:22.641 [bus debug] arbitration delay 17 micros
2022-04-26 15:04:22.641 [bus debug] switching from ready to send command
2022-04-26 15:04:22.641 [bus debug] notify request: ERR: wrong symbol received
2022-04-26 15:04:22.641 [bus error] poll mc DisplayedRoomTempDesired failed: ERR: wrong symbol received
2022-04-26 15:04:22.641 [bus debug] ERR: wrong symbol received during send command, switching to skip
2022-04-26 15:04:22.753 [bus debug] ERR: read timeout during receive command, switching to skip
2022-04-26 15:04:23.716 [update info] received MS cmd: 1050b505053c54015401 / 00
2022-04-26 15:04:23.716 [update notice] received unknown MS cmd: 1050b505053c54015401 / 00
2022-04-26 15:04:24.057 [update info] received MS cmd: 1050b5040118 / 0600000054010f
2022-04-26 15:04:24.057 [update notice] received unknown MS cmd: 1050b5040118 / 0600000054010f
2022-04-26 15:04:24.521 [update info] received MS cmd: 1050b503020001 / 0affffffffffffffffffff
2022-04-26 15:04:24.522 [update notice] received read mc currenterror QQ=10: -;-;-;-;-
2022-04-26 15:04:24.793 [update info] received MS cmd: 1050b509040e010000 / 00
2022-04-26 15:04:24.793 [update notice] received unknown MS cmd: 1050b509040e010000 / 00
2022-04-26 15:04:25.367 [update info] received MS cmd: 1050b509040e200000 / 00
2022-04-26 15:04:25.367 [update notice] received unknown MS cmd: 1050b509040e200000 / 00
2022-04-26 15:04:26.311 [bus debug] ERR: ACK error during receive command ACK, switching to skip
2022-04-26 15:04:26.312 [bus info] poll cmd: 3150b509030d0400
2022-04-26 15:04:26.312 [bus debug] start request 31
2022-04-26 15:04:26.312 [bus debug] arbitration start with 31
2022-04-26 15:04:26.545 [bus debug] arbitration lost
2022-04-26 15:04:26.545 [bus debug] ERR: arbitration lost during ready, retry
2022-04-26 15:04:26.610 [bus debug] ERR: read timeout during receive command, switching to skip
2022-04-26 15:04:26.610 [bus debug] start request 31
2022-04-26 15:04:26.610 [bus debug] arbitration start with 31
2022-04-26 15:04:26.834 [main debug] performing regular tasks
2022-04-26 15:04:26.834 [bus info] scan 08 cmd: 3108070400
2022-04-26 15:04:26.844 [mqtt debug] publish ebusd/global/uptime 2544
2022-04-26 15:04:27.132 [bus debug] arbitration lost
2022-04-26 15:04:27.132 [bus debug] ERR: arbitration lost during ready, retry
2022-04-26 15:04:27.214 [bus debug] ERR: read timeout during receive command, switching to skip
2022-04-26 15:04:27.214 [bus debug] start request 31
2022-04-26 15:04:27.214 [bus debug] arbitration start with 31
2022-04-26 15:04:27.904 [bus debug] arbitration lost
2022-04-26 15:04:27.904 [bus debug] ERR: arbitration lost during ready, retry
2022-04-26 15:04:27.983 [bus debug] ERR: read timeout during receive command, switching to skip
2022-04-26 15:04:27.983 [bus debug] start request 31
2022-04-26 15:04:27.983 [bus debug] arbitration start with 31
2022-04-26 15:04:28.777 [bus debug] arbitration won
2022-04-26 15:04:28.778 [bus debug] arbitration delay 12 micros
2022-04-26 15:04:28.778 [bus debug] switching from ready to send command
2022-04-26 15:04:28.778 [bus debug] notify request: ERR: wrong symbol received
2022-04-26 15:04:28.778 [bus error] poll mc FloorPavingDryingTemp failed: ERR: wrong symbol received
2022-04-26 15:04:28.778 [bus debug] ERR: wrong symbol received during send command, switching to skip
2022-04-26 15:04:28.779 [bus debug] start request 31
2022-04-26 15:04:28.779 [bus debug] arbitration start with 31
2022-04-26 15:04:28.848 [bus debug] arbitration lost
2022-04-26 15:04:28.848 [bus debug] ERR: arbitration lost during ready, retry
2022-04-26 15:04:28.922 [bus debug] ERR: read timeout during receive command, switching to skip
2022-04-26 15:04:28.922 [bus debug] start request 31
2022-04-26 15:04:28.922 [bus debug] arbitration start with 31
Hello
I’ve placed the ebusd files from github on my RPi and updated the ebusd add-on.
First i linked to the ‘latest’ shortcut (/config/ebusd-configuration/latest), this gave no solution.
But when i changed it into the following directory (/config/ebusd-configuration/ebusd-2.x.x/en) i got 10 devices on the ebusd devices page, but still all values stay in the ‘unknown’ state… does anyone know how i can debug this?
Sorry, but I can’t help with these issues. An arbitration issue sounds like there is a communication issue between the boiler and your ebus adapter. Have you checked the cable?
For more support I would post here Discussions · john30/ebusd · GitHub
Hi,
it seems it can’t be installed anymore (I tried the edge version).
Probably due to John’s new eBUSd release yesterday?
Maybe the Add-on needs some love to support it?
The command '/bin/ash -o pipefail -c git clone https://github.com/john30/ebusd.git && cd ebusd && cmake -B build -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=MinSizeRel -DBUILD_TESTING=ON && cmake --build build && cmake --install build && mkdir /etc/ebusd && cp contrib/etc/ebusd/mqtt*.cfg /etc/ebusd/' returned a non-zero code: 1
It’s a build error. Spotted it yesterday and trying to debug
1 Like