poggs
commented
1 year ago Further info: running with ./src/ebusd/ebusd --device=udp:192.168.100.50:5000 --scanconfig -f --log=all:info --lograwdata=bytes shows regular 'aa' bytes received:
2023-11-22 23:05:48.579 [main notice] ebusd 23.2.p20231122 started with auto scan on device: udp:192.168.100.50:5000
2023-11-22 23:05:48.579 [main info] loading configuration files from https://cfg.ebusd.eu/
2023-11-22 23:05:48.868 [main info] reading templates /
2023-11-22 23:05:49.159 [main info] read templates in /
2023-11-22 23:05:49.159 [main info] reading file broadcast.csv
2023-11-22 23:05:49.452 [main info] successfully read file broadcast.csv
2023-11-22 23:05:49.452 [main info] reading file memory.csv
2023-11-22 23:05:49.743 [main info] successfully read file memory.csv
2023-11-22 23:05:49.743 [main info] read config files, got 11 messages
2023-11-22 23:05:49.744 [main info] registering data handlers
2023-11-22 23:05:49.744 [main info] registered data handlers
2023-11-22 23:05:49.744 [bus notice] bus started with own address 31/36
2023-11-22 23:05:49.771 [bus notice] <f5
2023-11-22 23:05:49.771 [bus notice] signal acquired
2023-11-22 23:05:49.813 [bus notice] <aa
2023-11-22 23:05:49.855 [bus notice] <aa
2023-11-22 23:05:49.900 [bus notice] <aa
2023-11-22 23:05:49.943 [bus notice] <aa
2023-11-22 23:05:49.986 [bus notice] <fa
2023-11-22 23:05:50.031 [bus notice] <ff
2023-11-22 23:05:50.072 [bus notice] <aa
2023-11-22 23:05:50.115 [bus notice] <aa
2023-11-22 23:05:50.157 [bus notice] <aa
2023-11-22 23:05:50.201 [bus notice] <aa
2023-11-22 23:05:50.244 [bus notice] <aa
2023-11-22 23:05:50.286 [bus notice] <ea
2023-11-22 23:05:50.333 [bus notice] <ff
2023-11-22 23:05:50.373 [bus notice] <aa
2023-11-22 23:05:50.416 [bus notice] <aa
2023-11-22 23:05:50.460 [bus notice] <aa
2023-11-22 23:05:50.503 [bus notice] <aa
2023-11-22 23:05:50.546 [bus notice] <aa
2023-11-22 23:05:50.589 [bus notice] <fe
2023-11-22 23:05:50.633 [bus notice] <f5
2023-11-22 23:05:50.675 [bus notice] <aa
2023-11-22 23:05:50.718 [bus notice] <aa
2023-11-22 23:05:50.762 [bus notice] <aa
2023-11-22 23:05:50.805 [bus notice] <aa
2023-11-22 23:05:50.848 [bus notice] <fa
2023-11-22 23:05:50.894 [bus notice] <fd
2023-11-22 23:05:50.936 [bus notice] <aa
2023-11-22 23:05:50.980 [bus notice] <aa
2023-11-22 23:05:51.023 [bus notice] <aa
2023-11-22 23:05:51.066 [bus notice] <aa
2023-11-22 23:05:51.109 [bus notice] <ea
2023-11-22 23:05:51.155 [bus notice] <ff
2023-11-22 23:05:51.195 [bus notice] <aa
2023-11-22 23:05:51.238 [bus notice] <aa
2023-11-22 23:05:51.282 [bus notice] <aa
2023-11-22 23:05:51.325 [bus notice] <aa```
Description
I have an esera eBUS Coupler Ethernet, connected directly to a Rasperry Pi 3 over an Ethernet cable, with a static IP address on each end. The coupler is set to send data over UDP to the Pi, and the Pi has nothing much running.
I've compiled ebusd from the latest releaesd version, and when I run it with --scanconfig=full, it never finds anything device on the eBUS, despite a Vaillant boiler being connected via one pair of wires in a Cat5 cable.
I only ever seem to get single bytes of data coming from the bus. If I power down the boiler, the data I receive changes to '00'.
Actual behavior
No devices are detected. Before the scan starts, data is received on the bus, but with what looks like warnings - see 'Logs'
Expected behavior
I'd expect ebusd to be able to find at least one device
ebusd version
23.2
ebusd arguments
--device=udp:192.168.100.50:5000 --scanconfig=full -f --log=all:debug --lograwdata
Operating system
Debian 12 (Bookworm) / Ubuntu 22-23 / Raspberry Pi OS 12 (including lite)
CPU architecture
arm64
Dockerized
None
Hardware interface
other
Related integration
other
Logs