danielwippermann / resol-vbus

A JavaScript library for processing RESOL VBus data

resol-vbus

A JavaScript library for processing RESOL VBus data.

Features

• Connects to various RESOL VBus devices
• Processes live and recorded VBus data streams
• Discovers LAN-enabled RESOL devices on the local network
• Allows to send parameterization commands to a controller
• Synchronizes recorded VBus data from a RESOL datalogger to your local file system
• Converts recorded VBus data into human or machine readable formats, optionally allowing to filter the output

Documentation

You can find the work-in-progress documentation for this project here:

http://danielwippermann.github.io/resol-vbus/

The JSDoc-generated documentation is located here:

http://danielwippermann.github.io/resol-vbus/#/jsdoc

Installation

If you want to use this module in your own application, you can just install it from the npm registry:

⌘  npm install --save resol-vbus

If you want to contribute to it you might want to check out the latest version from GitHub:

⌘  git clone https://github.com/danielwippermann/resol-vbus.git
⌘  cd resol-vbus
⌘  npm install

Running the console examples

⌘  node examples/<name>/index.js

Running the tests

To start a single run of the test suite just enter the following command into your shell:

⌘  npm test

To run the tests after each change to the source just enter the following command into your shell:

⌘  npm test -- --watch

Supported Devices & Services

• All current RESOL controllers with VBus
• RESOL DL2 Datalogger
• RESOL DL3 Datalogger
• RESOL KM2 Communication module
• RESOL VBus/LAN interface adapter
• RESOL VBus/USB interface adapter
• RESOL VBus.net

Technical Information & Specifications

• RESOL VBus Google Group
• RESOL VBus Protocol Specification
• RESOL VBus Packet List
• RESOL VBus Recording File Format
• RESOL VBus Specification File Format v1
• RESOL VBus over TCP Specification
• RESOL DL2 (v2) & DL3 Data Download API

Known issues

• The ConfigurationOptimizers do not yet detect the firmware version running on the controller to be configured. That sometimes causes configuration loads and saves to fail because unknown values are read from or written to (e.g. using the "customizer" example on a DeltaSol MX with firmware version 1.11 or below).

Short-term plans

• Remove current ConfigurationOptimizer constructs in favor of RESOL's official support.

Projects using resol-vbus

• https://github.com/BenniG82/vbus-to-homie

Changelog

Work in progress

Version 0.29.0 (2024-01-22)

• [BREAKING CHANGE] Changed IPv6 device discovery support activation. Previously the options object passed into TcpDataSourceProvider#discoverDevices needed an ipv6 boolean value set to true. That option was removed in favor of a family string value which defaults to "IPv4" but can be set to "IPv6" to perform a IPv6 device discovery. In that case the two other options localAddress and broadcastInterface are required as well. See the documentation for more details.
• Add verifiers for VBus-over-TCP commands to TcpConnectionEndpoint.
• Add connectionAttemptFailed event to TcpConnectionEndpoint.

Version 0.28.0 (2024-01-06)

• Add extendFieldData option to DLxJsonConverter.
• Add SpecificationFile#getPacketTemplate.
• Add password and channel checks to TCP endpoint. (#93)
• Add TcpConnection#disableReconnect.
• Correctly propagate errors during TcpConnection reconnect.

Version 0.27.0 (2022-03-09)

• Fix bugs in SerialConnection and SerialDataSourceProvider

Version 0.26.0 (2022-12-18, never released publicly)

• [BREAKING CHANGE] Removed Recorder, DLxRecorder and FileSystemRecorder The Recorder style of interfaces was not well thought out and unreliable. This version removes it, with no replacement!
• [BREAKING CHANGE] Removed lodash dependency Although this removal was done with great caution and a lot of test coverage, there might be side effects we have not thought of.

Version 0.25.0 (2022-04-12)

• Update several dependencies to fix security issues.
• Update VBus specification file to 20220206.
• Add support for CRC7 in protocols using minor version 1.
• Add Datagram and Telegram support to VBusRecordingConverter.

Version 0.24.0 (2021-09-12)

• [BREAKING CHANGE] Replaced the deprecated "request" dependency with Fetch API impl Since the "request" dependency that was used in the DLxRecorder class has been deprecated, the code was refactored to use a Fetch API implementation instead. But since the method DLxRecorder#downloadToStream expected "request"-specific options, it had to be changed, too. This method was renamed to DLxRecorder#_downloadToStream to indicate that it is a class-private method and its signature was changed to accept Fetch API specific options.

Version 0.23.0 (2021-05-14)

• [BREAKING CHANGE] Replacing custom inheritance code with class syntax Up to this version inheritance was established using a custom extend function. Since only modern ECMAscript runtimes are supported since the last release the code was refactored to use the ECMAscript class syntax instead. In that process the extend function was removed, both the standalone one and the static class function that was added to every "class".

• [BREAKING CHANGE] Returning a Promise from channelListCallback callback The TcpConnection accepts a channelListCallback. This callback gets called with the list of channels returned from the CHANNELLIST command and a done callback.

  Up to this version the return value of the channelListCallback was ignored. Starting with this version this behaviour is changed if the return value of the callback is a Promise:

  • if the Promise reject, the done callback is automatically called with done(reason)
  • if the Promise resolves, the done callback is automatically called with done(null, result)

  This allows the channelListCallback to be async.

• Errors thrown by TcpConnection#connect now have a vbusPhase member describing on which VBus-over-TCP command the error occurred

Version 0.22.0 (2021-05-10)

• [BREAKING CHANGE] Dropping support for Node.js versions < 12

Version 0.21.0 (2020-05-02)

• [BREAKING CHANGE] Returning a Promise from filterPacket or filterDatagram callbacks The Connection#transceive method and many of the helper methods that use it accept a filterPacket and/or filterDatagram callback. Those callbacks get called with the data to filter and a done callback.

  Up to this version the return value of the filter callbacks was ignored. Starting with this version this behaviour is changed if the return value of the filter callbacks is a Promise:

  • if the Promise rejects, the done callback is automatically called with done(reason)
  • if the Promise resolves with null or undefined, the done callback is not called
  • if the Promise resolves with any other result, the done callback is automatically called with done(null, result)

  This allows async filter callbacks!

• Add SerialConnection#baudrate option.

• Stop running Travis tests under Node 6. Some dependency of jest does not work under Node 6 making tests break for that target. The resol-vbus library itself might still work under Node 6, but there is no guarantee...

Version 0.20.0 (2019-06-15)

• This version contains several breaking changes! You have been warned...
  • Refactor code to make use of ES2018 features (using Babel to back-support up to Node.js 6)
  • Remove custom Promise implementation in favor of built-in, native one.
  • Promise return values no longer provide the finally and done methods.
  • Remove utils.promise, utils.Promise and utils.cancelablePromise.
  • Add reportProgress and checkCanceled options to ConnectionCustomizer#transceive{Configuration,Value} as a replacement to the previously used cancelablePromise solution.
• Add RESOL DeltaSol C configuration optimizer.
• Add support for VBus-over-TCP wrapped in TLS.

Version 0.17.0 (2018-02-10)

• Add Buffer support to Connection#(get|set)ValueById for values larger than 32-bit.
• Add Connection#getCaps1.
• Add bulk value transaction support to Connection class.
• Add support to generate and parse "type 9" comment records using VBusRecordingConverter.
• Make it easier to create a Specification from a SpecificationFile.
• Extend vbustouch-proxy example with text data logging feature.
• Update dependencies.
• Some minor bug fixes.

Version 0.16.0 (2017-02-01)

• Use VSF binary file to load VBus specification data
• Add support to read and write raw data in VBus recordings
• Extend VBusRecordingConverter to support fast topology-only scan
• Code clean up
• Several minor bug fixes

Version 0.15.0 (2016-03-30)

• Update VBus specification data
• Several minor bug fixes

Version 0.14.0 (2015-10-29)

• Improve configuration optimizers and their discovery
• Update VBus specification data

Version 0.13.0 (2015-05-14)

• Add configuration optimizers for RESOL DeltaSol SLT
• Add BlockType support

Version 0.12.2 (2015-05-05)

• Update VBus specification data

Version 0.12.1 (2015-04-27)

• Add configuration optimizers for RESOL DeltaSol MX and BS/4 v2
• Add a simple JSON live data server example
• Add some documentation
• Several bug fixes

Version 0.12.0 (2015-02-28)

• Add vbustouch-proxy example
• Add support for rounding floating point numbers

Version 0.11.1 (2014-11-04)

• Fix a floating point bug caused by setRawValue

Version 0.11.0 (2014-10-29)

• Added support for setting packet field values
• Several bug fixes

Version 0.10.0 (2014-04-26)

• Finalized support for customizing controller configuration.
• Several bug fixes.

Version 0.9.0 (2014-03-16)

• Completed Recorder class by adding support for recording
• Added unit conversion to VBus specification
• Several bug fixes.

Version 0.8.0 (2014-03-03)

• Extended Converter and VBusRecordingConverter to support object mode in stream (for performance reason)
• Fixed several bugs
• Increased test coverage and completed documentation.

Version 0.7.0 (2014-02-17)

First release to the NPM registry.

Contributors

• Thorsten Müller
• Paul Hanna
• Sabine Käß
• Andrew Thompson (@thompsa)
• @t9zx
• @SurfGargano
• @epenet

Legal Notices

RESOL, VBus, VBus.net and others are trademarks or registered trademarks of RESOL - Elektronische Regelungen GmbH.

All other trademarks are the property of their respective owners.

License

The MIT License (MIT)

Copyright (c) 2013-present, Daniel Wippermann.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

resol-vbus's Issues

Use RS232/RS486 USB Adapter

How can I use resol-vbus to decode data from a USB Serial adapter like RS232/485?
I have the raw data being logged in Resol Service Center but was hoping to use this software to decode it?

Support for upload to pvoutput.org

Pvoutput.org provides a very nice log for Solar generations, and a nice API to do so, both by interval and by day summary.

Before I start digging into the code, would you consider adding support for data upload to this site ?
example:
https://pvoutput.org/list.jsp?id=52161&sid=47420
The 'extended data' variables could be used for the Temperatures (for example).

Missing Documentation for example/json-live-data-server

The json-live-data-server is missing documentation for the use case of publishing data from a serial port based vbus device (like VBus/USB Adapter).

VBus/LAN not connecting properly

Hi,
I'm trying to get data into my home automation system from my DeltaSol BS/2 via a VBus/LAN but I'm not getting a connection.

I have the VBus/LAN and DeltaSol BS2 setup and working.
I can connect to the VBus/LAN with RSC and see valid data and its updating.
Running on a Windows 10 64bit machine and the VBus/LAN is firmware V2.0.

I tried to Telnet to the VBus/LAN and get the folloing issue.
It seems to half process and then falls over :(

Any help would be appreciated.

Bernie

Write data to Deltasol MX

I have a Deltasol MX with VBUS Adapter (USB).

It is possible to send data to the Deltasol MX ?

My plan: I will check the weather data (primary the sun data) for next 1-2 hourse before the burner will start (Temp: <=44•C).

If i see, as example, in the next 1-2 hours the sun will shining the stop/hold the start of the burner

It is possible ? The logic i can self develop. The question is, how can i send to the deltasol MX or stop/hold the burning process ?

with iobroker.resol (daniel wippermann) v 0.22.0 the connection can't be established

Daniel has changed the connection procedure in thje v0.22.0 , so an error is shown and no connection is established : Unable to create optimizer for master with address 0x1121

I cannot seem to enjoy getting (and setting) values in the controller - Deltasol BX + KM2

Context - I have the Deltasol BX controller working with the KM2 interface.

What works (thank you!!)
-> getting the sensor values and publishing it to mqtt
-> getting device address with connection.waitForFreeBus(20000)

What doesn't work
-> I cannot seem to enjoy getting (and setting) values in the controller. Is this functionality available for BX controller?
// result is always null,

connection.getValueIdByIdHash(deviceAddress, 0x7087886A).then(result => {
logger.debug('in result -> ' + JSON.stringify(result) );
//tried other getters too
// set the values using Connection#setValueById. didn't go so far as my result for get is always null
}); //

// I found following in BX_3.03-Menu.xml (but i tried 3.02-Menu also)

        /**	<value id='Handbetrieb1' idHash='0x70878869' index='368'>
		<type id='VtHandbetrieb1' base='ManualMode' externalDescriptorFunc='true'>
			<default>0</default>
		</type>
	</value>
	<value id='Handbetrieb2' idHash='0x7087886A' index='369'>
		<type id='VtHandbetrieb2' base='ManualMode' externalDescriptorFunc='true'>
			<default>0</default>
		</type>
	</value>
	<value id='Handbetrieb3' idHash='0x7087886B' index='370'>
		<type id='VtHandbetrieb3' base='ManualMode' externalDescriptorFunc='true'>
			<default>0</default>
		</type>
	</value>
	<value id='Handbetrieb4' idHash='0x7087886C' index='371'>
		<type id='VtHandbetrieb4' base='Tristate'>
			<default>0</default>
		</type>
	</value>

Openhab Resol Binding with Citrin SLR

Hi there,

I installed Openhab 3.1 with Resol Binding on a Raspberry Pi 4. For the connection to the Citrin SLR heating control, I have a Resol KM2. The integration of the KM2 and the Citrin SLR in Openhab works without any problems.
Unfortunately, the values are only transferred once (when integrating, or after restarting the KM2). I also don't know whether all values will be transferred.
For information: The values are updated again and again on vbus.net and the binding also works perfectly under openHAB 2.5.
Unfortunately I saw that my Citrine SLR is not on the list of compatible devices, maybe that's my problem.

Could it be possible to add my device?

Best regards
Yokes

PS: The translation into English was done by Google :-)

Determine KM2 version via GET request

Hey @danielwippermann is there any api on KM2 besides cgi-bin/resol-webservice or any call that returns us if this is a KM2 device. For the Home Assistant plugin we are currently trying to improve the error handling and on DL2/DL3 devices we found a way of checking if it is a DL2/DL3 but for KM2 we don't. Best, DIrk

Lacking documentation for `VBusRecordingConverter`

I'd like to use the VBusRecordingConverter to get data out of VBus dump files, but I can't figure out how to make it read a file! The furthest I've got is that I need to provide a Buffer to rxBuffer in the converter's constructor, but I'm unsure after that how to go about getting data out of the converter.

If you can point me in the right direction I'd be happy to write some documentation for the class, or provide a commented example!

Error in the documentation

For a client I had to implement a custom implementation of resol-vbus.

The client has a TiSUN Multiplex, a TiSUN Webmodule EX and two Multiplex expansion modules.

Thanks to this packet list I was able to decode the information my client needed. It also needed the states of the relays of the expansion modules. The tech support at TiSUN told me, that EM #0 (0x6650) <= Broadcast (0x0000), command 0x0200 is the packet I was looking for.

However when I scanned the whole vbus, such a packet was never sent, instead there were two other packages (with targets 0x6651 and 0x6652) that had the same structure. At first I didn't realize that these packages were the relays values and my implementation dropped them. After careful inspection I realized that these packages contained the relays values. Also the spec XML files in the resol software do not list these packages.

These two packages should be added to the documentation.

TcpConnection socket unable to connect

Hi,

I've used the library with success for one year peer with a Resol Vbus Lan Adapter. Sadly, since a few days, the tcp connection can't be established anymore:
The error is the following:
Error: Unable to connect at onSocketTermination (*****/tcp-connection.js:336:16) at Socket.OnError (*****/tcp-connection.js:367:9) at Socket.emit (events.js:189:13) at emitErrorNT (internal/streams/destroy.js:82:8) at emitErrorAndCloseNT (internal/streams/destroy.js:50:3) at process._tickCallback (internal/process/next_tick.js:63:19)

I've checked the wiring and everything seems find on that side.

When I press the reset button on the device, I'm able to reconnect and read data, but when I close the connection, I'm unable to re-connect. The device seems to be still working/connected (led active) even though the program exited.

I activated some log on the tcp-connection.js class and force connect, but it seems that I'm stuck at the PASS instruction:
onData
+HELLO

onLine phase:0
newPhase:40
onData
+HELLO

onLine phase:0
newPhase:40
onData
+HELLO

Add documentation on how parametrization works

Home Assistant implementation

Hi Daniel, like your work! Very easy to implement it to Home Assistant. Maybe something for the readme?

Home Assistant implementation:

setup as described in: https://github.com/danielwippermann/resol-vbus/tree/master/examples/json-live-data-server

Home assistant configuration.yaml settings to add:

rest:

• resource: http://127.0.0.1:3333/api/v1/live-data
  scan_interval: 60
  sensor:
  • name: "Resol Temperature sensor 1"
    value_template: '{{value_json[0].rawValue | round(1)}}'
    unit_of_measurement: '°C'
    json_attributes_path: "$[0]"
    json_attributes:
    • "name"
    • "rawValue"
  • name: "Resol Temperature sensor 2"
    value_template: '{{value_json[1].rawValue | round(1)}}'
    unit_of_measurement: '°C'
    json_attributes_path: "$[1]"
    json_attributes:
    • "name"
    • "rawValue"
  • name: "Resol Temperature sensor 3"
    value_template: '{{value_json[2].rawValue | round(1)}}'
    unit_of_measurement: '°C'
    json_attributes_path: "$[2]"
    json_attributes:
    • "name"
    • "rawValue"
  • name: "Resol Temperature sensor 4"
    value_template: '{{value_json[3].rawValue | round(1)}}'
    unit_of_measurement: '°C'
    json_attributes_path: "$[3]"
    json_attributes:
    • "name"
    • "rawValue"
  • name: "Resol Temperature sensor 5"
    value_template: '{{value_json[4].rawValue | round(1)}}'
    unit_of_measurement: '°C'
    json_attributes_path: "$[4]"
    json_attributes:
    • "name"
    • "rawValue"
  • name: "Resol Pump speed relay 1"
    value_template: '{{value_json[6].rawValue}}'
    unit_of_measurement: '%'
    json_attributes_path: "$[6]"
    json_attributes:
    • "name"
    • "rawValue"
  • name: "Resol Pump speed relay 2"
    value_template: '{{value_json[7].rawValue}}'
    unit_of_measurement: '%'
    json_attributes_path: "$[7]"
    json_attributes:
    • "name"
    • "rawValue"

go to Home Assistant, configuration, server management --> Check configuration.

If ok, restart Home Assistant and the values should be available now. Search for "Resol" entities.

TypeError: No path specified

Hi Daniel,

I am trying to get resol-vbus running on a RaspberryPi connected via USB to the Resol USB device http://www.resol.de/index/produktdetail/kategorie/2/id/74/sprache/en-us/.
Albeit some warnings npm seemed to have installed resol-vbus and the json-live-data-server example successfully.
When running node index.js I get this error:

/home/pi/resol-vbus/examples/json-live-data-server/node_modules/q/q.js:155
                throw e;
                ^

TypeError: No path specified
    at new SerialPort (/home/pi/resol-vbus/node_modules/serialport/lib/serialport.js:92:11)
    at Connection.extend._createSerialPort (/home/pi/resol-vbus/src/serial-connection.js:208:16)
    at Connection.extend._connect (/home/pi/resol-vbus/src/serial-connection.js:192:27)
    at Connection.extend.connect (/home/pi/resol-vbus/src/serial-connection.js:78:21)
    at /home/pi/resol-vbus/examples/json-live-data-server/index.js:121:25
    at _fulfilled (/home/pi/resol-vbus/examples/json-live-data-server/node_modules/q/q.js:854:54)
    at self.promiseDispatch.done (/home/pi/resol-vbus/examples/json-live-data-server/node_modules/q/q.js:883:30)
    at Promise.promise.promiseDispatch (/home/pi/resol-vbus/examples/json-live-data-server/node_modules/q/q.js:816:13)
    at /home/pi/resol-vbus/examples/json-live-data-server/node_modules/q/q.js:624:44
    at runSingle (/home/pi/resol-vbus/examples/json-live-data-server/node_modules/q/q.js:137:13)

Is there something missing in the config.js file? Is SerialConnection correct?

Here is mine:

/*! resol-vbus | Copyright (c) 2013-2017, Daniel Wippermann | MIT license */
'use strict';



var path = require('path');



var config = {

        /**
         * The port number for the HTTP server to listen to.
         * @type {Number}
         */
        httpPort: 3333,

        /**
         * The inteval in milliseconds between two writes of the logging file.
         * @type {Number}
         */
        loggingInterval: 10000,

        /**
         * The filename of the logging file.
         * @type {String}
         */
        loggingFilename: path.resolve(__dirname, 'live-data.json'),

        /**
         * The name of the `Connection` subclass to use for connecting to the VBus.
         * @type {String}
         */
        connectionClassName: 'SerialConnection',

        connectionOptions: {
                /**
                 * The host name / IP address of the VBus/LAN or Datalogger device.
                 * @type {String}
                 */
                host: '192.168.13.21',

                /**
                 * The password for the VBus/LAN or Datalogger device.
                 * @type {String}
                 */
                password: 'vbus',
        },

};



module.exports = config;

Many thanks in advance,
Daniel

resol-vbus installations probleme

Hallo Daniel

Ich habe versucht dein RESOL-VBUS auf meinem Raspberry Pi 2 zu installieren.
Leider habe ich dabei einige Fehlermeldungen erhalten.
Könntest Du mir dabei vielleicht weiter helfen?

Schlussendlich versuche ich Daten aus einem Resol VBus/USB Interface Adapter zu lesen.
http://www.resol.de/index/produktdetail/kategorie/2/id/13/sprache/en

Folgendes habe ich (auf einer nackten Rasbian Installation) ausgeführt:

1. sudo apt-get install nodejs npm node-semver
2. sudo npm -g install npm
3. sudo npm install --save resol-vbus

Beim 3. Befehl ist folgendes rausgekommen:

npm WARN deprecated [email protected]: lodash@<3.0.0 is no longer maintained. Upgrade to lodash@^4

> [email protected] install /home/pi/mystuff/resol-vbus/node_modules/serialport
> node-pre-gyp install --fallback-to-build

gyp WARN EACCES user "root" does not have permission to access the dev dir "/root/.node-gyp/0
gyp WARN EACCES attempting to reinstall using temporary dev dir "/home/pi/mystuff/resol-vbus/dules/serialport/.node-gyp"
make: Entering directory '/home/pi/mystuff/resol-vbus/node_modules/serialport/build'
make: *** No rule to make target '../.node-gyp/0.10.29/common.gypi', needed by 'Makefile'.  S
make: Leaving directory '/home/pi/mystuff/resol-vbus/node_modules/serialport/build'
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-/build.js:276:23)
gyp ERR! stack     at ChildProcess.emit (events.js:98:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:809:12)
gyp ERR! System Linux 4.4.13-v7+
gyp ERR! command "node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.jld" "--fallback-to-build" "--module=/home/pi/mystuff/resol-vbus/node_modules/serialport/builde/serialport.node" "--module_name=serialport" "--module_path=/home/pi/mystuff/resol-vbus/nodes/serialport/build/Release"
gyp ERR! cwd /home/pi/mystuff/resol-vbus/node_modules/serialport
gyp ERR! node -v v0.10.29
gyp ERR! node-gyp -v v3.3.1
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute 'node-gyp build --fallback-to-build --modulepi/mystuff/resol-vbus/node_modules/serialport/build/Release/serialport.node --module_name=ser --module_path=/home/pi/mystuff/resol-vbus/node_modules/serialport/build/Release' (1)
node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/home/pi/mystuff/resol-vbus/node_modrialport/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:98:17)
node-pre-gyp ERR! stack     at maybeClose (child_process.js:755:16)
node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:822:5)
node-pre-gyp ERR! System Linux 4.4.13-v7+
node-pre-gyp ERR! command "node" "/home/pi/mystuff/resol-vbus/node_modules/serialport/node_mobin/node-pre-gyp" "install" "--fallback-to-build"
node-pre-gyp ERR! cwd /home/pi/mystuff/resol-vbus/node_modules/serialport
node-pre-gyp ERR! node -v v0.10.29
node-pre-gyp ERR! node-pre-gyp -v v0.6.26
node-pre-gyp ERR! not ok
Failed to execute 'node-gyp build --fallback-to-build --module=/home/pi/mystuff/resol-vbus/noles/serialport/build/Release/serialport.node --module_name=serialport --module_path=/home/pi//resol-vbus/node_modules/serialport/build/Release' (1)
npm WARN install:[email protected] [email protected] install: `node-pre-gyp install --fallback-d`
npm WARN install:[email protected] Exit status 1
npm WARN saveError ENOENT, open '/home/pi/mystuff/resol-vbus/package.json'
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/har-validator/nodes/chalk/node_modules/has-ansi/node_modules/ansi-regex -> node_modules/ansi-regex
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/har-validator/nodes/chalk/node_modules/ansi-styles -> node_modules/ansi-styles
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/http-signature/node_modupk/node_modules/asn1 -> node_modules/asn1
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/http-signature/noles/assert-plus -> node_modules/assert-plus
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/form-data/node_modules/> node_modules/async
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/aws-sign2 -> node_maws-sign2
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/aws4 -> node_modules/aws
[email protected] node_modules/resol-vbus/node_modules/buffer-more-ints -> node_modules/more-ints
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/caseless -> node_moaseless
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/bl/node_modules/e-stream/node_modules/core-util-is -> node_modules/core-util-is
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/http-signature/nodes/sshpk/node_modules/dashdash -> node_modules/dashdash
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/combined-streamodules/delayed-stream -> node_modules/delayed-stream
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/combined-streode_modules/combined-stream
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/har-valiode_modules/chalk/node_modules/escape-string-regexp -> node_modules/escape-string-regexp
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/extend -> node_modules
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/http-signature/nodes/jsprim/node_modules/extsprintf -> node_modules/extsprintf
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/forever-agent -modules/forever-agent
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/har-validat_modules/is-my-json-valid/node_modules/generate-function -> node_modules/generate-function
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/http-signature/node_msshpk/node_modules/getpass -> node_modules/getpass
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/har-validat_modules/commander/node_modules/graceful-readlink -> node_modules/graceful-readlink
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/har-validator/node_/commander -> node_modules/commander
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/har-validator/node_mchalk/node_modules/has-ansi -> node_modules/has-ansi
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/hawk/node_modules/hoek _modules/hoek
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/hawk/node_modules/boom _modules/boom
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/hawk/node_modules/cs -> node_modules/cryptiles
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/bl/node_modules/readream/node_modules/inherits -> node_modules/inherits
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/har-validator/nodes/is-my-json-valid/node_modules/generate-object-property/node_modules/is-property -> node_mos-property
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/har-or/node_modules/is-my-json-valid/node_modules/generate-object-property -> node_modules/generact-property
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/is-typedarray -modules/is-typedarray
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/bl/node_modules/readaeam/node_modules/isarray -> node_modules/isarray
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/isstream -> node_modstream
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/http-signature/node_modupk/node_modules/jsbn -> node_modules/jsbn
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/http-signature/nodes/sshpk/node_modules/jodid25519 -> node_modules/jodid25519
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/http-signature/node_/sshpk/node_modules/ecc-jsbn -> node_modules/ecc-jsbn
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/http-signature/noles/jsprim/node_modules/json-schema -> node_modules/json-schema
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/json-striafe -> node_modules/json-stringify-safe
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/har-validator/nodes/is-my-json-valid/node_modules/jsonpointer -> node_modules/jsonpointer
[email protected] node_modules/resol-vbus/node_modules/lodash -> node_modules/lodash
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/mime-types/node_modue-db -> node_modules/mime-db
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/mime-types -> nodes/mime-types
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/form-data -> noles/form-data
[email protected] node_modules/resol-vbus/node_modules/moment -> node_modules/moment
[email protected] node_modules/resol-vbus/node_modules/moment-timezone -> node_modules/momezone
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/node-uuid -> node_mnode-uuid
[email protected] node_modules/resol-vbus/node_modules/numeral -> node_modules/numeral
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/oauth-sign -> nodes/oauth-sign
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/har-validator/node_modnkie-promise/node_modules/pinkie -> node_modules/pinkie
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/har-validator/dules/pinkie-promise -> node_modules/pinkie-promise
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/bl/node_/readable-stream/node_modules/process-nextick-args -> node_modules/process-nextick-args
[email protected] node_modules/resol-vbus/node_modules/q -> node_modules/q
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/qs -> node_modules/qs
- [email protected] node_modules/resol-vbus/node_modules/request/node_modules/har-validator/noles/chalk/node_modules/strip-ansi/node_modules/ansi-regex
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/hawk/node_modules/sntp -modules/sntp
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/hawk -> node_modules/haw
[email protected] node_modules/resol-vbus/node_modules/sprintf -> node_modules/sprintf
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/http-signature/noles/sshpk/node_modules/assert-plus -> node_modules/sshpk/node_modules/assert-plus
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/bl/node_modudable-stream/node_modules/string_decoder -> node_modules/string_decoder
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/stringstream -> dules/stringstream
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/har-validator/nodes/chalk/node_modules/strip-ansi -> node_modules/strip-ansi
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/har-validator/dules/chalk/node_modules/supports-color -> node_modules/supports-color
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/har-validator/node_modulk -> node_modules/chalk
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/tough-cookie -> dules/tough-cookie
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/tunnel-agent -> dules/tunnel-agent
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/http-signature/nodes/sshpk/node_modules/tweetnacl -> node_modules/tweetnacl
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/http-signature/node_modhpk -> node_modules/sshpk
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/bl/node_moduleble-stream/node_modules/util-deprecate -> node_modules/util-deprecate
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/bl/node_modulable-stream -> node_modules/readable-stream
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/bl -> node_modules/bl
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/http-signature/node_mosprim/node_modules/verror -> node_modules/verror
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/http-signature/node_mosprim -> node_modules/jsprim
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/http-signaturee_modules/http-signature
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/har-validator/node_modumy-json-valid/node_modules/xtend -> node_modules/xtend
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/har-validat_modules/is-my-json-valid -> node_modules/is-my-json-valid
[email protected] node_modules/resol-vbus/node_modules/request/node_modules/har-validator -modules/har-validator
[email protected] node_modules/resol-vbus/node_modules/request -> node_modules/request
/home/pi/mystuff/resol-vbus
└─┬ [email protected]
  └─┬ [email protected]
    └─┬ [email protected]
      └─┬ [email protected]
        ├─┬ [email protected]
        │ └── [email protected]
        └─┬ [email protected]
          └── [email protected]

npm WARN enoent ENOENT, open '/home/pi/mystuff/resol-vbus/package.json'
npm WARN resol-vbus No description
npm WARN resol-vbus No repository field.
npm WARN resol-vbus No README data
npm WARN resol-vbus No license field.

Vielen Dank und lieber Gruss
Daniel

Protocol version 3.x VFD/RPD-Sensoren

Guten Tag,

Ich suche eine genauere Beschreibung des Protokolls Version 3.x für die VFD und RPD Sensoren. Leider kann ich zu den gesendeten Daten der Sensoren keine genaue Beschreibung finden. Ich würde gerne die Daten der Sensoren über den VBus auslesen und interpretieren können (ohne zusätzlichen Regler). Können Sie mir da vielleicht weiter helfen? Für eine Unterstützung bedanke ich mich schon im voraus.

Grüßen

Andreas

Disable logging file

Hi Daniel

Firstly, thank you so much for your work and contribution. Kudos to you!

I'm using the json-live-data-server and don't want to write the logging file because I am looking to reduce the number of writes to the SD card of my Pi. I only want to make the json available via http where I retrieve it and consume it. I've tried commenting out the loggingFilename which works but throws "error: undefined" when the process runs. Is there currently a "clean" way to achieve this?

Thanks again

Jason

system date - format

Hi,
Wonderfull work! Following your instructions I had the json-live-data-server example running with my deltasol in minutes.
What I was not able to figure out is the format of the 'system date'. No clue how to parse this to a better readable format. See below my json. Any suggestions, I must be missing something obvious. Not a coding expert.
thanks!
{
"id": "00_0010_1001_10_0100_000_4_0",
"name": "System date",
"rawValue": 676801591
},

Documentation Menu Links Broken

Hi Daniel,

You probably know this already but just in case, all the menu links are broken.

Cheers

http://danielwippermann.github.io/resol-vbus/docs.html

Missing example file for use em example

credentials for http://{{resol_IP}}/cgi-bin/resol-webservice REST API

I have a new KM2 working. I can get to the local web application but I want to use the REST API as well.
The GET http://{{resol_IP}}/cgi-bin/get_resol_device_information works fine and returns:

vendor = "RESOL"
product = "KM2"
serial = "40A36BCB595A"
version = "2.0.0"
build = "rc1"
name = "KM2-40A36BCB595A"
features = "vbus,wifi"

But for the calls to POST http://{{resol_IP}}/cgi-bin/resol-webservice I need the "authId" parameter (I got that much from reading the other issues and internet posts).
To get an authId I try to call with "method": "login" . But I don't know which username/password to provide in the body. I tried my vbus.net user/pw and that does not work (did not think it would - was expecting some local authentication). But the local webinterface has no named users and I can't leave the username empty either. So I keep getting this error.

Any tipps would be greatly appreciated. I do understand I could use the Javascript VBUS server from this Git repo - but for my purpose some simple REST calls are much easier to integrate (I want to use this with node red).

Thanks in advance for the help!

[
{
"jsonrpc": "2.0",
"id": "1",
"error": {
"category": "App",
"message": "Invalid credentials"
}
}
]

Error: Cannot find module 'fs/promises'

I created an Add-on for Home Assistant but getting this error:

internal/modules/cjs/loader.js:818
  throw err;
  ^
Error: Cannot find module 'fs/promises'
Require stack:
- /bin/resol-vbus/src/file-list-reader.js
- /bin/resol-vbus/src/index.js
- /bin/resol-vbus/examples/resol-vbus.js
- /bin/resol-vbus/examples/json-live-data-server/index.js
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:815:15)
    at Function.Module._load (internal/modules/cjs/loader.js:667:27)
    at Module.require (internal/modules/cjs/loader.js:887:19)
    at require (internal/modules/cjs/helpers.js:74:18)
    at Object.<anonymous> (/bin/resol-vbus/src/file-list-reader.js:2:12)
    at Module._compile (internal/modules/cjs/loader.js:999:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
    at Module.load (internal/modules/cjs/loader.js:863:32)
    at Function.Module._load (internal/modules/cjs/loader.js:708:14)
    at Module.require (internal/modules/cjs/loader.js:887:19) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '/bin/resol-vbus/src/file-list-reader.js',
    '/bin/resol-vbus/src/index.js',
    '/bin/resol-vbus/examples/resol-vbus.js',
    '/bin/resol-vbus/examples/json-live-data-server/index.js'
  ]
}

The installation process is documented here: https://github.com/dm82m/hassio-addons/blob/main/resol-vbus/Dockerfile

Kudos for providing the resol-vbus JS-library

This is not to report an issue but rather to give kudos to you, Daniel @danielwippermann
for your brilliant and continuing work to provide an easy access tool for Resol VBus devices
to the community.
It made putting together a VBus Adapter for ioBroker https://github.com/ioBroker
really simple.
So, thanks once again for your high-quality resol-vbus library - and keep up the good work.
Best Regards
@pdbjjens

Integrate em-simulator into json-live-data-server

Hi,
not really a issue more a feature suggestion:

Is it possible to integrate the em-simulator as (POST) endpoint into the json-live-data-server?

E.g.:

POST -> http://127.0.0.1:3333/api/v1/em/<EmSubAddress>/sensor/<sensorId>/resistance
{
    "value": int (resistant)
}

POST -> http://127.0.0.1:3333/api/v1/em/<EmSubAddress>/sensor/<sensorId>/bas
{
    "temperature": float
    "mode": int
}

GET -> http://127.0.0.1:3333/api/v1/em/<EmSubAddress>/relay/<relayId>
{
    "value": int
}

Unfortunately, I'm no Java(Script) guy, so I did not manage to get it together.
This would make the integration of Resol devices into Home Assistant etc. much easier and provide a lot of new possibilities.

Thank you for your work! And as I said, just a suggestion, no pressure :)

not able to build/install

Hi Daniel,

I'm trying to install your work on a raspberry to be able to read my vbus-lan however i have no experience with node.js. So I try to just simply follow the instructions: (i use node v8.11.1 and npm 1.4.21 and i also tried it with sudo, same error)

git clone https://github.com/danielwippermann/resol-vbus.git
cd resol-vbus
npm install

But this gives errors:

(node:7495) [DEP0022] DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.
npm ERR! Error: Method Not Allowed
npm ERR! at errorResponse (/usr/share/npm/lib/cache/add-named.js:260:10)
npm ERR! at /usr/share/npm/lib/cache/add-named.js:203:12
npm ERR! at saved (/usr/share/npm/node_modules/npm-registry-client/lib/get.js:167:7)
npm ERR! at FSReqWrap.oncomplete (fs.js:135:15)
npm ERR! If you need help, you may report this entire log,
npm ERR! including the npm and node versions, at:
npm ERR! http://github.com/npm/npm/issues

npm ERR! System Linux 4.19.66+
npm ERR! command "/usr/bin/node" "/usr/bin/npm" "install"
npm ERR! cwd /home/pi/projects/resol-vbus
npm ERR! node -v v8.11.1
npm ERR! npm -v 1.4.21
npm ERR! code E405
npm WARN deprecated [email protected]: request has been deprecated, see request/request#3142
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /home/pi/projects/resol-vbus/npm-debug.log
npm ERR! not ok code 0

pi@raspberrypi:~/projects/resol-vbus $ sudo npm install
(node:7555) [DEP0022] DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.
npm ERR! Error: Method Not Allowed
npm ERR! at errorResponse (/usr/share/npm/lib/cache/add-named.js:260:10)
npm ERR! at /usr/share/npm/lib/cache/add-named.js:203:12
npm ERR! at saved (/usr/share/npm/node_modules/npm-registry-client/lib/get.js:167:7)
npm ERR! at FSReqWrap.oncomplete (fs.js:135:15)
npm ERR! If you need help, you may report this entire log,
npm ERR! including the npm and node versions, at:
npm ERR! http://github.com/npm/npm/issues

npm ERR! System Linux 4.19.66+
npm ERR! command "/usr/bin/node" "/usr/bin/npm" "install"
npm ERR! cwd /home/pi/projects/resol-vbus
npm ERR! node -v v8.11.1
npm ERR! npm -v 1.4.21
npm ERR! code E405
npm WARN deprecated [email protected]: request has been deprecated, see request/request#3142
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /home/pi/projects/resol-vbus/npm-debug.log
npm ERR! not ok code 0

any clues?

Thanks in advance, Arthur

With npm install the new version all the optimizer and src / dist directory are gone

With npm install the new version all the optimizer files and src / dist directory are gone

rpt-files folder does not exist

The 'rpt-files' directory mentioned on line 189 of the configuration-importer example does not exist

[Question] Will this be updated further?

Hello,

first of all thank you for this, currently building a angularJS web dashboard for showing live data.
I noticed some warning when installing the packet as other packets are deprecated or out of date.
Will this be updated? And will you push those updates to the npm then? Or should I build it from the source here?

Wrong Password

Hi,
i start the example but got an error with my KM2 Module.

~/resol-vbus/examples/json-live-data-server $ node index.js
debug: Starting server...
debug: Connect to VBus data source...
error: undefined {"vbusPhase":"PASS"}

In the config i have set the correct IP of my KM2 and the password which i got/set from here:

can you help me?

VBUS with just a usb ftdi connector?

Hi,

Not an issue, just a question

Do I need additional hardware like a datalogger or resol proprietary usb interface to use this? or can I connect a usb rs232 or RS485 serial port to the vbus connections?

Thanks for all your work.

json-live-data-server not updating values

hi,

i dont know if the problem is on vbus side or on json-live-data-server. i have two resol, one 5611 and 2271. i am monitoring with grafana and sometimes i see that the values arent updated for some period. if i curl i get the same values, they are not updatet:

root@stony2:/resol-vbus/examples/json-live-data-server# curl -s http://127.0.0.1:3333/api/v1/live-data
[
{
"id": "00_0010_2271_10_0100_000_4_0",
"name": "System date",
"rawValue": 582795724
},
{
"id": "00_0010_2271_10_0100_004_2_0",
"name": "Temperature sensor 1",
"rawValue": 60
},
{
"id": "00_0010_2271_10_0100_006_2_0",
"name": "Temperature sensor 2",
"rawValue": 58.5
},
{
"id": "00_0010_2271_10_0100_008_2_0",
"name": "Temperature sensor 3",
"rawValue": 50.5
},
{
"id": "00_0010_2271_10_0100_010_2_0",
"name": "Temperature sensor 4",
"rawValue": 56
},
{
"id": "00_0010_2271_10_0100_012_2_0",
"name": "TAGE",
"rawValue": 881
},
{
"id": "00_0010_2271_10_0100_016_4_0",
"name": "Flow rate V40",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_020_1_0",
"name": "Pump speed relay 1",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_021_1_0",
"name": "Pump speed relay 2",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_022_1_0",
"name": "Pump speed relay 4",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_024_4_0",
"name": "Heat quantity",
"rawValue": 88177
},
{
"id": "00_0010_2271_10_0100_028_2_0",
"name": "SW Version",
"rawValue": 1.04
},
{
"id": "00_0010_2271_10_0100_032_4_0",
"name": "Operating hours relay 1",
"rawValue": 54
},
{
"id": "00_0010_2271_10_0100_036_4_0",
"name": "Operating hours relay 2",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_040_4_0",
"name": "Operating hours relay 3",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_044_1_1",
"name": "Holiday function",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_045_1_0",
"name": "Blocking protection 1",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_046_1_0",
"name": "Blocking protection 2",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_047_1_0",
"name": "Blocking protection 3",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_048_4_0",
"name": "Initialise",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_052_4_0",
"name": "Filling",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_054_4_0",
"name": "Stabilise",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_060_1_0",
"name": "Pump delay",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_061_1_1",
"name": "Heat dump",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_062_1_0",
"name": "Overrun",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_063_1_0",
"name": "Thermal disinfection",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_064_1_1",
"name": "Store cooling",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_065_1_1",
"name": "System cooling",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_066_1_0",
"name": "Spreading",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_067_1_0",
"name": "Antifreeze",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_068_1_1",
"name": "Collector cooling",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_069_1_1",
"name": "Maximum store temperature",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_070_1_1",
"name": "Restarts",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_072_4_0",
"name": "Error mask",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_072_1_1",
"name": "Error: Sensor fault",
"rawValue": 0
},
{
"id": "00_0010_2272_10_0100_000_4_0",
"name": "Value",
"rawValue": 88676
},
{
"id": "00_0010_2272_10_0100_004_4_0",
"name": "Power",
"rawValue": 0
},
{
"id": "00_0010_2272_10_0100_008_4_0",
"name": "Value today",
"rawValue": 733
},
{
"id": "00_0010_2272_10_0100_012_4_0",
"name": "Value week",
"rawValue": 75458
},
{
"id": "00_0010_5611_10_0100_000_2_0",
"name": "Temperature sensor 1",
"rawValue": 27.200000000000003
},
{
"id": "00_0010_5611_10_0100_002_2_0",
"name": "Temperature sensor 2",
"rawValue": 59.800000000000004
},
{
"id": "00_0010_5611_10_0100_004_2_0",
"name": "Temperature sensor 3",
"rawValue": 61.6
},
{
"id": "00_0010_5611_10_0100_006_2_0",
"name": "Temperature sensor 4",
"rawValue": 25.6
},
{
"id": "00_0010_5611_10_0100_008_1_0",
"name": "Pump speed relay 1",
"rawValue": 0
},
{
"id": "00_0010_5611_10_0100_009_1_0",
"name": "Pump speed relay 2",
"rawValue": 100
},
{
"id": "00_0010_5611_10_0100_010_1_0",
"name": "Mixer open",
"rawValue": 0
},
{
"id": "00_0010_5611_10_0100_011_1_0",
"name": "Mixer closed",
"rawValue": 0
},
{
"id": "00_0010_5611_10_0100_018_1_0",
"name": "System message",
"rawValue": 0
},
{
"id": "00_0010_5611_10_0100_012_4_0",
"name": "Date",
"rawValue": 20190621
},
{
"id": "00_0010_5611_10_0100_016_2_0",
"name": "Time",
"rawValue": 514
}
]root@stony2:/resol-vbus/examples/json-live-data-server# curl -s http://127.0.0.1:3333/api/v1/live-data
[
{
"id": "00_0010_2271_10_0100_000_4_0",
"name": "System date",
"rawValue": 582795724
},
{
"id": "00_0010_2271_10_0100_004_2_0",
"name": "Temperature sensor 1",
"rawValue": 60
},
{
"id": "00_0010_2271_10_0100_006_2_0",
"name": "Temperature sensor 2",
"rawValue": 58.5
},
{
"id": "00_0010_2271_10_0100_008_2_0",
"name": "Temperature sensor 3",
"rawValue": 50.5
},
{
"id": "00_0010_2271_10_0100_010_2_0",
"name": "Temperature sensor 4",
"rawValue": 56
},
{
"id": "00_0010_2271_10_0100_012_2_0",
"name": "TAGE",
"rawValue": 881
},
{
"id": "00_0010_2271_10_0100_016_4_0",
"name": "Flow rate V40",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_020_1_0",
"name": "Pump speed relay 1",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_021_1_0",
"name": "Pump speed relay 2",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_022_1_0",
"name": "Pump speed relay 4",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_024_4_0",
"name": "Heat quantity",
"rawValue": 88177
},
{
"id": "00_0010_2271_10_0100_028_2_0",
"name": "SW Version",
"rawValue": 1.04
},
{
"id": "00_0010_2271_10_0100_032_4_0",
"name": "Operating hours relay 1",
"rawValue": 54
},
{
"id": "00_0010_2271_10_0100_036_4_0",
"name": "Operating hours relay 2",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_040_4_0",
"name": "Operating hours relay 3",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_044_1_1",
"name": "Holiday function",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_045_1_0",
"name": "Blocking protection 1",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_046_1_0",
"name": "Blocking protection 2",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_047_1_0",
"name": "Blocking protection 3",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_048_4_0",
"name": "Initialise",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_052_4_0",
"name": "Filling",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_054_4_0",
"name": "Stabilise",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_060_1_0",
"name": "Pump delay",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_061_1_1",
"name": "Heat dump",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_062_1_0",
"name": "Overrun",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_063_1_0",
"name": "Thermal disinfection",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_064_1_1",
"name": "Store cooling",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_065_1_1",
"name": "System cooling",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_066_1_0",
"name": "Spreading",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_067_1_0",
"name": "Antifreeze",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_068_1_1",
"name": "Collector cooling",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_069_1_1",
"name": "Maximum store temperature",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_070_1_1",
"name": "Restarts",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_072_4_0",
"name": "Error mask",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_072_1_1",
"name": "Error: Sensor fault",
"rawValue": 0
},
{
"id": "00_0010_2272_10_0100_000_4_0",
"name": "Value",
"rawValue": 88676
},
{
"id": "00_0010_2272_10_0100_004_4_0",
"name": "Power",
"rawValue": 0
},
{
"id": "00_0010_2272_10_0100_008_4_0",
"name": "Value today",
"rawValue": 733
},
{
"id": "00_0010_2272_10_0100_012_4_0",
"name": "Value week",
"rawValue": 75458
},
{
"id": "00_0010_5611_10_0100_000_2_0",
"name": "Temperature sensor 1",
"rawValue": 27.200000000000003
},
{
"id": "00_0010_5611_10_0100_002_2_0",
"name": "Temperature sensor 2",
"rawValue": 59.800000000000004
},
{
"id": "00_0010_5611_10_0100_004_2_0",
"name": "Temperature sensor 3",
"rawValue": 61.6
},
{
"id": "00_0010_5611_10_0100_006_2_0",
"name": "Temperature sensor 4",
"rawValue": 25.6
},
{
"id": "00_0010_5611_10_0100_008_1_0",
"name": "Pump speed relay 1",
"rawValue": 0
},
{
"id": "00_0010_5611_10_0100_009_1_0",
"name": "Pump speed relay 2",
"rawValue": 100
},
{
"id": "00_0010_5611_10_0100_010_1_0",
"name": "Mixer open",
"rawValue": 0
},
{
"id": "00_0010_5611_10_0100_011_1_0",
"name": "Mixer closed",
"rawValue": 0
},
{
"id": "00_0010_5611_10_0100_018_1_0",
"name": "System message",
"rawValue": 0
},
{
"id": "00_0010_5611_10_0100_012_4_0",
"name": "Date",
"rawValue": 20190621
},
{
"id": "00_0010_5611_10_0100_016_2_0",
"name": "Time",
"rawValue": 514
}
]root@stony2:/resol-vbus/examples/json-live-data-server# curl -s http://127.0.0.1:3333/api/v1/live-data
[
{
"id": "00_0010_2271_10_0100_000_4_0",
"name": "System date",
"rawValue": 582795724
},
{
"id": "00_0010_2271_10_0100_004_2_0",
"name": "Temperature sensor 1",
"rawValue": 60
},
{
"id": "00_0010_2271_10_0100_006_2_0",
"name": "Temperature sensor 2",
"rawValue": 58.5
},
{
"id": "00_0010_2271_10_0100_008_2_0",
"name": "Temperature sensor 3",
"rawValue": 50.5
},
{
"id": "00_0010_2271_10_0100_010_2_0",
"name": "Temperature sensor 4",
"rawValue": 56
},
{
"id": "00_0010_2271_10_0100_012_2_0",
"name": "TAGE",
"rawValue": 881
},
{
"id": "00_0010_2271_10_0100_016_4_0",
"name": "Flow rate V40",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_020_1_0",
"name": "Pump speed relay 1",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_021_1_0",
"name": "Pump speed relay 2",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_022_1_0",
"name": "Pump speed relay 4",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_024_4_0",
"name": "Heat quantity",
"rawValue": 88177
},
{
"id": "00_0010_2271_10_0100_028_2_0",
"name": "SW Version",
"rawValue": 1.04
},
{
"id": "00_0010_2271_10_0100_032_4_0",
"name": "Operating hours relay 1",
"rawValue": 54
},
{
"id": "00_0010_2271_10_0100_036_4_0",
"name": "Operating hours relay 2",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_040_4_0",
"name": "Operating hours relay 3",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_044_1_1",
"name": "Holiday function",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_045_1_0",
"name": "Blocking protection 1",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_046_1_0",
"name": "Blocking protection 2",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_047_1_0",
"name": "Blocking protection 3",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_048_4_0",
"name": "Initialise",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_052_4_0",
"name": "Filling",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_054_4_0",
"name": "Stabilise",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_060_1_0",
"name": "Pump delay",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_061_1_1",
"name": "Heat dump",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_062_1_0",
"name": "Overrun",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_063_1_0",
"name": "Thermal disinfection",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_064_1_1",
"name": "Store cooling",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_065_1_1",
"name": "System cooling",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_066_1_0",
"name": "Spreading",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_067_1_0",
"name": "Antifreeze",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_068_1_1",
"name": "Collector cooling",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_069_1_1",
"name": "Maximum store temperature",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_070_1_1",
"name": "Restarts",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_072_4_0",
"name": "Error mask",
"rawValue": 0
},
{
"id": "00_0010_2271_10_0100_072_1_1",
"name": "Error: Sensor fault",
"rawValue": 0
},
{
"id": "00_0010_2272_10_0100_000_4_0",
"name": "Value",
"rawValue": 88676
},
{
"id": "00_0010_2272_10_0100_004_4_0",
"name": "Power",
"rawValue": 0
},
{
"id": "00_0010_2272_10_0100_008_4_0",
"name": "Value today",
"rawValue": 733
},
{
"id": "00_0010_2272_10_0100_012_4_0",
"name": "Value week",
"rawValue": 75458
},
{
"id": "00_0010_5611_10_0100_000_2_0",
"name": "Temperature sensor 1",
"rawValue": 27.200000000000003
},
{
"id": "00_0010_5611_10_0100_002_2_0",
"name": "Temperature sensor 2",
"rawValue": 59.800000000000004
},
{
"id": "00_0010_5611_10_0100_004_2_0",
"name": "Temperature sensor 3",
"rawValue": 61.6
},
{
"id": "00_0010_5611_10_0100_006_2_0",
"name": "Temperature sensor 4",
"rawValue": 25.6
},
{
"id": "00_0010_5611_10_0100_008_1_0",
"name": "Pump speed relay 1",
"rawValue": 0
},
{
"id": "00_0010_5611_10_0100_009_1_0",
"name": "Pump speed relay 2",
"rawValue": 100
},
{
"id": "00_0010_5611_10_0100_010_1_0",
"name": "Mixer open",
"rawValue": 0
},
{
"id": "00_0010_5611_10_0100_011_1_0",
"name": "Mixer closed",
"rawValue": 0
},
{
"id": "00_0010_5611_10_0100_018_1_0",
"name": "System message",
"rawValue": 0
},
{
"id": "00_0010_5611_10_0100_012_4_0",
"name": "Date",
"rawValue": 20190621
},
{
"id": "00_0010_5611_10_0100_016_2_0",
"name": "Time",
"rawValue": 514
}
]root@stony2:/resol-vbus/examples/json-live-data-server#

after some time everything is working fine

do you have a idea how to debug this?

best regards
ben

Resol with Home assistant

Hello Daniel,

Do you know if its possible to connect a resol dl2 datalogger with homeassistant?

Greetings,
Klaas

Add datagram and telegram support to `VBusRecordingConverter`

Allow custom date and time format in text-converter

Add an option to add a custom date and time format in text-converter.js (appendDateAndTimeColumns).

VBUS protocol 2.0 parameters documentation

Hi,
is there any known source of the documentation for protocol 2.0 parameters?

I mean specifically a documentation which would allow to match specific menu functionalities to parameter index/address.

And I'm specifically referring to DeltasolMX controller.

Thanks,
Adam

Vitosol 200

Excellent Code and highly useful Daniel, many thanks for providing such an amazing toolset.

Im using the vbus-proxy because it data logs ;-) and to get the app to work, however the Vitosol 200 presents itself as exactly that and not the ?MX? product.

The app says unknown controller (all tool true).

Im not sure were would be a good place to amend the responses going to the app and also what I would need to "pretend" to be (what strings will the app accept).

Perhaps you can help me ?

Setup adapter showing multiple subfolder; addtl. parameter from Controller DeltaMX available?

Dear owner of the adapter,

1st of all: great that you spent your time so far to enable others to access resol devices for IOBroker integration.

After the installation (Base is the KM2 with an Resolte Delta MX Controller) the object tree shows various subfolders. Would you mind to share what is the differentation? Purpose of each subfolder.

Is renaming possible to have more than just the standard out of the initial setup based on the output of the controller? E.g. Sensor 1 = renamed in Sensor Roof-Kollektor?

Where and do I get access the more specific parameters of the delta Sol controller? E.g. the Delta Temperature between Sensor 1 and e.g. the linked buffersensor S2. Delta T is about 10 Greed where to start the solar pump. Would it be posible to read these parameters as well with the adapter per standard and convert it inot a nice subfolder. I have read all your hints to access deeper into the controller but Ißm not so familiar with JS etc. So a kind of Pro-Support from your side would be fantatstic.... Regasds Reiner

Installing adapter: done
accessing VBUS KM2 interface: done
how to use the objects in IOBroker (States): open

KM2 API current_packets.vbus

Hallo Daniel,
gibt es eine Möglichkeit die current_packets.vbus meines KM2 zu entschlüsseln ?
Ich habe mittlerweile schon andere Methoden ausprobiert an die Daten des KM2 zu bekommen leider alles ohne Erfolg.
Auf telefonische Anfrage beim Support von Vbus.net bekam ich folgende Anwort auf meine Frage nach der API für das KM2: Man könnte nicht auch noch andere Systeme unterstützen oder supporten.
Ich hatte eigentlich vor das KM2 per API anzusprechen und diese Werte dann bei mir in der KNX Hausinstallations anzeigenzulassen bzw. weiterzuverarbeiten. Dies sollte dann über den Gira X1 erfolgen. Leider habe ich keine API Dokumentation vom KM2.
Ich nutze einen Kamin zur Warmwasseraufbereitung und Heizungsunterstützung. Die Steuerung erfolgt über den Resol Delta Therm FK und das KM2 greift die Daten ab.

Does DeltasolMX broadcast frames/packets with calculated temperatures from EMs' inputs?

Hi,
does DeltasolMX broadcast frames/packets with calculated temperatures from EMs' inputs? EMs broadcasts packets containing resistance measured on their inputs. Based on the knowledge what kind of sensor (PT100, PT1000 etc) is connected to the corresponding input it is possible to calculate the measured temperature but does DeltasolMX also broadcast any packet with already calculated temperature?

Edit: I found a doc for this packet: http://danielwippermann.github.io/resol-vbus/#/vsf/fields/00_0010_1161_10_0100 but not sure what is 'MFR' device that broadcasts this. This packet looks like what I'm loking for: http://danielwippermann.github.io/resol-vbus/#/vsf/fields/00_0010_7E12_10_0100 , it seems to be broadcasted by DeltasolMX controller, but is it supported in all firmware versions ( originally DeltasolMX seemed to have device address: 0x7E11 while this packet mentions 0x7E12 referring to the same device )?

Thanks,
Adam

FYI: Node sample to get vbus data into openhab, HomeAssistant, Node-RED with the help of MQTT-Homie

Hi Folks,

if somebody is interested in getting vbus data to openhab, HomeAssistant and Node-RED, take a look at my sample:
https://github.com/BenniG82/vbus-to-homie
It uses this nice lib and provides the data in a Homie structure in your MQTT-Server.
openhab, HomeAssistant and Node-RED should now be able to easily access this data. I'm only using openhab, but the Homie-website says that HomeAssistant and Node-RED also support their spec.

@daniel if you don't like this "advertisement", feel free to close/delete the issue :)

Have fun and stay healthy
Benjamin

MQTT Socket Error

I'm using vbus-touch-proxy and getting the following error when connecting to MQTT Broker:

Socket error on client mqttjs_aa7d437e, disconnecting.

Here is my config.js:

mqttConnect: {
    host: '10.10.50.3',
    port: '1883',
    username: 'myuser',
    password: 'mypassword',
},

/**
 * MQTT topic to publish to.
 */
mqttTopic: 'home/resol',

Any idea where to troubleshoot this?

Deltasol LAN

Hey @danielwippermann,

and again a questions from your Home Assistant Crew: we are currently able to get data from KM2 via cgi-bin. And we are also getting data from DL2/DL3. Is the LAN adapter also supporting to get the data? And if so: how?

Best,
Dirk

Supported Devices and Services / DL2 and DL3

http://danielwippermann.github.io/resol-vbus/dlx-data-download-api-docs

Api Documentation not working.

delta therm fk pumpendrehzahl

hi daniel,

i need the pwm pump speed. i think it is in the standard infos 0x0015. because "id": "00_0010_5611_10_0100_008_1_0",
"name": "Pump speed relay 1",
"rawValue": 100
always shows 100% if the pump is running.
i use your sample live json server. can you please help me to get the right data?

best regards from germany
ben

Daten von DL1 auslesen

Hi @ all,

I'm currently trying to read the Data sent from the Resol DL1 which is attached to COM6 at my Windows machine. I allready tryed two different approches:

var vbus = require('resol-vbus');
var connection = new vbus.SerialConnection({ path: 'COM6' });
	connection.on('connectionState', function(state) {
	console.log(state);
});
connection.on('packet', function(packet) {
	console.log(packet.getId());
});
connection.on('datagram', function(datagram) {
	console.log(datagram.getId());
});
connection.connect();

I get es successfull connection but no packet data.
The I modified the example of the json-live-data-server example as floows:

var config = {
	/**
	 * The port number for the HTTP server to listen to.
	 * @type {Number}
	 */
	httpPort: 3333,
	/**
	 * The inteval in milliseconds between two writes of the logging file.
	 * @type {Number}
	 */
	loggingInterval: 10000,

	/**
	 * The filename of the logging file.
	 * @type {String}
	 */
	loggingFilename: path.resolve(__dirname, 'live-data.json'),
	/**
	 * The name of the `Connection` subclass to use for connecting to the VBus.
	 * @type {String}
	 */
	connectionClassName: 'SerialConnection',
	connectionOptions: {
		/**
		 * The host name / IP address of the VBus/LAN or Datalogger device.
		 * @type {String}
		 */
		path: 'COM6',
		/**
		 * The password for the VBus/LAN or Datalogger device.
		 * @type {String}
		 */
		password: '',
	},
};
module.exports = config;

But the json keeps empty. What am I doing wrong?

Normaly I use the following approach wich is working almost perfect (except of providing live data)
--> Dialup to the DL1 via Null Modem connection resulting in an IP 192.168.192.1
--> Connect the ResolServiceCenter to the IP
--> Data incomming and saving every 15 minutes to log (so far so good)

But it whould be nice to have access to the live data.

Any sugestions?

Kind Regards

Thank you very much for your work!

Thanks for your work. I've installed a raspberry pi with your code, accessing to a km2 module connected to an old deltasol M.
Then, in my HA, I've created a REST sensor and and a platform sensor vinculated to it and finally I've got deltasol regulator values in my dashboard.
Thanks a lot!

Error: "Unhandled promise rejection" in serial-connection.js

There seems to be a bug in serial-connection.js ("[email protected]") which triggers an Unhandled promise rejection when a non-existent serial port is attempted to be opened. This can be fixed by removing the extra "null" argument in line

176 return new SerialPort(path, options, null, onCompletion);

(see error logs "Before" and "After" below).

Environment:

Platform: Windows
operating system: win32
Architecture: ia32
CPUs: 2
Speed: 2394 MHz
Model: Intel(R) Core(TM)2 Duo CPU T7700 @ 2.40GHz
RAM: 3.2 GB
System uptime: 00:43:40
Node.js: v14.21.0
time: 1677311416247
timeOffset: -60
adapters count: 558
NPM: v6.14.17
Disk size: 118.3 GB
Disk free: 42.7 GB
Uptime: 00:35:10
Active instances: 1
Path: C:\iob-dev\ioBroker.myvbus.dev-server\default
alive:

"serialport": "^9.2.8",
"[email protected]"

Before:

serial-connection.js line 176:

175    _createSerialPort(path, options, onCompletion) {
176        return new SerialPort(path, options, null, onCompletion);
    }

}

new SerialPort() receives the wrong number of arguments, Instead of the openCallback, "null" is passed. Therefore the module crashes with "Unhandled promise rejection"

Remark: The "path" argument can be included in the options object since some time. Also the undocumented option "disconnectedCallback:" is deprecated and removed from node SerialPort since V4.x. So I assume that the code for the reconnect will not be working anymore. (I haven't tried it yet). Since V5.x "the close event now fires with a disconnect error object in the event of a disconnection". (err.disconnect)
EDIT: I have tried to disconnect and it does not work as expected. So it would be desirable that you also fix the reconnect code.

2023-02-26 08:57:00.909 - info: myvbus.0 (10664) starting. Version 0.2.2 in C:/iob-dev/ioBroker.myvbus/.dev-server/default/node_modules/iobroker.myvbus, node: v14.21.0, js-controller: 4.0.24
2023-02-26 08:57:01.069 - debug: myvbus.0 (10664) Language: en
2023-02-26 08:57:01.085 - debug: myvbus.0 (10664) Connection Type: serial
2023-02-26 08:57:01.086 - debug: myvbus.0 (10664) Connection Identifier: COM8
2023-02-26 08:57:01.087 - debug: myvbus.0 (10664) Connection Port: 7053
2023-02-26 08:57:01.088 - debug: myvbus.0 (10664) VBus Password encrypted:
2023-02-26 08:57:01.259 - debug: myvbus.0 (10664) VBus Channel: 1
2023-02-26 08:57:01.370 - debug: myvbus.0 (10664) VBus Via Tag:
2023-02-26 08:57:01.470 - debug: myvbus.0 (10664) VBus Interval: 30
2023-02-26 08:57:01.583 - info: myvbus.0 (10664) Serial Connection at COM8 selected
2023-02-26 08:57:01.739 - info: myvbus.0 (10664) Wait for Connection...
2023-02-26 08:57:01.851 - debug: myvbus.0 (10664) Connection state changed to CONNECTING
2023-02-26 08:57:01.976 - error: myvbus.0 (10664) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2023-02-26 08:57:02.007 - error: myvbus.0 (10664) unhandled promise rejection: Opening COM8: File not found
2023-02-26 08:57:02.248 - error: myvbus.0 (10664) Error: Opening COM8: File not found
2023-02-26 08:57:02.264 - error: myvbus.0 (10664) Opening COM8: File not found
2023-02-26 08:57:02.381 - debug: myvbus.0 (10664) Connection state changed to DISCONNECTING
2023-02-26 08:57:02.412 - debug: myvbus.0 (10664) Connection state changed to DISCONNECTED
2023-02-26 08:57:02.510 - info: myvbus.0 (10664) Cleaned up everything...
2023-02-26 08:57:02.608 - info: myvbus.0 (10664) terminating
2023-02-26 08:57:02.675 - warn: myvbus.0 (10664) Terminated (UNCAUGHT_EXCEPTION): Without reason
[nodemon] app crashed - waiting for file changes before starting...

After:

175    _createSerialPort(path, options, onCompletion) {
176        return new SerialPort(path, options, onCompletion);
    }

}

The error is correctly handed up from SerialPort to the ioBroker adapter.

2023-02-26 09:02:42.759 - info: myvbus.0 (14268) starting. Version 0.2.2 in C:/iob-dev/ioBroker.myvbus/.dev-server/default/node_modules/iobroker.myvbus, node: v14.21.0, js-controller: 4.0.24
2023-02-26 09:02:43.056 - debug: myvbus.0 (14268) Language: en
2023-02-26 09:02:43.137 - debug: myvbus.0 (14268) Connection Type: serial
2023-02-26 09:02:43.349 - debug: myvbus.0 (14268) Connection Identifier: COM8
2023-02-26 09:02:43.511 - debug: myvbus.0 (14268) Connection Port: 7053
2023-02-26 09:02:43.634 - debug: myvbus.0 (14268) VBus Password encrypted:
2023-02-26 09:02:43.664 - debug: myvbus.0 (14268) VBus Channel: 1
2023-02-26 09:02:43.689 - debug: myvbus.0 (14268) VBus Via Tag:
2023-02-26 09:02:43.701 - debug: myvbus.0 (14268) VBus Interval: 30
2023-02-26 09:02:43.707 - info: myvbus.0 (14268) Serial Connection at COM8 selected
2023-02-26 09:02:43.738 - info: myvbus.0 (14268) Wait for Connection...
2023-02-26 09:02:43.745 - debug: myvbus.0 (14268) Connection state changed to CONNECTING
2023-02-26 09:02:43.771 - error: myvbus.0 (14268) [onReady] error: Opening COM8: File not found, stack: Error: Opening COM8: File not found

Resol Adapter

Hey Daniel,

ich bin aktuell nicht sicher welchen Resol Adapter ich mir sinnvollerweise kaufen sollte. Ich schwanke zwischen dem VBus LAN und KM2.

Mein Szenario sieht so aus, dass ich Home Assistant einsetze und dort gerne meinen Regler auslesen würde im in Erfahrung zu bringen, wie viel Energie meine Anlage z.B. heute abgegriffen hat. Ich möchte diese Information nutzen um die Warmwasser Aufbereitung meiner Heizanlage ein- bzw. ausschalten zu können.

Ich vermute aktuell, dass ich den LAN Adapter irgendwie per curl/wget ansprechen kann und dann ein JSON zurückbekomme in dem ich verschiedene Werte (ggf. einen den ich auch brauchen kann) zurück bekomme. Was ich aber nicht finden konnte war eine Schnittstellenbeschreibung. Grundsätzlich glaube ich, dass dieser LAN Adapter auch das ist was ich brauche.

Den KM2 interpretiere ich eher als Gerät, dass mir die Daten dann ins VBus Portal schickt und mir dort eben eine Auswertung u.s.w. ermöglicht. Auch da bin ich nicht sicher ob und wie ich die dann von mir benötigten Daten sinnvoll und automatisiert wieder auslesen könnte.

Ich hoffe Du kannst mir da etwas unter die Arme greifen.

Danke und Gruß
Dirk

whet nodejs version supported ?

I try multiple different version of nodejs
have lot of problem with npm install
anyway when I try execute examples it fails on mostly every line :(
can you recommend nodejs version that will work with this examples
I try run vbustouch-proxy