Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"connection failed" #6

Open
trcyprkr opened this issue Apr 7, 2019 · 1 comment
Open

"connection failed" #6

trcyprkr opened this issue Apr 7, 2019 · 1 comment

Comments

@trcyprkr
Copy link

trcyprkr commented Apr 7, 2019

Hello sir,
I've checked and rechecked the sketch, editing and rechecking the ssl fingerprint many times.
I get a "connection failed" message every time regardless of what I try.
Any ideas?

@rgrokett
Copy link
Owner

rgrokett commented Apr 9, 2019

First thing I would check for "connection failed" is the Wifi info:

  • Can your ESP8266 connect to your wifi? i.e. does the SSID and password match the one in ESP8266_PIRv2.ino (both SSID & pwd are CaSe SensiTive!)

If Wifi is good, you should see something like:
WiFi connected
IP Address: 192.168.x.x
and the LED blink 3 times.

Next is to verify the IFTTT settings:

  1. Log into your account IFTTT and go to "My Applets" https://ifttt.com/my_applets

  2. Select the "pirtrigger" and click on the "Check Now" and look for the email in your inbox. It can take 5-10 min to receive at times.
    Capture

  3. If that works, you can then verify the IFTTT API itself is working: Go to https://ifttt.com/services/maker_webhooks/settings and copy/paste the URL: displayed (looks like https://maker.ifttt.com/use/b8rXq5k... ) and follow the instructions to trigger the event.

  4. If this is all working, then that will tell you that IFTTT is set up properly.

  5. Does your IFTTT API key match the one in the ESP8266_PIRv2.ino ? (the API key is that long text string shown in step 3 above. Something like b8rXq5k... .)

NOTE: that SSL fingerprint is ONLY needed if line 58 shows bool verifyCert = true;
Otherwise it is ignored.

Most likely things: wrong API key, wrong SSID/Password

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants