Firmware 3.6.4 is downgrading after restart or power loss #1620
Comments
|
This is a known problem with previous versions and the way the firmware was flashed to the BBQKees devices. You will need to make a backup of your settings and re-flash using the Flash tool. See https://emsesp.github.io/docs/#breaking-changes-in-v36x |
|
Thanks for the quick response. That's what I had done when I upgraded to 3.5.1. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
PROBLEM DESCRIPTION
Successful upgraded to firmware 3.6.4. But when I restart the device through webUI or disconnect the power it is downgrading to firmware 3.6.0.
REQUESTED INFORMATION
System information output
{ "System Info": { "version": "3.6.0", "platform": "ESP32", "uptime": "000+00:09:32.543", "uptime (seconds)": 572, "free mem": 147, "max alloc": 95, "free app": 8, "reset reason": "Power on reset / APP CPU reset by PRO CPU" }, "Network Info": { "network": "WiFi", "hostname": "ems-esp", "RSSI": -43, "IPv4 address": "192.168.20.69/255.255.255.0", "IPv4 gateway": "192.168.20.1", "IPv4 nameserver": "192.168.20.1", "static ip config": true, "enable IPv6": false, "low bandwidth": true, "disable sleep": false, "enable MDNS": false, "enable CORS": false, "AP provision mode": "disconnected", "AP security": "wpa2", "AP ssid": "ems-esp" }, "NTP Info": { "NTP status": "connected", "enabled": true, "server": "time.google.com", "tz label": "Europe/Amsterdam" }, "OTA Info": { "enabled": false, "port": 8266 }, "MQTT Info": { "MQTT status": "connected", "MQTT publishes": 211, "MQTT queued": 0, "MQTT publish fails": 0, "MQTT connects": 1, "enabled": true, "client id": "ems-esp", "keep alive": 60, "clean session": false, "entity format": 0, "base": "nefit", "discovery prefix": "homeassistant", "discovery type": 0, "nested format": 1, "ha enabled": true, "mqtt qos": 0, "mqtt retain": false, "publish time heartbeat": 60, "publish time boiler": 10, "publish time thermostat": 10, "publish time solar": 10, "publish time mixer": 10, "publish time other": 10, "publish time sensor": 10, "publish single": false, "publish2command": false, "send response": false }, "Syslog Info": { "enabled": false }, "Sensor Info": { "temperature sensors": 0, "temperature sensor reads": 0, "temperature sensor fails": 0, "analog sensors": 0, "analog sensor reads": 0, "analog sensor fails": 0 }, "API Info": { "API calls": 0, "API fails": 0 }, "Bus Info": { "bus status": "connected", "bus protocol": "Buderus", "bus telegrams received (rx)": 292, "bus reads (tx)": 44, "bus writes (tx)": 0, "bus incomplete telegrams": 0, "bus reads failed": 0, "bus writes failed": 0, "bus rx line quality": 100, "bus tx line quality": 100 }, "Settings": { "board profile": "S32", "locale": "en", "tx mode": 1, "ems bus id": 11, "shower timer": false, "shower alert": false, "hide led": false, "notoken api": false, "readonly mode": false, "fahrenheit": false, "dallas parasite": false, "bool format": 1, "bool dashboard": 1, "enum format": 1, "analog enabled": true, "telnet enabled": true, "max web log buffer": 50, "web log buffer": 8 }, "Devices": [ { "type": "boiler", "name": "Topline/GB162", "device id": "0x08", "product id": 115, "version": "03.06", "entities": 67, "handlers received": "0x10 0x11 0x15 0x1C 0x18 0x19 0x34", "handlers fetched": "0x14 0x16 0x33", "handlers pending": "0xBF 0xC2 0x1A 0x35 0x26 0x2A 0xD1 0xE3 0xE4 0xE5 0xE6 0xE9 0xEA" }, { "type": "controller", "name": "BC10", "device id": "0x09", "product id": 114, "version": "01.03", "entities": 0 } ] }TO REPRODUCE
Upload latest firmware 3.6.4 through webUI
Restart with button on system status, or disconnect the power
After restart EMS-ESP Version is back to 3.6.0
EXPECTED BEHAVIOUR
A restart should stay with firmware 3.6.4
ADDITIONAL CONTEXT
Log after upgrade 3.6.4
Log after reboot
The text was updated successfully, but these errors were encountered: