Closed aspyk closed 10 months ago
well if no unit is willing to respond to the broadcast scan, then just try with a full scan instead. anyway, if there is no traffic at all on the bus, it'll probably be hard to find useful data. either way, this does not look like an ebusd issue in the first place, so closing
Ok indeed the full scan make the device pop... I'm going to start the exploration now, thank you very much!
Description
I run for the first time the docker version of ebusd on a rapsberry pi with a v5 adapter. The adapter is connected to the heater directly. Everything seems to run fine except it looks like no other device is found on the ebus. Here is the output:
And here the output of
ebusctl info
in another terminal connected to the container:Do you know what's going wrong ? Thank you !
Actual behavior
The scan seems to be ok but no other device is found on the bus (except itself) in
ebusctl info
.Expected behavior
another address should be detected in the output of
ebusctl info
.ebusd version
current source from git
ebusd arguments
--scanconfig -d ens:/dev/ttyAMA0 --latency=50
Operating system
Debian 11 (Bullseye) / Ubuntu 20-21 / Raspbian 11 / Raspberry Pi OS 11 (including lite)
CPU architecture
arm64
Dockerized
same as ebusd version
Hardware interface
Adapter Shield v5 via Raspberry GPIO
Related integration
No response
Logs
output with loglevel=debug