I’m 100% sure the location was not needed in previous app versions (and I still think is not needed it’s just a constrain on app’s side not server side), I know this because I was always selecting “Andorra” out of laziness and let the app figure it out my country in background based on my ip (the same flow is used in the component as a failsafe for people who misconfigure the location in HA). maybe they’re just trying to optimize/analyze where&how the users are located to deploy the servers better and whatnot
ps: i live in Milano for the time being and I had an italian IP all the time
regarding the previous FW conversation, the idea was to be able to restore a sonoff device to current available firmware by downloading its firmware file from itead servers just like a device would & ready for flashing (aka tasmota -> original sonoff) and NOT downgrading. i don’t think the time i might spent on cracking this will make much of help
Thanks a lot peterbuga for your incredible work and your time. After activate my Home Assistant’s python virtual environment (source bin/activate) and install websocket and websocket-client (pip3 install websocket websocket-client) your component works as expected. Are there any option to put my switch in living room area?. I can’t put the switch in any area beacause i can’t see it in “Integrations” panel.
Thanks a lot for your answer CoreyMaxim. I have searched about “custom buttom” in Home Assistant but i don’t find specific official documentation. Maybe you refer to Button Card? Lovelace: Button card
friend I had the same problem as you, after the last update my sonoff pow did not give an updated reading of consumption, just disable lan mode in each sonoff pow and the problem will be solved
I am new to this. I followed your instructions. The sonoff component is not starting. I have the below error in my log file.
2019-08-28 18:58:38 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for sonoff which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2019-08-28 18:58:41 ERROR (MainThread) [homeassistant.setup] Error during setup of component sonoff
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/urllib3/connection.py", line 160, in _new_conn
(self._dns_host, self.port), self.timeout, **extra_kw)
File "/usr/local/lib/python3.7/site-packages/urllib3/util/connection.py", line 57, in create_connection
for res in socket.getaddrinfo(host, port, family, socket.SOCK_STREAM):
File "/usr/local/lib/python3.7/socket.py", line 748, in getaddrinfo
for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
socket.gaierror: [Errno -2] Name does not resolve
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 603, in urlopen
chunked=chunked)
File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 344, in _make_request
self._validate_conn(conn)
File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 843, in _validate_conn
conn.connect()
File "/usr/local/lib/python3.7/site-packages/urllib3/connection.py", line 316, in connect
conn = self._new_conn()
File "/usr/local/lib/python3.7/site-packages/urllib3/connection.py", line 169, in _new_conn
self, "Failed to establish a new connection: %s" % e)
urllib3.exceptions.NewConnectionError: <urllib3.connection.VerifiedHTTPSConnection object at 0x722ddb70>: Failed to establish a new connection: [Errno -2] Name does not resolve
@Fernando_Donan i’m pretty sure that 8 gang switch it’s not ewelink supported, as the logos imply it’s Tuya (also it’s kinda impossible for itead devices to support 8 gangs without some supplemental update to their API + clearly the app) if someone else knows otherwise please correct me.
@Dean_Olivier on the 1st view looks like the component is unable to connect to the required servers, if you’re running the HA instance behind PiHole or some other kind of connection please double-check or temporarily disable it and see if that fixes it