ESP-07 (ESP8266) - Relay toggle loop on 'power1 0' command #23059
Replies: 7 comments 3 replies
-
|
Some additional strange behaviour. If I send 'SetOption31 1' command and restart the device, the relay toggle is twice as fast for about 30 seconds, and then stops and the device behaves as I expect i.e. it closes relay on 'Power1 0' and it stays closed and on 'power1 1' it opens the relay. When I restart the device and execute 'power1 0' it starts 'quick' toggling the relay again for approx. 30 seconds. I then send 'SetOption31 0' and it goes back to the 'normal issue' behaviour where the toggle is slower after 'power1 0', but it never ends until I send 'power1 1' |
Beta Was this translation helpful? Give feedback.
-
|
GPIO0 must be 1 at boot. How do you hookup the relay?
El El dom, 23 feb. 2025 a la(s) 16:06, blackbasilisk <
***@***.***> escribió:
… Some additional strange behaviour. If I send 'SetOption31 1' command and
restart the device, the relay toggle is twice as fast for about 30 seconds,
and then stops and the device behaves as I expect i.e. it closes relay on
'Power1 0' and it stays closed and on 'power1 1' it opens the relay. When I
restart the device and execute 'power1 0' it starts 'quick' toggling the
relay again for approx. 30 seconds. I then send 'SetOption31 0' and it goes
back to the 'normal issue' behaviour where the toggle is slower after
'power1 0', but it never ends until I send 'power1 1'
—
Reply to this email directly, view it on GitHub
<#23059 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACXBW4OBSVEJKVD27LMC4732RIL37AVCNFSM6AAAAABXWSTPWWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMRZGM2TOMA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Relay Module: Driver Circuit: Pull-Up Resistors and Boot Requirements: |
Beta Was this translation helpful? Give feedback.
-
|
You make assumptions about GPIO 0 pull up resistor. If you you connect a driver transistor, you have to add an external strong pull up resistor to make sure a defined high state is there at boot. The internal pull up is to weak when connecting a external driver transistor. |
Beta Was this translation helpful? Give feedback.
-
|
Unless it’s a fet. ;-)
El El lun, 24 feb. 2025 a la(s) 11:55, Jason2866 ***@***.***>
escribió:
… You make assumptions about GPIO 0 pull up resistor. If you you connect a
driver transistor, you have to add an external strong pull up resistor to
make sure a defined high state is there at boot. The internal pull up is to
weak when connecting a external driver transistor.
—
Reply to this email directly, view it on GitHub
<#23059 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACXBW4LY4HK5T7HANTLUIOD2RMXERAVCNFSM6AAAAABXWSTPWWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMZQGE3TSMQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Would not use GPIO 0. With this module the unrestricted GPIOs 4 and 5 are available. Anyways without the circuit drawing it is all guess work and no real help can be done. |
Beta Was this translation helpful? Give feedback.
-
|
Here is the circuit drawing. Does this help ?
…On Mon, 24 Feb 2025 at 19:57, Jason2866 ***@***.***> wrote:
Would not use GPIO 0. With this module the unrestricted GPIOs 4 and 5 are
available. Anyways without the circuit drawing it is all guess work and no
real help can be done.
—
Reply to this email directly, view it on GitHub
<#23059 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AU2SEOEHGYONT472EMPVZQD2RNMRVAVCNFSM6AAAAABXWSTPWWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMZQGM4TMMI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
Sincerely,
Dave Coates
084 548 0077
|
Beta Was this translation helpful? Give feedback.
-
|
When you say GPIO 0 needs to be 1 at boot, do you mean it needs to be 1
during boot and then return to 0 at some point? (when?)
…On Mon, 24 Feb 2025 at 21:01, Dave Coates ***@***.***> wrote:
Here is the circuit drawing. Does this help ?
[image: image.png]
On Mon, 24 Feb 2025 at 19:57, Jason2866 ***@***.***> wrote:
> Would not use GPIO 0. With this module the unrestricted GPIOs 4 and 5 are
> available. Anyways without the circuit drawing it is all guess work and no
> real help can be done.
>
> —
> Reply to this email directly, view it on GitHub
> <#23059 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AU2SEOEHGYONT472EMPVZQD2RNMRVAVCNFSM6AAAAABXWSTPWWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMZQGM4TMMI>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
--
Sincerely,
Dave Coates
084 548 0077
--
Sincerely,
Dave Coates
084 548 0077
|
Beta Was this translation helpful? Give feedback.
-
|
The point is that if gpio 0 is pulled down at boot time, the Espressif chip will enter bootloader mode instead of actually booting the firmware (like Tasmota). After boot, this does not apply, meaning that you need to be careful with anything you connect to gpio 0, as you may not have detailed control over spurious levels while powering up. The simplest is to avoid using gpio 0, but stay with the unencumbered gpio 4,5,12,13,14,15 when practical. Still, many dev boards (including yours) will use gpio 0 for a button, where you can push it (while powering up) to get into bootloader mode, and also connect it to a circuit allowing the CH340 USB/serial adapter chip to be used to control bootloader mode via USB (also after power-up). This further complicates using gpio 0 for anything else, but still possible if you know exactly what you're doing, and where the pitfalls are. |
Beta Was this translation helpful? Give feedback.
-
|
Regarding the schematic the relais is connected to GPIO 13. |
Beta Was this translation helpful? Give feedback.
-
In short, my issue is that when I am NOT connected to WiFi, and execute 'Power1 0'. The relay that is connected to GPIO0 toggles on and off repeatedly until I send 'Power1 1' command. When I run 'Power1 0' command it starts toggling again. As soon as I connect to WiFi this behaviour stops and it does what I expect i.e. energizes the relay with Power1 0 and it stays energized until I send 'Power1 1' command.
I have searched high and low and I can find very little info about this. I even tried ChatGPT and the only suggestion in the end after going through hours of troubleshooting was not very helpful. I have validated the template, firmware and can repeat the process and 'issue' on multiple devices.
In summary, the relay toggle issue persists until I connect to Wifi. As soon as I disconnect WiFi and clear WiFi settings, the issue starts again
Information:
Device: ESP-07
I am connected via serial
I reset device back to factory settings completely (i.e. not just Wifi /MQTT settings etc.), then I install Tasmota-Minimal firmware, power cycle, then I install Tasmota-Lite firmware. I then power cycle the device and apply the following template:
Template {"NAME":"ESP07 v2","GPIO":[21,0,56,0,0,0,0,0,0,0,0,0,0,0],"FLAG":0,"BASE":18}
I also tried inverting the relay on GPIO0 by applying the following template:
Template {"NAME":"ESP07 v2","GPIO":[224,0,56,0,0,0,0,0,0,0,0,0,0,0],"FLAG":0,"BASE":18}
All rules are turned OFF
PowerOnState is 0 (zero)
PulseTimer is 0 (zero)
No additonal info in logs really, i.e. all seems normal. No error messages or strange behaviour that is obvious to me. Serial log snippet I just took attached. I turned the device on and ran some power1 commands, applied the template etc.
Tasmota_SerialLog.txt
Beta Was this translation helpful? Give feedback.
All reactions