question

geomz avatar image
geomz asked

Time to go from BMV on VRM, considers infinite as 0

I have an alarm rule on my BMV, in VRM, set to trigger when the Time To Go value is less than 5 hours. The rule works well enough and allows me to trap high-load scenarios before they deplete the batteries too much.

However, when the system is charging, the time to go value is set to "infinite", but on VRM, it sees that value as 0, which is less than 5, and it erroneously triggers the alert. Even worse, it sort of reverses the logic when I'm discharging, thus clearing the alarm.

Is there a way to get around that behavior?

Also, some of the trigger points for several alarms on VRM don't even make sense. There are several examples where alarm trigger value make no sense at all. Like why necessitate a "high" value for time to go -it's a "required" value so I fudge the value at 1000.

If I've got 1000 hours to go on my batteries, I don't want an alarm on that, except perhaps one hooked up to streamers and ticker-tape :)


VRMBMV Battery Monitorbug report
2 |3000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

1 Answer
mvader (Victron Energy) avatar image
mvader (Victron Energy) answered ·

Hi @Geomz, thanks for reporting this.

Knowing how the alarm system works; I’m not so sure if there is an simple to implement fix for this; might take a while.

What GX device do you have? As a workaround you could consider using node-red, see here:

https://community.victronenergy.com/questions/549/feature-request-scheduled-virtual-switch-for-venus.html


Do note that its (a) in beta and (b) quite a more technical solution than configuring an alarm on VRM.

3 comments
2 |3000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

geomz avatar image geomz commented ·

Thanks @mvader, I appreciate the response. I had wondered if it could be fixed -due to the way it considers "infinite".

But I was thinking that perhaps whatever parser is reading infinite as 0 could be redefined as 9999 (or whatever integer max value the field allowed instead)? Not sure if that's possible, but a thought :)


I am considering a node-red install, and I'm not averse to "getting my hands dirty", so to speak; but admittedly my CCGX, tied in to VRM rules is a super-easy quick-win solution that most average consumers will be most likely willing to delve into.

Thanks again!

0 Likes 0 ·
Show more comments