Koky

I have no luck on Windows 11. So if you @pepsonEL could share your VM I will be glad.

I apply setting recommanded by [kalledausb](https://github.com/kalledausb) in issue #680 and restart heater and my communication for now working. I am curios for how long. So for now I leave this...

So after 5 days of running it today stoped with same error `arbitration lost` on all three masters. (15.f47, 50.V61 and 26.f47.2). Only broadcast still working.

WiFi signal is strength enough. So only solution will be to catch 5 days detail logs? Because it take that long from normal running to lost arbitration. Maybe som cache...

After upgrade to ebusd-esp (20221105) it looks stabile: > version: ebusd 22.4.v22.4-28-gbc3e611 > update check: revision v22.4 available, broadcast.csv: different version available, memory.csv: different version available, vaillant/15.f47.csv: different version available,...

So it is 10 days up and running and no Arbitration lost. Looks like latest ebusd-esp in combination with older firmware and longer timeouts make it works.

Today it starts again with error. Log from ebus adapter: ``` 10:00:45.8: wifi evt 1 10:00:48.6: wifi evt 8 10:00:50.8: wifi evt 2 10:00:52.9: wifi evt 0 10:00:54.9: check eBUS...

@mf76130 here is my mqtt code for that purpouse: ``` climate: - name: Hot water circuite entity_category: config max_temp: 70 min_temp: 35 precision: 0.1 temp_step: 0.5 temperature_unit: "C" action_topic: "ebusd/bai/Status01"...

If you send `ebusd/720/OpMode/set` and value 2 what happens? You can be limited by default `filter-direction = r|u` in `mqtt-hassio.csv` it makes it read-only.

It is strange tat you load 15.ctlv2.csv instead of 15.720.csv, but ok. Then according your results you have configured only one zone and should operate on that mode: `ebusd/cltv2/z1OpMode/set`