Replies: 6 comments 2 replies
-
|
Hi all, Thank you for your effort. I am in a similar situation because I have at home a Wolf heatpump (CHC/CHA) with Solar module SM-1 and control module BM-2. As you can see in #776 I am encountering difficulties getting the data (also getting devices to properly show up). I checked out your files in the 22.4.x/de folder and I am currently using them, just restarted ebusd. Please count me in if you need any further information, as I can debug and give data from the system. Mainly because I want this to work :D |
Beta Was this translation helpful? Give feedback.
-
|
My System Layout as Example and a small update on whats going on I have a CGB-35 with BM integrated and directly controlling the hot water tank I scanned my bus and sorted the devices by id and function. I see this communication on regular basis:
Most communication uses the speced protocol messages. |
Beta Was this translation helpful? Give feedback.
-
|
Hello! Currently i cannot get the .csv stuff to work Is this as it looks at your setup: 1 directory, 5 files Greetings |
Beta Was this translation helpful? Give feedback.
-
|
I just pushed my latest working config into my github repro for you to checkout |
Beta Was this translation helpful? Give feedback.
-
Ohh my setup was rubbish, its however working now using other .csv's |
Beta Was this translation helpful? Give feedback.
-
|
@ulda you are correct, that there is no publicly available documentation from Wolf regarding their messages on the ebus, but they published a desktop application in the past and are still publishing an android app which contains metadata files with all information needed to map ebus addresses to readable names and even find out which are supported by a concrete setup. I've "looked closely" at the Wolf Smartset application (and written an ISM to MQTT Adapter). I've already linked the information in #460 (comment) and hoped it would spread further within this community. This tool is not directly talking to the bus, but to an ISM module from Wolf, which basically translates XML to ebus. In the meantime i also extracted, packaged and used the official binaries in a tool to automatically extract all parameters from a given setup without the requirement to run the Wolf app just by connecting to the ISM. So from a user perspective (with the required hardware) it's just:
and you have read and write access to all parameters I haven't thought this through, but I'm pretty confident that it should be possible to write some kind of adaptation layer which translates the protocol from the official app to ebusd or some kind of adapter and thus be able to use the app to extract the exact configuration needed for ebusd. So it should be possible to get the same experience of "run this binary to generate a complete config" for users with an ebus adapter/without an ISM. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, is this topic still relevant? I actually only want to read out 3 values, pump on or off, temperature in the solar buffer and the modules on the roof. Thanks this is how it looks at the moment: root@vclin:~# cat /var/log/ebusd.log |
Beta Was this translation helpful? Give feedback.
-
|
#950 helped a lot. At least I have some basic fields working now, working on getting more to work. |
Beta Was this translation helpful? Give feedback.
-
Hi everybody
I started this discussion to collect everything we have about WOLF Heiztechnik hardware.
and this nearly nothing at the moment (2022-12-29). At least I did not find much googling.
The WOLF systems sometimes also announce manufacturer KROMSCHROEDER. Hold these as synonome.
I did not find any documentation of manufacutrers side of the bus - they keep every docu closed behind ther support portal.
But in the ebus spec there are some defaults documented, and over on ebus-wiki.org they collected the spec documents.
Some of the 05xx and 07xx and 08xx messages can be decoded using this documentation.
But until now nobody used this to create some default CSVs to use for unknown systems.
They also startet to collect about the vendor specific command set 50xx but they did not come far and what I found in the 2.x.x part of this repository look better.
It looks to me like someone poked on the user terminal for each setting and then looked at the messages it generates on the bus.
This would be another way to come forward with reverse-engineering the 50xx command set at least to get some data out of it.
The configs of the 2.x.x directory of this repo did not work for me, either.
Some messages had errors on my CGB-35/KK/BM system. And it was a hazzle to get mqtt autoconfiguration running.
becaus the old names do not fit with the default mqtt-hassio.cfg filtering sheme.
So I startet a fork of the ebusd-configuration repo here at github to put in what I have now: some small set of entities generated from the ebus of my CGB-35 gas heating system.
Now I want you to join to create some working default configuration from this devices.
You can help out
We all would be happy if you post your findings here.
Beta Was this translation helpful? Give feedback.
All reactions