-
-
Notifications
You must be signed in to change notification settings - Fork 138
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
Incorrect roomtemp and questions about errors and ebusctl -h commands #64
Comments
okay, added a note to https://github.com/john30/ebusd/wiki/6.-Hardware |
Thanks for your answers. Hope the note in hardware wiki helps others. A full scan doesn't give me any additional info about the BAI product number... That leaves me with the hex messages: But the errors in the readall output are not all listed in the scan result. When I try to read bai Status01 with: "ebusctl write -h 08b5110101" (copied from grab result above but without the master) |
interesting. you bai seems to be very special :-)
In this case you can only use the hardware version fallback (see end of 08.bai.csv) and maybe include thw software version as well.
please post the complete grab result in hex
That's interesting. Need to investigate first. |
Not sure how to do that. I don't see a -h option listed in de ebusctl help for grab. |
the output of grab result (without the decode option) is in hex |
This is due to the message bai Status01 being defined as "read" message. Consequently, you need to issue "ebusctl read -h 08b5110101" in order to use the hex retrieval. |
That worked! pi@raspberrypi:/etc/ebusd $ ebusctl read -h 08b5110101
Isn't that what I posted above? Anyway, I ran a grab and below are the results. grab result all: Errors from readall: Decode option is not supported in the version I'm running (2.4.79708d2) |
is this really the complete grab result? seems that some messages are missing |
At the time it was. Grab has been running since then and now looks like this: pi@raspberrypi:/etc/ebusd $ ebusctl grab result all |
I don't know where the "360 SavingsFunctionTime" comes from in your readall output. seems you have done something weird with the CSVs. |
Hi,
I've been struggling with my heater combination (Vaillant hrSolide VHR NL 30 - 34/3 C in combination with a calorMATIC 360 room thermostat) for a week now and finally have most things running.
(It took me a lot of Google searches to find that the GPIO UART on the PI shouldn't be used)
I use the readall script to read all the data and store it in a MySQL database.
One of the things that keeps bugging me is that the room temperature on the display in the living room is not the same value as reported bij de output of readall
for example:
when the display shows 16.5 the collected data says the displayed temp is 17.75
when the display shows 17.5 the collected data says the displayed temp is 18.69
According to the collected data the offset = 0 (360 RoomTempOffset = 0.00)
In addition I get several errors that I would like to fix (if possible).
I listed some of the errors below.
To figure out what hex-data is actually received by ebusd I have been trying to send the commands myself but I guess I don't understand how to do this correctly because all variations on commands I have tried so far gave me an error message form ebusctl (ERR: element not found or ebusctl syntax info)
Can someone show my what ebustctl write -h xxxxxxx I should send to read "Roomtemp" and let's say "bai status" and "360 SavingsFunctionTime" ?
Finally I get some errors at the bottom of the readall output (broadcast, memory and scan). I assume the broadcast messages should be available so what could be the cause of this?
As for the scan result errors: It looks like the readall script doesn't send the correct data to ebusdctl read resulting in those errors.
Is this something that can be fixed?
Thanks in advance,
Mario
----- System info and logs snippets ----------
These are some of the errors I get in de readall output:
The text was updated successfully, but these errors were encountered: