ESP32 losing configuration #19408
-
|
Hi all, I bought a module from Rocket Controller, which is en ESP32 + 4 relay and an expander with 8 more relays through an i2C with the PCF8574 chip. So I compiled a version (13.1.0.1) of ESP32 with the PCF8574 and some EZO chip enabled. Issues: Here's some screenshot
I've put weblog 4 to try to capture something, but I did not see anything usefull. When I have only the i2c configured, I can see this page: If I enable first i2c, all 8 relays work. Then I can enable relay 1 (GPIO25), relay 2 (GPIO26). Any help would be appreciated! Weird! |
Beta Was this translation helpful? Give feedback.
Replies: 9 comments 20 replies
-
|
What are the i2c addresses of the EZO chips? |
Beta Was this translation helpful? Give feedback.
-
|
Tasmota losing config after a restart is typically due to a boot loop where Tasmota will remove config details till able to boot without crashing. |
Beta Was this translation helpful? Give feedback.
-
|
I don't have the EZO connected yet. I did a full reset, reload the config with i2c only: Then loaded the config with the 4 relays, removed the RFrecv on GPI027 The added the i2c config... same issue, rebooted with no configuration. |
Beta Was this translation helpful? Give feedback.
-
|
Ah, I thought it was the Astra family, not the ESP32R4 I will try later this week to test the same configuration |
Beta Was this translation helpful? Give feedback.
-
|
Here's what I documented for myself: Following instructions removed comments on those lines in my_user_config.h and those line for the EZO: |
Beta Was this translation helpful? Give feedback.
-
|
@sfromis is there any way to capture this in the logs to see where the issue is? Any ideas you may have for me to try, I would appreciate. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Here's what I tried just now: I found this template from the restore of a configuration from the vendor: I went to configure other and pasted the template and saved. Now I go to configure module and try to apply this ESP32R4 (0) template: Then a restart with the config not applied and this log: Is there anything here, pointing to an issue preventing Tasmota to accept this template? I then tried to modify the template and put all RED lines to NONE and removed the RFRecv. |
Beta Was this translation helpful? Give feedback.
-
|
Bad news:
Tasmota has been boot looping, and disabled features until able to boot without crashing. Watching log via serial is a good way to see what happens. |
Beta Was this translation helpful? Give feedback.
-
|
Ha! I see it now! I'm trying to connect the ESP32 with serial, but no luck so far, need to research this a bit more. Any good resources for that. What I have now is a UART to serial, trying to use Putty to connect, but I have access denied. Bummer! SCRAP THAT, I'm connected! I forgot to check the baudrate command on the console! |
Beta Was this translation helpful? Give feedback.
-
|
Ok, here's the output of the serial log 4, and I see the "Core 1 panic'ed" line. Does that help in any way understanding why this template make the core panic? |
Beta Was this translation helpful? Give feedback.
-
|
OK. I can reproduce: Let me chk where it goes wrong.... |
Beta Was this translation helpful? Give feedback.
-
|
Diving in the code I think Mode1 could never co-exist with GPIO relays; it tries to index an array to short dimensionend based on available relays. I suggest you use Mode2 by keeping below commented: but enable: once restarted add this as rule 3: and then perform a restart (command |
Beta Was this translation helpful? Give feedback.
-
|
@arendst, you're the MEN! (Let me know if I can buy you coffee!) I had to adjust the rule3 to this: This is what works with the 4 relay on GPIO and the 8 extender relay on the i2c PCF8574. So to recap:
Hope this help other use this kit from Rocket Controller |
Beta Was this translation helpful? Give feedback.
-
|
One detail: In general, it is not really recommended to modify |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, still learning! |
Beta Was this translation helpful? Give feedback.
-
|
With version v13.1.0.2 mode 1 is fixed solving the initial issue from OP too. |
Beta Was this translation helpful? Give feedback.
-
|
I think the problem is not solved with 13.1.0.2. I can't see the PCF8574 menu in Mode1. Log: |
Beta Was this translation helpful? Give feedback.
-
|
sorry my config was wrong, it works. |
Beta Was this translation helpful? Give feedback.
-
|
In my case the same thing happens. Simply program the esp32 with GPIO34/35/36/39 with a button, after a short time it restarts and is left with the default configuration |
Beta Was this translation helpful? Give feedback.
-
|
But the GPIO34/35/36/39 on the esp32 can be configured as input, but after programming them the esp32 restarts and remains with the default programming. |
Beta Was this translation helpful? Give feedback.
-
|
What exactly do you mean by "input"? Tasmota config as a "Button"? |
Beta Was this translation helpful? Give feedback.
-
|
Yes, when I configure it as button |
Beta Was this translation helpful? Give feedback.
-
|
What barbudor alluded to was that a pin configured as a Button, and registered as "pushed" for 40 seconds, will activate a recovery feature resetting to initial state. You should not configure pins without making sure that the electrical connection works for what you want. Maybe your inputs should be configured as "Switch" instead of "Button", or maybe as inverted Button, depending on how you want to use them. |
Beta Was this translation helpful? Give feedback.
-
|
ok, I'll try it this way. Thank you for your help |
Beta Was this translation helpful? Give feedback.
-
|
Just popping here to say I've had the exact same issue with my new ESP32R4. The device fully reset itself and lost all configuration (even the relays). I was only using relay 1 via an automation using MQTT. What information do you need to confirm if this is the same problem? The device is running: Oddly enough, I've had that exact same issue (device fully resetting) with cheaper 1 relay ESP8266 controllers running latest tasmota. It was the reason I purchased the ESP32R4 initially. |
Beta Was this translation helpful? Give feedback.
-
|
Well, without any details of your config or operation, this does not mean much. Tasmota has recovery features designed to let you trigger a full reset, and you may have unintentionally activated one of them. https://tasmota.github.io/docs/Device-Recovery/ |
Beta Was this translation helpful? Give feedback.
-
|
If this can help: The cheaper board that had the same issue is that one: https://templates.blakadder.com/ESP12F_Relay_X1_V2.html {"NAME":"LC-Relay-ESP12-1R-D8","GPIO":[255,255,157,255,255,21,255,255,255,255,255,255,57],"FLAG":15,"BASE":18} The relay port is on IO5 if that plays a role (noticed arendts post with code showing I2C using GPIO05). Only thing that I configure on the device is rename it and connect to to my MQTT broker to turn the relay on/off. No other modification is brought to it. I reflashed it using Program Version 14.3.0 (release-tasmota-4M). We'll see if the same issue occurs within the next few days. I will try to do the same with the ESP32R4. |
Beta Was this translation helpful? Give feedback.
@arendst, you're the MEN! (Let me know if I can buy you coffee!)
I had to adjust the rule3 to this:
rule3 on file#pcf8574.dat do {"NAME":"PCF8574 A=R5-12","GPIO":[224,225,226,227,228,229,230,231]} endon
This is what works with the 4 relay on GPIO and the 8 extender relay on the i2c PCF8574.
So to recap:
I compiled on gitpod
modified /tasmota/my_user_config.h
2.1) removed comments here:
#define USE_PCF8574
#define USE_PCF8574_MODE2
2.2) added the EZO chip I need:
#define USE_EZOPH
#define USE_EZOORP
#define USE_EZOEC
#define USE_EZODO
2.3) Removed some other module I don't need (for fun)
2.4) in /platform_overide_sample.ini
commented tasmota
uncommented tasmota32
Compiled with : plat…