-
Notifications
You must be signed in to change notification settings - Fork 274
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[HOWTO] Wolf CGB-11, SM-1 and eBus adapter 3 #216
Comments
is one able to change the field names in the config files? |
sure. each field may have a name associated with it in the columns titles "field..." |
Any response to the question, why no solar data shows up? |
you don't have the fields defined that you are querying, e.g.
|
you can define a field with read command but instead of field type
|
I get stuck with: It's getting stuck with: ebusctl i brings this: Any ideas? |
@ngblume Thanks a lot for your detailled step by step description. ebusctrl f gives Any idea where to look or go ahead? |
hm.. very long time ago.... Suggestion:
It appears to me, that I might have made some incorrect assumptions in my original post:
|
Hallo, 2024-02-12` 02:15:45.690 [bus notice] device status: transport opened ebusctl i ebusctl f -F name,comment |
Hi. Great description! I followed the way defined in the opening and in consequence I am able to read the fires from my WOLF gas heating system, however, just in task 22 it needs a small correction. The correct command is cp -r /home/pi/ebus-configs/ebusd-configuration/ebusd-2.x.x/de/* /etc/ebusd/ … the “-r” was missing. Next task: to get the data via MQTT into my iOBroker. |
Hey everyone,
since I recently started working with eBus and the Wolf heating systems, I would like to post my findings / how far I got and how I got there (for everyone looking to get started).
>> Questions at the end of post
System:
eBus-Adapter and tools
Status
HowTo (get there)
sudo apt-get update
sudo apt-get upgrade
sudo nano /etc/default/ebusd
DO NOT use "scanconfig" since the Wolf systems apparrently do not adhere to the specification in this context, at least the CGB-11 does not, see here: Could not read field values (ERR: element not found) #71 (comment))
cd /home/pi/
mkdir ebus-configs
cd ebus-configs
git clone https://github.com/john30/ebusd-configuration.git
sudo mkdir /etc/ebusd/
cd /etc/ebusd
cp /home/pi/ebus-configs/ebusd-configuration/ebusd-2.x.x/de/* /etc/ebusd/
For autostart:
Once: "sudo update-rc.d ebusd defaults",
then to activate or deactive autostart: "update-rc.d ebusd enable" or "update-rc.d ebusd disable"
Result should look something like this:
ebusctl scan full
Results could look something like this:
Results could look something like this:
(And if I understood @john30 correctly, the "error: ERR: argument value out of valid range" is the reason, why scanconfig does not work properly)
Result could look something like this:
Results could look something like this:
=======================
Questions
Now, onto my actual question(s):
Why are there no solar values showing up from the SM-1?
There is the "50.csv" file but that states those values as "w" (Write).
Changing to "r" (Read) puts them in the list of readable as per config (see 31.), but reads timeout (would have been to easy..)
The message show up at the adapter, but the config isn't sufficient to alow the ebusd to decode them:
As per this link somewhen / somehow this ussed to work with these config files: https://forum.fhem.de/index.php?topic=64039.0
But when I try "ebusctl r solar kollektortemp" or "ebusctl r solar wwsolartemp" or "ebusctl r solar pumpe", I get an error:
Could anyone give me a pointer as to how to get those values decoded as well again?
I don't think I need to do "Creating new message definition files" (https://github.com/john30/ebusd/wiki/HowTos#creating-new-message-definition-files), since the definitions are there, but not working properly... but I might be wrong..
Found: #100
But not sure, why this is required since it worked before.. Will try it out tonight...
And second question:
These values (or some of them) should go into a database for logging and plotting... (Grafana und InfluxDB)
Is the best way to poll for data from the ebus daemon at specific intervals or can I register to an event that triggers once a broadcast is received (for all data broadcasted)? And is there any work in this direction in Python that someone is aware of?
Thanks !
Cheers
Niels Göran
The text was updated successfully, but these errors were encountered: