Warm water circulation pump frequency - can not be changed (neither API nor MQTT)

Question

Warm water circulation pump frequency - can not be changed (neither API nor MQTT)

tp1de opened this issue 4 years ago · 13 comments

I tried to change the ww circulation pump frequency - but without success.

On the thermostat I can change wwcircmode to of,on,auto,own by web api or mqqt - both are working fine

On the boiler the changing of wwcircmode to values between 1..7 does not work. (API returns OK but no changes done)
Maybe the changes should be send to the thermostat? Any idea how to bring it to work?

ESP32: v3.0.0b1 - RC310 / KB192i

tp1de commented 4 years ago

No data:

Answer 1 · 2021-02-16T17:45:24.000Z

@MichaelDvP I did the code change but it is still not working ....

Answer 2 · 2021-02-16T18:53:26.000Z

can you check with commands and read 8 33 the values, for me it's working:

ems-esp:/# read 8 33
000+00:02:55.209 N 1: [emsesp] Boiler(0x08) -> Me(0x0B), UBAParameterWW(0x33), data: 08 FF 30 FB FF 28 FF 07 46 00 00
ems-esp:/# call boiler wwcircmode 5
000+00:03:11.391 I 2: [boiler] Setting warm water circulation mode 5x3min
ems-esp:/# read 8 33
000+00:03:20.269 N 3: [emsesp] Boiler(0x08) -> Me(0x0B), UBAParameterWW(0x33), data: 08 FF 30 FB FF 28 FF 05 46 00 00
ems-esp:/# call boiler wwcircmode 7
000+00:03:40.364 I 4: [boiler] Setting warm water circulation mode continuos
ems-esp:/# read 8 33
000+00:03:46.427 N 5: [emsesp] Boiler(0x08) -> Me(0x0B), UBAParameterWW(0x33), data: 08 FF 30 FB FF 28 FF 07 46 00 00

Answer 3 · 2021-02-16T19:55:14.000Z

I changed bus id into service key an tried again:

Answer 4 · 2021-02-17T08:08:31.000Z

Ok, i think i've found it, please try again.

Answer 5 · 2021-02-17T09:22:32.000Z

@MichaelDvP
It is working now - Super.

By the way one question:
What is the difference between the datafields wWCirc and wWCircPump in boiler_data_ww?

Answer 6 · 2021-02-17T09:33:06.000Z

@tp1de great! There's a brief description of the datafields in https://emsesp.github.io/docs/#/MQTT?id=thermostat

and thanks @MichaelDvP for the quick fix

Answer 7 · 2021-02-17T09:38:58.000Z

The definition:
wWCircPump = Warm water circulation pump available
wWCirc = Warm water circulation active

But in my case both values are the same and indicating when circulation pump is running.

Answer 8 · 2021-02-17T10:51:17.000Z

I think telegram 0xE9, boiler.cpp line 497 should be the status,wWCirc not the configuration. @tp1de Can you check that?
(wWCirc is also in E5, maybe no need to read it in E9).

Answer 9 · 2021-02-17T11:26:39.000Z

@MichaelDvP

I think telegram 0xE9, boiler.cpp line 497 should be the status,wWCirc not the configuration. @tp1de Can you check that?

Yes I can confirm - changing to wWCirc keeps wWCircPump constant on 1

(wWCirc is also in E5, maybe no need to read it in E9).

Yes I can confirm too - for me no need to read wWCirc in E9 - for you @MichaelDvP too?

Answer 10 · 2021-02-17T11:47:28.000Z

E5 is the slow monitor sended periodically, maybe E9 status is triggered on change and more accurate. Can you check this with logging while wwCirc is triggered?

I have a ems-boiler and circulation is in telegrams 33 and 18. The boiler do not send 0xE telegrams and i can not test.

Answer 11 · 2021-02-17T11:57:08.000Z

I can't see any difference in MQTT Explorer:

first change to wWCirc
take message out in E9

Answer 12 · 2021-02-18T11:26:42.000Z

I've checked older logs: E9 is broadcasted completely every 10 sec, E5 is only sended out in parts whenever something changed. I think we should read both to have the current state (E9) and the change (E5).
Fixed in dev8266 and dev32.