How to check a "config reset because of boot loop" in TuyaMCU #17625
Unanswered
ortegafernando
asked this question in
Q&A
Replies: 7 comments 116 replies
-
|
Sorry, anyone has any key? Thanks |
Beta Was this translation helpful? Give feedback.
10 replies
-
I will try, thanks. |
Beta Was this translation helpful? Give feedback.
-
|
HI, I got this log from syslog. First I update to last OTA version, then I select TUYAMCU(54) module and then... I get the reset of the module's type to SonOff Basic. Could you see in this log any reason for that? Thanks. (NOTE: There is simply rule that I used as I explained here: #17562 I think it doesn't affect, I only forget to clear it before selecting TuyaMCU(54) module. (it is a basic serialsend5 after 20 seconds) If you help me by guiding me, I could try to find why this S09 clock/temp/humidity device is not accepting TuyaMCU(54) as module. Thanks Log with syslog 4: |
Beta Was this translation helpful? Give feedback.
-
|
Any help about this "Some settings have been reset (6)" ? Thanks |
Beta Was this translation helpful? Give feedback.
-
|
FRC : Fast Reboot Check If it was a software crash, the RestartReason in "INFO3" would state some exception code This may be key: Tasmota receive a command (36) that he doesn't know Command 36 (0x1C) seems to be Get Wifi Signal Strength which is not currently implemented I will check if I can do something |
Beta Was this translation helpful? Give feedback.
-
|
Hi @barbudor thanks a lot. I am using ready made binary. In the log you can see that I have updated via web gui OTA (http://ota.tasmota.com/tasmota/release/tasmota.bin.gz) Sorry, I haven't got any oscilloscope or logic analyser. If it is a "new command", this must be happened before to more people, don't it? May be not with an S09 clock/temp/humidity device, may be with other Tuya devices. During my tests with Generic Module and direct RXTX communication I wrote down this information: May be this helps. I want to investigate about boot loop to help future tuya devices. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, I have seen this code: xdrv_08_serial_bridge.ino That is called in AddLogData in support.ino So I supposed that tasmota is prepared to log to "hardware serial" and to "software serial bridge" if it is defined. And also, in tasmota.ino I can see: and Here tasmota defines the Serial output for its logs. I am not an expert, but any of you ... could you tell me if any of these options will work?:
Could anyone who knows well Tasmota's code internals guide me? Thanks. Possible option 4 (replace Serial with Serial1 for TasConsole): and |
Beta Was this translation helpful? Give feedback.
23 replies
-
|
Hi, I left it during night without touching. It has reset every 2 and a half minutes. I have a big syslog file with more than 70 reboots. This is what is reapeating: Could be:
Today I will try to do more test, but it will be at afternoon/night |
Beta Was this translation helpful? Give feedback.
-
Likely to be point 2 : probleme on my side |
Beta Was this translation helpful? Give feedback.
-
No problem, i will wait your next version and check it again, thanks. |
Beta Was this translation helpful? Give feedback.
-
|
Sorry I wanted to finalize the final version to solve the GPIO problem Now, for your 2nd question : You want to have both:
There is no standard build that have both features together so you need to compile your own, either with online tools like TasmoCompiler or with VSCode (or GitPod which is a VSCode in the cloud) So with LED on GPIO4 and Button on GPIO13 like you said above, this is what it should finally be:
Note that you don't need to wait for my PR to build a binary that fits as if you apply the complete above template, LED1 and KEY1 will be defined by the template and the current code will ignore the message from the TuyaMUC that was creating the boot loop. Keep me posted |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, I will work on it this night. (we must to change the screenshoot, as button1 is on gpio10 in it, when phisically is gpio13) |
Beta Was this translation helpful? Give feedback.
-
|
Hi sorry for the delay. I have compiled with gitpod to check your PR. Reset 6, configure syslog 4 and syslog server IP and only configure TUYAMCU (54) (I have not configured any pins) and ..... reboots appears again!. (sorry) (led and button pis are NOT soldered to ESP12F, but also not configured) This is the output in syslog 4. Main lineas: Whole syslog: |
Beta Was this translation helpful? Give feedback.
5 replies
-
|
I don't see any reboot and "FRC : Some settings have been cleared" That are not followed by any reboot I see that as a success |
Beta Was this translation helpful? Give feedback.
-
|
Sorry, it is tru that there is no "settings cleared", but I see reboots every two and a half minutes. This is why I have post some "info3" messages: RestartReason: PowerOn. Always after this: Do you find any reason? Cmnd 43? RX unknown command makes ESP8266 to reboot? |
Beta Was this translation helpful? Give feedback.
-
|
Ah |
Beta Was this translation helpful? Give feedback.
-
Ok, I will wait and test again your PR |
Beta Was this translation helpful? Give feedback.
-
|
@benjaminnestler has been faster than me with : #17745 |
Beta Was this translation helpful? Give feedback.
-
|
Hi, I have just compiled the developement branch after #17745 was merged. I have still got some reboots. You can see here these ones (one every X minutes): There is another strange thing as I have more boot count than INFO MQTT messages (may be syslog server problem? I don't know): Full log |
Beta Was this translation helpful? Give feedback.
43 replies
-
|
Syslog works as soon as wifi is connected and logs includes a buffer so in most case you should get logs from the early boot However if the esp-reset-by-MCU is in place you may loose a few lines that are still in the buffer and not sent |
Beta Was this translation helpful? Give feedback.
-
Yes I agree with @barbudor. I don't think that you lose some log entries. Maybe the TuyaMCU is in an undefined communication state --> therefore the reset of the device |
Beta Was this translation helpful? Give feedback.
-
|
I will do some test this night/weekend with Test5 firmware and with last developement firmware (compiled with gitpod) and I will attach here. |
Beta Was this translation helpful? Give feedback.
-
It's sufficient to use the latest development firmware.
Yes okay, but as barbudor wrote ... if we get the |
Beta Was this translation helpful? Give feedback.
-
|
Hi @barbudor and @benjaminnestler , I mean about "last log entries just before reset", not "first ones". I have compile last developement source code with gitpod and upload that firmware. We have a problem. logs are different between not connected to MQTT or connected. With MQTT connected I can see any 36, 28, 43 commands. Even not DEVICE ID response from TuyaMCU. Just in case, I have also check another log after powering off the S09 and power it on again (with last saved state, I mean, MQTT configured) As you can see, in this case we "lost" some log entries (as ESP-HDW ESP8266EX, for example) I hope you see that logs are different. What do I new to flash and check now? Thanks |
Beta Was this translation helpful? Give feedback.
-
|
Hi @barbudor , just in case, in previous message I have included a log to show that if I connect to an mqtt server in tasmota, I can't get the same log from tasmota as if I dont connect to the broker. I can't get the same commands from TuyaMCU, so I think that we may update code in developement branch to work with an mppt connection in our tasmotas. I dont know if I am explaning well. All my previous tests were always without connecting to an mqtt broker. Bye |
Beta Was this translation helpful? Give feedback.
25 replies
-
whre I bought it And probably the same: |
Beta Was this translation helpful? Give feedback.
-
Ok, I will wait, if you want me to test new firmware, please, write down and I will try to do the same day. I wanted to know only we are agree that seems that there is something to solve. But we are not in a hurry, of course. Thanks a lot. |
Beta Was this translation helpful? Give feedback.
-
|
Sorry @barbudor , any news? Remember this discussion. May be is it better (or do you prefer) to open a issue ? |
Beta Was this translation helpful? Give feedback.
-
|
Hi @ortegafernando |
Beta Was this translation helpful? Give feedback.
-
|
Hi @barbudor, no need to apologize. If I know you have this discussion on your mind, that's fine for me. We can wait what you need, of course!!! |
Beta Was this translation helpful? Give feedback.
-
|
Hi, any news @barbudor , thanks a lot |
Beta Was this translation helpful? Give feedback.
10 replies
-
|
@ortegafernando |
Beta Was this translation helpful? Give feedback.
-
|
Hi, I will use it with MQTT, but I was only waitinh you and @benjaminnestler to test any firmware to solve all problems. Why? I tought that it will be usefull to improve tasmota source code because in future new tuya devices could have the same problem. Ok, let's test number 7. Again with MQTT ON, no problem, no reboot. With MQTT OFF: no problem, no reboots. May you can PR and include in tasmota firmware to avoid future problems, I don't know. What do you think? |
Beta Was this translation helpful? Give feedback.
-
|
Looks like we finally nailed it |
Beta Was this translation helpful? Give feedback.
-
Barbudor you are the best! I hope your effort and my test will avoid future "tuya" problems in other devices. Thanks a lot. |
Beta Was this translation helpful? Give feedback.
-
|
PR #18085 done |
Beta Was this translation helpful? Give feedback.
-
|
I have the exact same device. If I hadn't read this, I wouldn't have known that when transplanting a new ESP chip you have to compile a custom firmware to support both Tuya MCU and the IR functions.. but also this reset thing, I wouldn't have figured out that you mustn't solder to Reset pin. The additional pin configurations for led and button as well.. Thank you all who contributed to this discussion and Tasmota code itself!! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi, any key to check a problem related with this: #17562
If I select TUYA DEVICE in module configuration..... I get my config reseted because of a boot loop.
If I desoldered TX pin of Tasmota from RX pin of TuyaMCU could I sniff serial debug log from TASMOTA to understant why it is resetting my config?
Or I can't because of "I need that TX pin connected to RX of TuyaMCU to "get" that boot loop"?
Could I make anything with weblog? Not to be clear after reset or something like that.
Thanks
Beta Was this translation helpful? Give feedback.
All reactions