Closed Cayn183 closed 1 year ago
Can you let me know what files you changed? Probably only the Configuration.h I am suspecting. Did you change anything apart from the WIFI SSID/PW and your blynk credentials?
I have changed a few things, i test it with a unchanged version only wifi, disabled blynk. Before change, I have used a modified diy-mashines with 24h and disabled 0 in the hour but not in the minute.
Could you please create a fork of the repository and commit your changed files? That way we will have a good diff and I would then be able to help and reproduce a potential bug on my side
I have tested it with the blank code. After ~15min i have got the corrupted file again in the terminal. Make it a change if i upload the code per serial? i actually load it via the ota updater?
I have not had any reports of this happening so far, and the new version has been out since quite some time now. It should not make a difference if you upload it via OTA or serial. If you are saying it happens without any changes, I assume that that means also without providing any WiFi or timezone information?
I have only disabled blynk for the test and have put wifi credentials. Also i have uploaded the blank without any changes. But i have found that it reboots after 30mins, thats the sinc time of the clock. When i edit it to 5mins, i get the problem every 5 mins.
You are right, I was also able to reproduce your issue now. Something seems to have changed since I developed it. I was able to find a fix, I think. It should already be on the master branch. Just pull and retry it and then let me know if you ran into any more issues
Hello Florian,
I am currently using my clock with the old code for over a year and I am very happy with it. Unfortunately, due to the recent shutdown of the old Blynk servers, I was forced to update the clock to the new version. I made the adjustments as with the old code and also tried various other variants to get the clock running. However, it keeps restarting itself. A file appears to be corrupt in the serial log. Could you please help me to find the error?
Best regards Aaron