WOLF FGB-K-28

[mzsolnay]

Description

Hi !

I'd like to use ebusd to communicate with a WOLF Heater, Type FGB-K-28.
Need help/assistance with configuration.

Thank you for taking the time helping me !

[tgrosz]

Hi, I see it was long time ago, but could you make it work?

[anxdroid]

I'm interested too, I'll try the ebusd v5 interface and let you know...

[tgrosz]

I made it work. I can query info but haven't tried writing to ebus

[anxdroid]

what kind of hardware are you using to query the bus ? I bought this https://adapter.ebusd.eu/v5/index.en.html and I'll use it with MQTT to make it available to home assistant

[tgrosz]

The same one, also with mqtt

[anxdroid]

I don't plan to write for the moment, I just need to have live data about the state, temperature, fails, amount of gas consumed

[anxdroid]

May I ask you to share the entities that home assistant or Just mqtt detects ? I am interested in tracking gas consumption and boiler status

[tgrosz]

08.csv
broadcast.csv
mqtt-hassio.cfg.txt
I use these files. In mqtt config I changed only the filters (I guess) to include data from boiler.
Other 2 was translated (mostly) to English by the boiler's manual. I don't send the boiler config (HG values) because they are constant.
The boiler does not send gas consumption data as I know (I do not have any Wolf controllers, only the boiler). If you can get it, please share it.

[anxdroid]

Many thanks as soon as I can get It work I'll share all my findings

[ningyichensha]

I run ebusd for an ochsner heatpump.
Maybe my solution using hex statements and python works for you as well.

I use hex statements to pass the commands to the ebus. This works without using message definitions.

For example setting the mode of hk1 = heating cicuit 1, submit this statement in the raspberry terminal:
ebusctl hex 1006230603b200480100
That returns "done" and changes the mode for the hk1 to automatic (third last byte = 1)
standby = 1006230603b200480000
manual = 1006230603b200480700

To make ebusctl accept hex input, add --enablehex in file: /etc/default/ebusd.
In my case the line is: EBUSD_OPTS="--enablehex -d ens:/dev/ttyAMA0 --latency=50"

To find out which hex code is needed to change the hk1 setting, I used the terminal of the heatpump and changed the hk1 setting a couple of times.
Then I looked at the log file (/media/user/rootfs/var/log/ebusd.log). The time stamps helped to locate the hex commands.

From the log file you copy the hex command without the source address, which is in the first and second byte.
Now you try the statement: ebusctl hex "your hexcode"
That should return the desired answer "done". Than you check the setting at the heater.

Next step is the implementation in python:
My code to change the mode of the heatpump is this:

import subprocess
...
befehl = subprocess.run("ebusctl hex 1006230603b200480100", shell = True ,capture_output=True)
antwort = befehl.stdout
out = antwort.decode()
out = out.strip()
if out == "done":
.....

example read hk1 temperature:
in the log file I found: received unknown MS cmd: 011506210400820048 / 0a02800d02e80300000301
deleting the source address (first and second byte) -> 1506210400820048
From the response take:
low byte: 03 = 3 + high byte: 01 = 256 -> 259 /10 = 25,9 C

in Python:
import subprocess
...
temp_vorlauf = subprocess.run("ebusctl hex 1506210400820048", shell = True ,capture_output=True)
vorlauf = temp_vorlauf.stdout
out = vorlauf.decode()
out_low = out[18:20] #low byte
out_high = out[20:22] #high byte
value = ''.join([out_high, out_low])
vorlauf = int(value,16) /10 #convert hex string to integer an divide by 10 --> hk1 temp in float