Petr

If you want to run a TCP Master, chances are you are running it on moře advance Platform such as raspberry pi. In that case consider to use some alternative...

As much as I would like to help, I am affraid I would not be able to write the readme correctly for a project I am not creating. I may...

@cibernox I have the same unit, and I did not yet have the possibility to test my hypothesis, but after reading through decompiled Brink Service Tool, it seems to me...

So I have good news and bad news. The bad news is I was wrong. The good news is I found the solution: instead of slave address, it has to...

At least for my latest SW version of Sky 300, I was able to reset the filter even when the warning was not up, and I confirmed it via the...

@cibernox Nope, I went to Settings -> Devices -> MQTT and there I found the device (the default name is `ebusd kwl`) and there is the list of the messages...

hmmm. no changes in yaml. But I had to use custom `[mqtt-hassio.cfg](https://github.com/john30/ebusd/blob/master/contrib/etc/ebusd/mqtt-hassio.cfg)` through the configuration of the add-on, and enable write operations there. The entity was created automatically by ebusd...

@Zwoet @tiotuba Just for clarity, changing the name from `FanSpeed` to `FanMode` is just a workaround. The root cause is, that `FanSpeed` is not matched by the "regex" in [mqtt-hassio.cfg](https://github.com/john30/ebusd/blob/master/contrib/etc/ebusd/mqtt-hassio.cfg)...

Hmm, I see, so the fact the comment name is different is not the problem, but the fact that the writable field is named the same as the readable might...

@cibernox I have not yet done that, but I am just now looking deeper into the Brink Configuration tool via decompiler, and I found a lot of possible settings that...