John
John
that's probably rather because the slave answer is not as expected
when running in foreground, the logs are sent to stdout and this is usually also what you do with docker containers. To see the log, use something like `docker logs...
ah ok, the command is fine but the 700 answers in a non-expected fashion. I get this response from a cc unit: 08021513020b121902, so this means: status=2 time=19:21 date=02.11.2018 error=537...
hm, then the 700 has some different data types in the message
well if you don't say which circuit you want to read from, then ebusd will pick the first in order of read definitions. this is a convenience and I'd rather...
ok, and what exactly do you want with this issue?
is your ebusd-converter able to write to the bus?
do you know that writing works? try sending a hex message like this: `ebusctl hex 08070400` (you might need to enable the hex command before by adding the `--enablehex` argument...
then either your boiler isn't willing to answer or your device can't write
i guess your version of the calormatic just doesn't support this particular value. or maybe another configuration setting is hindering it from using that one. can you do adjust this...