I installed v3.70~34 on three of my systems. Two of the systems work fine, but my 3-phase ESS system with Pytes batteries constantly cycles with no data on the Touch 50, then data, no data, etc. and the inverters are in pass-thru mode. It’s as if it’s losing and reconnecting to the Pytes batteries, but the Pytes device always shows in the device list. Reverting back to ~26 solves the issue. The other two systems use Victron batteries and BMS’s and no issues.
Why are we still debating the forum? What interests me is the original technical issue and a clear workaround.
Issue:
- Multiple venusOS instances in test and production. No (direct) access to latest 3.7 point release when Victron decides (on very short notice) to do a 3.6 beta. Therefore not able to plan our own roll-out schedule.
Possible workarounds:
- Keep an additional venusOS instance constantly updated on latest 3.7 and make a private copy of all updates.
- Put sd-cards in all other GX devices / venusOS instances, enable remote access to upload f/w of choice and do manual updates from sd-cards.
- Create a private library of updates and hack venusOS to point it toward that library
- A better way?
The whole point here is autonomy over our own roll-out agenda, independent of Victron’s development agenda.