-
-
Notifications
You must be signed in to change notification settings - Fork 104
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
HA dhw control is not working since 3.7.0-dev.30 [BC400] #1932
Comments
could you post the value of the MQTT topic |
complete: I guess that is also where we need to implement cooling/heating.... |
And please post also the acutal value from the MQTT topic |
check also related ticket: depending to what mode is set at HP the mode looks different (pics from Buderus App (MX300 Interface): |
I think we need to adapt more for BC400, my feeling is that 20% of the signals are not fitting for the new BC400 systems. As I understand the system, "summer/winter" also called "Betriebsart" (operating mode?) is used to activate cooling or heating functionality (or "auto" to switch on temperature conditions). |
the file system of my ESP32 was damaged/not compatible. OTA updates worked and everything looks OK, but the SW was doing unexpected things like not sending some messages randomly. I fixed it by a fresh format with EMS-ESP-Flasher v1.0.3. tool. DHW is working but only shows heating, since summer/winter signal is not present in dev30 see #1904 my posted photos are valid, we could check this again once the summer/winter signal works again. |
Shall we close this one (which is about dhw control) and create a new issue, or re-open 1904 for the summer mode and more BC400 settings? |
In Home Assistance the climate control is not working anymore.
It always shows off state (see screenshot below). It should say "heating" because cooling is on.
SW: 3.7.0-dev.30
HP with BC400
Hint: was working w/ 3.7.0-dev.23
only changes I see below:
95c995f
PS: nice improvement would be: to differentiate between heating and cooling.
The text was updated successfully, but these errors were encountered: