It’s a measure to make sure the ip is correct.
Is it borthering you in anyway?
If so, we’ll optimize it in future version.
We’ll looking into it.
The log provided about 16 hours of information. (UTC time: 2024-12-24T22:41:52 -----2024-12-25T15:22:33).
And there were 3 consecutive hours of network anomalies (UTC time: 2024-12-25T02:02:33-----2024-12-25T05:14:57)
During this period, the add-on failed to scan LAN device and lost access to the cloud.
Is your network acting normal in the time period above?
Do not consider that period between 2am and 5am, which I turned off my network.
Take a look on the events “online:false” and “online:true”.
When the devices lost connection, it becomes online again in 20 seconds. During this time, the network led (on Sonoff TX Smart Light Switch) keeps blinking.
Example from today morning:
We failded to reproduce the upload error.
Maybe try it in another browser?
The offline info is sended by cloud.
So it’s not smart-home add-on’s fault that the device offline.
If the device is offline both in app and iHost.
Maybe see if the device itself malfunctions?
I have 4 smart switches and all of them are having the same behavior.
They becomes offline one after another, and then becomes online again after 20 seconds.
On the router, they are always connected.
And the malfunctions are the same in the eWeLink app?
Yes, when they start to blink, when I open the eWeLink app, they are offline.
Can you send a feedback about the problem in you app?
I’ll let the app team know about the problem.
1 Like
Sent now from the app.
Feedback ID: 225063
Maybe the log should record errors only.
When everything is fine, there is no need to record anything.
Or we can have different levels of log verbose where the user can set a log level that will record errors only.
This can save the erase/write cycles increasing the lifetime of the eMMC.
Yes, we have some ideas about the log.
We’ll continue to optimize it.
Still can’t reproduce the upload error, even in Firefox.
What’s the version of your firefox?
Here’s mine:
It’s the same version.
The problem is on the level of privacy.
To reproduce the problem, go to Firefox settings → Privacy & Security
Then set the level to Strict (instead of the default “Standard”) and then reload the pages and try to upload an attachment.
Yes.
I can reproduce the problem alright.
It’s a CORS issue.
We’ll find some way to bypass it.
1 Like