-
Notifications
You must be signed in to change notification settings - Fork 423
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
POWR320D automatically turning off #1527
Comments
Your device has several auto off settings (power protection). You can find them in your file. |
With a POW Origin, today i've the same problem. At the same time I get this error: It may be a coincidence, but now, by deactivating Auto Option and setting Cloud Option, the problem seems to have disappeared. The shutdowns are not visible in the Ewelink log and the statistics for the month have disappeared (Ewelink) If it helps, I have Power on state:off |
I have the same problem for the last 3-4 days. |
504 not related to this issue. Your problem with bad WiFi connection. |
The error is pretty obvious. Cloud can't send command to device. |
No problem with other sonoff devices |
ZigBee or wifi? Bridge? |
I also don't have wifi problems and have never had them. |
|
Ah. It's energy sensor problem. It's other issue. You should disable energy sensor for this device. And find issue about it. I don't remember it's number. It's known problem with this device model. |
I have an device POWR320D from sonoff and after integration it turn off automatically after 7-10 minutes of power on regardless of having or not consumption on the device. After this switching off the device even the setting of "Power-on State" reset. I've search all the integration and i've remade the integration several times but still didn't find what trigger this switching off the device. Did anyone ran into this problem? Where can I search to see what is triggering my device?
sonoff-01JCG83RP5T034ZSPD6C7QN4QT-AC power -d0d41937218dbc595d228e0e69b397d6.json
config_entry-sonoff-01JCG83RP5T034ZSPD6C7QN4QT.json
The text was updated successfully, but these errors were encountered: