ghosty.be

ok messing around with mkspiffs ... I saw in your partitions.csv the spiffs is 500kB ? Tried something like mkspiffs -c ./data -s 512000 spiffs.bin but that says ... /captive/app.js...

so after a bit more searching: spiffs by default use 4k block ... du -B4K data/ 130 when I multiply that by 4 it's 520k :/ So you use a...

just wondering how you got all the data there in the end :/ As I assume that your github /data should be a reflection of the data onto the spiffs...

Did not really find how to trigger it *yet* still trying with the current release v0.07.2 tried deleting a bunch of images and uploading the backup config.json *ok* reflashed tried...

running it for a solid week now without problems... but then again since I didn't mess with it much I can't really say if its now gone :) I could...

I today played a lot with the config, copy - pasting other configs and reloading... that's what trashed mine before, but this version has been running fine for 18 days...

so far been messing with it quite a bit ... not seen the spiffs corruption issue with the version attached to this thread... (did not get it corrupted despite rewriting...

isn't it rebooting at that point? (see other bugs where we reported random reboots when it looses wifi or something) I have never seen any other reason why it would...

yeah i keep values from domoticz on there like temp / humidity ... so when it reboots it looses all state of those so everything shows 0 ... I have...

So that would probably be a no... :) Just grepped through your code and found this in Homepoint-master/main/fs/ConfigReader.cpp: if (sceneType == "Light" || sceneType == "Switch")