meteohub.de

I've successfully used an http push service to activate an IFTTT applet to control my Nest Thermostat and to send me a notification. This has worked great for the last couple of years during the summer. When my Accurite weather station went above 80F then went below 76F the http push one time alarm to IFTTT would trigger the Thermostat to turn off and a notification would be sent to my phone (again via IFTTT in response to the same http push from my Metobridge) to remind me to open the windows of my house.

All of sudden, it stopped working on Sept. 17th. I can activate the IFTTT applet by running the http push request in a new tab in my Chrome Browser successfully (so I know it's not IFTTT), but if Meteobridge sends it (either in response to my One Time Alarm or due to a TEST), IFTTT fails to receive it. There is an Orange i on the Services screen next to the http one time alarm event definition and another one to the right of Triggered Alarms on the Live Data tab (with a green checkmark to the left of it) but I don't know if it means anything. HTTP upload has a green checkmark next to it. I paid for another 2 years of updates hoping a newer version might fix it but it does not appear to have helped.

All other functionality seems OK. All my weather data is being uploaded to Wunderground, Weather for You, and CWOP. I'm hoping someone smarter than I can help me figure it out

As I am not using IFTTT I ask the community here. Is anybody else experiencing similar problems with IFTTT?

Did you try calling "https" instead of "http"? May be they switched over to https completely? Just guessing...

It's always been https. Today I deleted the push service and recreated it. It looks like https://maker.ifttt.com/trigger/outdoor ... /123456789. Now I get the message "Error: Unable to establish SSL connection. (no more tries)". This time however I tried adding a Success text generated by IFTTT in response. If I leave the Success text blank meteobridge will report that the http upload was successful (although IFTTT says it never received the http push notification). All other data is transmitting normally.

Just a follow up to my issue. I did some more experimenting today. I first verified that my IFTTT applet would respond to an insecure http push request rather than the usual secure https push request I've used for the last couple of years by posting the same push request as http instead of https in a web browser. Once I verified that it worked, I changed the push url on the services tab of meteobridge from an https to an http push request. When I pressed the test button it also worked.

I may be wrong but this appears to be an issue of IFTTT rejecting whatever SSL method that the meteobridge is currently using. Perhaps IFTTT changed the SSL method it uses when this stopped working and the meteobridge version of SSL is not compatible.

While I've sort of solved my issue, I would prefer to use a secure https push request rather than an insecure http request.

Thanks for finding and sharing a work-around. I will try to find out what blocked the HTTPS connection. Do others share same experience with HTTPS an IFTTT?