Skip to content
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

Closed
andreihoreica opened this issue Nov 19, 2024 · 12 comments
Closed

POWR320D automatically turning off #1527

andreihoreica opened this issue Nov 19, 2024 · 12 comments
Labels
question Further information is requested

Comments

@andreihoreica
Copy link

andreihoreica commented Nov 19, 2024

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

@AlexxIT AlexxIT added the question Further information is requested label Nov 19, 2024
@AlexxIT
Copy link
Owner

AlexxIT commented Nov 19, 2024

Your device has several auto off settings (power protection). You can find them in your file.

@driagi
Copy link

driagi commented Jan 10, 2025

With a POW Origin, today i've the same problem. At the same time I get this error:
Home Assistant : 2025-01-10 10:05:37.712 WARNING (MainThread) [custom_components.sonoff.core.ewelink.cloud] Cloud ERROR: {'error': 504, 'reason': 'Request Timeout', 'deviceid': '1002xxxxxxxx', 'apikey': 'xxxxx3de-7347-488e-88e2-54dxxxxxxxxxxx', 'sequence': '1736499932689'}

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 don't have any security settings

image
image
image

@vegos
Copy link

vegos commented Jan 10, 2025

I have the same problem for the last 3-4 days.
Cloud ERROR: {'error': 504, 'reason': 'Request Timeout'
POWR320D running Firmware: 1.1.1
I changed yesterday from auto to cloud mode, it worked for a couple of hours and then started again to turned off.

@AlexxIT
Copy link
Owner

AlexxIT commented Jan 10, 2025

504 not related to this issue. Your problem with bad WiFi connection.

@AlexxIT AlexxIT closed this as completed Jan 10, 2025
@vegos
Copy link

vegos commented Jan 10, 2025

AP is one meter with clear view
IMG_20250110_144531

@AlexxIT
Copy link
Owner

AlexxIT commented Jan 10, 2025

The error is pretty obvious. Cloud can't send command to device.
It could also be a problem with your Internet. Connection from your router to the ewelink servers.

@vegos
Copy link

vegos commented Jan 10, 2025

It happened again right now.
Checked logs, no disconnection or low signal.
Screenshot_2025-01-10-14-53-46-770_io homeassistant companion android

@vegos
Copy link

vegos commented Jan 10, 2025

No problem with other sonoff devices

@aferende
Copy link

ZigBee or wifi? Bridge?

@driagi
Copy link

driagi commented Jan 10, 2025

I also don't have wifi problems and have never had them.
I also reported that in correspondence with those errors, the POW turns off.

@driagi
Copy link

driagi commented Jan 10, 2025

ZigBee or wifi? Bridge?
Wifi

@AlexxIT
Copy link
Owner

AlexxIT commented Jan 10, 2025

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

5 participants