Cannot write to Bosch Condens 2500W #951
Comments
|
For some settings the controller (or thermostats) takes control and overwrites every setting from ems-esp. This is known for the controllers with mechanical knobs like Buderus MC10 and Junkers HT3. Also the troubleshooting section of FAQ mention this. |
MichaelDvP
added
help wanted
|
Yeah i saw the mention in the FAQ, but my boiler has no mechanical knobs, its all digital and i don't have a thermostat either. |
|
Your log does not show the telegrams, only that the write was successfull, so boiler has acknowledged. Try to check if it the contoller resets the command or the boiler itself, set |
|
If i understand the output correctly then, it looks like its the boiler. I was not seeing anything from the controller except my write command (i presume in this scenario the controller is the EMS-EPS, or there should be another controller inside the boiler?), but i tried the other write command anyway, with the same results it looks like. |
|
The boiler do not store the new setting, the readback of telegram 0x16 gives heating on. There is no overwrite from controller. Bu the controller also stores the settings in telegram 0x16. This is different from my system. My boiler accepts heatingactivated off, but controller overwirites and writing to controller does not work. |
|
Okay, i tried it, and i'm seeing zero messages to and from controller, and no writes whatsoever. The only thing i see here is that the boiler is broadcasting the new states. I'll read up on the protocol today, so maybe i can be a better help figuring this out :) |
|
Yes, the boiler set first two bytess to zero (activated and selflowtemp), a little chance that writing both values stops the heating. Try: |
|
I set the loglevel to notice so it would be easier to monitor. (if its better for you in debug mode, i'll turn it back) |
|
@hpeter1994 : is there any change, did you succedd to turn off boiler? I'm experiencing the very same issue in a very same setup... |
|
No, and sadly I can't make any test jet. Beacuse the other boiler user
it's afraid to spent huge gas bill, and I had to remove the interface.
Matteo
Il giorno mar 21 feb 2023 alle ore 19:31 ahhoj ***@***.***>
ha scritto:
… @hpeter1994 <https://github.com/hpeter1994> : is there any change, did
you succedd to turn off boiler? I'm experiencing the very same issue in a
very same setup...
—
Reply to this email directly, view it on GitHub
<#951 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEUI6BNXC5IAF6ZTVW7EOSDWYUCYBANCNFSM6AAAAAAUUG2YSU>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
--
*Matteo Pedani*
phone +39 069415152
|
|
@matteopedani : if it helps in any way, I can execute some tests, just kindly instruct me what should be checked. |
|
I've logged what my thermostat sends to stop the heating. I've set to permanent summermode and there is only one message: |
|
Tried all, but really nothing happens when I try to send telegram to dest 1A. If I try to send to 08 with type 16, I do observe the same behaviour as described above. |
|
Ups, sorry, destination should be boiler 08 and type 1A: |
|
Looks like it didn't have any effect either, effective heating was still on after this. I mean not just the heating activated telegram remained ON, but I see that the boiler actually heating as well. |
Looks to me as both works. Before command you have: |
|
Yes, probably I should descibed that originally. It just a coincidence that the flow temperature just exceeded he heating temperature, and burnerpower is automatically set to 0 by the boiler, and only the pump was running. But, after some minutes, the heating still turned on, consuming gas and pump was running at full speed again. |
Yes, i already wrote that this command have to be repeated every minute. |
|
Ohh, sorry, my bad, I do really missed that part. And yes, you are right. Sending this every minute caused that heating do really turned off after either pump delay or burn min period time (I'm not sure, as those are both the same for me). When I stopped sending this command, the heating started after around 4 minutes. Is is possible to incorporate this behaviour into EMS-ESP (hope so :) )? Or do I have to make this work from my controlling device? |
It is a bit of a special function (out of normal scope of ems-esp), but we already have the wwtapactivated for shower coldshot function, so i think it's ok to add. Please try the 3.5.1-dev from my repo, i named it |
|
I'm about to try it out. In the mean time, may I ask why make it dependent on the boiler's selflowtemp initial value? I think since this feature would be used to control the boiler via ems-esp, only this device should hold and retain the information if the boiler should be turned off or on. |
|
The esp-flash have very limited write cycles, if you use this for controlling the boiler and change setting many times a day, you will kill your esp in a few month. We can add in settings section a power-on-default state for boiler-forceOff, and initialize with this state. |
|
1, Setting forceheatingoff either to on or off does the expected thing: sending (or not) the required telegram periodically, and making the boiler stop heating I understand your concerns regarding the flash lifecycle, and yes, I agree, don't store the value. Your suggestion to have a default power-on-state sounds good. What I'd like to avoid that after a full power outage (ems-esp, boiler), when the power returns, I think it would be better not to turn on heating. At least I don't feel the neccessity for it in the summer ;). And if we are in the middle of winter: the controlling device will turn it on anyway in couple of minutes. |
|
I've added the option in settings. Please test. The init checks this setting and the state of boiler (selflowtemp == 0). |
|
Updated to latest. After that, I don't see anymore the force heating off entity at the boiler. It is still visible at customization, but have no value. |
|
Yes, there was a typo in first upload, this is fixed now. Please download again. Also after disable i set now heatingTemp, burnMaxPower and pumpModMax. |
|
Tried the setting for both states with both preceding value with forceheatingoff. Also, tried how heating activates when forceheatingoff is turned off. Maybe one more thing to consider until final release: it is somewhat "strange" to turn something ON so the boiler will turn off, and vica versa. Not a big problem, but maybe another name and inversed logic for on/off would be more straightforward. |
Yes, but this is not a native boiler setting and it's more common to have a default "off" and explicide activate special functiions. |
Good point, I didn't thought about it. And looking at the other issue... Well, nothing better wording comes to my mind. Maybe just let it as it is. |
|
v3.6.0 lost the "force heating off" option. Downgrading to v3.5.1 fixes the issue. |
|
Thanks for reporting. I'll create a new issue and I'm sure Michael will take a look when he's back. |
|
In 3.6 you have to create a schedule with timer option to use the heating off. It's not an extra option anymore.
|
|
I don't use the scheduling bits of ems-esp though, I use it as an interface to control my boiler through Home Assistant. |
Bug description
Hello.
I just connected my brand new E32 Gateway to my Bosch Condens 2500W boiler. It recognizes it as "Boiler: Condens 2500/Logamax/Logomatic/Cerapur Top/Greenstar/Generic HT3".
I have no other devices connected to the bus (no termostat as i'm not using it).
I can read the status of every entity, but can't change anything, as it will immediately change back to the previous setting.
I have zero TX errors and the log says the command was sent successfully.
I'm using v3.5.0b7
Steps to reproduce
Default settings. I tried changing the "selected flow temperature", "heating activated", "dwh selected temperature", "dwh activated", "dwh one time charging" parameters but nothing sticks.
Expected behavior
I would expect to be able to switch on and off my boiler from the gateway. I read on the wiki that some Junkers boilers have this issue but i have found nothing to indicate that my boiler would be effected as well.
Device information
Telnet console output
The text was updated successfully, but these errors were encountered: