search

AlexxIT / SonoffLAN

Control Sonoff Devices with eWeLink (original) firmware over LAN and/or Cloud from Home Assistant
https://github.com/AlexxIT/Blog
MIT License
2.69k stars 414 forks source link

New Update WARNING #1106

Closed milandzuris closed 1 year ago

milandzuris commented 1 year ago

after new update every device stop working, logs clear image

AlexxIT commented 1 year ago

Well. Nothing useful if you not provide more info

vlaryn commented 1 year ago

I am having same issue

milandzuris commented 1 year ago

LOGS CLEAR!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! YOU KNOW

fotis3d commented 1 year ago

I also face the same.

Edit: I only work it in "local" mode. So after a while all my Sonoff devices become unavailable. I reverted to the previous version for the time being where I do not face that.

Logs do not show anything

@AlexxIT if I can somehow help you to solve this please let me know :)

barto64 commented 1 year ago

Same issue in here. I had to rollback to previous version. I look the logs and nothing indicates an error.

AlexxIT commented 1 year ago

None of you have attached diagnostics and debug logs https://github.com/AlexxIT/SonoffLAN#issues

barto64 commented 1 year ago

You are right, apologies. At work now, late in the day when at home will try to troubleshoot the issue and provide you as much info as I can.

bax137 commented 1 year ago

I posted a message in this issue: https://github.com/AlexxIT/SonoffLAN/issues/1108#issuecomment-1422297688 but it seems that this is the same issue as here.

Spp595 commented 1 year ago

Same issue in here. I had to rollback to previous version. I look the logs and nothing indicates an error.

How can I roll back to the previous version?

barto64 commented 1 year ago

Go to the integrations page, chose the Sonoff one and pick the option Reload, then you can chose the version. I am not seeing in English but wording will be similar

barto64 commented 1 year ago

This is what i have been able to see when activating DEBUG for 3 different devices just before they become disabled in HA. Not sure if it helps. There is not any ERROR. After they become disabled they stop appearing in the list of what seems to be a polling to all the devices every minute or so. It looks like some sort of validation of the communication failed and the device were marked as offline and forgotten afterwards.

Device 1:

2023-02-08 20:39:44.351 DEBUG (MainThread) [custom_components.sonoff.core.ewelink.local] 10006ca1e3 => Local4 | {'cmd': 'info'} <= info: 200
2023-02-08 20:40:59.609 DEBUG (MainThread) [custom_components.sonoff.core.ewelink.local] 10006ca1e3 => Local4 | {'cmd': 'info'} <= info: 200
2023-02-08 20:41:07.743 DEBUG (MainThread) [custom_components.sonoff.core.ewelink] 10006ca1e3 <= Local0 | {'online': False} | 
2023-02-08 20:41:18.235 DEBUG (MainThread) [custom_components.sonoff.core.ewelink.local] 10006ca1e3 => Local4 | {'cmd': 'info'} !! Timeout 10
2023-02-08 20:41:18.235 DEBUG (MainThread) [custom_components.sonoff.core.ewelink] 10006ca1e3 !! Local4 | Device offline

Device 2:

2023-02-08 21:11:15.368 DEBUG (MainThread) [custom_components.sonoff.core.ewelink.local] 10005ca789 => Local4 | {'cmd': 'info'} <= info: 200
2023-02-08 21:12:30.420 DEBUG (MainThread) [custom_components.sonoff.core.ewelink.local] 10005ca789 => Local4 | {'cmd': 'info'} <= info: 200
2023-02-08 21:13:44.845 DEBUG (MainThread) [custom_components.sonoff.core.ewelink.local] 10005ca789 => Local4 | {'cmd': 'info'} <= info: 200
2023-02-08 21:13:58.051 DEBUG (MainThread) [custom_components.sonoff.core.ewelink] 10005ca789 <= Local0 | {'online': False} | 
2023-02-08 21:14:08.249 DEBUG (MainThread) [custom_components.sonoff.core.ewelink.local] 10005ca789 => Local4 | {'cmd': 'info'} !! Timeout 10
2023-02-08 21:14:08.249 DEBUG (MainThread) [custom_components.sonoff.core.ewelink] 10005ca789 !! Local4 | Device offline

Device 3:

2023-02-08 21:09:59.598 DEBUG (MainThread) [custom_components.sonoff.core.ewelink.local] 1000b90c39 => Local4 | {'cmd': 'info'} <= info: 200
2023-02-08 21:11:15.390 DEBUG (MainThread) [custom_components.sonoff.core.ewelink.local] 1000b90c39 => Local4 | {'cmd': 'info'} <= info: 200
2023-02-08 21:12:29.682 DEBUG (MainThread) [custom_components.sonoff.core.ewelink.local] 1000b90c39 => Local4 | {'cmd': 'info'} <= info: 200
2023-02-08 21:13:44.578 DEBUG (MainThread) [custom_components.sonoff.core.ewelink.local] 1000b90c39 => Local4 | {'cmd': 'info'} <= info: 200
2023-02-08 21:13:58.050 DEBUG (MainThread) [custom_components.sonoff.core.ewelink] 1000b90c39 <= Local0 | {'online': False} | 
2023-02-08 21:14:08.240 DEBUG (MainThread) [custom_components.sonoff.core.ewelink.local] 1000b90c39 => Local4 | {'cmd': 'info'} !! Timeout 10
2023-02-08 21:14:08.241 DEBUG (MainThread) [custom_components.sonoff.core.ewelink] 1000b90c39 !! Local4 | Device offline
dbullendsl commented 1 year ago

Same issue Sonoff IFan04 goes off line after unknown time. Reload of integration gets it going again but eventually it drops.

jawn22 commented 1 year ago

Same issue here

dmspils commented 1 year ago

Same issue, logs look exactly the same so no point in posting. I have to reload also to get it working again.

ChrisB85 commented 1 year ago

I also had this problem. Downgrading to version 3.3.1 resolved it.

Tamsy commented 1 year ago

Similar issues with all my Sonoff POW R2: While those are correctly detected by the integration/HA all readings like Current, Power and Voltage read 0 with v.3.4.0. Reloading the integration doesn't help. Rolled back to v.3.3.1 and all issues are solved.

heidricha commented 1 year ago

Would be nice to use one issue for the device unavailable issue, instead of three (minimum)...

Still interested if you guys use fixed IP address for the devices, or not? For me, downgrade didn't help, but setting a fixed IP in the router seems to. I need more time to test, but it looks definitely better now.

barto64 commented 1 year ago

All my Sonoff devices have fixed Ip and the last update of the integration killed them all.

Tamsy commented 1 year ago

Would be nice to use one issue for the device unavailable issue, instead of three (minimum)...

Still interested if you guys use fixed IP address for the devices, or not? For me, downgrade didn't help, but setting a fixed IP in the router seems to. I need more time to test, but it looks definitely better now.

Yup, same here: All devices on fixed IP addresses. After downgrading to v.3.3.1 all POW R2's work again as expected sending data to HA..

heidricha commented 1 year ago

All my Sonoff devices have fixed Ip and the last update of the integration killed them all.

yep... I also got disconnection with fixed IP too, with integration version 3.3.1 (downgraded). It is true, that I didn't have this with 3.3.1 BEFORE I upgraded to 3.4

kamilparczewski commented 1 year ago

Go to config/integrations click configure for sonoff, select your home and save. That helped me

fotis3d commented 1 year ago

Go to config/integrations click configure for sonoff, select your home and save. That helped me

@kamilparczewski Can you please confirm that in 2-3 days ? Cause I do not see why would that help. It was not checked and worked fine before as it is now at the old release. Thanks :)

@heidricha I believe if not all at least the majority of us in this field use static IPs for our IOT devices. ;)

heidricha commented 1 year ago

I cannot select home there..

image

Tamsy commented 1 year ago

I cannot select home there..

The poster might mean "My Home"

myhome

davidolrik commented 1 year ago

Go to config/integrations click configure for sonoff, select your home and save. That helped me

This also worked for me. Scratch that, it seemed to work for a little while and then it didn't.

heidricha commented 1 year ago

Go to config/integrations click configure for sonoff, select your home and save. That helped me

This also worked for me.

still don't have any options to select there

does anyone knows how to reset device data? looks like the integration doesn't connect to the cloud, nor it refresh device data locally. It works for a while somehow, then the device goes offline. Sometimes just one of them, but usually both of them.

devices already run fw version 3.6, but in HA they are still ion 3.5.1. in the logs there is a cache mentioned, looks like the integration gets the data from some stored data in the homeassistant environment, and doesn't connect the cloud or the devices themselves.

barto64 commented 1 year ago

The option to click "My Home" does NOT even appear in my HA, only the header appears.

heidricha commented 1 year ago

The option to click "My Home" does NOT even appear in my HA, only the header appears.

I finally tried to remove the integration. It didn't get removed but removed the previous configuration with the outdated device info, and possibly bad cloud-config. Also initialized the cloud access again from the config.yaml, and updated the device data too. Now I have got the default home, and I could check it

Now waiting for the long-term effect...

Masterz69 commented 1 year ago

Reg. device disappearing mentioned in https://github.com/AlexxIT/SonoffLAN/issues/1106#issuecomment-1423203426

3.4.0. have different zeroconf browser, which claim device as locally offline as soon received ZC REMOVED state change. But this is wrong idea. Cause ZC remove device after some time device NOT sending any data. And mostly SONOFF switches behave that - NOT sending any data unless operated manually or by Cloud or locally.

See my small test in https://github.com/AlexxIT/SonoffLAN/issues/1112#issuecomment-1436067690

You can see history of ADDED/REMOVED events by ZC browser on different machine (not HA server). Only devices 1000cf7638 & 1000f3e195 was actually unpowered.

All other state changes actually NOT reflect devices availability - they all the time was locally online. Unfortunately periodic check_offline call in run_forever does not help. ZC, as I see in my test, only react on data sent FROM device, not answers on info command.

Masterz69 commented 1 year ago 
2023-02-08 21:13:58.051 DEBUG (MainThread) [custom_components.sonoff.core.ewelink] 10005ca789 <= Local0 | {'online': False} |
2023-02-08 21:14:08.249 DEBUG (MainThread) [custom_components.sonoff.core.ewelink.local] 10005ca789 => Local4 | {'cmd': 'info'} !! Timeout 10

^^ that is staff, can't understand for now. After new ZC browser (3.4.0.) receive ZC REMOVED state change, it looks do same staff as in 3.3.1. But device actually stops responding to info requests from integration, to wget from console, to ON/OFF commands. And local mode will NOT recover till integration restart (at least in my case - https://github.com/AlexxIT/SonoffLAN/issues/1112#issuecomment-1436033587).

Masterz69 commented 1 year ago

PR https://github.com/AlexxIT/SonoffLAN/pull/1116 created with some ideas for @AlexxIT to deal with "False local offline" issue.

So far it works fine in my HA - no devices falling out. Tried also disconnect Internet - see no issues.

thefunkygibbon commented 1 year ago

I too am experiencing this (or very similar). I'm having to 'reload' the plugin every morning else none of my sonoff sockets work

georgepauna commented 1 year ago

Go to config/integrations click configure for sonoff, select your home and save. That helped me

This!

My devices were "unavailable" for few seconds/minutes few times each hour (6 devices so tens of disconnects total). After doing this, 0 disconnects so far (almost 2 hours)

Tamsy commented 1 year ago

PR #1116 created with some ideas for @AlexxIT to deal with "False local offline" issue.

So far it works fine in my HA - no devices falling out. Tried also disconnect Internet - see no issues.

Tested with your patches for the last 24 hours and can confirm: No devices falling out, no issues so far.

thefunkygibbon commented 1 year ago

I changed mine yesterday to "select my home" in the plugin options, but i still woke today to a bunch of non-responding smart plugs. :-(

AlexxIT commented 1 year ago

@barto64 same problem like here #1126 Should work better after v3.5.0 But you wouldn't have this problem at all in mode auto

AlexxIT commented 1 year ago

I haven't saw any debug info from author, so closing issue

AlexxIT commented 1 year ago

@barto64 Homes list loaded at the moment when you open Options window. Maybe you have some cloud issues at that moment.

AlexxIT commented 1 year ago

PR #1116 from @Masterz69 very helpful and should fix LAN problems. But anyway it's better always use auto mode (cloud+local). Because Sonoff devices sometimes stop responding on LAN requests.

thefunkygibbon commented 1 year ago

Dude. Just because this is the first time you've looked at these posts in the past few months and it's pretty overwhelming with the amount of problems people are having. It's a bit harshe to start dismissing everything.