-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Viessmann Vitodens 100-W DHW temperature is displayed as Heating in opentherm. #58
Comments
Please describe the problem in more detail. |
I can assume that this is the temperature of the primary heat exchanger. Therefore, when you turn on the DHW, the heating temperature correlates with the DHW temperature. Try closing the DHW tap and see how the value of this sensor changes. If the LEDs do not work, try lower value resistors P8-P10 (50-100 ohms). The resistance must be calculated; the maximum current (mA) is usually in the specification for the LED. |
Your heating temperature is set to 30 degrees. According to the table you provided, this is about 60 degrees at an outside temperature of 10 degrees. I don’t know what delta your boiler has, but perhaps this is normal behavior. Can you set 21 degrees on the heating thermostat in Home Assistant? |
Updated to v1.4.0-rc.22. Still... |
Hmm. It looks like we have to use other IDs to set the temperature if the curve mode on the boiler is enabled. Does the boiler react to changes in the DHW temperature from the home assistant? |
So, let's go in order:
I'll think about what can be done, but not right now. Now I see this solution:
|
Did add the internal temperature via automation just after my post.
What about Danfoss thermostats that are used for setting separate room temperatures. I was expecting Opentherm for fault troubleshooting, and not for room temperature control. Or is OpenTherm still better option than original boiler settings? If no, is it possible for Opentherm gateway not to control the boiler heating, just DHW and reset boiler on F2 fault via HA automation? |
Let's start by testing my hypothesis. Try disabling the "curve mode" and check if the boiler will respond correctly to changes in setpoint temp. |
Any news? |
Now I am testing Equitherm with disabled "curve mode" by removing outdoor temperature sensor from the connection to the boiler and am at the point, where N=0,7, and K, and T are 0-es. Now going for K to set on 2 and test. P.S. DHW flow rate show some numbers. Do not know if it is accurate. Member ID set to 0 in settings.
|
Ok thx |
I did not change anything on HA except setting N to 0.7, and later today adding K with 2.0 , just set all rooms including garage temperature to 23 on Danfoss Link. |
Ok. After the weekend, please upload screenshots of these graphs again. |
@nedievas Kas tau neveikia su tuo boileriu? Aš turiu tokį pat ir pas mane viskas gerai veikia. Sorry neturiu laiko į šį topiką įsigilinti ir viską išanalizuoti, tad jei gali trumpai mestelk info. Temperatūra kaip rašai pirmam poste taip pat veikė ir pas mane blogai, bet atrodo įjungus PID (būtent PID) viskas buvo tvarkoj. Taip pat su nustatymais reiktų pažaisti, uždėti varneles. Pas mane: |
Feel a lot chiller than before :)
O kaip atrodo visi settings? PID ir panašiai... pas mane grindinis šildymas per Danfoss Link kuris su HA nekalba ir boileris buvo pajungtas per lauko temp daviklį. Tai kaip ir viskas veikė, bet F2 kodą mesdavo kai staiga lauko temp nukrisdavo, tai užmačiau Opentherm gateway - pasigaminau ir bandau pajungti tam kad per HA turėčiau galimybę reset jei tas F2 išlenda, bet čia jis perima valdymą, todėl bandau prisiderinti. |
Pas mane gridinis 1 aukšte ir radiatoriai - 2. Visur Danfoss pavaros, zigbee jungikliai jas junginėja ir temperatūros jutikliai kiekviena kambary. Viskas suintegruota į HA. |
Tai katilo temperatūra tik per HA termostato valdymą ir tesireguliuoja. Daugiau nėra būdų. |
Mano ir toks planas pasidaryti per jau esamas Danfoss pavaras. Kokius tam zigbee naudojate? |
Tai aš supratau, kad katilas mano kaip buvo nustatytas - aš jo in nereguliavau, bet tas error F2 mane užkniso ir sugalvojau ieškoti sprendimų. |
Tai tokius Zigbee aš apšvietimui naudoju :) Gal yra kur info kaip pasijungti kaip Jūsų? Galvojau apie tuos kinietiškus kur daug relių ant pcb ir esphome jungiasi, bet nenorėjau bandyti per šildymo sezoną. |
It looks like your boiler heats up to 80 degrees when set to ~40 degrees. It is not right. Try set the checkboxes as @Pajuris wrote. |
Tai kad ten nereikia jokios info. Viskas labai paprasta. Ant kiekvieno kontūro montuoji Normaly closed galvą, ją pajungi prie pasirinkto jungiklio. Jungiklį prijungi prie HA. Kambariuose išmėtai pasirinktus temperatūros jutiklius. Juos taip pat prijungi prie HA. HA config faile, kuri virtualų termostatą, nurodai kad heateris yra tas galvą įijungiantis išjungiantis jungiklis, o temperatūros rodmenis imsi iš konkretaus kambario jutiklio. Viskas. Restartuoji HA, atsiranda termostatas, kurį gali valdyti kaip tinkamas. |
@nedievas could you then test the "Native heating control" option in 1.4.0-rc.24? This option must work with an outdoor temperature sensor connected to the boiler. |
This is today. The last commit version. Equitherm and PID off. [x] DHW present Outdoor sensor connected to boiler. |
Native heating control does not work with your boiler, because in the logs:
The boiler does not accept the current room temperature and the room temperature setpoint. This may be due to the boiler settings (parameters in the service menu) or such an implementation of the opentherm protocol in the boiler. The only solution I see is to use equitherm in the firmware. Opentherm options: |
Will test right now. |
The graph is getting better (will update in the morning). But log is still not good:
|
ID 8 - CH2 setpoint This is not critical and does not affect work. Duplicate heating CH1 to CH2 option can be disabled. |
Hmm. How does this work with outdoor temperature sensor connected to the boiler? Earlier you wrote:
|
You asked to build the commit with PLATFORMIO and test it. Later you recommended to disable Native heating control. |
Hi @nedievas |
Caught some FAULT log:
ID 4 fails? |
Yes. ID 4 is used to reset the fault, but the boiler does not accept data. |
This issue is stale because it has been open 15 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
I suppose it is as it is. I think |
Nope. In the table, column ID4 is empty for most boilers, that is ID4 was not tested. This does not mean that this feature does not work for these boilers. |
This issue is stale because it has been open 15 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This issue was closed because it has been stalled for 5 days with no activity. |
The text was updated successfully, but these errors were encountered: