batrium / watchmonudplistener

WatchMon UDP Binary Listener translates to JSON and stores to influxdb

WatchMonUdpListener

WatchMon UDP Binary Listener translates to JSON and stores to influxdb or sends it to MQTT

Getting Started

git clone https://github.com/Batrium/WatchMonUdpListener

or

npm install watchmonudplistener

or

Download premade Raspberry PI 3 ISO with everything built in: http://diytechandrepairs.nu/raspberry-solar/

Prerequisites

MQTT Binary-Parser Influx

How to install them: (If you clone from GitHub)

npm install mqtt
npm install binary-parser
npm install influx

Installing

Main install in "Get started"

Start with copying the batrium_config.json_dist to batrium_config.json

Example code in linux:

cp config.json_dist config.json

Edit the file to suit your needs. In the file you have 4 tags for each message:

• mqtt-> Here you enable or disable if you want a message to be sent to your MQTT brooker

• Influx -> Enable or disable to send the message to Influx DB. Its not recommended to send more than needed!

• tag -> Its possible to add tagging to Influx db. Currently run it as is unless you want something special

• series -> If you want to split out data for instance slow running data from the fast running for easier query in the database this is what you use

The configuration also holds ip/dns for the MQTT brooker and Influx. If you have them on localhost you can leave it as is.

Example config for main setup:

 	"config" : {
                "mqtthost" : "localhost",
                "influxhost" : "localhost",
                "influxdatabase" : "batrium"
        },

Example config for a message:

 "3e" : {
             "mqtt" : true,
             "influx" : true,
             "tag" : "general",
             "serie" : "generic"
     },

When you have cloned the git repo and setup the configuration in the configuration files you also need to prepare the database. In the config section you define the influxdatabase and that one need to be created in InfluxDB

Run:

influxdb

then you run: (Change to the database you want to use)

create database batrium 

When all this is done its just a matter of running the application

Automatic startup

cp systemctl/batrium.service /etc/systemd/system/

Be sure to update paths in the file acordingly to where you installed the Batrium UDP listener

systemctl --system daemon-reload

To enable:

systemctl enable batrium.service

To disable

systemctl disable batrium.service

Contributing

For contributing to this project you can support Batrium by getting HW from them. Supporting the creator of this script by Patreon/Paypal/Subscribing to youtube channel. Patreon: https://www.patreon.com/diytech Youtube: https://www.youtube.com/user/daromeresperyd Webpage with more ways to contribute: http://diytechandrepairs.nu/ And the most important is to report any issues/bugs or features that you want to see sorted or fixed. All added contributions are much appreciated!

Authors

• Daniel Römer - Initial work - daromer2

License

This project is licensed under the MIT License - see the LICENSE.md file for details

Acknowledgments

• Hat tip to anyone who's code was used
• Inspiration
• etc

watchmonudplistener's Issues

amd 64 version

hi this isn't running for me but my system isnt running on arm is there used to be a pc version but can't find it

DataStruckture Change with WachMon 2.15.10

With the Last WachMon 2.15.10 there is a change in UDP Data Structure, so some (a lot) of measurements are not longer function.

Most from Status Rapid. I will try to fix it by Myself, but would be nice to recive an update here!

Greetz
Michael

config/config.json not being created?

I'd copied config.json_dist and modified into config.json (as I did in the previous version) and it was not working.

Then checking the source code I saw that now is being read from the config directory and if doesn't exist, created there:
var config = JSON.parse(fs.readFileSync('config/config.json', "utf8"));

However this was not happening for me (I'm using a Raspberry Pi 4).

So I just changed the code to

var config = JSON.parse(fs.readFileSync('config.json', "utf8"));

and resolved the issue for my case.

DailySessionCumulShuntkWhCharge and DailySessionCumulShuntkWhDischg not being logged to influx

I've been using WatchMonUdpListener for several months and then having it displayed in a Grafana panel. Everything working fine.

After upgrading the WatchMon 4 to the latest firmware, I noticed that some parameters were not working. Then noticed that the github has been updated to I reinstalled it.

Now everything is working (see some other issues being reported after this one), however even if I'm using message 5432:
"54" : {
"mqtt" : false,
"influx" : true,
"tag" : "general",
"serie" : "daily"
},

DailySessionCumulShuntkWhCharge and DailySessionCumulShuntkWhDischg aren't being collected in the DB.

I did the update from github around noon today, and as you can see, previously they were available but not anynmore:

select DailySessionCumulShuntkWhCharge FROM "batrium".."generic" group by * order by desc limit 10
name: generic
tags: messageId=5432, messageType=generic, systemId=8162
time DailySessionCumulShuntkWhCharge

---

2021-03-07T11:16:55Z 1.8071395263671874
2021-03-07T11:16:05Z 1.7943203125
2021-03-07T11:04:32Z 1.5418182373046876
2021-03-07T10:57:07Z 1.4297069091796875
2021-03-07T10:53:49Z 1.339310791015625
2021-03-07T10:50:31Z 1.2914351806640625
2021-03-07T10:49:41Z 1.2800699462890626
2021-03-07T10:47:13Z 1.254539306640625
2021-03-07T10:46:23Z 1.24687158203125
2021-03-07T10:43:05Z 1.211105224609375

select DailySessionCumulShuntkWhDischg FROM "batrium".."generic" group by * order by desc limit 10
name: generic
tags: messageId=5432, messageType=generic, systemId=8162
time DailySessionCumulShuntkWhDischg

---

2021-03-07T11:16:55Z 7.61065234375
2021-03-07T11:16:05Z 7.61065234375
2021-03-07T11:04:32Z 7.61065234375
2021-03-07T10:57:07Z 7.61065234375
2021-03-07T10:53:49Z 7.61065234375
2021-03-07T10:50:31Z 7.61065234375
2021-03-07T10:49:41Z 7.61065234375
2021-03-07T10:47:13Z 7.61065234375
2021-03-07T10:46:23Z 7.61065234375
2021-03-07T10:43:05Z 7.61065234375

influx user/pwd

In the previous version, I've not created any specific user/password in influx, but it seems that this version assumes that root/root is there.

Before that I was getting no data and the error message:
A 401 Unauthorized error occurred: {"error":"authorization failed"}\n' }

I think it will be good to make sure that you can change in the config.json or another file the user and password, so it matches your own security policy.

Space at end of identifier

example: https://github.com/Batrium/WatchMonUdpListener/blob/master/payload/Msg_4733_StatusControlLogic.js#L76

In this file there are multiple identifier that have a space at the end in the string of the identifier.

README.md need some general information

Could there be added som general information in README.md about how to connect the watchmon(hardware) to mqtt and/or influxdb?

What is the latest supported Batrium SW?

Hello,

I have recently updated to 2.15.11 and the corresponding firmware on my WM4 and I can see that the messages have changed quite a bit. One message that I use particularly was the StatusRapid at 3e32 or 3e5a, but my WM never transmits any of these. I am connected to WiFi and it is set to verbose (thinking this will transmit everything possible):

Setting my config to throw everything at the MQTT server I get a list of the following IDs after a while:

Anybody able to point me at the right direction in order to get the data delivered from StatusRapid?

duplicate entries in payload 4733

https://github.com/Batrium/WatchMonUdpListener/blob/master/payload/Msg_4733_StatusControlLogic.js#L39
is same as https://github.com/Batrium/WatchMonUdpListener/blob/master/payload/Msg_4733_StatusControlLogic.js#L47

same for line 40 and 48.

Grafana crashes with mobile browser

Hi have the pre compiled image on a pi 3
Works great when accessing from a pc

The moment I use my phone to access grafana loose access from any external device

It's like networking stops can't even SSH to it without reboot

comment for bit is wrong

https://github.com/Batrium/WatchMonUdpListener/blob/master/payload/Msg_4733_StatusControlLogic.js#L104 & line 105 have same byte and bit identifier.

.bit1('hasDischgShuntSocLo')        // boolean index  28 - bit0
.bit1('hasDischgShuntSocPause')     // boolean index  28 - bit0

Does this still work with new Batrium Firmware/Products

I got this up and running without errors but it isn't pushing any data to MQTT. I have a new WatchmonCore, does this not work with the newest firmware?