I just posted an update to support it as a switch, but I haven’t added the temperature to the component yet. I will do in due course if you can confirm that it is working as a switch now
Switch is working! thanks…
When will the sensors be supported?
Please refer to the GitHuib issue https://github.com/mattsaxon/sonoff-lan-mode-homeassistant/issues/12
Multi Outlet devices such as the 4CH, 4CH Pro are now supported with the R3 fork.
@Bluhme, can you confirm if the TH16 now has V3 firmware on it. @tsouza85 seems to be using V3 firmware with theirs.
If so, is there any reason to continue to support the earlier firmware versions in the component?
Hi all,
i can confirm sonoff mini is working well!
Is anyone get the sonoff tx us 3gang working?
What firmware version is it running? I saw some info that said LAN mode wasn’t supported with the multi gang T1s, but they may we’ll be out of date as the same page had lots of information I know to be out of date!
Updated to 100.4 and my entities in this custom_component are listed as unavailable.
I get the following error message in the log
Logdetaljer (ERROR)
Thu Jan 16 2020 11:55:40 GMT+0100 (CET)
Error decrypting for device 10006533c5: Padding is incorrect., probably wrong API key
its running 3.3.0 firmware. using eweling app lan mode is working, i can control the tx 3gang without internet enabled. THe only problem is that i cannot get the apikey. with sonoff mini i used the 10.10.7.1/device while connected to the itead wifi, now i reset the device through ewelink app but i cannot see the itead wifi…how to get the apikey?
edit: it was my error, i have now device id and apykey, but added to HA i see only a switch, instead of 3 switch…ho to get all of them?
Yep, its getting harder to get the key, here’s my docs I’ve written on it. Basically, for these 3.3 devices, I think you need to sniff the LAN, there a couple of pointers on how to go about this in the docs
Reference to issue here https://github.com/mattsaxon/sonoff-lan-mode-homeassistant/issues/18. Short summary, its related to the zeroconf components that has been upgraded, it’s faulty and I’m working on a solution. There is a workaround in the issue.
All its working! I got the api Key with http://10.10.7.1/device
The 3gang Is working with the outlet parameter set for each gang
No issues! Its US model
So is it true that this integration doesn’t work with Hassio 0.104.3? I obtained the API key via proxy sniffing but HA complains about
Padding is incorrect., probably wrong API key: eWeLink_10007329af._ewelink._tcp.local.
I am missing something here. Is it needed for mattsaxon’s component to have the jumper set (DIY-mode)? Or not? I put it but can also not pair anymore then.
The component works in either mode. If in DIY mode you don’t use the API key.
That error indicates wrong API key. Don’t get mixed up between the selfAPIkey it is not the same. You need to capture API key during pairing
I got the key according to the article you link to in documentation:
https://community.hubitat.com/t/sonoff-ewelink-via-homebridge-node/3753
so probably something changed.
I was told that someone had used this successfully, but can’t attest to that as I’ve never used this method.
Sorry if it doesn’t work, I think I’m going to remove that link.
The way I do this is with a local LAN sniff using tcpdump. I find this very reliable, but is not trivial.
I’m sorry that Itead make this so difficult!
Thanks Matt for your work!
@mattsaxon I’m trying to use your custom component for my Sonoff Basic, Basic R2 and RF R2 devices. I got API key from last method in your article:
Sonoff EWeLink via Homebridge/Node, but as @Stooovie suggested maybe something changed on Ewelink side. I have also noticed that length and format of my API is different then one shown in your example on Github. All of my devices added in Home Assistant (Hass.io on RPi3 B+ - HA version 0.104.3) are unavailable and I get this error in log:
Also some zeroconf is mentioned:
2020-01-28 01:04:02 DEBUG (zeroconf-ServiceBrowser__ewelink._tcp.local.) [homeassistant.components.switch.sonoff_lan_mode_r3] Service eWeLink_1000568b68._ewelink._tcp.local. updated (not our switch)I have read about some issues regarding this but this is solved right? I don’t know how to check which zeroconf my Home Assistant is using and how to revert on maybe older version. I’m new to Home Assistant, so I’m still learning…
Also @mattsaxon i have made some tcpdump of local LAN traffic in my home WIFI when Internet connection was disabled but I don’t know where to find proper API KEY for my Sonoff devices. Also one more question is this API KEY different for each device or it’s the same for all of my devices under my Ewelink account. Thank you Matt for your work on this excellent component…