Sonoff /eWeLink component for original firmware

I suspect this is the problem. You have literally cut and pasted from the sample config. The characters “(optional)” should NOT be in there.

This is what I have now:

sonoff:
    username: [email protected]
    password: MyPassword1
    scan_interval: 60
    grace_period: 600
    api_region: 'eu' 

config does not show any errors, but I still can’t get any sonoff entities even I have working switches in eWeling application

Is eu your correct region?

are your username and password correct?

Actually what I think we need is that @monaco bumps up his logging and posts his log. See https://www.home-assistant.io/components/logger/

I have it already and it doesn’t resolve…

(homeassistant) msev@orangepipc:~/homeassistant$ pip3 install --upgrade certifi
Requirement already up-to-date: certifi in ./lib/python3.7/site-packages (2018.11.29)

Btw could I add this inside the code somewhere - http://blog.pengyifan.com/how-to-fix-python-ssl-certificate_verify_failed/ :smiley:

hi peter i bought a smart circuit breaker that has also power control but it is not a sonoff but it is used with ewelink app. smart circuit breaker is cnzjsc. producer is WDYK How can i see in home assistant??please help me thank you

@marksev1 i think you could add this lines here. it’s just an idea which i do not recommend it! might work or it might not, just give it a try. (doesn’t matter on what branch you are)
ps: if it doesn’t work please do not post the errors here, do it on github because we might end up spamming the thread with this particular error that might spread into other areas

import ssl
ssl._create_default_https_context = ssl._create_unverified_context

@Hdjweb read the project’s description! if you have get errors post them here or open an issue on github, I cannot help you without providing a real problem :face_with_raised_eyebrow:

Peterbuga solved thank you you can add to compatibility list also cnzjsc smart break circuit

1 Like

yes, I am from EU. I pasted here fake username and password, but I have verified a few times to make sure I have put the right one.

Please run this steps to get a better view what’s happening on your side https://github.com/peterbuga/HASS-sonoff-ewelink/tree/master/sonoff-debug
If this script doesn’t work then the component is not going to work either.

Sorry to hijack the thread but I just got a couple of different SONOFF smart light switches on aliexpress and wanted to connect them to my ha/hass.io. I was pointed to your repo here:

but Im not sure how to “install” the files in my hass.io install. In your readme you talk about adding some code to automation.yaml but then you mention a custom_components folder I cant find.

You “install” the files by copying the files into the folder structure he specifies. If you don’t have the custom_components folder you will have to add it to the config folder.

The file and how to is in the first post.

If any setting you don’t understand please feel free to ask.

Ok i created the folder and copied the files over and added the code to the configuration.yaml.

Thanks!

Many thanks to you @peterbuga !!!
You saved a lot of time for me :slight_smile:

1 Like

Has anyone managed to integrate with the “Sonoff RF”? For me it was the only one that did not work.

@dougbaptista via WIFI or RF? please give more details about your setup

Hello, come on. My “Sonoff RF” is connected via Wifi and I have a “DW1 433Mhz” connected without RF. I’m not at home at the moment, arrived in 5 hours to pass more details. I’m from Brazil and I just configured it as follows:

  sonoff:
    username: !secret sonoff_user
    password: !secret sonoff_senha

My other “sonoffs” connected perfectly. (Basic and T1)

@peterbuga Just realized the state changes if done from ewelink/google home are not reflecting on HA instantly like they used to before. (Didn’t notice this for quite some time)

I think this happened on updating to the latest code that was updated 18 days back or so.

I see this not working with multiple outlet devices, but single outlet devices are working fine.

Reverting to old backup to see if that fixes it.