What automations do you run?

[mtthidoteu]

Heya! We have a Oekofen Compact Pellet Boilet with the default "smart-dumb-ish" thermostat (no screen). What cool Home Assistant automations have you guys set up ?

[dominikamann]

The only automations I have are currently quite basic

• Notification on errors
• Notification before "Ash container is full"

[mtthidoteu]

The only automations I have are currently quite basic

• Notification on errors
• Notification before "Ash container is full"

Do you know of any resources for tuning and understanding how it works?
For example, If I were to interact with the boiler's heating schedule. I wouldn't want to stop/start it too often as I understand pellet boilers like long cycles so as not to waste pellets

[Ventusfahrer]

We operate a relatively complex configuration in our gliding club based on an Oekofen Pelematic Compact (32 kW).

In addition to the club room with kitchen, toilets and separate training rooms (heating circuit 2), there is also a small caretaker's flat (heating circuit 1) and a very large workshop, which is heated by three fan blowers fed directly from the boiler via a separate circulation pump without a mixer. In addition, there is a heated fresh air fan that is temporarily required for events with more than 80 people.

If only the rooms with radiators are needed, the Pellematik's outdoor temperature-controlled heating circuit control can be used.

The fresh air fan and workshop require high flow temperatures. When these are needed, the Pellematik is reprogrammed via the home automation system using push buttons in HomeAssistant.

The logic for this currently runs on a Node-Red node in Homeassistant. The sensor data is retrieved once per minute by a small Python script and published directly to MQTT. Changes to the configuration are sent to the Pellematik via a Node-Red HTTP request node.

This works very robustly as long as you don't send too many requests to the Pellematic. The Pellematic had (or still has) quite primitive protection against denial of service attacks: it only counts the number of requests, regardless of whether they are successful or not, and eventually blocks them when they reach a limit in a certain time span.

For various reasons, I am currently trying to switch from this configuration to a one which makes use of the OekOfen Integration.

Unfortunately, I currently lack support for displaying and changing the time programme of a heating circuit, as the current control concept is based on two different heating programmes per heating circuit.

[dominikamann]

That sounds very interesting. Let us make the time program steerable 👍 I will let you know soon.

[Ventusfahrer]

Hi Dominik!

This would be really great!
On the HTTP level it is no problem:

Issuing the command:

Results in Zeit 1 now being the active heating program: