Repository navigation
L2/L3 LED Strips not working in Local mode & Power Consumption sensors not updating in Auto mode #1763
Description
Description
I am experiencing two related issues with the Sonoff LAN integration that seem to stem from the global nature of the mode setting (Cloud/Local/Auto).
L2/L3 LED Strip Local Mode Issue:
My Sonoff L2 and L3 LED strips do not work at all when the integration is set to local mode. They appear as unavailable or do not respond to commands. They only function correctly when the mode is set to cloud.
Power Consumption Update Issue (Auto Mode):
When using auto mode (to allow the LED strips to work via Cloud), my power-monitoring devices (e.g., Sonoff POW) stop updating their power consumption data (Watts/Amps) in real-time. The data only refreshes if I manually reload the integration or open the eWeLink mobile app. It seems that in auto mode, the integration prioritizes a local connection that doesn't push telemetry updates as frequently as the cloud connection would.
Problem Summary
Currently, the mode setting is global for the entire integration. There is no way to specify a connection mode per device. This creates a conflict:
If I set mode: cloud, everything works, but I lose the benefits of local control for my switches.
If I set mode: local, my L2/L3 strips stop working.
If I set mode: auto, power monitoring devices fail to report data consistently.
Desired Solution/Feature Request
Fix the local support for L2/L3 LED strips if possible.
More importantly: Please allow per-device mode configuration. For example, the ability to force cloud mode for specific entities (like L2/L3 strips) while keeping the rest of the system in local mode.
LOG:
"data": {
"version": "71e47be",
"cloud_auth": true,
"config": null,
"options": {
"mode": "auto",
"debug": false
},
L2:
"device": {
"uiid": 137,
"params": {
"bindInfos": "***",
"version": 8,
"init": 1,
"fwVersion": "1000.2.1050",....
},
"model": "L2",
"online": true,
"local": null,
"localtype": null,
"host": null,
}
Pow_R2:
"params": {
"bindInfos": "***",
"version": 8,
"sledOnline": "off",
"fwVersion": "3.7.1",
"staMac": "***",
"rssi": -61,
"init": 1,
"alarmType": "pcv",
"alarmVValue": [
-1,
257
],
"alarmCValue": [
-1,
-1
],
"alarmPValue": [
-1,
3000
],
"switch": "on",
"startup": "on",
"pulse": "off",
"pulseWidth": 500,
"power": "357.51",
"voltage": "240.05",
"current": "1.86",
"oneKwh": "stop",
"uiActive": 60,
"timeZone": 2,
"hundredDaysKwh": "get",
"endTime": "2024-04-06T11:28:31.851Z",
"startTime": "2024-04-06T11:28:29.048Z",
"only_device": {
"ota": "success"
},
"ssid": "***",
"bssid": "***",
"demNextFetchTime": 1773352800000,
"rstReason": 0,
"exccause": 0,
"epc1": 0,
"epc2": 0,
"epc3": 0,
"excvaddr": 0,
"depc": 0,...
},
"model": "Pow_R2",
"online": true,
"local": true,
"localtype": "enhanced_plug",
"host": "192.168.0.116:8081",
Activity
AlexxIT commentedon Mar 12, 2026
Your L2/L3 are not on the local network. This can be seen in the device info. Why they are not there - perhaps you know better.
You can read about pow in the documentation or in the integration changelog.
Borekss commentedon Mar 12, 2026
L2 is listed in Readme as tested device with cloud functionality only. It's what it is. I'm also using it this way in auto mode.
Regarding power consumption please see #1707
Borekss commentedon Mar 14, 2026
This is because L2 doesn’t support LAN mode, as you can see in the eWeLink app. There’s no option for LAN mode there.