Where can I find the ebus values

[Lorilatschki]

After having some trouble with a docker container on my raspberry pi I have created a docker container on my windows machine by strating:

docker run --name ebusd --rm -it -v c:\temp:/var/log/ -p 8888 john30/ebusd --scanconfig -d ens:192.168.1.135:5000 --latency=20 --loglevel=debug -l=/var/log/ebusd.log

When looking into the logs on the docker output I see the following:

2023-06-24 13:41:14.870 [main notice] ebusd 23.1.23.1 started with auto scan on enhanced device 192.168.1.135:5000
2023-06-24 13:41:14.870 [main info] loading configuration files from https://cfg.ebusd.eu/
2023-06-24 13:41:14.955 [main info] reading templates /
2023-06-24 13:41:15.060 [main info] read templates in /
2023-06-24 13:41:15.060 [main info] reading file memory.csv
2023-06-24 13:41:15.166 [main info] successfully read file memory.csv
2023-06-24 13:41:15.166 [main info] reading file broadcast.csv
2023-06-24 13:41:15.251 [main info] successfully read file broadcast.csv
2023-06-24 13:41:15.251 [main info] read config files, got 11 messages
2023-06-24 13:41:15.281 [bus notice] device status: resetting
2023-06-24 13:41:15.281 [bus notice] bus started with own address 31/36
2023-06-24 13:41:15.281 [main info] registering data handlers
2023-06-24 13:41:15.282 [main info] registered data handlers
2023-06-24 13:41:25.282 [main debug] performing regular tasks
2023-06-24 13:41:35.283 [main debug] performing regular tasks
2023-06-24 13:41:45.284 [main debug] performing regular tasks
2023-06-24 13:41:55.284 [main debug] performing regular tasks
2023-06-24 13:42:05.285 [main debug] performing regular tasks
2023-06-24 13:42:15.286 [main debug] performing regular tasks
2023-06-24 13:42:25.287 [main debug] update check: OK
2023-06-24 13:42:35.287 [main debug] performing regular tasks

But where I can see the values the ebusd has read? I thought they will be printed into the logs as well, but unfrotunatelly I cannot see any values. I have checked the voltage on the eBus connected to my ECO 305 PROFESSIONELL eBUS GATEWAY and I seems that there is traffic ~20V DC.

When disconnecting the eBUS wire I get the following which indicates that the eBUS in general works. But where I can find the data?

2023-06-24 13:45:37.966 [bus notice] signal acquired
2023-06-24 13:45:39.060 [bus debug] ERR: read timeout during skip, switching to no signal
2023-06-24 13:45:39.060 [bus error] signal lost

I also throught there will be a logfile where the standard out is written to /var/log/ebusd.log but I cannot find any file into the mapped volumn.

[Lorilatschki]

I got some progress on it. After switching the ebus port to 5001 (5000 is reserved for debug purpose on the gateay) I get data, how ever no valid config can be found.

2023-06-26 13:53:57.674 [bus notice] device status: resetting
2023-06-26 13:53:57.674 [bus notice] bus started with own address 31/36
2023-06-26 13:53:57.692 [bus notice] signal acquired
2023-06-26 13:53:58.390 [bus notice] new master 01, master count 1
2023-06-26 13:53:58.451 [bus notice] new master 10, master count 2
2023-06-26 13:53:58.452 [update notice] received unknown MS cmd: 011506210400840040 / 0a04800d02e80300000102
2023-06-26 13:53:59.557 [update notice] received unknown MS cmd: 011506210400800040 / 0a00800d02f4010cfe3e01
2023-06-26 13:53:59.989 [bus notice] new master 03, master count 3
2023-06-26 13:53:59.991 [update notice] received unknown MM cmd: 031005030c010000002712ff3f40000600
2023-06-26 13:54:00.621 [update notice] received unknown MS cmd: 011506210402c80040 / 0a4841042a9f050000e103
2023-06-26 13:54:01.053 [bus notice] new master 13, master count 4
2023-06-26 13:54:01.056 [update notice] received unknown MM cmd: 131005030c0100000024ffff3f02000100
2023-06-26 13:54:01.732 [update notice] received unknown MS cmd: 011506210402c60040 / 0a46410428ffff00002eb0
2023-06-26 13:54:02.015 [update notice] received unknown MM cmd: 100305010a00132320000000000060
2023-06-26 13:54:02.627 [update notice] received unknown MM cmd: 101305010a00000a20000000000160
2023-06-26 13:54:02.841 [update notice] received unknown MS cmd: 011506210402b50040 / 0a35810000ff0000000000
2023-06-26 13:54:03.301 [update notice] received unknown BC cmd: 10fe0802080000002364000200
2023-06-26 13:54:04.073 [update notice] received unknown MS cmd: 011506210400e00040 / 0a60800d02e8030000b400
2023-06-26 13:54:05.089 [update notice] received unknown MS cmd: 011506210400840040 / 0a04800d02e80300000102
2023-06-26 13:54:06.199 [update notice] received unknown MS cmd: 011506210400800040 / 0a00800d02f4010cfe3e01
2023-06-26 13:54:07.065 [update notice] received unknown MS cmd: 1091101203070602 / 087fff0080f4001900
2023-06-26 13:54:07.324 [update notice] received unknown MS cmd: 011506210402c80040 / 0a4841042a9f050000e103
2023-06-26 13:54:07.675 [main error] scan config 06: ERR: element not found
2023-06-26 13:54:07.990 [update notice] received unknown MM cmd: 031005030c010000002712ff3f40000600
2023-06-26 13:54:08.387 [update notice] received unknown MS cmd: 011506210402c60040 / 0a46410428ffff00002eb0
2023-06-26 13:54:08.762 [update notice] received unknown MS cmd: 1091103100 / 070001004af7007f
2023-06-26 13:54:09.379 [update notice] received unknown MM cmd: 131005030c0100000024ffff3f02000100
2023-06-26 13:54:09.590 [update notice] received unknown MS cmd: 011506210402b50040 / 0a35810000ff0000000000
2023-06-26 13:54:09.677 [main error] scan config 08: ERR: element not found
2023-06-26 13:54:10.108 [update notice] received unknown MS cmd: 109110310bf701800d02f4010000f400 / 073f7f000000007f
2023-06-26 13:54:10.605 [update notice] received unknown MS cmd: 011506210400e00040 / 0a60800d02e8030000b400
2023-06-26 13:54:11.670 [update notice] received unknown MS cmd: 011506210400840040 / 0a04800d02e80300000102
2023-06-26 13:54:11.677 [main error] scan config 15: ERR: element not found
2023-06-26 13:54:12.101 [update notice] received unknown MM cmd: 100305020101
2023-06-26 13:54:12.669 [update notice] received unknown MM cmd: 101305020101
2023-06-26 13:54:12.771 [update notice] received unknown MS cmd: 011506210400800040 / 0a00800d02f4010cfe3e01
2023-06-26 13:54:13.321 [update notice] received update-read broadcast datetime QQ=10: 31.801;16:33:28;26.06.2023
2023-06-26 13:54:13.678 [main error] scan config 18: ERR: element not found
2023-06-26 13:54:14.044 [update notice] received unknown MS cmd: 011506210402c80040 / 0a4841042a9f050000e103
2023-06-26 13:54:15.014 [update notice] received unknown MS cmd: 011506210402c60040 / 0a46410428ffff00002eb0
2023-06-26 13:54:15.678 [main error] scan config 91: ERR: element not found

When using ebusctl find I get:

broadcast datetime = 31.801;16:38:59;26.06.2023
broadcast error = no data stored
broadcast id = no data stored
broadcast id = no data stored
broadcast signoflife = no data stored
memory eeprom = no data stored
memory ram = no data stored
scan.06  = no data stored
scan.08  = no data stored
scan.15  = no data stored
scan.18  = no data stored
scan.91  = no data stored

Since I have a Ochsner Heating, there might be no matching configuration. So how to proceed in such a situation? Can I get the data from the manufacturer? Is there a way to reverse engineer the data when listing to the eBUS data?

[knalltuete86]

Hi,
did you try to run ebusctl read scan.06 for example?
If there is no config for your Heater available you can find some information about how they are build here:

https://github.com/john30/ebusd/wiki/4.1.-Message-definition

Regards

[Lorilatschki]

@knalltuete86 when executing the command:

root@25ffdc808734:/# ebusctl read scan.06 
ERR: element not found