Batrium and Grafana

Has anyone been able to get the realtime minimum cell voltage value from the newer updates?

I'm currently using > Msg_3e33 > MinCellVolt but it doesnt seem to be correct and doesnt have a fast refresh value, anyone got any tips on how to get this because I want to use logic based on the lowest value of the cell in the pack.
 
Possibly Msg_3233? It updates every 2 min which is not the 300ms update from Msg_3e33>
Also are you still getting Msg_3e32 if so that should have the same data as the older version Msg_3e5a
Wolf
 
I would remind again that there is a working system out there on Batriums github that i created. It do have the latest messages and all documented :)
 
working system out there on Batriums github
Yep we or at least I know. Some of us just want to go through the pain and suffering on our own.😛
I of course have not updated to the new version. Can anyone tell me what's new and improved?
New UI? Any new whiz-bang features I cannot live with out?
I unfortunately only have 1 watchmon4 so I do not have a play unit. Maybe someday if someone wants to donate a unit........................
Wolf
 
Their webpage doesnt say much. But i know they remodeled some to not have as many duplicate messages and to often. They also changed to use smaller packets. Optimization.
I cant test either. I have given away My batrium since i run diybms now.
 

Attachments

  • Screenshot_20210629-082228.jpg
    Screenshot_20210629-082228.jpg
    344.6 KB · Views: 119
I cant test either. I have given away My batrium since i run diybms now.
Aha and you didn't think to ask me if I wanted it. I traveled all the way to Austria so you could have sent it to me cheep.
Just kidding;)
I could have of course visited the batrium website and found out what was new but thank you for indulging my laziness.
The one thing that does intrigue me is this:
1624963672618.png
Has anyone done anything with this tool?
So you have jumped ship and went with the diybms.
I have followed the evolution of it for a bit and I think I may build one for the Shed ~12V~ battery to test it.
Has a lot of features. Sounds fun.
Wolf
 
@Cell-King
I'm sure you have this info also but I split all the Msg_****.js into versions and this is what I have come up with.
Valid from SW 1.0.30
1624967440113.png

And Valid from SW 2.14
1624967577847.png

So I think those are the Msg_****.js that we can work with.

Wolf
 
I went the 'parsing the automatic snapshot report' route. Its limited to once every 5 minutes because the 1 minute and 30 seconds option never worked - but whatever changes have occurred have not broken the parsing software. :)
 
I went the 'parsing the automatic snapshot report' route. Its limited to once every 5 minutes because the 1 minute and 30 seconds option never worked - but whatever changes have occurred have not broken the parsing software. :)
Well that's good to know.
Have you played with the voltage calibration tool?
Wolf
 
Just in case it's useful for anyone. I changed the (for me) most important payloads of the original Dirtyoptics example (and also removed the local Node-Red dashboard given I display everything in Grafana anyway) to work with the SW 2.15 Batrium changes.
This does NOT completely update everything that changed but maybe is enough to get some of you folks going again.

Node-Red json attached (in the batrium.zip), change your Influxdb server to your environment to make it work.
 

Attachments

  • batrium.zip
    18.4 KB · Views: 110
Last edited:
I know this is an old thread, but maybe someone here can help. I got the WatchMonUdpListener up and running without errors. I have it pointed to my MQTT server (with influxdb disabled) but it does not push any messages to MQTT. My question is

Do I need to point my Batrium device to this listener, or is the listener automatically picking up what Batrium is broadcasting over UDP? Is there any other Batrium config I'm supposed to enable for this to work? I'm fairly competent with docker/mqtt/scripting and am wondering what I'm doing wrong. Any help appreciated.

@kevinjaye @daromer

I just tried running in NodeRed and get the following errors:
29 Aug 18:36:05 - [error] [function:Msg_3233_LiveDisplay] TypeError: Packet is not a constructor
29 Aug 18:36:05 - [error] [function:Msg_415a_CellNodeStatus] TypeError: Packet is not a constructor
29 Aug 18:36:05 - [error] [function:Msg_4232_CellNodeFull] TypeError: Packet is not a constructor
29 Aug 18:36:05 - [error] [function:Msg_415a_CellNodeStatus] TypeError: Packet is not a constructor
....
 
Last edited:
@hummmingbear
Batrium broadcasts on UDP port 18542 Since it is a broadcast message there is no need to point anything to anything. The UDP listener just has to be set up to "listen" on port 18542. From there depending on your firmware version there are several prebuilt flows available for you to manipulate to your liking. See ^^^^^ (posts above).
1662465700222.png
@daromer also has a prebuild pi image available using a UDP listener and MQTT
Also the source code
That should get you up and running.

Wolf
 
@hummmingbear
Batrium broadcasts on UDP port 18542 Since it is a broadcast message there is no need to point anything to anything. The UDP listener just has to be set up to "listen" on port 18542. From there depending on your firmware version there are several prebuilt flows available for you to manipulate to your liking. See ^^^^^
I am on their newest firmware (just had an update yesterday actually). Does this require the toolkit to be up and running, or is it broadcasting from the Watchmon itself?

I actually downloaded and got https://github.com/Batrium/WatchMonUdpListener up and running, but it doesn't receive any data. I'm wondering if that repo is out of date and not retrieving the current values from the newest firmware? I feel a bit confused as I can't get any data, but I have my batrium up and running on my wifi and displaying data in the toolkit app.
 
Does this require the toolkit to be up and running, or is it broadcasting from the Watchmon itself?
All the toolkit is is a UDP port listener in itself and no it does not need to be running, the broadcast comes from the Watchmon.
Since I still run the original firmware 1.0.30 firmware and not the new 2.15 or whatever it is now I have no issues with my node red flow.
But if you set up a UDP listener in node red like the picture below you should get a bunch of stuff in the debug window.
Make sure your firewall is set to allow UDP traffic on port 18542. Since you are getting the toolkit data though, unless you are directly connected via USB, I am assuming your firewall settings are ok.
1662485266857.png

Wolf
 
All the toolkit is is a UDP port listener in itself and no it does not need to be running, the broadcast comes from the Watchmon.
Since I still run the original firmware 1.0.30 firmware and not the new 2.15 or whatever it is now I have no issues with my node red flow.
But if you set up a UDP listener in node red like the picture below you should get a bunch of stuff in the debug window.
Make sure your firewall is set to allow UDP traffic on port 18542. Since you are getting the toolkit data though, unless you are directly connected via USB, I am assuming your firewall settings are ok.
View attachment 28237

Wolf
Ok, thank you that is making a bit more sense now. I'll setup a generic listener. From that point do I just need to manually map each message to an Item? Is the `topic_id` the key that would map to a variable like Cell1Voltage for example (just making that part up).

I have to say I am a bit disappointed with Batrium. I paid a lot for what I thought was a well designed product, but the more I dig in the more I am disappointed by the poor documentation and the fact that they haven't published a more consistent API that is easy to use. Maybe I'm the only one with this gripe...
 
@Wolf ok I am spitting out UDP messages to debug, but the payload looks very different than yours
1662490769470.png


I'm on Hardware Version: 14.5, Firmware Version: 14.3.23 and Software Version 2.17.15
 
Last edited:
Back
Top