build a spezial version don't work - littlefs not build

[linuxdep]

Hello, I have a special board from the manufacturer Kinetos, who are now insolvent. Since EVCC doesn't work with the installed version, I wanted to compile my own version. I had already found a modified version, but it disabled littlefs. Now I wanted to build everything with littlefs and followed the build guide:

• clone repo + subrepo gui-v2
• then npm commands... npm build, everything seemed fine.

Compiling the firmware, bootloader, and partitions.ini files worked. But the filesystem seems to be missing, because I wanted to test it on a new WT32-ETH01 board, but it doesn't boot without littlefs and reports a mounting error.

Then I saw there's a build filesystem image, but it doesn't boot because there's no src/data directory. I can't find where it comes from. The AI ​​suggested there must be a script or something that copies the data, but I can't find anything like that. But how do you guys do that? What am I missing?

My WB is no longer accessible after the last OTA update. I'll have to do it on-site, but first I need to test if everything works on the separate board. I hope you can help me quickly, thanks.

[jeremypoulter]

Little FS is only used to store config and stats files. You will get an error the first time you boot, but after that it will format the Little FS partition and you should not see the error again.

The UI is built in to the firmware and you should see some header files with the UI in the web directory. I am not aware of there ever have being a src/data file so can not help with that.

[linuxdep]

Thanks, after full clean and new build, flash erase und upload ist works, second boot no issus to see.

But why is littlefs integrated into the software if it's not needed? What was originally intended to be stored there? As an outsider, it seems like something's missing. I'm still inexperienced in software development, but I wanted to be able to use the Kinetos WB properly again. I think there are others who have this box but no solution for EVCC.

I've connected a CT terminal for current measurement, but I'd also like to read and integrate the built-in electricity meter via RS485 if I can manage that. What's the best way to integrate the current values ​​and the total kWh into the software? The AI ​​suggested MQTT, but could I send charging currents there that are already being transmitted to EVSE?

the communication from ESP32 with the data (L1,L2,L3,energy) was send to EVSE with
$T0 L1 L2 L3 send
$T1 energy (mA) send
$T2 get L1 L2 L3

[jeremypoulter]

But why is littlefs integrated into the software if it's not needed? What was originally intended to be stored there? As an outsider, it seems like something's missing.

Little FS is used to store files generated by the firmware, config, stats, etc

In regards to the energy meter this is not something that is currently available, the $T... are for testing so may not do what you expect and I think you need a special build of the OpenEVSE firmware to enable these.

Currently the current is read from the OpenEVSE module and the voltage is either a fixed value or feed from an external source via MQTT.

There is the energy_monitor module that handles turning these into power/energy and storing the daily/weekly/yearly stats. You can probably write an alternative that feeds from the dedicated hardware, and maybe the current can be feed to the safety module via the $T commands, but as I said above these are only really for testing, so it may be safer to use the built in current sensor as this has been validated.

[linuxdep]

OK, the openEVSE Board has this implemetation inside, the old ESP32 FW don't work with EVCC. That's why I updated the firmware.
The old FW has use this $T commands... and openEVSE FW i don't have touch.

Even if I wanted to update them, the board isn't based on the standard ATmega328 but apparently on the LGT8F328P. I didn't want to mess with that. But this firmware seems to have other peculiarities, because the Current Scale and Offset parameters are being sent but not applied. These are supposed to be sent to the EVSE and stored there, right? I have firmware E532_L-8.2.0 and ESP32-5.1.5 (the latest version from GitHub) installed; previously, it had version 4.x.x. Or could there be problems if the latest EVSE firmware isn't used?

There were some old values ​​entered for Current Scale and Offset, but the current reading didn't match the CT; instead of 6A, it showed 2A. After I tried to adjust it, it only shows 0 and isn't applying any values.
For the first part, the CT scan will certainly suffice for me.

What could be causing this?