Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RTC WAtchdog reboots and strange system/send with NAN #1935

Closed
harvey637 opened this issue Aug 14, 2024 · 29 comments
Closed

RTC WAtchdog reboots and strange system/send with NAN #1935

harvey637 opened this issue Aug 14, 2024 · 29 comments

Comments

@harvey637
Copy link

harvey637 commented Aug 14, 2024

see below ... :-)

@harvey637
Copy link
Author

harvey637 commented Aug 14, 2024

Since some versions I experience ems-esp reboots and strange sytem/send every few seconds.

Log says:

2024-08-14 07:59:40.000 INFO 1: [emsesp] Starting EMS-ESP version 3.7.0-dev.30 from app0 partition
2024-08-14 07:59:40.000 INFO 2: [emsesp] Last system reset reason Core0: RTC watch dog reset: CPU+RTC, Core1: APP CPU reset by PRO CPU
2024-08-14 07:59:40.000 INFO 3: [emsesp] Loading board profile CUSTOM
2024-08-14 07:59:40.000 INFO 4: [emsesp] Starting Scheduler service
2024-08-14 07:59:40.000 INFO 5: [emsesp] Starting Custom Entity service
2024-08-14 07:59:40.000 INFO 6: [emsesp] Starting Modules service
2024-08-14 07:59:40.000 INFO 7: [module] No external library modules found
2024-08-14 07:59:40.000 INFO 8: [emsesp] Loaded EMS device library (120 records)
2024-08-14 07:59:43.069 INFO 9: [emsesp] WiFi connected (IP=192.168.23.95, hostname=ems-esp, TxPower=19.3 dBm)
2024-08-14 07:59:43.096 INFO 10: [emsesp] Starting mDNS Responder service
2024-08-14 07:59:43.096 INFO 11: [emsesp] Starting NTP service
2024-08-14 07:59:47.807 INFO 12: [emsesp] Recognized new boiler with deviceID 0x08
2024-08-14 07:59:47.807 INFO 13: [emsesp] Recognized new thermostat with deviceID 0x10
2024-08-14 07:59:47.807 INFO 14: [emsesp] Recognized new thermostat with deviceID 0x38
2024-08-14 07:59:47.807 INFO 15: [emsesp] Recognized new gateway with deviceID 0x48
2024-08-14 08:00:07.454 INFO 16: [thermostat] ems-esp time set from thermostat
2024-08-14 08:00:46.078 INFO 17: [command] Called command system/send (Sende EMS-Telegramm) with value 0B NAN FF 13 01 01 BA 
2024-08-14 08:01:15.350 INFO 18: [command] Called command system/send (Sende EMS-Telegramm) with value 0B NAN FF 13 01 01 BA 
2024-08-14 08:01:27.636 INFO 19: [command] Called command system/send (Sende EMS-Telegramm) with value 0B NAN FF 13 01 01 BA 
2024-08-14 08:01:38.697 INFO 20: [command] Called command system/send (Sende EMS-Telegramm) with value 0B NAN FF 00 12 01 6A 
2024-08-14 08:01:46.074 INFO 21: [command] Called command system/send (Sende EMS-Telegramm) with value 0B NAN FF 00 12 01 6A 
2024-08-14 08:02:04.503 INFO 22: [command] Called command system/send (Sende EMS-Telegramm) with value 0B NAN FF 00 12 01 6A 
2024-08-14 08:02:16.789 INFO 23: [command] Called command system/send (Sende EMS-Telegramm) with value 0B NAN FF 00 12 01 6A 
2024-08-14 08:02:27.848 INFO 24: [command] Called command system/send (Sende EMS-Telegramm) with value 0B NAN FF 00 12 01 6C 
2024-08-14 08:02:35.227 INFO 25: [command] Called command system/send (Sende EMS-Telegramm) with value 0B NAN FF 00 12 01 6C 
2024-08-14 08:02:53.658 INFO 26: [command] Called command system/send (Sende EMS-Telegramm) with value 0B NAN FF 00 12 01 6C 
2024-08-14 08:03:05.945 INFO 27: [command] Called command system/send (Sende EMS-Telegramm) with value 0B NAN FF 00 12 01 6C 
2024-08-14 08:03:17.001 INFO 28: [command] Called command system/send (Sende EMS-Telegramm) with value 0B NAN FF 00 FF 01 C4 
2024-08-14 08:03:24.376 INFO 29: [command] Called command system/send (Sende EMS-Telegramm) with value 0B NAN FF 00 FF 01 C4 
2024-08-14 08:03:42.604 INFO 30: [command] Called command system/send (Sende EMS-Telegramm) with value 0B NAN FF 00 FF 01 C4 
2024-08-14 08:03:54.889 INFO 31: [command] Called command system/send (Sende EMS-Telegramm) with value 0B NAN FF 00 FF 01 C4 
2024-08-14 08:04:05.960 INFO 32: [command] Called command system/send (Sende EMS-Telegramm) with value 0B NAN FF 00 FF 03 4A 

This is something I cannot remember a few weeks ago. Can reproduce (just sitting waitung ...) at least with dev-28 and dev-30.

...system |  
version | "3.7.0-dev.30"
uptime | "000+00:18:07.750"
uptimeSec | 1087
platform | "ESP32"
arduino | "Tasmota Arduino v2.0.17"
sdk | "4.4.8.240628"
freeMem | 115
maxAlloc | 51
freeCaps | 66
usedApp | 1690
freeApp | 294
partition | "app0"
resetReason | "RTC watch dog reset: CPU+RTC / APP CPU reset by PRO CPU"
network |  
network | "WiFi"
hostname | "ems-esp"
RSSI | -29
TxPowerSetting | 78
staticIP | false
lowBandwidth | false
disableSleep | false
enableMDNS | true
enableCORS | false
APProvisionMode | "disconnected"
APSecurity | "wpa2"
APSSID | "ems-esp"
ntp |  
NTPStatus | "connected"
enabled | true
server | "192.168.23.1"
tzLabel | "Europe/Amsterdam"
mqtt |  
MQTTStatus | "disconnected"
enabled | false
clientID | "ems-esp"
keepAlive | 60
cleanSession | false
entityFormat | 0
base | "ems-esp"
discoveryPrefix | "homeassistant"
discoveryType | 0
nestedFormat | 1
haEnabled | false
mqttQos | 0
mqttRetain | false
publishTimeHeartbeat | 60
publishTimeBoiler | 30
publishTimeThermostat | 10
publishTimeSolar | 60
publishTimeMixer | 60
publishTimeWater | 10
publishTimeOther | 60
publishTimeSensor | 30
publishSingle | false
publish2command | false
sendResponse | false
syslog |  
enabled | false
sensor | {}
api |  
APICalls | 1697
APIFails | 0
bus |  
busStatus | "connected"
busProtocol | "HT3"
busTelegramsReceived | 4694
busReads | 1077
busWrites | 0
busIncompleteTelegrams | 0
busReadsFailed | 0
busWritesFailed | 0
busRxLineQuality | 100
busTxLineQuality | 100
settings |  
boardProfile | "CUSTOM"
locale | "de"
txMode | 2
emsBusID | 11
showerTimer | false
showerMinDuration | 120
showerAlert | false
phyType | 0
rxGPIO | 4
txGPIO | 2
dallasGPIO | 0
pbuttonGPIO | 0
ledGPIO | 0
hideLed | false
noTokenApi | false
readonlyMode | false
fahrenheit | false
dallasParasite | false
boolFormat | 6
boolDashboard | 1
enumFormat | 2
analogEnabled | false
telnetEnabled | true
maxWebLogBuffer | 50
webLogBuffer | 50
modbusEnabled | false
devices |  
0 |  
type | "boiler"
name | "Wärmepumpe"
deviceID | "0x08"
productID | 172
brand | ""
version | "01.16"
entities | 59
handlersReceived | "0xBF 0xC2 0xD1 0xE3 0xE4 0xE5 0xE9 0x0494 0x0495 0x048F"
handlersFetched | "0x14 0xE6 0xEA 0x048D 0x048A 0x04A2 0x0485 0x0486 0x0492 0x0488 0x0484 0x048B 0x0491 0x0499 0x049C 0x049D 0x02CC"
handlersPending | "0x10 0x11 0x15 0x1C 0x18 0x19 0x1A 0x35 0x16 0x33 0x34 0x26 0x2A 0x28 0x04AE 0x04AF 0x04A5"
handlersIgnored | "0x0240 0x0291 0x029B 0xE7 0x02E0 0x02EA 0x049F 0x04A0 0x04A3"
1 |  
type | "thermostat"
name | "RC300/RC310/Moduline 3000/1010H/CW400/Sense II/HPC410"
deviceID | "0x10"
productID | 158
brand | ""
version | "13.07"
entities | 26
handlersReceived | "0x06 0x02BA 0x02BB 0x02BC 0x02BD 0x02BE 0x02BF 0x02C0 0x031D 0x0267"
handlersFetched | "0x02A5 0x02B9 0x02AF 0x029B 0x0471 0x02CC 0x0467 0x0291 0x0292 0x0293 0x0294 0x02F5 0x023A 0x0240 0xBB 0x023E 0x0269"
handlersPending | "0xA3 0xA2 0x12 0x13 0x02A6 0x02B0 0x029C 0x0472 0x02A7 0x02B1 0x029D 0x0473 0x02A8 0x02B2 0x029E 0x0474 0x02A9 0x02B3 0x029F 0x0475 0x02AA 0x02B4 0x02A0 0x0476 0x02AB 0x02B5 0x02A1 0x0477 0x02AC 0x02B6 0x02A2 0x0478 0x02CE 0x0468 0x02D0 0x0469 0x02D2 0x046A 0x02F6 0x031B 0x031E"
handlersIgnored | "0xBF"
2 |  
type | "thermostat"
name | "RC100H Raumthermostat mit Hygrometer"
deviceID | "0x38"
productID | 200
brand | ""
version | "40.07"
entities | 3
handlersReceived | "0x042B 0x047B"
handlersFetched | "0x0273"
handlersPending | "0x0A6A"
handlersIgnored | "0xBF"
3 |  
type | "gateway"
name | "KM200/MB LAN 2"
deviceID | "0x48"
productID | 189
brand | ""
version | "04.08"
entities | 0
handlersIgnored | "0xF9"

```

@harvey637
Copy link
Author

Some more detailed log:

2024-08-14 08:21:46.240 TRACE 244: [emsesp] Me(0x0B) -R-> boiler(0x08), HPSilentMode(0x0484), length: 230 (offset 25)
2024-08-14 08:21:46.277 TRACE 245: [emsesp] boiler(0x08) -W-> Me(0x0B), HPSilentMode(0x0484), data: 01 90 00 F6 00 00 64 00 00 E1 00 00 00 00 0A 64 00 64 54 20 01 01 00 00 23 (offset 25)
2024-08-14 08:21:46.526 TRACE 246: [emsesp] Me(0x0B) -R-> boiler(0x08), HPSilentMode(0x0484), length: 205 (offset 50)
2024-08-14 08:21:46.530 TRACE 247: [emsesp] boiler(0x08) -W-> Me(0x0B), HPSilentMode(0x0484), data: 54 14 00 00 00 00 00 (offset 52)
2024-08-14 08:21:46.751 TRACE 248: [emsesp] Me(0x0B) -R-> boiler(0x08), HPSilentMode(0x0484), length: 196 (offset 59)
2024-08-14 08:21:46.755 TRACE 249: [emsesp] boiler(0x08) -W-> Me(0x0B), HPSilentMode(0x0484), data: <empty> (offset 59)
2024-08-14 08:21:46.755 TRACE 250: [emsesp] Me(0x0B) -R-> boiler(0x08), HPPumps(0x048B), length: 255
2024-08-14 08:21:46.825 DEBUG 251: [command] Called command system/response (Hole Antwort)
2024-08-14 08:21:46.825 TRACE 252: [emsesp] boiler(0x08) -W-> Me(0x0B), HPPumps(0x048B), data: 00 0A 1E 46 00 1E 01 2C 00 01 64 55 05 1F 00 38 00 00 00 1E 01 2C 00 (offset 1)
2024-08-14 08:21:46.863 DEBUG 253: [command] Called command system/response (Hole Antwort)
2024-08-14 08:21:46.904 INFO 254: [command] Called command system/send (Sende EMS-Telegramm) with value 0B NAN FF 00 FF 02 09 
2024-08-14 08:21:47.041 TRACE 255: [emsesp] gateway(0x48) -R-> thermostat(0x10), RC300WW2mode(0x02F6), length: 1 (offset 11)
2024-08-14 08:21:47.044 TRACE 256: [emsesp] thermostat(0x10) -W-> gateway(0x48), RC300WW2mode(0x02F6), data: <empty> (offset 11)
2024-08-14 08:21:47.124 DEBUG 257: [command] Called command system/response (Hole Antwort)
2024-08-14 08:21:47.147 TRACE 258: [emsesp] Me(0x0B) -B-> All(0x00), Version(0x02), data: 09
2024-08-14 08:21:47.569 TRACE 259: [emsesp] gateway(0x48) -R-> thermostat(0x10), RC300WW2mode(0x02F6), length: 1 (offset 10)
2024-08-14 08:21:47.572 TRACE 260: [emsesp] thermostat(0x10) -W-> gateway(0x48), RC300WW2mode(0x02F6), data: <empty> (offset 10)
2024-08-14 08:21:47.607 TRACE 261: [emsesp] gateway(0x48) -R-> thermostat(0x10), RC300WW2mode(0x02F6), length: 1 (offset 5)
2024-08-14 08:21:47.616 TRACE 262: [emsesp] thermostat(0x10) -W-> gateway(0x48), RC300WW2mode(0x02F6), data: <empty> (offset 5)
2024-08-14 08:21:47.726 TRACE 263: [emsesp] Me(0x0B) -R-> boiler(0x08), HPPumps(0x048B), length: 231 (offset 24)
2024-08-14 08:21:47.730 TRACE 264: [emsesp] boiler(0x08) -W-> Me(0x0B), HPPumps(0x048B), data: 00 1E 00 96 00 32 (offset 24)
2024-08-14 08:21:47.730 TRACE 265: [emsesp] Me(0x0B) -R-> boiler(0x08), HPAdditionalHeater(0x0491), length: 255
2024-08-14 08:21:47.798 TRACE 266: [emsesp] boiler(0x08) -W-> Me(0x0B), HPAdditionalHeater(0x0491), data: 00 00 00 00 00 0A 64 00 00 04 01 2C 00 0A 00 01 00 1E 00 00 1E 0A
2024-08-14 08:21:47.798 TRACE 267: [emsesp] Me(0x0B) -R-> boiler(0x08), HPDhwSettings(0x0499), length: 255
2024-08-14 08:21:47.825 TRACE 268: [emsesp] boiler(0x08) -W-> Me(0x0B), HPDhwSettings(0x0499), data: 3C 3F 3F 3B 00 37
2024-08-14 08:21:47.825 TRACE 269: [emsesp] Me(0x0B) -R-> boiler(0x08), HPSettings2(0x049C), length: 255
2024-08-14 08:21:47.869 TRACE 270: [emsesp] boiler(0x08) -W-> Me(0x0B), HPSettings2(0x049C), data: 00 00 00 00 00
2024-08-14 08:21:47.869 TRACE 271: [emsesp] Me(0x0B) -R-> boiler(0x08), HPSettings3(0x049D), length: 255
2024-08-14 08:21:47.911 DEBUG 272: [command] Called command system/response (Hole Antwort)
2024-08-14 08:21:47.911 TRACE 273: [emsesp] boiler(0x08) -W-> Me(0x0B), HPSettings3(0x049D), data: 00 00 00 00 00 00 00 00 00 00 00 00
2024-08-14 08:21:47.911 TRACE 274: [emsesp] Me(0x0B) -R-> boiler(0x08), HPPressure(0x02CC), length: 255
2024-08-14 08:21:47.961 DEBUG 275: [command] Called command system/response (Hole Antwort)
2024-08-14 08:21:47.961 TRACE 276: [emsesp] boiler(0x08) -W-> Me(0x0B), HPPressure(0x02CC), data: 00 (offset 3)
2024-08-14 08:21:48.121 TRACE 277: [emsesp] gateway(0x48) -R-> thermostat(0x10), RC300WW2mode(0x02F6), length: 1 (offset 7)
2024-08-14 08:21:48.124 TRACE 278: [emsesp] thermostat(0x10) -W-> gateway(0x48), RC300WW2mode(0x02F6), data: <empty> (offset 7)
2024-08-14 08:21:48.151 DEBUG 279: [command] Called command system/response (Hole Antwort)
2024-08-14 08:21:48.289 TRACE 280: [emsesp] Me(0x0B) -R-> boiler(0x08), HPPressure(0x02CC), length: 251 (offset 4)
2024-08-14 08:21:48.295 TRACE 281: [emsesp] boiler(0x08) -W-> Me(0x0B), HPPressure(0x02CC), data: <empty> (offset 4)
2024-08-14 08:21:48.295 TRACE 282: [emsesp] Me(0x0B) -R-> thermostat(0x10), RC300Monitor(0x02A5), length: 255
2024-08-14 08:21:48.394 TRACE 283: [emsesp] thermostat(0x10) -W-> Me(0x0B), RC300Monitor(0x02A5), data: 00 ED 61 28 00 00 28 2A 05 A0 03 03 03 05 A0 05 A0 00 00 11 02 03 09 42 00
2024-08-14 08:21:48.553 TRACE 284: [emsesp] gateway(0x48) -R-> thermostat(0x10), RC300WW2mode(0x02F6), length: 1 (offset 6)
2024-08-14 08:21:48.556 TRACE 285: [emsesp] thermostat(0x10) -W-> gateway(0x48), RC300WW2mode(0x02F6), data: <empty> (offset 6)
2024-08-14 08:21:48.639 TRACE 286: [emsesp] Me(0x0B) -R-> thermostat(0x10), RC300Monitor(0x02A5), length: 230 (offset 25)
2024-08-14 08:21:48.685 TRACE 287: [emsesp] thermostat(0x10) -W-> Me(0x0B), RC300Monitor(0x02A5), data: 06 08 00 00 00 00 11 00 30 00 3C 01 3C (offset 25)
2024-08-14 08:21:48.685 TRACE 288: [emsesp] Me(0x0B) -R-> thermostat(0x10), RC300Set(0x02B9), length: 255
2024-08-14 08:21:48.766 TRACE 289: [emsesp] thermostat(0x10) -W-> Me(0x0B), RC300Set(0x02B9), data: FF 2E 28 26 1C 01 00 FF FF 05 22 01 E1 20 01 0F 05 33 00 01
2024-08-14 08:21:48.766 TRACE 290: [emsesp] Me(0x0B) -R-> thermostat(0x10), RC300Summer(0x02AF), length: 255
2024-08-14 08:21:48.820 TRACE 291: [emsesp] thermostat(0x10) -W-> Me(0x0B), RC300Summer(0x02AF), data: 00 28 00 00 3C 2D 00 00 19 1E 00
2024-08-14 08:21:48.820 TRACE 292: [emsesp] Me(0x0B) -R-> thermostat(0x10), RC300Curves(0x029B), length: 255
2024-08-14 08:21:48.880 TRACE 293: [emsesp] thermostat(0x10) -W-> Me(0x0B), RC300Curves(0x029B), data: 01 03 00 00 00 02 05 30 4B
2024-08-14 08:21:48.880 TRACE 294: [emsesp] Me(0x0B) -R-> thermostat(0x10), RC300Summer2(0x0471), length: 255
2024-08-14 08:21:48.937 TRACE 295: [emsesp] thermostat(0x10) -W-> Me(0x0B), RC300Summer2(0x0471), data: 01 0B 04 01 01 21 01 02
2024-08-14 08:21:48.937 TRACE 296: [emsesp] Me(0x0B) -R-> thermostat(0x10), RC300Set2(0x02CC), length: 255
2024-08-14 08:21:48.962 DEBUG 297: [command] Called command system/response (Hole Antwort)
2024-08-14 08:21:48.962 TRACE 298: [emsesp] thermostat(0x10) -W-> Me(0x0B), RC300Set2(0x02CC), data: 00 (offset 3)
2024-08-14 08:21:49.023 DEBUG 299: [command] Called command system/response (Hole Antwort)
2024-08-14 08:21:49.169 TRACE 300: [emsesp] gateway(0x48) -R-> thermostat(0x10), RC300WW2mode(0x02F6), length: 1 (offset 3)
2024-08-14 08:21:49.172 TRACE 301: [emsesp] thermostat(0x10) -W-> gateway(0x48), RC300WW2mode(0x02F6), data: <empty> (offset 3)
2024-08-14 08:21:49.193 DEBUG 302: [command] Called command system/response (Hole Antwort)
2024-08-14 08:21:49.314 TRACE 303: [emsesp] Me(0x0B) -R-> thermostat(0x10), RC300Set2(0x02CC), length: 251 (offset 4)
2024-08-14 08:21:49.317 TRACE 304: [emsesp] thermostat(0x10) -W-> Me(0x0B), RC300Set2(0x02CC), data: <empty> (offset 4)
2024-08-14 08:21:49.317 TRACE 305: [emsesp] Me(0x0B) -R-> thermostat(0x10), HPSet(0x0467), length: 255
2024-08-14 08:21:49.379 TRACE 306: [emsesp] thermostat(0x10) -W-> Me(0x0B), HPSet(0x0467), data: 12 11 00 01 02
2024-08-14 08:21:49.379 TRACE 307: [emsesp] Me(0x0B) -R-> thermostat(0x10), HPMode(0x0291), length: 255
2024-08-14 08:21:49.428 TRACE 308: [emsesp] thermostat(0x10) -W-> Me(0x0B), HPMode(0x0291), data: 01 00 00 03 FF 02
2024-08-14 08:21:49.428 TRACE 309: [emsesp] Me(0x0B) -R-> thermostat(0x10), HPMode(0x0292), length: 255
2024-08-14 08:21:49.478 TRACE 310: [emsesp] thermostat(0x10) -W-> Me(0x0B), HPMode(0x0292), data: 00 00 00 00 FF 00
2024-08-14 08:21:49.478 TRACE 311: [emsesp] Me(0x0B) -R-> thermostat(0x10), HPMode(0x0293), length: 255
2024-08-14 08:21:49.527 TRACE 312: [emsesp] thermostat(0x10) -W-> Me(0x0B), HPMode(0x0293), data: 00 00 00 00 FF 00
2024-08-14 08:21:49.527 TRACE 313: [emsesp] Me(0x0B) -R-> thermostat(0x10), HPMode(0x0294), length: 255
2024-08-14 08:21:49.576 TRACE 314: [emsesp] thermostat(0x10) -W-> Me(0x0B), HPMode(0x0294), data: 00 00 00 00 FF 00
2024-08-14 08:21:49.576 TRACE 315: [emsesp] Me(0x0B) -R-> thermostat(0x10), RC300WWmode(0x02F5), length: 255
2024-08-14 08:21:49.675 TRACE 316: [emsesp] thermostat(0x10) -W-> Me(0x0B), RC300WWmode(0x02F5), data: 01 00 00 03 00 00 08 01 00 08 04 00 00 00 00 00 00 00 00 00
2024-08-14 08:21:49.675 TRACE 317: [emsesp] Me(0x0B) -R-> thermostat(0x10), RC300OutdoorTemp(0x023A), length: 255
2024-08-14 08:21:49.684 TRACE 318: [emsesp] thermostat(0x10) -W-> Me(0x0B), RC300OutdoorTemp(0x023A), data: 00 CB
2024-08-14 08:21:49.684 TRACE 319: [emsesp] Me(0x0B) -R-> thermostat(0x10), RC300Settings(0x0240), length: 255
2024-08-14 08:21:49.766 TRACE 320: [emsesp] thermostat(0x10) -W-> Me(0x0B), RC300Settings(0x0240), data: 32 00 03 00 00 00 00 00 FF 02 F6 06 FF 00 00
2024-08-14 08:21:49.766 TRACE 321: [emsesp] Me(0x0B) -R-> thermostat(0x10), HybridSettings(0xBB), length: 255
2024-08-14 08:21:49.785 TRACE 322: [emsesp] thermostat(0x10) -W-> Me(0x0B), HybridSettings(0xBB), data: 21 (offset 14)
2024-08-14 08:21:49.902 TRACE 323: [emsesp] boiler(0x08) -R-> thermostat(0x10), RC300Settings(0x0240), length: 1 (offset 12)
2024-08-14 08:21:49.918 TRACE 324: [emsesp] thermostat(0x10) -W-> boiler(0x08), RC300Settings(0x0240), data: FF (offset 12)
2024-08-14 08:21:49.964 TRACE 325: [emsesp] boiler(0x08) -R-> thermostat(0x10), HPMode(0x0291), length: 1
2024-08-14 08:21:49.984 TRACE 326: [emsesp] thermostat(0x10) -W-> boiler(0x08), HPMode(0x0291), data: 01
2024-08-14 08:21:50.019 DEBUG 327: [command] Called command system/response (Hole Antwort)
2024-08-14 08:21:50.027 TRACE 328: [emsesp] boiler(0x08) -R-> thermostat(0x10), RC300Curves(0x029B), length: 1 (offset 1)
2024-08-14 08:21:50.045 TRACE 329: [emsesp] thermostat(0x10) -W-> boiler(0x08), RC300Curves(0x029B), data: 03 (offset 1)
2024-08-14 08:21:50.054 DEBUG 330: [command] Called command system/response (Hole Antwort)
2024-08-14 08:21:50.088 TRACE 331: [emsesp] boiler(0x08) -R-> thermostat(0x10), RC300Curves(0x029B), length: 2 (offset 7)
2024-08-14 08:21:50.111 TRACE 332: [emsesp] thermostat(0x10) -W-> boiler(0x08), RC300Curves(0x029B), data: 30 4B (offset 7)
2024-08-14 08:21:50.242 DEBUG 333: [command] Called command system/response (Hole Antwort)
2024-08-14 08:21:50.269 INFO 334: [command] Called command system/send (Sende EMS-Telegramm) with value 0B NAN FF 00 FF 01 C4 
2024-08-14 08:21:50.285 TRACE 335: [emsesp] Me(0x0B) -R-> thermostat(0x10), HybridSettings(0xBB), length: 240 (offset 15)
2024-08-14 08:21:50.285 TRACE 336: [emsesp] thermostat(0x10) -W-> Me(0x0B), HybridSettings(0xBB), data: <empty> (offset 15)
2024-08-14 08:21:50.285 TRACE 337: [emsesp] Me(0x0B) -R-> thermostat(0x10), HybridSettings(0xBB), length: 240 (offset 15)
2024-08-14 08:21:50.317 TRACE 338: [emsesp] thermostat(0x10) -W-> Me(0x0B), HybridSettings(0xBB), data: <empty> (offset 15)
2024-08-14 08:21:50.317 TRACE 339: [emsesp] Me(0x0B) -R-> thermostat(0x10), PVSettings(0x023E), length: 255
2024-08-14 08:21:50.366 TRACE 340: [emsesp] thermostat(0x10) -W-> Me(0x0B), PVSettings(0x023E), data: 01 02 00 00 00 00
2024-08-14 08:21:50.366 TRACE 341: [emsesp] Me(0x0B) -R-> thermostat(0x10), RC300Holiday1(0x0269), length: 255
2024-08-14 08:21:50.451 TRACE 342: [emsesp] thermostat(0x10) -W-> Me(0x0B), RC300Holiday1(0x0269), data: 11 01 01 11 01 01 02 0F 02 FF 00 00 00 00 00 00 00 FF
2024-08-14 08:21:50.451 TRACE 343: [emsesp] Me(0x0B) -R-> thermostat(0x38), RemoteCorrection(0x0273), length: 255
2024-08-14 08:21:50.474 TRACE 344: [emsesp] thermostat(0x38) -W-> Me(0x0B), RemoteCorrection(0x0273), data: 00 00
2024-08-14 08:21:51.109 DEBUG 345: [command] Called command system/response (Hole Antwort)
2024-08-14 08:21:51.144 DEBUG 346: [command] Called command system/response (Hole Antwort)
2024-08-14 08:21:51.512 DEBUG 347: [command] Called command system/response (Hole Antwort)
2024-08-14 08:21:52.342 DEBUG 348: [command] Called command system/response (Hole Antwort)
2024-08-14 08:21:52.377 DEBUG 349: [command] Called command system/response (Hole Antwort)
2024-08-14 08:21:52.743 DEBUG 350: [command] Called command system/response (Hole Antwort)
2024-08-14 08:21:53.090 TRACE 351: [emsesp] boiler(0x08) -B-> All(0x00), UBAMonitorFastPlus(0xE4), data: 10 20 30 48 00 CB 00 00 CD 00 00 00 00 02 B2 00 00 00 D0 00 00 00 00 00 CF 00 CD

@proddy
Copy link
Contributor

proddy commented Aug 14, 2024

Max Alloc looks very low (51). Also any idea why all those calls to the system/response command?

@harvey637
Copy link
Author

harvey637 commented Aug 14, 2024

Hi Proddy,
great to hear from you!

I have no idea of the origin of the system/response commands. Can you easy read what this command is?

With the iobroker/ems-esp interface I have 300 secs for actualisation, no energy statiscics, no km200, no heatdemand.
From raspberrymatic I do a single call to api/boiler and api/thermostat every 5 mins ...

thank you!

@MichaelDvP
Copy link
Contributor

@proddy This is a ESP32 4M. I think i set the scheduler to sync for versions without PSRAM, this gives ~5-8kB free ram and on these chips we need every kB. For psram versions we can leave scheduler async and also set mqtt to async.

@tp1de Can you look at this, seems the system/send system/response is from ioBroker-adapter. I do not see this on RC35, maybe you automatic activate it for RC300? Maybe for the timer programs.

@MichaelDvP
Copy link
Contributor

@harvey637 Have you enabled in ioBroker adapter "enable search for additional EMS+ entities (switchTimes & holidayModes) - write access needed"?

@harvey637
Copy link
Author

harvey637 commented Aug 14, 2024

Hi,
when speaking of timer programs ... is this the reading of the prog_1 and prog_2 from the thermostat?
I remember, that at some time in history i checked this and found an array with my switching timestamps.
But now I dont see this anymore .... gone? not filled by this NAN request?

@harvey637
Copy link
Author

harvey637 commented Aug 14, 2024

YES .... enabled search for additional ...

@tp1de
Copy link
Contributor

tp1de commented Aug 14, 2024

@tp1de Can you look at this, seems the system/send system/response is from ioBroker-adapter. I do not see this on RC35, maybe you automatic activate it for RC300? Maybe for the timer programs.

@harvey637 have you selected the search for additional EMS+ entities within ioBroker adapter?
If yes, please deactivate since you have 2 thermostats

@harvey637
Copy link
Author

harvey637 commented Aug 14, 2024

Hmmmmmm,
I have physically one thermostat (device), the RC100H in my living room.
The other "thermostat" is/looks like an rc310 which in my opinion is the integrated "console" in my bosch 7000 ... heatpump.
Flapping down the cover, reveals a small LCD, where I see/modify setting of my heatpump, actually this whole devide is aclled AMWB (looks like a big refrigirator) as I remember, not quite shure

@harvey637
Copy link
Author

harvey637 commented Aug 14, 2024

On the RC100H I have my switching programs like prog_1 and prog2, which I filled with the bosch easycon tools. I switch them by for my homematic centered holiday, so homematic has the variable with my holiday calender and switches to prog_2 for holiday and back for normal working days.

@tp1de
Copy link
Contributor

tp1de commented Aug 14, 2024

I am not happy with the actual solution of sending raw telegrams from ioBroker adapter and trying to read response for holidayModes and switchPrograms.
We discuss other solutions in #1594

@harvey637
Copy link
Author

ok, I can switch OFF the additional search (for now), but is WAS working!

@harvey637
Copy link
Author

ok, the log entries like

2024-08-14 10:40:22.093    INFO 2014:   [command]    Called command system/send (Sende EMS-Telegramm) with value 0B NAN FF 00 FF 01 C4
2024-08-14 10:40:22.120    INFO 2015:   [command]    Called command system/send (Sende EMS-Telegramm) with value 0B NAN FF 00 FF 02 09 

are gone.

@tp1de
Copy link
Contributor

tp1de commented Aug 14, 2024

You have an gateway as well. Is km200 search not working within ioBroker?

@harvey637
Copy link
Author

I started long time ago with no km200 structure. So now I am afraid of loosing my historical data, which is sometimes quite interesting eg. in relation to the transition from heating to cooling.
So the gateway never had any entities, so i ignored it. I thougt it as an internal bosch gateway pushing the data into their easycon cloud.

@tp1de
Copy link
Contributor

tp1de commented Aug 14, 2024

You can try to read by a 2nd instance and just activate km200 there (no ems-esp).
It depends, what kind of gateway is installed. You need to set a private password with the MyDevice App first.
If this is working you will get next to holidayModes and switchPrograms recordings as well (12 months energy statistics)

@harvey637
Copy link
Author

I will give it a try, thank you

@harvey637
Copy link
Author

harvey637 commented Aug 14, 2024

Hmmmmm, i did not use the Bosch HomeCom for some years (no need for it), now it has no connection to my devices. I have to solve this first, then I will check out the second instance.

refreshing the device does not work "Es ist ein Fehler aufgetreten" after scanning the bosch QR-Code :-(

thank you
Harvey

@tp1de
Copy link
Contributor

tp1de commented Aug 14, 2024

You do not need HomeCom which is cloud based. Bosch has changed the login recently ...
You need the MyDevice App which connects locally (LAN) and for this you need to set a private password.
This pw together with the gateway pw is used to decrypt api messages.

@harvey637
Copy link
Author

okidoki, i have connection and second instance emsesp.1 with - at first look - same same info as with ems-esp.0.

Does this also mean, that i do not need a tools like bkees ems-gateway (ok, i have it, so i wont thow it away :-) ?

I see my times for prog_1 (called A) and prog_2 (called B), perfect.

thank you, this helped a lot!!!!!!!

I will try to switch the instances, so my historical data will not be lost .... this is my job. After that, i can completly remove the ems-esp connection?!? ok, trying to do so.

ciao
Harvey
(this might be closed, as everything, especially the source of this repeated NAN system/call is identified.)

@MichaelDvP
Copy link
Contributor

Just a last question before you disconnect the ems-esp: Are the WDT resets still happen after disable the raw reads from adapter?

@tp1de
Copy link
Contributor

tp1de commented Aug 14, 2024

@harvey637 do not disconnect EMS-ESP since the gateway supports much more entities compared to original gateway and can be polled much faster (up to 15 secs). But do not use the extended search.

Big advantage of original gateway are recordings, switchPrograms (until in ems-esp) and holidayPrograms.
For me the combination of both is the best solution.

@harvey637
Copy link
Author

no watchdog resets in the last half hour ..... everything running.
I already switched instance.0 to km200, all my historical data is still there - wow!
Some minor adjustion needed still (eg hppower is (null) and not 0 :-)

@tp1de
Copy link
Contributor

tp1de commented Aug 14, 2024

I already switched instance.0 to km200, all my historical data is still there - wow!

If you do not enable the parameter to delete states (or do it manually) then you might get double entries.
The delete states parameter will not delete states with history / db entries but the object names are now changed.

@harvey637
Copy link
Author

Thank you for the answer, i guess you you wanted to write: "do not disconnect EMS-ESP since the ems-esp-gateway supports much more entities compared to original build-in-gateway"
I will keep that in mind, but for now I am happy with 5 minutes intervals, my heating is floor heating, so 15 secs poll will only bloat data, may be not, as I only save different values, but I will see.

@harvey637
Copy link
Author

thank you for the warning, but i had the "delete" enabled, so no double entries.
With no heating in summer there will be little change in values, only outdoortemp and curtemp and like this.

If I run into (visable) trouble you will be the first to know! (by creating issue)
It is a pleasure to talk to you, gives me more insight and good ideas, what to try.
ciao
Harvey

@tp1de
Copy link
Contributor

tp1de commented Aug 14, 2024

I added an issue within the ioBroker adapter repo.
@harvey637 have a look in recordings (see pdf docu) - this might be interesting to see energy consumption

@harvey637
Copy link
Author

yep, just scrolling through the iobroker objects ..... nice infos.

@proddy proddy closed this as completed Sep 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants