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]

Hello I'm back :-) I finally got my new Wolf heater installed and I wanted to try the connection to mqtt/home assistant through the https://adapter.ebusd.eu/v5/index.en.html. So far I managed to connect the ebusd adapter to the heater (ebus + and - with no regard to polarity) using USB power and no RPI, hoping to get all I needed from MQTT. The adapter is connected to my home wifi network and send some info to my MQTT broker.

Now I have two issues that I hope to get through if you can help me:

• on my MQTT broker I can only see a few info related to the adapter (temperature, uptime, RSSI, version, signal...) but nothing related to the heater
• in the adapter home page I have this alarming message:
  Chip ID: ecda3b02342c, ESP32-C3, rev 4
  Hostname: ebus-02342c
  Up time: 181
  Free heap: 87676 / 255652
  ebusd connected: no
  eBUS signal: acquired
  MQTT connected: yes
• I hoped to see some data popping up in the eas MQTT topic just plugging the adapter to the heater but it is not happening. Should I provide some extended configuration file to the adapter? Should I send some command through the network or easy interface to start polling data ? Thank you so much !

[anxdroid]

some update: I finally managed to connect to the heater using ebusd addon in HASS. This is the log:

in /config/ebusd-configuration/latest/en I put the files you linked (thank you !)

ebusd --foreground --httpport=8889 --mqtthost=192.168.1.5 --mqttport=1883 --mqttuser=xxx --mqttpass=xxx --scanconfig --mqttjson --configpath=/config/ebusd-configuration/latest/en --latency=9 --mqttint=/config/ebusd-configuration/mqtt-hassio.cfg --mqtttopic=ebusd --device=ens:192.168.1.36:9999 --log=all:notice --log=bus:notice --log=update:notice --log=network:notice
2024-11-09 16:58:15.227 [main notice] ebusd 23.2.p20230716 started with auto scan on device: 192.168.1.36:9999, enhanced
2024-11-09 16:58:15.228 [main error] error reading config files from /config/ebusd-configuration/latest/en/: ERR: element not found, last error: 08.csv:3: ERR: element not found, field type TEMP in field 2
2024-11-09 16:58:15.256 [bus notice] device status: resetting
2024-11-09 16:58:15.256 [bus notice] bus started with own address 31/36
2024-11-09 16:58:15.260 [bus notice] device status: reset, supports info
2024-11-09 16:58:15.260 [mqtt notice] connection established
2024-11-09 16:58:15.265 [bus notice] device status: extra info: firmware 1.1[4a1b].1[4a1b], jumpers 0x0b
2024-11-09 16:58:15.268 [bus notice] signal acquired
2024-11-09 16:58:18.325 [bus notice] new master 03, master count 2
2024-11-09 16:58:18.326 [update notice] received unknown BC cmd: 03fe050308010000005428ff3f
2024-11-09 16:58:25.496 [update notice] store 08 ident: ERR: argument value out of valid range
2024-11-09 16:58:25.497 [update error] unable to parse scan-read scan.08 from 3108070400 / 0a410126002000002a0001: ERR: argument value out of valid range
2024-11-09 16:58:25.497 [bus notice] scan 08: ;65; &;
2024-11-09 16:58:25.497 [main error] scan config 08: ERR: argument value out of valid range
2024-11-09 16:58:26.498 [mqtt error] decode scan.08 : ERR: argument value out of valid range
2024-11-09 16:58:28.431 [update notice] received unknown BC cmd: 03fe050308010000005428ff3f

still no useful info and as I'm reading this correctly, ebus cannot convert messages. Any idea ?

[anxdroid]

...and finally I did it !! There was the _template file missing in the local dir and all the data appeared:

now, I'll try to extract something more and share any findings

[tgrosz]

I assembled an excel (will share soon) from a wolf pc app. It has a few more commands, but something is missing. Ebusd config has 3 bytes after the 5022 command but this source has only two - still that two matches the 2nd,3rd of ebusd bytes.

[tgrosz]

And one more thing: if you change the UIN to SIN where the value is 32768, then they'll undefined which is better I think

[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