[DESS HACK] Unexpected Bat2Grid and Solar-Feedin. (Green Mode)

Wie wann wodurch?

Bitte, es geht nicht darum, wann und wie (durch ein Update) überschrieben wird (bei mir schon 2 mal geschehen) - sondern um die Möglichkeit, den Hack von extern zu triggern. Bitte nicht das Thema wechseln. Die Frage war auch explizit an dognose gestellt.

Bfo

Sorry, aber hier lesen viele mit. Daher wäre es nett Fragen so zu stellen, dass sie auch von anderen verstanden werden.

Wenn du Fragen ausschließlich an ihn persönlich stellen möchtest, dann schreib ihm eine PM.

Edit: aber ich habs schon gecheckt, worums geht, somit erledigt

Hätte ich gerne gemacht, habe die Funktion aber hierzu nicht gefunden.

1 Like

Meanwhile there’s v3.51 :grinning:

The hack still works on v3.51 :slight_smile:

1 Like

Does the new gui v2 show the DESS HACK settings in v3.51?

No, not yet. That’s WIP.
(Work In Progress)

You can already do that, by using

dbus -y com.victronenergy.settings /Settings/DynamicEss/MaxTargetSocForIdle SetValue 90
and
dbus -y com.victronenergy.settings /Settings/DynamicEss/AdhocChargeRate SetValue 3000

The system should only overwrite this on firmware updates. And it that case, it is intended to not automatically apply the hack. If the modified files are changed with the new firmware, injecting old code may lead to a totally broken System-Calc script, which would be kinda uncool.

Exactly :slight_smile:

Hi,
thanks for this info.
But i get

root@victron:~# 

dbus -y com.victronenergy.settings /Settings/DynamicESS/MaxTargetSocForIdle SetValue 50
Traceback (most recent call last):
  File "/usr/bin/dbus", line 374, in <module>
    ret = obj.object.get_dbus_method(method.name, iface.name)(*args)
AttributeError: 'NoneType' object has no attribute 'name'


dbus -y com.victronenergy.settings /Settings/DynamicESS/AdhocChargeRate SetValue 2500
Traceback (most recent call last):
  File "/usr/bin/dbus", line 374, in <module>
    ret = obj.object.get_dbus_method(method.name, iface.name)(*args)
AttributeError: 'NoneType' object has no attribute 'name'

Bfo

My bad, it’s DynamicEss not DyanamicESS in the dbus-key.

Now it runs like charme :wink:

for all others, i use this bash script:

#!/bin/bash

ess="192.168.4.15"
maxWatt=10000
minWatt=250
minSoc=10
maxSoc=100
sudoUser="www-data"	# or empty
########################################################################################################################


[ "$sudoUser" ] && scmd="sudo -u $sudoUser " || scmd=""


usage(){
    printf "\n\t%s [start [soc] [watt]] | [stop]\n" "$(basename "$0")"
    printf "\t   soc must be >= %d && <= %d\n" "$minSoc" "$maxSoc"
    printf "\t   watt must be >= %d && <= %d\n\n" "$minWatt" "$maxWatt"
    echo -e "\t  ~*(c)ontact repcom@gmail.com 11/2024*~ \n"
    exit 1
}

do_start(){
    soc="$1"
    watt="$2"
    if [[ $soc =~ ^[0-9]+$ && $watt =~ ^[0-9]+$ ]] && \
       [[ $soc -ge $minSoc && $soc -le $maxSoc ]] && \
       [[ $watt -ge $minWatt && $watt -le $maxWatt ]]; then
        echo "Starting with SOC=$soc and Watt=$watt"
        ret=$(eval $scmd ssh root@$ess dbus -y com.victronenergy.settings /Settings/DynamicEss/MaxTargetSocForIdle SetValue "$soc")
        echo -n -e "Soc set to $soc "; [ $ret -eq 0 ] && echo "successfull" || echo "unsuccessfull"
        ret=$(eval $scmd ssh root@$ess dbus -y com.victronenergy.settings /Settings/DynamicEss/AdhocChargeRate SetValue "$watt")
        echo -n -e "Watt set to $watt "; [ $ret -eq 0 ] && echo "successfull" || echo "unsuccessfull"
    else
        usage
    fi
}

do_stop(){
    echo -n "Stopping ... "
    ret=$(eval $scmd ssh root@$ess dbus -y com.victronenergy.settings /Settings/DynamicEss/AdhocChargeRate SetValue "0")
    echo -n -e "Watt set to 0 "; [ $ret -eq 0 ] && echo "successfull"|| echo "unsuccessfull"
}


case $1 in
    start)
        do_start "$2" "$3"
    ;;
    stop)
        do_stop
    ;;
    *)
        usage
    ;;
esac

To stop later the adHoc charging, you can use something like that:

echo /opt/vicAdhoc.sh stop | at now + 70min

Dont forget to exchaneg ssh keys :wink:

Comments are welcome

Bfo

2 Likes

For those who may or may not have noticed yet: VenusOS v3.52 stable is out.
Just tested the hack against this version and it still works !

There have been some changes in dynamicess.py so maybe @dognose can update his version to reflect these changes.

2 Likes

I will have a look at it over the weekend.

The dynamicess.py I used for the 3.50-patch already was a little more recent than the one shipping with 3.50, so possibly the changes are already contained.

Hello,
I dont have that menu on DESS.

Old GUI or new GUI v2?
At the moment the hack-menu is only shown in the old GUI

In the old GUI

What is the Hack Menu?

Did you install the Hack?

1 Like

no.
where do i can get that?

Read this thread, then you will find the answer…

2 Likes