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
Device: NOUS A1T Smart Socket with power monitoring
Original Verion: 13.0.0
Original features enabled: MQTT, Syslog
Chipset: 8266, 1M Flash
Upgrade path: 13.0.0-sensors -> 14.1.0 minimal -> 14.1.0 sensors (hopefully)
I have a lot of these smart sockets and the majority updated correctly apart from two; one is bricked and requires flashing via serial port and the other refuses to upgrade beyond minimal.
I've tried the upgrade via the web interface and from the console:
- [ ] If using rules, provide the output of this command: `Backlog Rule1; Rule2; Rule3`:
```lua
Rules output here:
13:26:39.117 MQT: pdu/stat/tasmota_154878/RESULT = {"Command":"Unknown"}
[ ] Provide the output of this command: Status 0:
STATUS 0 output here:
13:26:39.117 MQT: pdu/stat/tasmota_154878/RESULT = {"Command":"Unknown"}
- [ ] Set `weblog` to 4 and then, when you experience your issue, provide the output of the Console log:
```lua
Console output here:
13:28:21.976 MQT: pdu/stat/tasmota_154878/RESULT = {"WebLog":4}
TO REPRODUCE
Steps to reproduce the behavior:
EXPECTED BEHAVIOUR
A clear and concise description of what you expected to happen.
SCREENSHOTS
If applicable, add screenshots to help explain your problem.
ADDITIONAL CONTEXT
Add any other context about the problem here.
(Please, remember to close the issue when the problem has been addressed)
PROBLEM DESCRIPTION
Device: NOUS A1T Smart Socket with power monitoring Original Verion: 13.0.0 Original features enabled: MQTT, Syslog Chipset: 8266, 1M Flash Upgrade path: 13.0.0-sensors -> 14.1.0 minimal -> 14.1.0 sensors (hopefully)
I have a lot of these smart sockets and the majority updated correctly apart from two; one is bricked and requires flashing via serial port and the other refuses to upgrade beyond minimal.
I've tried the upgrade via the web interface and from the console:
OtaUrl http://ota.tasmota.com/tasmota/release/tasmota-sensors.bin.gz
Upgrade 1
It says it is upgrading and will reset but after reset it is still minimal. Upgrading via file upload does not work because of inadequate space.
Jun 7 11:50:45 192.168.200.200 tasmota-XXXXXX ESP-MQT: pdu/stat/tasmotaXXXXXX/RESULT = {"OtaUrl":"http://ota.tasmota.com/tasmota/release/tasmota-minimal.bin.gz"}
Jun 7 11:51:18 192.168.200.200 tasmota-XXXXXX ESP-MQT: pdu/tele/tasmotaXXXXXX/STATE = {"Time":"2024-06-07T10:51:18","Uptime":"0T00:20:10","UptimeSec":1210,"Vcc":3.667,"Heap":33,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"POWER":"ON","Wifi":{"AP":1,"SSId":"XXXXXXX","BSSId":"AA:BB:CC:DD:EE:FF","Channel":6,"Mode":"11n","RSSI":68,"Signal":-66,"LinkCount":1,"Downtime":"0T00:00:04"}}
Jun 7 11:51:24 192.168.200.200 tasmota-XXXXXX ESP-CMD: otaurl http://ota.tasmota.com/tasmota/release/tasmota-sensors.bin.gz
Jun 7 11:51:24 192.168.200.200 tasmota-XXXXXX ESP-MQT: pdu/stat/tasmotaXXXXXX/RESULT = {"OtaUrl":"http://ota.tasmota.com/tasmota/release/tasmota-sensors.bin.gz"}
Jun 7 11:51:39 192.168.200.200 tasmota-XXXXXX ESP-CMD: upgrade 1
Jun 7 11:51:39 192.168.200.200 tasmota-XXXXXX ESP-MQT: pdu/stat/tasmotaXXXXXX/RESULT = {"Upgrade":"Version 14.1.0 from http://ota.tasmota.com/tasmota/release/tasmota-sensors.bin.gz"}
Jun 7 11:52:34 192.168.200.200 tasmota-XXXXXX ESP-MQT: Attempting connection...
Jun 7 11:52:34 192.168.200.200 tasmota-XXXXXX ESP-MQT: Connected
Jun 7 11:52:34 192.168.200.200 tasmota-XXXXXX ESP-MQT: pdu/tele/tasmotaXXXXXX/LWT = Online (retained)
Jun 7 11:52:34 192.168.200.200 tasmota-XXXXXX ESP-MQT: pdu/cmnd/tasmotaXXXXXX/POWER =
Jun 7 11:52:34 192.168.200.200 tasmota-XXXXXX ESP-MQT: pdu/stat/tasmotaXXXXXX/RESULT = {"Command":"Unknown"}
Jun 7 11:55:14 192.168.200.200 tasmota-XXXXXX ESP-CFG: Loaded from flash at FB, Count 192
Jun 7 11:55:14 192.168.200.200 tasmota-XXXXXX ESP-Project tasmota - sonoff11 Version 14.1.0(release-minimal)-2_7_6(2024-06-03T11:53:06)
Jun 7 11:55:14 192.168.200.200 tasmota-XXXXXX ESP-WARNING This version does not support persistent settings
Jun 7 11:55:14 192.168.200.200 tasmota-XXXXXX ESP-WIF: Connecting to AP1 YYYYYYY Channel 6 BSSId AA:BB:CC:DD:EE:FF in mode 11n as tasmota-XXXXXX...
Jun 7 11:55:14 192.168.200.200 tasmota-XXXXXX ESP-WIF: Connected
Jun 7 11:55:14 192.168.200.200 tasmota-XXXXXX ESP-HTP: Web server active on tasmota-XXXXXX with IP address 192.168.200.200
Jun 7 11:55:15 192.168.200.200 tasmota-XXXXXX ESP-MQT: Attempting connection...
Jun 7 11:55:15 192.168.200.200 tasmota-XXXXXX ESP-MQT: Connected
Jun 7 11:55:15 192.168.200.200 tasmota-XXXXXX ESP-MQT: pdu/tele/tasmotaXXXXXX/LWT = Online (retained)
Jun 7 11:55:15 192.168.200.200 tasmota-XXXXXX ESP-MQT: pdu/cmnd/tasmotaXXXXXX/POWER =
Jun 7 11:55:15 192.168.200.200 tasmota-XXXXXX ESP-MQT: pdu/tele/tasmotaXXXXXX/INFO1 = {"Info1":{"Module":"NOUS A1T","Version":"14.1.0(release-minimal)","FallbackTopic":"cmnd/DVESXXXXXX_fb/","GroupTopic":"pdu/cmnd/tasmotas/"}}
What is curious is that it has retained the syslog and MQTT settings, I'm still getting these messages evn though there isn't a config option for it.
Does anyone have any advice before I dismantle the socket and flash them via the serial port?
Thanks,
Simon
REQUESTED INFORMATION
Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!
Backlog Template; Module; GPIO 255
:Status 0
:TO REPRODUCE
Steps to reproduce the behavior:
EXPECTED BEHAVIOUR
A clear and concise description of what you expected to happen.
SCREENSHOTS
If applicable, add screenshots to help explain your problem.
ADDITIONAL CONTEXT
Add any other context about the problem here.
(Please, remember to close the issue when the problem has been addressed)