My website solution using RaspberryPi and vbus/usb

[Tobias Tangemann]

Hi,

I just want to show my solution do save and view the data from my Resol BS+ system.

The solution is a return rising masonry heater system controlled by an Resol BS unit.

I'm using the original resol vbus/usb interface adapter connected to my RaspberryPi NAS system.

On the RPi a service is running capturing the data every minute and saving it to a sqlite database.

To view the data I wrote a small cgi program in C to read the data out of the sqlite database and generate an interactive website.

The code is open source.

The cgi program to generate the website: 

https://github.com/tripplet/vbus-server

The capturing service based on another open source project and extend to save the data to sqlite:

https://github.com/tripplet/vbus-collector

For the interactive charting I used http://dygraphs.com.

Hopefully this allows other people to create their own solution.

Feel free to ask if you have any questions.

Best regards

Tobias Tangemann

Screenshot (german):

[Cam]

Hi Tobias,

Interesting project, do you have more info/pictures on the heater itself?

Cheers 

Cam

Away from office - sent from mobile.

--
You received this message because you are subscribed to the Google Groups "Resol Vbus" group.
To unsubscribe from this group and stop receiving emails from it, send an email to resol-vbus+...@googlegroups.com.
To post to this group, send email to resol...@googlegroups.com.
Visit this group at http://groups.google.com/group/resol-vbus.
For more options, visit https://groups.google.com/d/optout.

<screenshot.png>

[Tobias Tangemann]

Hi,

sure the heater is a Quattro Flux HEW 10 and was installed by a firm together with a buffer tank, pump and is included in out normal oil heating.

It was installed in an old masonry heater.

The returning water from the radiators first goes through a water buffer with is being heated by the normal heater via a heat exchanger.

The pumps and valves are controlled by the the Resol BS+, as you know normally for solar ;) but works here too.

The heater is not with out problems, as lever for the the air vent was very poorly designed and had to be exchanged/repaired, luckily inside the warranty period.

But it does it's job.

Tobi

Pictures of the installed heater:

[Tobias Tangemann]

Link to the heater: http://mayr-heiztechnik.com/heizeinsaetze/quattro-flux-hew-10-2/

[Cam]

Thanks for the info Tobias, very interesting, always interesting to see what people use the Resol controllers for :-)

 

Cheers,

 

Cam

 

[Dylan Macleod]

Tobias, 

Hi  I would like to use your setup for my Solar thermal.  So Here is what I have:

Pi Rasp. 1 512mb gen 1 has 2 usb and  WIF dongle. 

4gb sd card, 

Resol Vbus to USB 

Same controller as you , 

Tell you the truth I am not sure where to began. I am kinda new at this.   I am a Mac user so linux should be the same lol.  Let me know

Thank you, 

Dylan 

[Tobias Tangemann]

Hi,

Glad to hear, that you want to use my code ;)

First you should install raspbian on the sdcard of your raspberry pi.

If you have shell access via ssh or locally via keyboard and monitor follow the steps I added in the repositories:

https://github.com/tripplet/vbus-collector

and

https://github.com/tripplet/vbus-server/blob/master/README.md

Most of it should be straight forward, but requires some understanding of linux shell.

Best regards

Tobias

[Dylan Macleod]

You sir are the man.    Can you tell me how to fix the stat /dev/tty_resol no such file or directory    I am using the Resol USB to vbus adaptor.    Maybe there is drivers I have to install?'  

--
You received this message because you are subscribed to the Google Groups "Resol Vbus" group.
To unsubscribe from this group and stop receiving emails from it, send an email to resol-vbus+...@googlegroups.com.
To post to this group, send email to resol...@googlegroups.com.
Visit this group at http://groups.google.com/group/resol-vbus.
For more options, visit https://groups.google.com/d/optout.

--

Dylan Macleod
Email: macleod...@gmail.com
Phone:518-727-8356   Cell

[Dylan Macleod]

Tobias, 

I am stuck at:

  If the VBUS-USB adapter is connected the file /dev/tty_resol should exist   

stat: cannot stat `/dev/tty_resol': No such file or directory   that is what I get.   Any idea?   I don't think the drivers are installed for the vbus to usb. Which that being said How do I go about doing that?  

Thanks 

On Wed, Sep 2, 2015 at 1:24 PM, Tobias Tangemann <tobias.t...@gmail.com> wrote:

--
You received this message because you are subscribed to the Google Groups "Resol Vbus" group.
To unsubscribe from this group and stop receiving emails from it, send an email to resol-vbus+...@googlegroups.com.
To post to this group, send email to resol...@googlegroups.com.
Visit this group at http://groups.google.com/group/resol-vbus.
For more options, visit https://groups.google.com/d/optout.

[Dylan Macleod]

Alright I figured out the Issue,  thanks to the forums there was a driver thing missing.   So Now I def. stuck  on this though.  

Start the monitor-vbus service

 Say's Bash : command not found.  Anything on this ?   

Thanks again 

[Tobias Tangemann]

Cool you got it to work, so I'm assuming the vbus-collector program is working in the step before?

The error message: "command not found" suggests that the command "systemctl" is not available.

Your raspbian might not the latest version and using the classic "SysV-style init" and not "systemd".

For the latest version

$ cat /etc/issue

should print "Raspbian GNU/Linux 7 \n \l"

and

$ cat /etc/debian_version

should print "7.8"

If you are not familiar with the linux init system(s) https://en.wikipedia.org/wiki/Init might give you a rough idea.

I wrote the vbus-monitor.service file for systemd to use the standard way to have daemon running and supervise it.

If you look inside it is not much monitor-vbus.service it basically executes the command given ExecStart

and makes sure the service is started automatic when the resol device is available/plugged in.

The basic behaviour can also be accomplished with and init.d script

See for example https://gist.github.com/naholyr/4275302 on how to create on.

I'll try to create a init.d script for you but i has been some time and I first have to create virtual machine with an old sysV init system

Might get to it this weekend.

As a workaround you can just run:

$ nohup /opt/vbus/collector/vbus-collector --no-print --delay 60 --db /opt/vbus/collector/data.db /dev/tty_resol &

this will execute the same command and keep it running even if you exit the ssh session (See https://en.wikipedia.org/wiki/Nohup)

And make sure you only execute it once otherwise to collevtor process might run and interfere with each other.

Other downside is you have to do this manually everytime you reboot the raspberry pi.

Put for me I also have to manually unplug, wait a few seconds and re plug the usb adapter back in every time I reboot the raspberry pi.

I'm assuming the is a bug in the firmware of the vbus usb adapter, it does not properly initialize itself if it stays connected during a reboot.

You can see if the adapter was recognized with

 $ lsusb

the output should contain

"Bus xxx Device xxx: ID 1fef:2018" which is the resol vbus usb adapter.

Just ask if you have are other questions, I'm glad to help.

Best regards

Tobias

[Evert Terpstra]

Hello Tobias,

Could you help me with this?

I have a Citrin Solar installation, it is an oem version of Resol DeltaSol BX. 

I bought myself a lan interface from Resol to see data flow from my controller.(works at my home at 192.168.178.40)

A friend help me made this script called lanresol.js 

START SCRIPT::::::

var vbus = require('resol-vbus');

var connection = new vbus.TcpConnection({

    host: '192.168.178.40',

    password: 'vbus',

});

var onConnectionStateChange = function(state) {

//        console.log(state);

    };

var headerSet = new vbus.HeaderSet();

var onPacket = function(packet) {

    headerSet.addHeader(packet);

//   console.log('Packet received: ' + packet.getId() + ' ' + packet);

};

connection.on('connectionState', onConnectionStateChange);

connection.on('packet', onPacket);

var spec = vbus.Specification.getDefaultSpecification();

var headerSet = new vbus.HeaderSet();

connection.connect().done(function() {

  setTimeout(function() {

    connection.disconnect();

    var packets = headerSet.getSortedHeaders();

//    console.log(packets)

    var spec = vbus.Specification.getDefaultSpecification();

    var packetFields = spec.getPacketFieldsForHeaders(packets);

    var packet = null;

    packetFields.forEach(function(packetField) {

      if (packet !== packetField.packet) {

        packet = packetField.packet;

        console.log(packetField.packetSpec.fullName);

      }

      console.log('    ' + packetField.name + ':' + packetField.formatTextValue());

    });

  }, 2000);

});

END SCRIPT

This script gives the next output on my command screen:

DeltaSol BX

    Temperature sensor 1:17.3 °C

    Temperature sensor 2:31.0 °C

    Temperature sensor 3:40.6 °C

    Temperature sensor 4:21.9 °C

    Temperature sensor 5:888.8 °C

    RPS temperature:-88.8 °C

    RPS pressure:-999.9 bar

    VFS temperature:-88.8 °C

    Flow rate VFS:-9999 l/h

    Pump speed relay 1:0%

    Pump speed relay 2:100%

    Pump speed relay 3:0%

    Pump speed relay 4:0%

    PWM 1:0%

    PWM 2:0%

    Flow rate VFS:-9999 l/h

    Flow rate V40:0 l/h

    Heat quantity:0 Wh

    System time:15:50

    Date:20150924

    Version:1.01

    Operating seconds relay 1:8004469 s

    Operating seconds relay 2:33025953 s

    Operating seconds relay 3:0 s

    Operating seconds relay 4:0 s

    Status:0

    Blocking protection 1:0

    Blocking protection 2:0

    Blocking protection 3:0

    Blocking protection 4:0

    Initialisation:0

    Filling:0

    Stabilisation:0

    Pump delay:0

    Heat dump:0

    Overrun:0

    Thermal disinfection:0

    System cooling:0

    Store cooling:0

    Spread:0

    Antifreeze:0

    Collector cooling:0

    Unit:11

    Error:0

    Error S1:0

    Error S2:0

    Error S3:0

    Error S4:0

    Error S5:0

    Error S6:0

    Error S7:0

    Error S8:0

    Error S9:0

    Error V40:0

    Leakage:0

    Overpressure:0

    Flow rate error:0

Is there any way to use this with your program, so I can see the following data on a web-page?

Temperature sensor 1:17.3 °C

Temperature sensor 2:31.0 °C

Temperature sensor 3:40.6 °C

Temperature sensor 4:21.9 °C

Pump speed relay 2:100%

System time:15:50

Date:20150924

Operating seconds relay 1:8004469 s

Operating seconds relay 2:33025953 s

Because my Citrin Solar is an OEM version, I can only see above data, but that's fine for me.

Thnxs 

Evert Terpstra

The Netherlands 

   

Op zaterdag 20 juni 2015 22:36:05 UTC+2 schreef Tobias Tangemann:

[Tobias Tangemann]

Hi,

ok so from my understanding you have a script on your desktop machine, which communicates with the resol-vbus lan adapter and displays you the data.

Waht excatly do you want, the time graph over the termeratures and valve positions or just the current temperature on an website.

• For the graph:

You will need a permanenty running machine, in my case this is a raspberry pi which captures the data every minute.

This is the vbus-capture tool which just writes the data into an sqlite database.

This must be adapted for the vbus lan adapter or replaces with your script, which than has to write the data to a sqlite database.

The vbus-server is just a small program which gets the data back out of the sqlite database and formats to csv.

 

• Just the current temperature:

You also need a permanently running machine (for example a RaspberryPi) if you want to access it from any devices (smartphone, ...)

For this solution, you have to copy your script to the machine and make in executable as an cgi script and also configure a webserver on that machine.

Best regards

Tobi 

[hello...@gmail.com]

Hello Everybody

I tried to use from github this: tripplet/vbus-collector

At this step I got this error message. Can some one help me?

Thanks

pi@RaspberryPi:/srv/vbus/collector $ sudo make
gcc -std=gnu99 -O3 -flto -c -Wall -Ipaho.mqtt.c/src/ -D__SQLITE__ kbhit.c -o obj/kbhit.o
gcc -std=gnu99 -O3 -flto -c -Wall -Ipaho.mqtt.c/src/ -D__SQLITE__ serial.c -o obj/serial.o
gcc -std=gnu99 -O3 -flto -c -Wall -Ipaho.mqtt.c/src/ -D__SQLITE__ vbus.c -o obj/vbus.o
gcc -std=gnu99 -O3 -flto -c -Wall -Ipaho.mqtt.c/src/ -D__SQLITE__ sqlite.c -o obj/sqlite.o
gcc -std=gnu99 -O3 -flto -c -Wall -Ipaho.mqtt.c/src/ -D__SQLITE__ mqtt.c -o obj/mqtt.o
gcc -std=gnu99 -O3 -flto -c -Wall -Ipaho.mqtt.c/src/ -D__SQLITE__ main.c -o obj/main.o
gcc obj/kbhit.o obj/serial.o obj/vbus.o obj/sqlite.o obj/mqtt.o obj/main.o -o vbus-collector -Lpaho.mqtt.c/build/src/ -O3 -flto -fuse-linker-plugin -lsqlite3 -lpaho-mqtt3c-static -lpthread
/usr/bin/ld: cannot find -lpaho-mqtt3c-static
collect2: error: ld returned 1 exit status
Makefile:32: die Regel für Ziel „vbus-collector“ scheiterte
make: *** [vbus-collector] Fehler 1

[Mark Richards]

Not familiar with this system, but the linker message tells you where to
focus:
    /usr/bin/ld: cannot find -lpaho-mqtt3c-static

Missing paho-mqtt3c-static library


On 11/24/2018 12:24, hello...@gmail.com wrote:
/usr/bin/ld: cannot find -lpaho-mqtt3c-static


--

[Tobias Tangemann]

You must clone the repository recursively so the submodule is also checked out.

    git clone --recurse-submodules https://github.com/tripplet/vbus-collector.git collector

[hello...@gmail.com]

vBusFan

thank your for your answer.

I'm trying to read an MX controller via VBus/USB converter to my Raspberry PI.

I need somehow to read the that controller and write values to an csv or DB in my Raspberry Pi.

Unfortunately I know only some Python and so I tried this github tutorial hopping to be able to write data to SQlite.

But with this error I'm already stucked.

[Tobias Tangemann]

You might also need to compile the paho.mqtt.c library,

The readme is a litte outdated, the mqtt library is also not mandatory, is is only needed if you want the collector service to push the data into an mqtt server.

e.g. to use them in an homeautomation like https://www.home-assistant.io/ (via sensor.mqtt)

You can look into the Dockerfile or the .travis.yml file for steps which are more up to date.

--
You received this message because you are subscribed to a topic in the Google Groups "Resol Vbus" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/resol-vbus/eDK9Zg6oUGw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to resol-vbus+...@googlegroups.com.

To post to this group, send email to resol...@googlegroups.com.

Visit this group at https://groups.google.com/group/resol-vbus.

[hello...@gmail.com]

Hello Tobias

Thank you for your answer but sorry I don't understand your instrution.

I found on my Raspberry Pi  /srv/vbus/collector/paho.mqtt.c

What should I do with it?

An other question on the README.md it says:

$ mkdir -p /opt/vbus 
$ cd /srv/vbus
Is this not an error? It should creat a folder in /srv/vbus instead /opt/vbus? or not?
I've created an folder vbus in /srv/vbus
Sorry for my basics questions

[Mark Richards]

>>the mqtt library is also not mandatory, is is only needed if you want the collector service to push the data into an mqtt server.

I'm not familiar with your system, but you might try

    make config

at a command line.  You should get a bunch of questions.  Select all the defaults except when it asks about mqtt, say no.

If you're using another set of tools, you can read about those in the docs provided.  There you might find "linker options".

This level of work will require a lot of effort.  I suggest you start by reading about unix compilers and linkers.

/m

You received this message because you are subscribed to the Google Groups "Resol Vbus" group.

To unsubscribe from this group and stop receiving emails from it, send an email to resol-vbus+...@googlegroups.com.

To post to this group, send email to resol...@googlegroups.com.
Visit this group at https://groups.google.com/group/resol-vbus.
For more options, visit https://groups.google.com/d/optout.

--

Mark Richards
29 Juniper
Littleton, MA 01460
617 592 4392
kmal...@gmail.com
k1mg...@gmail.com

[Tobias Tangemann]

You are right this is a mistake in the readme.md, should now be fixed and also include instruction on how to compile the mqtt library.

[hello...@gmail.com]

Hello Tobias thank you,sorry I got an other error after.

pi@RaspberryPi:/srv/vbus/build $  sudo cmake -DPAHO_BUILD_STATIC=TRUE ..

It says:

CMake Error: The source directory "/srv/vbus" does not appear to contain CMakeLists.txt.
Specify --help for usage, or press the help button on the CMake GUI.

Any idea?

[Tobias Tangemann]

You are not in the correct directory, the first command should change the directory to
/srv/vbus/collector/paho.mqtt.c

See step: Compile the data collector service and the include mqtt library...

$ cd /srv/vbus/collector/paho.mqtt.c
$ mkdir build && cd build
$ cmake -DPAHO_BUILD_STATIC=TRUE ..
$ make -j
$ cd /srv/vbus/collector
$ make

[hello...@gmail.com]

Sorry it still doesn't work out.

pi@RaspberryPi:/srv/vbus/collector/paho.mqtt.c $ sudo  cmake -DPAHO_BUILD_STATIC=TRUE ..

CMake Error: The source directory "/srv/vbus/collector" does not appear to contain CMakeLists.txt.

Specify --help for usage, or press the help button on the CMake GUI.

I do the following steps:

1. Downloading the code

$ cd /srv/vbus

$ git clone --recurse-submodules https://github.com/tripplet/vbus-collector.git collector

2.Change to folder paho.mqtt.c

$ cd /srv/vbus/collector/paho.mqtt.c

3.This makes an empty folder or not? And what else?

$ mkdir build && cd build

Executing this command in folder paho.mqtt.c 

$ cmake -DPAHO_BUILD_STATIC=TRUE ..

4.CMake error.

CMake Error: The source directory "/srv/vbus/collector" does not appear to contain CMakeLists.txt.

Specify --help for usage, or press the help button on the CMake GUI.

I can see an CMakeLists.txt file. in the folder, it contains instructions

Sorry I'm really low-level user. I even don't know what you mean with

See step: Compile the data collector service and the include mqtt library... 

It would be very nice if you could help me out.

Am Montag, 26. November 2018 00:46:14 UTC+1 schrieb Tobias Tangemann:

You are not in the correct directory, the first command should change the directory to

/srv/vbus/collector/paho.mqtt.cSee step: Compile the data collector service and the include mqtt library...

[Tobias Tangemann]

No problem it's just one of the steps mentioned in the README file inside the githup repository just work through the manual.

[hello...@gmail.com]

Great it woks! I see some values of my MX Contorller

In your Readme is an error in the beginning of the path, should be
$ sqlite3 /srv/vbus/collector/data.db "SELECT * FROM data ORDER BY id DESC LIMIT 4;"

$ sqlite3 /opt/vbus/collector/data.db "SELECT * FROM data ORDER BY id DESC LIMIT 4;"
  174837|2015-09-02 11:28:10|10:24|18.8|20.9|22.6|22.9|0|0|2302|2425
  174836|2015-09-02 11:29:07|10:22|18.9|20.9|22.7|22.9|0|0|2302|2425
  174835|2015-09-02 11:30:05|10:21|18.8|20.9|22.6|22.9|0|0|2302|2425
  174834|2015-09-02 11:31:03|10:20|18.9|20.9|22.6|22.9|0|0|2302|2425

[Tobias Tangemann]

Glad to hear, thanks for the issue report. The path is fixed now

[Gerrit de Vrij]

Op za 1 dec. 2018 om 11:51 schreef Tobias Tangemann <tobias.t...@gmail.com>:

--

You received this message because you are subscribed to the Google Groups "Resol Vbus" group.

To unsubscribe from this group and stop receiving emails from it, send an email to resol-vbus+...@googlegroups.com.

[It's me]

Just bought a solar plant from https://www.volkssolaranlage.com/ and the controller is a rebranded DeltaSol SLT called SLTV.

I installed HA and the VBus addon from Tobias. There is data on the USB port of the controller and without any interface using "/dev/ttyACM0" in the configuration of the addon.

My question: is there any chance and easy was to rename or translate the legend to Sn and Rn?

Thanks,

John.

[johnd2...@googlemail.com]

Hi Thomas,

I own a DeltaSol SLT which has a USB port and Resol SC can receive data. PID is 0005

Tried your vbus-collector but it seems to be depended on HA. No way to install it in raspian without it. Installed HA, but can not configure the channels. Two temperatures are correct, but wrong named, three others are completely out of scoope. One pump shows 184 percent, the other 34. Both fixed.

Any idea how to change the configuration. SSH is no option because I can not access to the docker container.

Thanks,

John

[Tobias Tangemann]

Hi,

Both projects can still be used without Homeassistant you just have to follow the "How to build" steps to compile the programs yourself.

I even run it myself in on a separate Raspbery PI zero as the Resol adapter causes some strange USB descriptor issues during reboot of my main rpi.

The homeassistant addon is just and easier way to run both programs if everything is on the same system.

Regarding your problem of naming the sensors and scaling you have to change the code yourself this is sadly hardcoded into the program at multiple locations for my usage.

See e.g.

https://github.com/tripplet/vbus-collector/blob/5f6bf700a67d1823156cb279f07446695cb7d907/sqlite.c#L54

https://github.com/tripplet/vbus-collector/blob/5f6bf700a67d1823156cb279f07446695cb7d907/main.c#L383

https://github.com/tripplet/vbus-server/blob/1578eaae14c9f08d4b5a6a7b1e8022082b80d6e3/web/index.htm#L53

...

Additionally there might be an incompatibility with your resol adapter there is also GitHub - danielwippermann/resol-vbus: A JavaScript library for processing RESOL VBus data

Which is a lot more active and supports a broader range of devices.

If you want to stick with my projects I would recommend compiling everything yourself to make the changes you need, afterwards fork vbus-collector, vbus-server and hassio-vbus on github with your changes.

If everything is working you can change the repository urls in hassio-vbus's Dockerfile (hassio-vbus/Dockerfile at master · tripplet/hassio-vbus · GitHub) to your repos.

Then install your own addon into homeassistant which has the modifications you need.

Be aware to always increase the version number in hassio-vbus/config.json at master · tripplet/hassio-vbus · GitHub so Homeassistant picks your changes up as an update.

Best regards

Tobias

[Stephen Harlow]

Thank you for this Tobias.

I've just installed Home Assistant on a Raspberry Pi 3B+ and want to interface it with my Deltasol BS/3 using the Resol VBus/USB interface (my electronics skills were not up to making my own). My intention is run your HA add-on. I have added the git repository to the Add-on store and it shows up, but when I attempted to install the add-on the spinning circle never stops. Rebooting the RP implies the add-on has installed, but it cannot be started, instead it throws the following error:

2022-05-28 11:50:16 ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /addons/fac19ebf_vbus/start - Image fac19ebf/aarch64-addon-vbus:2022.05 does not exist for addon_fac19ebf_vbus

Any idea what I am doing wrong? Is there anything I need to install to locally build container files?

[Tobias Tangemann]

For reference, now fixed with pre build images: https://github.com/tripplet/hassio-vbus/issues/2

[TriLife]

Hello all;

So, there is cleary a way to extract information from the Deltsol BX. But, is there a way to control the unit remotely as well? As in, is there a way to send a command to turn a relay on/off via TCP/IP or USB or anything?

I have a DeltaSol BX Plus, V 2.08 and would like to connect it to my home automation system, ideally via TCP/IP.

Cheers.