Frequent restarts/crashes and values going backwards...

[VlastiBroucek]

DESCRIPTION

dev.8 and and dev.7 are restarting for me quite often (dev.8 3 times in the last 2 hours, did not notice dev7 until now, been away). What is worse, with dev.8 some values are not correctly retained as indicated here:

I have never had random restarts and never seen value being less after restart.

REQUESTED INFORMATION

Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!

• Searched the issue in issues
• Searched the issue in discussions
• Searched the issue in the docs
• Searched the issue in the chat
• Provide the System information in the area below, taken from http://<IP>/api/system

{
  "system": {
    "version": "3.8.3-dev.8",
    "uptime": "000+00:19:43.588",
    "uptimeSec": 1183,
    "resetReason": "Software reset CPU / Software reset CPU",
    "platform": "ESP32",
    "cpuType": "ESP32-D0WD-V3",
    "arduino": "ESP32 Arduino v2.0.17",
    "sdk": "v4.4.7-dirty",
    "freeMem": 169,
    "maxAlloc": 107,
    "freeCaps": 4184,
    "usedApp": 2381,
    "freeApp": 3315,
    "partition": "app0",
    "flash_chip_size": 16384,
    "psram": true,
    "psramSize": 4093,
    "freePsram": 4048,
    "model": "",
    "txpause": false,
    "gpios_allowed": "2, 4, 5, 14, 34",
    "gpios_in_use": "2, 4, 5, 14, 34",
    "gpios_available": ""
  },
  "network": {
    "network": "Ethernet",
    "hostname": "ems-esp",
    "TxPowerSetting": 0,
    "staticIP": false,
    "lowBandwidth": false,
    "disableSleep": true,
    "enableMDNS": true,
    "enableCORS": false
  },
  "ntp": {
    "NTPstatus": "connected",
    "enabled": true,
    "server": "time.cloudflare.com",
    "tzLabel": "Australia/Hobart",
    "timestamp": 1782775049,
    "NTPStatus": "connected"
  },
  "ap": {
    "provisionMode": "disconnected",
    "ssid": "ems-esp",
    "security": "wpa2",
    "channel": 1,
    "ssidHidden": false,
    "maxClients": 4,
    "localIP": "192.168.4.1",
    "gatewayIP": "192.168.4.1",
    "subnetMask": "255.255.255.0"
  },
  "mqtt": {
    "MQTTStatus": "connected",
    "MQTTPublishes": 564,
    "MQTTQueued": 0,
    "MQTTPublishFails": 0,
    "MQTTReconnects": 0,
    "enabled": true,
    "clientID": "esp32-d767b4fc",
    "keepAlive": 60,
    "cleanSession": false,
    "entityFormat": 1,
    "base": "ems-esp",
    "discoveryPrefix": "homeassistant",
    "discoveryType": 0,
    "nestedFormat": 1,
    "haEnabled": true,
    "mqttQos": 0,
    "mqttRetain": false,
    "publishTimeHeartbeat": 60,
    "publishTimeBoiler": 10,
    "publishTimeThermostat": 10,
    "publishTimeSolar": 10,
    "publishTimeMixer": 10,
    "publishTimeWater": 10,
    "publishTimeOther": 60,
    "publishTimeSensor": 10,
    "publishSingle": false,
    "publish2command": false,
    "sendResponse": true
  },
  "syslog": {
    "enabled": false
  },
  "modbus": {
    "enabled": false
  },
  "sensor": {
    "temperatureSensors": 3,
    "temperatureSensorReads": 708,
    "temperatureSensorFails": 0
  },
  "analog": {
    "enabled": false
  },
  "api": {
    "APICalls": 0,
    "APIFails": 0
  },
  "bus": {
    "busStatus": "connected",
    "busProtocol": "HT3",
    "busTelegramsReceived": 1789,
    "busReads": 600,
    "busWrites": 0,
    "busIncompleteTelegrams": 0,
    "busReadsFailed": 0,
    "busWritesFailed": 0,
    "busRxLineQuality": 100,
    "busTxLineQuality": 100
  },
  "settings": {
    "boardProfile": "E32V2",
    "locale": "en",
    "txMode": 5,
    "emsBusID": 73,
    "showerTimer": false,
    "showerMinDuration": 180,
    "showerAlert": false,
    "hideLed": false,
    "noTokenApi": false,
    "readonlyMode": false,
    "fahrenheit": false,
    "dallasParasite": false,
    "boolFormat": 1,
    "boolDashboard": 1,
    "enumFormat": 1,
    "analogEnabled": false,
    "telnetEnabled": true,
    "maxWebLogBuffer": 100,
    "modbusEnabled": false,
    "forceHeatingOff": false,
    "developerMode": true
  },
  "devices": [
    {
      "type": "boiler",
      "name": "Condens 5000 W",
      "deviceID": "0x08",
      "productID": 95,
      "brand": "BOSCH",
      "version": "12.16",
      "entities": 69,
      "handlersReceived": "0x10 0x11 0x15 0x1C 0x18 0x19 0x34 0x2A 0x04",
      "handlersFetched": "0x14 0x16 0x33",
      "handlersPending": "0xBF 0xC2 0xC6 0x1A 0x35 0x27 0x2E 0x3B",
      "handlersIgnored": "0x23"
    },
    {
      "type": "thermostat",
      "name": "CR50",
      "deviceID": "0x18",
      "productID": 157,
      "brand": "BOSCH",
      "version": "43.02",
      "entities": 57,
      "handlersReceived": "0x06 0xA2 0x031D 0xBF 0xC0",
      "handlersFetched": "0x02A5 0x02B9 0x02AF 0x029B 0x0421 0x0291 0x02F5 0x023A 0x0241 0x043F",
      "handlersPending": "0xA3 0x12 0x13 0x0471 0x02A6 0x02BA 0x02B0 0x029C 0x0472 0x02A7 0x02BB 0x02B1 0x029D 0x0473 0x02A8 0x02BC 0x02B2 0x029E 0x0474 0x02A9 0x02BD 0x02B3 0x029F 0x0475 0x02AA 0x02BE 0x02B4 0x02A0 0x0476 0x02AB 0x02BF 0x02B5 0x02A1 0x0477 0x02AC 0x02C0 0x02B6 0x02A2 0x0478 0x0467 0x0422 0x0468 0x0292 0x0423 0x0469 0x0293 0x0424 0x046A 0x0294 0x02F6 0x031B 0x031E 0x0267 0xBB 0x023E 0x016E"
    },
    {
      "type": "controller",
      "name": "HT3",
      "deviceID": "0x09",
      "productID": 95,
      "brand": "",
      "version": "12.16",
      "entities": 0
    },
    {
      "type": "temperaturesensor",
      "name": "temperaturesensor",
      "entities": 3
    },
    {
      "type": "scheduler",
      "name": "scheduler",
      "entities": 1
    },
    {
      "type": "custom",
      "name": "custom",
      "entities": 1
    }
  ]
}

TO REPRODUCE

Not sure how to reproduce. Until dev7 my system almost never restarted. From dev.7 I have many restarts and dev8 added the value issue. However, it does not seem to be consistent, last restart just now, did not throw that error.

(Please remember to close the issue when it has been addressed)

[VlastiBroucek]

Not sure what is happening here, but last restart I got also this:

[VlastiBroucek]

Further update, I am now getting the modes message with every restart, and this is what's in mqtt explorer:

{
  "~": "ems-esp",
  "uniq_id": "thermostat_hc1",
  "def_ent_id": "climate.thermostat_hc1",
  "name": "hc1",
  "mode_stat_t": "~/thermostat_data",
  "mode_stat_tpl": "{%if value_json.hc1 is undefined or value_json.hc1.mode is undefined%}off{%elif value_json.hc1.mode=='manual'%}heat{%elif value_json.hc1.mode=='day'%}heat{%elif value_json.hc1.mode=='heat'%}heat{%elif value_json.hc1.mode=='night'%}off{%elif value_json.hc1.mode=='eco'%}off{%elif value_json.hc1.mode=='off'%}off{%else%}auto{%endif%}",
  "temp_cmd_t": "~/thermostat/hc1/seltemp",
  "temp_stat_t": "~/thermostat_data",
  "temp_stat_tpl": "{{value_json.hc1.seltemp if value_json.hc1 is defined and value_json.hc1.seltemp is defined else 0}}",
  "curr_temp_t": "~/thermostat_data",
  "curr_temp_tpl": "{{value_json.hc1.currtemp if value_json.hc1 is defined and value_json.hc1.currtemp is defined else 0}}",
  "min_temp": "5",
  "max_temp": "30",
  "temp_step": "0.5",
  "mode_cmd_t": "~/thermostat/hc1/mode",
  "act_t": "~/boiler_data",
  "act_tpl": "{% if value_json.hpactivity=='cooling'%}cooling{%elif value_json.heatingactive=='on'%}heating{%else%}idle{%endif%}",
  "modes": [
    "auto",
    "heat"
  ],
  "dev": {
    "ids": [
      "ems-esp-thermostat"
    ]
  },
  "avty": [
    {
      "t": "~/thermostat_data",
      "val_tpl": "{{'online' if value_json.hc1 is defined and value_json.hc1.seltemp is defined else 'offline'}}"
    },
    {
      "t": "~/thermostat_data",
      "val_tpl": "{{'online' if value_json.hc1 is defined and value_json.hc1.currtemp is defined else 'offline'}}"
    },
    {
      "t": "~/thermostat_data",
      "val_tpl": "{{'offline' if value_json.hc1 is undefined or value_json.hc1.mode is undefined else 'online'}}"
    },
    {
      "t": "~/status"
    }
  ],
  "avty_mode": "all"
}

I think, it might be coming from this line:

"mode_stat_tpl": "{%if value_json.hc1 is undefined or value_json.hc1.mode is undefined%}off{%elif value_json.hc1.mode=='manual'%}heat{%elif value_json.hc1.mode=='day'%}heat{%elif value_json.hc1.mode=='heat'%}heat{%elif value_json.hc1.mode=='night'%}off{%elif value_json.hc1.mode=='eco'%}off{%elif value_json.hc1.mode=='off'%}off{%else%}auto{%endif%}",

[proddy]

thanks for reporting, we'll compare dev.7 with dev.8 to see what could have caused this.

edit dev.8 only had one line changed for date/time setting on a Junkers/HT3 thermostat. So more likely this was introduced in dev.7 and the changes in the scheduler

[MichaelDvP]

The warning about energy is normal after crashes. These values are calculated by ems-esp and stored every full hour and on planed reboots (updates, etc). After a crash the stored value is from last hour change. Because of limited flash writing we can't store more often.
Your system info shows one schedule and on custom entity, please tell what these are.

[VlastiBroucek]

Oh OK, I get it about the values.

Here are answers:

[VlastiBroucek]

thanks for reporting, we'll compare dev.7 with dev.8 to see what could have caused this.

edit dev.8 only had one line changed for date/time setting on a Junkers/HT3 thermostat. So more likely this was introduced in dev.7 and the changes in the scheduler

Yes, I also think that dev.7 introduced it. Unfortunately, if I recall correctly, dev.7 was released twice...

[MichaelDvP]

Are you using the system/message command? This is the only change i see in dev.7 that could blow the stack and crash the esp when called from api or mqtt.

[VlastiBroucek]

No, don't use anything like that.
This is the only thing I have been doing since I started with EMS-ESP and it DID NOT cause restart this morning:

alias: Monthly boiler energy reset
description: >-
  This will reset energy consumption for the boiler to zero at the start of each
  month.
triggers:
  - at: "00:00:05"
    trigger: time
conditions:
  - condition: template
    value_template: "{{today_at().day==1}}"
    note: Trigger at the start of each month
actions:
  - action: mqtt.publish
    metadata: {}
    data:
      topic: ems-esp/boiler/nrgheat
      payload: "0"
    enabled: true
  - action: mqtt.publish
    metadata: {}
    data:
      topic: ems-esp/boiler/dhw/nrg
      payload: "0"
    enabled: true
  - action: notify.mobile_app_vlasti_iphone16
    metadata: {}
    data:
      message: Boiler energy values have been reset to zero
      title: Energy reset
  - action: persistent_notification.create
    metadata: {}
    data:
      message: Boiler energy values have been reset to zero
      title: Energy reset
mode: single

Interestingly, has been now running for over 26 hours without restart... So, to be safe, I have checked all my log files and no, there were no strange network activities, no other services were affected, and EMS-ESP is on wired connection.

[proddy]

it's most likely the lwip stack, which MQTT also uses which was increased. Hopefully the core3 builds would be better. You can try and switch over - you would need to make a backup & restore as it has a different filesystem format. Eventually this core3 branch will replace dev so everyone will need to make the switch at some point.

On the HA modes warning, please keep an eye on it. If it happens again then it's something we need to look into

[MichaelDvP]

I don't think it's related to the changed stack size. The stack change was for system/message command handling and was ported from core3 branch.

The HA message is because the thermostat is not available after reboot and the mode template sets off to this thermostat without off mode. Maybe we should change to if value is undefined%}heat{, as most thermostat have heat mode and every setting in undefined mode is basically wrong.

[VlastiBroucek]

HA message - that's exactly what I was thinking too @MichaelDvP

The restarts puzzle me. Up until I installed dev.7 I was extremely stable, usually lasted the whole week between restarts that I do every Sunday morning. I gradually restart router and other various devices, giving them enough time to settle before next one goes. No problems at all. Since Saturday when I installed dev.7 and later updated to dev.8 I had around 15 crashes until Wednesday afternoon. Since then, it was stable until 10 minutes ago when there was another crash. Here is what's in log file right now:

2026-07-02T18:19:39.000 I 1: [emsesp] EMS-ESP version 3.8.3-dev.8
2026-07-02T18:19:39.000 I 2: [emsesp] Last system reset reason Core0: Software reset CPU, Core1: Software reset CPU
2026-07-02T18:19:39.000 I 3: [emsesp] Loaded board profile E32V2 (PSRAM: 4093 KB)
2026-07-02T18:19:39.000 I 4: [emsesp] Library loaded: 129 EMS devices, 569 device entities, 11 languages (en,de,nl,sv,pl,no,fr,tr,it,sk,cz)
2026-07-02T18:19:39.000 I 5: [emsesp] Starting Scheduler service
2026-07-02T18:19:39.000 I 6: [emsesp] Starting Custom Entity service
2026-07-02T18:19:39.000 I 7: [emsesp] Ethernet connected (Local IP=192.168.50.132, speed 100 Mbps)
2026-07-02T18:19:39.000 I 8: [emsesp] Starting mDNS Responder service
2026-07-02T18:19:39.000 I 9: [emsesp] Starting NTP service
2026-07-02T18:19:39.000 I 10: [temperaturesensor] Starting Temperature Sensor service
2026-07-02T18:19:39.000 I 11: [emsesp] Starting Modules service
2026-07-02T18:19:39.000 I 12: [emsesp] Starting Web Server
2026-07-02T18:19:44.478 I 13: [mqtt] MQTT connected
2026-07-02T18:19:45.470 I 14: [system] NTP connected
2026-07-02T18:19:45.570 I 15: [emsesp] IPv6 (Eth) local: fe80:0000:0000:0000:feb4:67ff:fed7:c5cb
2026-07-02T18:19:46.570 I 16: [emsesp] IPv6 (Eth) global: 2001:8003:1424:3300:feb4:67ff:fed7:c5cb
2026-07-02T18:19:56.519 I 17: [emsesp] Detected EMS device: boiler (0x08)
2026-07-02T18:19:57.425 I 18: [emsesp] Detected EMS device: controller (0x09)
2026-07-02T18:19:57.805 I 19: [emsesp] Detected EMS device: thermostat (0x18)
2026-07-02T18:21:11.570 I 20: [emsesp] IPv6 (Eth) ULA: fd86:2c98:d884:09b6:feb4:67ff:fed7:c5cb

[MichaelDvP]

Sadly the esp does not have a real reset (software or button), a lot of internal registers stay on their values.
If you see crashes, try a power-on-reset by switching the power supply. This is the only reset that sets the esp to a defined state.
To analyze the crash reason it only helps to connect a serial terminal to the USB, than you get a traceback.

[VlastiBroucek]

My EMS-ESP crashed twice last night, so I power cycled it and will see... If it starts again, I've spare laptop that I can use to connect serial terminal and collect more data. Hope I won't have to...