0
Under review

IFTTT Webhook error Eproto

CS Domotic CS Domotic 2 weeks ago in bOS Configurator updated by ComfortClick Support 3 days ago 9


Hello,

Since 2 or 3 months I have noticed that all my webhooks return the error below:

I think that a ssl certificat problem or error. 

What is the way to remove this problem ? Any Idea ??

Hi,

Zero problems here, using WebHooks (from IFTTT > bOS). I'm using the RPC on bOS, and use WebHooks everyday to fire up sleep mode etc (as widgets on my Android phone).

Is your problem from IFTTT to bOS or the opposite?

Best regards


Thanks for your answer.

The problem is from IFTTT to bOs. The command from bOS to IFTTT work fine.

You use the rpc with an "https" command ?

I don't understand because the problem appeared a few weeks ago.


I try with Roomba iRobot but the result is the same .... error ssl

Hi,

RPC is only available over HTTPS for a long time (since the new RPC version was published).

I don't have any problems from ifttt to bos.



So you're having problems with ifttt > roomba?

Well then, that means that bOS has nothing to do with the problem...

Probably it's some problem on ifttt services, but probably based on your location (don't have any problem here on Portugal).

Where are you at?


What server are you using?

Jigsaw? Grinder? Own server?

The problem is with Roomba and Husqwarna (two robot on my home). I try yesterday to integrate the Roomba on ifttt and the error is the same.

In my case I use the RPC/API/setvalue.

My applet worked fine for a year and suddenly I have this error.

I have the beta version 4.7.30 and the server is mine but identically same of Grinder (Intel NUC).

I try with Callfunction for testing, but is the same issue.

Comfortclik support have you an idea about this issue ?

Under review

Hello,

you mentioned you started having this errors 2-3 months ago? Do you remember if they started after you updated bOS ?

We tested RPC/IFTTT using webhooks to control devices in the office using the latest bOS beta version and everything checks out and everything is working here.

Looking trough the update notes for our betas, there weren't any changes done on the RPC service so the communication should be working normally.

You tested directly roomba/IFTTT and you get the same results?


Best regards.