Changes (v2.40~38 up to and including ~45)
General:
- Add "Inverter only" option to the On/Off/Charger-only switch in the Multi/Quattro menus
- Add support to give a custom name to our SmartSolar VE.Can chargers. Note that some other devices connected via VE.Can can also be given a customer name, such as a Skylla-i. But others unfortunately don't support that feature, such as our VE.Can Tank Sender Adapter.
- The "Multiple managed batteries" warning was removed, thanks Wilco.
- Send custom names to the VRM Portal. Soon we'll improve the VRM Portal to use those names, making it possible to customers to set their system up such that all those graphs on the Advanced page are named; rather than the "Solar charger (288)" naming.
- Fix issues related to DVCC and solar chargers; these issues were introduced together with the new features introduced earlier in v2.40 (charge current sense and more).
- Hide the bluetooth on/off switch on devices that don't have bluetooth. (the Cerbo GX has bluetooth).
- Fix bug where, in certain conditions, the Multi/Quattro could not be switched on.
- Fix bug that prevented disabling the Sunday in the ESS Scheduled Charging settings. Bug was introduced in v2.40~19, thank you John H for reporting!.
- Update VE.Bus Error 8 and Error 11 titles to be in line with the updated documentation.
- Add support for the Discovery AES battery, including forcing the DVCC & SVS options to their required setting (DVCC on, SVS off).
- Rename "Battery measurements" menu to "Marine MFD App Configuration" menu. Thank you Matej!
- Force the BMS-Can port on the EasySolar-II GX and MultiPlus-II GX to be able to be used only for that purpose, no longer as a VE.Can port. The reason why we changed that is that we can't guarantee proper functioning of that port for connecting VE.Can products, even worse: we know for sure it won't work reliable. The hardware is not good enough. Product documentation of those products has been updated already a while ago.
Developers:
- Change address of mqtt server. More info here. Note that, for now, there is still only one and the same mqtt server behind all those addresses. A few weeks from now we'll deploy the new cluster. After which still the old server remains in tact: any customer that has issues because of this change, and needs more time to adapt his own setup and software, can solve the problem by reverting back to v2.33.
- Cerbo GX preparations.
- VictronConnect remote settings preparations.
- Add ntp and gpsd as optional opkg installable packages