@OGPS : noted your remark there on the Pytes system. Can you email me that vrm url, enable remote support & bring it in the fault condition? Then someone will check tomorrow - thanks for the report!
@rajjinator 
wrt “handbags at the ready”, had to look that one up! 
(I translated it as: careful, discussion coming !)
Could it be that this also fixes v3.7~33 ESS feeding non-critical loads, while set to only critical loads, under other conditions?
If so, I’d really appreciate anybody willing to send me copy of v3.7~34 for Cerbo GX (I can ask can’t I).
Would a rollback not work? Usually that is an option if you already had it on the device?
We don’t auto update, missed the ~34 point release, can’t revert to what we don’t have. To be honest, I didn’t even realize until an hour ago that the ~34 change log had an item that might very well correspond to an issue I only recently noticed when looking at the charge and power history in VRM.
It’s a minor issue for us though, not related to our larger development projects. At least I know that, for now, I can stop trying to figure out why ESS behaves counterintuitive w.r.t. this particular setting and revisit this when 3.7 comes back online.
Perhaps yes. I’m not sure to be honest.
v3.70~34 (or a later version) will be available again tomorrow or Wednesday latest.
And we’ll see to it that for a future interruption due to “backport-testing”, we can keep a downloadable copy available.
That is great news, thanks.
Thanks!
Can we have the latest SignalK (2.16) included in the 3.70 beta release please
Back in business
Installed v3.70~35 a few minutes ago, seems to work fine.
This works even when bat2grid restriction is in place. But I wonder, the battery will discharge a bit faster, does this cause a problem for the dess schedule?
3 posts were split to a new topic: How to combine a virtual gps in Node-RED with a real one
For archiving and testing purposes I try to keep a local copy of the beta versions but I missed v3.70~34 since v3.66~1 and v3.70~35 were released before I could grab a copy of v3.70~34.
Not a big deal of course, just a hiatus in my archive repository (sometimes I don’t have the time to check for updates and my cron-fu is weak lately).
By the way: there’s a copy of v3.63~2 lurking around in the “Official release” download folder that probably shouldn’t be there.
I’m not sure if this is a firmware or VRM issue but it seems a bug with vrm alerts and the GX IO Extender. Vrm portal reports “No value available, product not connected?”
The IO extender is otherwise working fine.
8 posts were split to a new topic: V3.70 beta issues when using mods (serial battery)
For what it’s worth, I’m running ESS with 3.70~35.
First time testing one of the 3.70 releases (3.70-35). Shelly plugs are shown and working fine (relais and power consumption) but a Shelly EM50 does not show the power consumption at all. Not sure if that is supposed to work.
Hi everyone,
with dynamic electricity prices from the EPEX day-ahead, ESS already has a strong foundation for smart load shifting and cost optimization. However, a new factor is coming into play: dynamic grid fees.
These fees vary depending on grid load and time of day. That means the “true” cost per kWh is not just the spot market price, but rather spot price + grid fee. Optimizing only by exchange prices might soon miss part of the picture.
This is not only relevant in Germany. Other countries are also introducing or already applying variable grid tariffs – for example Sweden, Norway, the Netherlands, parts of the UK,
For example:
it would much more often pay off to charge the battery during cheap/low-fee hours and discharge it during peak hours.
The actual cost difference for running large loads (heat pumps, EV charging, storage cycles) could be far greater once both elements are included.
That’s why I think it could be very interesting if Victrons DESS did not only integrate dynamic exchange prices, but also considered dynamic grid fees in its optimization logic. This would allow for more precise cost savings and closer alignment with how future tariffs are structured.
My question: Do you think Victron could implement such a calculation within DESS in 3.70?
Some users already mentioned that claim here:
https://community.victronenergy.com/t/dynamic-tarifs-in-dess/10490/19
https://community.victronenergy.com/t/variable-grid-charges-in-germany-from-2025/9042/26
https://community.victronenergy.com/t/dess-and-german-14a-enwg-modul-3-dynamic-grid-fees/12747/36
Any clarity on how these grid fees will work in practice, how will they be published and how long in advance?
PS v3.70~37 beta started under a new thread
