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
21.71k stars 4.72k forks source link

Saved to flash at FB, Count 9310, Bytes 409 after button pressed single #19989

Closed smartboart closed 7 months ago

smartboart commented 7 months ago

PROBLEM DESCRIPTION

Sometimes my Node MCU is not accessilble / working anymore till i make a hard reset. Thats why i implemented a sys log web server more debug to check whats going on. Saw following entry when i use single press button.

NodeMCU-Heizungsraum ESP-CFG: Saved to flash at F7, Count 9306, Bytes 4096

see complete log below.

REQUESTED INFORMATION

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

{"Rule2":{"State":"ON","Once":"OFF","StopOnError":"OFF","Length":37,"Free":474,"Rules":"ON button1#state=10 DO power1 2 ENDON"}}

- [x ] Provide the output of this command: `Status 0`:
```lua
  STATUS 0 output here:
 {"StatusSTS":{"Time":"2023-11-12T16:22:06","Uptime":"0T01:04:02","UptimeSec":3842,"Heap":19,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"POWER1":"OFF","POWER2":"OFF","POWER3":"OFF","POWER4":"OFF","POWER5":"OFF","POWER6":"OFF","Wifi":{"AP":1,"SSId":"michaswlan","BSSId":"DC:15:C8:2B:53:0F","Channel":1,"Mode":"11n","RSSI":64,"Signal":-68,"LinkCount":1,"Downtime":"0T00:00:03"}}}


### TO REPRODUCE
_Steps to reproduce the behavior:_
{"Button1":{"Action":"SINGLE"}}

### EXPECTED BEHAVIOUR
_A clear and concise description of what you expected to happen._
Everything is working when {"Button1":{"Action":"SINGLE"}} will be carried out, but another thing happen too..
NodeMCU-Heizungsraum ESP-CFG: Saved to flash at F7, Count 9306, Bytes 4096

### SCREENSHOTS
_If applicable, add screenshots to help explain your problem._

![grafik](https://github.com/arendst/Tasmota/assets/38385805/c1ae55dc-1872-446c-8d5c-4df6266ef63d)

### ADDITIONAL CONTEXT
_Add any other context about the problem here._

**(Please, remember to close the issue when the problem has been addressed)**
sfromis commented 7 months ago

The message you mention is in no way about a "problem"

Nov 12 15:53:05 NodeMCU-Heizungsraum ESP-BTN: Button1 multi-press 1
Nov 12 15:53:05 NodeMCU-Heizungsraum ESP-RUL: BUTTON1#STATE=10 performs "power1 2"
Nov 12 15:53:05 NodeMCU-Heizungsraum ESP-SRC: Rule
Nov 12 15:53:05 NodeMCU-Heizungsraum ESP-CMD: Grp 0, Cmd 'POWER', Idx 1, Len 1, Pld 2, Data '2'
Nov 12 15:53:05 NodeMCU-Heizungsraum ESP-MQT: stat/sonoff/RESULT = {"POWER1":"OFF"}
Nov 12 15:53:05 NodeMCU-Heizungsraum ESP-MQT: stat/sonoff/POWER1 = OFF (retained)
Nov 12 15:53:05 NodeMCU-Heizungsraum ESP-MQT: stat/sonoff/RESULT = {"Button1":{"Action":"SINGLE"}}
Nov 12 15:53:06 NodeMCU-Heizungsraum ESP-CFG: Saved to flash at F7, Count 9306, Bytes 4096

Your analog Button input is registering as "pushed", and therefore Tasmota triggers your rule to toggle Power2. And by default (unless you disable this), a power output (like a relay) status change is saved in flash, to enable it being available after restart.

This is unrelated to the device not being accessible, unless you have some borderline electrical situation starving the ESP8266 of power. And having relays are drawing a fair amount of power. Maybe more than is available without voltage drops.