There seems to be a (cosmetic) bug in the BMV-702 Battery Monitor node, under the general “Alarm” status.
Other alarms have a status of 0 for “No alarm” and status 2 for “Alarm”.
The general Alarm status appears to use values 0 for “No Alarm” and value 1 for Alarm, which gets translated as “undefined”, probably because the descriptive text expects a value of 2 to indicate “Alarm”.
This is present in v3.55 up to and including v3.60~80.
Not sure if this really counts as a bug but since Venus OS 3.60 release is around the corner it could be a quick fix to include
Note: I only tested a few output variables of this node and kind of stumbled over this “undefined” status text, so there might (or not) be more values that could benefit from a status text update.
And since I’m already rambling and complaining, I just might go on a bit
In VenusOS v3.55 (node-red-contrib-victron v1.5.23) there’s text describing the possible output values of a node.
Can we get these back please ?
As an example (and there are many more), the “VE.Bus state” has 12 different possible output values that are described in Venus OS v3.55 (node-red-contrib-victron v1.5.23)
Unfortunately, nada descriptive text in Venus OS 3.60~80 (node-red-contrib-victron v1.6.30).
Without a hint of the possible output values, it gets rather tricky to work with them.
Edit: the possible output values seem to be described in the “Help” section of the Node Red sidebar.
So at least they’re not gone completely
I’ll leave it to the rest of the community to vote if they’d like to see these in the node Edit page or in the sidebar under the Help menu.
From one nighthawk to another: go to bed please.
It’s bad enough that community nerds like myself are up & at it in the middle of the night on a weekend, you are Staff and don’t need / shouldn’t be following the same wacked up schedule.
(We need you to be fit for the v3.60 release )
I hate to say it but it seems the cosmetic bug isn’t completely solved yet
In v3.60~80 : Alarm value 1 gets translated as “undefined”, no value description in the node edit window.
In the right hand help window, it is stated that the node gives value 0 for “No alarm” and 2 for “Alarm”.
Somehow my BMV-702 node gives out a 1 for the general alarm.
Since this isn’t an expected value, the node status text says “(undefined)”.
After updating to v3.60~83 : BMV-702 still gives out value 1 for “Alarm”, while value 2 is expected.
Therefor the node text still says “(undefined)”.
In the righthand node help window, it does state values 1 and 2 for Alarm, but a 1 isn’t correctly shown in the node status.
You probably need to delete that node and pull it in again fresh. When storing the node on the flow, all possible values are stored with it, so that node you already have won’t know about value 1.
Good point, I should’ve thought of that.
Done now, we’ll see if that fixes it.
This (test) installation has a string of 24x 2V AGM batteries, of which I suspect one is going bad.
Annoying battery-wise, interesting for testing all kinds of stuff
