search

arendst / Tasmota

Alternative firmware for ESP8266 and ESP32 based devices with easy configuration using webUI, OTA updates, automation using timers or rules, expandability and entirely local control over MQTT, HTTP, Serial or KNX. Full documentation at
https://tasmota.github.io/docs
GNU General Public License v3.0
22.26k stars 4.81k forks source link

Upgrade to 4.2.0 #382

Closed aferraz closed 7 years ago

aferraz commented 7 years ago

Hi, I upgrade from 4.1.3 to 4.2.0 a sonoff pow, 3 electrodragon and 1 nodemcu. Except the POW in all other cases I have lose my configuration and the electrodragon/esp startup with the user_config data. I try via firmware upload and ota, same result.

Now on the electrodragon I also have this situation: 21:18:04 CMND: power1 21:18:05 MQTT: /esp12/RESULT = {"POWER1":"POWER"} 21:18:05 MQTT: /esp12/POWER1 = POWER 21:18:08 CMND: power2 21:18:08 MQTT: /esp12/RESULT = {"POWER2":"POWER"} 21:18:08 MQTT: /esp12/POWER2 = POWER

How I can revert to ON/OFF state ?

Thanks

aferraz commented 7 years ago

Sorry, found the solution in StateText1 and StateText2. But what about the configuration lost ?

arendst commented 7 years ago

How did you upgrade? Did you use the new linker? If so then please keep using the old linker. I removed the new linker until further notice as the this version (4.2.0) has to be installed with the old linker first before the new can be used.

aferraz commented 7 years ago

Hi @arendst, I have compiled the source as always. Non change IDE side.

aferraz commented 7 years ago

I've tried now with the old linker with the same results. The configuration of the item is gone and was taken from user_config. Tried on electrodragon

arendst commented 7 years ago

What happens if you go back to version 4.1.3? Are the configuration items also gone or do they re-appear?

Version 4.2.should have copied the settings from spiffs flash to eeprom flash. It does this by comparing the CFG_HOLDER value in spiffs flash with the value in user_config.h. If they miscompare then the result you noticed will occur as it will load default settings in eeprom. As long as there is no new linker used the old settings in spiffs are still there so going back to the previous version should just work.

aferraz commented 7 years ago

I'll try and give you a feedback

arendst commented 7 years ago

No need to test. Problem is caused by residue data already present in the eeprom area. I narrowed the test window to limit the problem you have encountered. Sorry for the inconvenience. Next version will hopefully work better but that's of no use to you anymore...

aferraz commented 7 years ago

No problems, thanks for your hard and very good work

aferraz commented 7 years ago

Hi @arendst, I have installed 5.0 on an nodemcu but I cant see more free program space: My values after flashing: Flash size 4096kB Program flash size 1024kB Program size 439kB Free program space 564kB Free memory 29kB

I have compiled the firmware with PlatformIO However, also in this case, I lost the settings, I recovered from the backup

arendst commented 7 years ago

You see the gain only in Free program space which is incremented by 64k allowing me to free up Free memory with 1k by moving all static data to Program.

Sorry the settings were lost once again. All my 15 devices worked fine...

Did you compile your nodemcu code for 1G or 4G flash size? If it was 4G before than this is expected as the spiffs area is in another location between 1G and 4G images.

aferraz commented 7 years ago

It's true, before was 4G.