-
Notifications
You must be signed in to change notification settings - Fork 4.8k
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uncommanded relay switch off's #11628
Comments
Do you use hardware serial for your PZEM004T module? You did not provide your GPIO config. |
yes using hardware serial.
Sent from Mailspring (https://getmailspring.com/), the best free email app for work
…On Apr 8 2021, at 4:57 pm, Jason2866 ***@***.***> wrote:
Do you use hardware serial for your PZEM004T module? You did not provide your GPIO config.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub (#11628 (comment)), or unsubscribe (https://github.com/notifications/unsubscribe-auth/AQJJIIWL7OEQLEAVBSA33JLTHXHAPANCNFSM42TEK36A).
|
Without a precise complete description of your setup there is no help possible |
with the PZEM in the configuration, I command relay POWER2 ON 2 secs later all 4 relays are set to off. that is not requested by me. remove PZEM operates as normal relays under my control. |
We still need a crystal ball to help. Provide details. Whole config and logs. |
thought I had done that following the template..
did I miss bits in the copy paste?
bit hard to do when the screen fills so quickly.
Sent from Mailspring (https://getmailspring.com/), the best free email app for work
…On Apr 8 2021, at 5:23 pm, Jason2866 ***@***.***> wrote:
We still need a crystal ball to help. Provide details. Whole config and logs.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub (#11628 (comment)), or unsubscribe (https://github.com/notifications/unsubscribe-auth/AQJJIIXNH647EHFAQK5W26TTHXKABANCNFSM42TEK36A).
|
If you add the pzem the enrgy monitoring gets precedent. It reacts on the system temperature and if too high it shutsdown all power. That is what happens here. You'll jeed to raise the temperature threshold to a level that it win't turn off all power. Look for a setoption comand to do this. |
I had a feeling it was temperature related. |
SetOption42 set over-temperature (Celsius only) threshold resulting in power off on all energy monitoring devices (default = 90) |
Yes that's it. Try to set it to 250. That's about the max in the 8-bit register. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
PROBLEM DESCRIPTION
A clear and concise description of what the problem is.
NodeMCU with 3 temperature sensors & 4 relays to semi automate beer making.
relays control pumps valves & heating elements. All has been working fine for year or so.
Recently added PZEM0004 to monitor energy use. ( also working fine independently)
During the boil cycle using 2 relays & one temp sensor, at a certain point the system malfunctions, and commanded relay 3 on switches are immediately followed with un-commanded relay switch off to all four.
Removing the PZEM00XX TX configuration, restores normal operation.
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
:Backlog Rule1; Rule2; Rule3
:Status 0
:weblog
to 4 and then, when you experience your issue, provide the output of the Console log:TO REPRODUCE
Steps to reproduce the behavior:
Add PZEM0004 to configuration & run a beer boil cycle.
EXPECTED BEHAVIOUR
A clear and concise description of what you expected to happen.
would be nice to run both concurrently.
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)
The text was updated successfully, but these errors were encountered: