yes, I entered the ebusd docker container for executing ebusctl. When I tried it a few days ago I did get some response but it didn’t show any other devices on the ebus. When I do the same now, I get no response. It just returns to the prompt after quite some time (20 seconds) without outputting anything. This even happens for
2ad9b828-ebusd:/# ebusctl info
2ad9b828-ebusd:/# ebusctl help
2ad9b828-ebusd:/#
which I find really strange. At least for help I would have expected a response. And I got it at other times.
Also, the ebusd start fails when rebooting HA with some MQTT not available error. When starting the ebusd add-on manually, it works but without visible messages. Maybe the starting order is wrong but I don’t know how to change it.