v3.2.1

what's new

Handling for WiFi and mqtt redesigned. Blocking while-loop with delay was removed. In the past this could lead to an unwanted activation of the setup mode. Also the mqtt Library was changed from pubsubclient to async-mqtt-client

see all details of the first V3 release here: Release v3.0.0

changelog

• change blocking mqtt reconnect handling to non-blocking implementation #33
• mqtt client Library changed to implementation based on AsyncTCP (async-mqtt-client)
• change blocking WiFi reconnect handling to non-blocking implementation
• Prevent division by ZERO if parameter Oil density is not set.
• Prevent writing the time on the Logamatic, 1 hour after the boot-up

v3.2.0

what's new

• new Option to configure config messages from Logamatic in mqtt as retain #28

see all details of the first V3 release here: Release v3.0.0

changelog

• mqtt option to set config messages as retain #28
• change format specifier for printf #27
• fix some typos in param.txt

v3.1.0

what's new

• new Widget with outdoor temperatures on the dashboard

see all details of the first V3 release here: Release v3.0.0

changelog

• fix LED config for Setup-Mode (for the78Mole Board, LED on GPIO21 is used to show Setup-Mode)
• fix virtual oilmeter is not shown in webUI #24
• fix mqtt info response message for ww_opmode

v3.0.1

what's new

this is a bugfix Version of the latest major release V3
see all details of the first V3 release here: Release v3.0.0

changelog

• fix some Translation issues #23
• increase char length of config.mqtt.server from [20] to [128]
• change datapoint of config.mqtt.port from int to uint16_t

v3.0.0

what's new

🎉 this is a major update with a lot of cool new features! 🎉

The webUI was redesigned for a better availability and stability. It reacts faster and the resource problem could hopefully be solved.
There is also a completely new configuration section in the webUI, where you can configure all the settings.
Its also now possible to show heating circuit 1 and heating circuit 2 in parallel.

The OTA Library has changed from ArduinoOTA to AsyncElegantOTA. With that, there is also the possibility to update the Software without PlatformIO.
In Future you can update the software with the esp_buderus_km271_XXX.bin files from the release section and upload this directly on the webUI.

To get access to the webUI, even when there is no valid WiFi configuration, there is a new "Setup-Mode".
The "Setup-Mode" starts automatically if the configuration is invalid or missing and can be activated manually.
To enable it manually, press the Reset-Button on the ESP and click it again within 5 Seconds.
If the ESP goes into "Setup Mode", it will automatically create a own network access point with SSID "ESP-Buderus-KM271" 📶
After you are connected to this network, you can open the webUI on ip-address "http://192.168.4.1"

changelog

• re-work of the webUI value Tables for better stability
• remove credentials.h
• remove configuration options in config.h
• add new possibility to configure everything in the webUI
• new "Setup-Mode" with fallback Access-Point
• remove Wiki and extend README.md

v2.3.0

what's new

CHANGE: summer mode threshold and frost_mode_threshold divided into separate values for heating circuit 1 and heating circuit 2 (#19)

❗️Attention: the mqtt commands changed ❗️

// NEW: Heating circuit 1
command:    heating circuit 1: summer mode threshold Temperature
topic:      {"setvalue/hk1_sommer_ab", setvalue/hc1_summer_mode_threshold"}
payload:    Resolution: 1 [°C] - Range: 9:Summer | 10°..30° | 31:Winter

command:    heating circuit 2: summer mode threshold Temperature
topic:      {"setvalue/hk2_sommer_ab", setvalue/hc2_summer_mode_threshold"}
payload:    Resolution: 1 [°C] - Range: 9:Summer | 10°..30° | 31:Winter

// NEW: Heating circuit 2
command:    heating circuit 1: frost mode threshold Temperature
topic:      {"setvalue/hk1_frost_ab", setvalue/hc1_frost_mode_threshold"}
payload:    Resolution: 1 [°C] - Range: -20 ... +10 [°C]

command:    heating circuit 2: frost mode threshold Temperature
topic:      {"setvalue/hk2_frost_ab", setvalue/hc2_frost_mode_threshold"}
payload:    Resolution: 1 [°C] - Range: -20 ... +10 [°C]

Also the webUI changed a bit depending this values. The values moved from "general values" to "heating circuit 1" and "heating circuit 2"

changelog

• #19 summer mode threshold and frost_mode_threshold divided into separate values for heating circuit 1 and heating circuit 2
• #19 bugfix in callback of operation modes (heating circuit 1, heating circuit 2 and hot water) in webUI - did not work before!
• bugfix a typo in description for summer mode threshold (9:winter / 31:summer => 9:summer / 31:winter)

v2.2.0

what's new

• new function to set the operation cycles of the warm water circulation pump over mqtt (#14)

command:    warm water pump cycles
topic:      {"setvalue/ww_pumpen_zyklus", setvalue/ww_pump_cycles"}  
payload:    Resolution: 1 [cyles/hour] - Range: 0:OFF | 1..6 | 7:ON

and also from the webUI:

• There is also a new param.txt that contains a List of all mqtt commands and status values.

changelog

• add mqtt_param.txt with all mqtt commands and config/status topics
• add mqtt config value for remaining holiday days (will count down from Logamatic every day)
• add contol panel for holiday days (heating circuit 1+2)
• add mqtt config value for warm water pump cycles
• add control panel for warm water pump cycles

v2.1.0

what's new

new function to set date and time from webUI
If the NTP Server is used, you can set the actual ESP time to the Logamatic.
But it is also possible to set date and time manually from the webUI.

changelog

- change remaining Strings from type String to type char  
- add limit function for cfgArray index  
- km271SetDateTime() - day of week was wrong, fix mqtt response message 
- rename km271SetDateTime() to km271SetDateTimeNTP()  
- new function km271SetDateTimeDTI() to set time manually from webUI 
- config options for NTP-Server and km271SetDateTimeNTP()  
- config options for hardware settings
- rename mqtt "info message" to "debug"
- add new info message with relevant logamatic status values

v2.0.0

what's new

this release brings a new onboard webUI to monitor and control your Logamatic from the web browser. 🥳
The webUI can be enabled/disabled within the config.h settings and can be accessed by the ip-address of your ESP.
The values are automatically refreshed if they change.

more details and screenshots can be found in the additional wiki section

changelog

• new webUI
• improved String handling (changed type String to type char for most variables)
• added calculated oil consumption (see config.h) #3

v1.3.4

what's new

As not every Logamatic Model seems to support the alarm messages, I have added a config flag to be able to disable this messages.

changelog

• Alarm message configurable #8