Report as GET parameters to HTTP

  • Hi

    I did enable " REPORT AS GET PARAMETERS TO HTTP" from the app, and set it to a php page that I own on a public website.

    But there is no help neither attached to the setting in the app, nor anything I can find on shelly websites.

    My web page logs GET and POST and HEADER, they are all empty, so how is the data attached to the request?

    thanks,

    Rod

    Einmal editiert, zuletzt von Black#Silence#5786 (17. Februar 2020 um 08:50)

    • Offizieller Beitrag

    Hi Rod,

    do you know the official MQTT & REST API description?:/

    You can find the link in our tips for beginners (# 3).;)

  • my question is about this setting

    "REPORT AS GET PARAMETERS TO HTTP"

    correct me if I'm wrong but this is not linked to those documentations.

    also is this setting/feature related to "REST API'? or "MQTT"? or is it something else?

    I put the shelly door/open device in an apartment that I rent with autonomous entry, so I can be warned when the guest arrives. I have a basic internet box, i can't expose the device from outside, so I can't make remote call, I don't want to put there a raspberry or whatever (like I have in my home for advanced automation) because guest will be in that apartment, not me.

    In this apartment I have other sensors from SONOFF and others, and they do have a Cloud where I can be notified by an event, and they do have an IFTT integration to receive those events and then use webhook to notify my web server. So that was easy.

    But SHELLY does not have such IFTTT integration to publish events to others (only the other way to allow others to send command to the device through shelly cloud).

    i can't connect directly to the device since I would have to expose the device to the internet and I can't.

    That's why I was very interested by the "REPORT AS GET PARAMETERS TO HTTP", it does connect to my web server every time there is an event, but without the info. Data/status is not attached. That's the only thing I miss :(

    I guess I could connect to shelly cloud when I receive the GET, but my guess is the time I connect to the cloud the event might have changed (like the door being closed right after being opened) and so the status will be wrongly reported.

    i looked here for HTTP request, but this device is not in the list:

    HTTP-Request - overview

    even here I don't see anything related to my device:

    https://shelly-api-docs.shelly.cloud/

    It is limited to this:

    Common MQTT commands

    [...]

    so do you see any means for this specific device to send events with data/status on a public IP:port?

    probably one way is to configure mqtt_server

    mqtt_server is your broker's address:port

    and just hope that my device support this even if not in the list of devices, and that it does not only report periodically state, but is also able to report an event as fast as it can when it happens.

    Since I can't connect from outside; I will have to go in the apartment to push my setting (when n,o guest inside) to send this command, and then hopefully I will get the status on my public website..

    It also seems I will loose Shelly CLoud by doing so, it is another reason why I thought the "REPORT AS GET PARAMETERS TO HTTP" parameter from the app would be nice by reporting events while still providing cloud access.

    thanks,

    Rod

    • Offizieller Beitrag

    Hi Rod,

    the Shelly D / W is relatively new and I think it's because it's not yet included in the official documentation.

    Indeed, Allterco should quickly add that.

    Unfortunately I don't work with MQTT myself.

    Still, I want to try to help you.

    Have a look at the screenshot in this post of my coupling to Homematic. Perhaps the trick will help you to enter your destination address there.

    I really hope so.

    Good luck. :thumbup:

  • Dieses Thema enthält 2 weitere Beiträge, die nur für registrierte Benutzer sichtbar sind, bitte registrieren Sie sich oder melden Sie sich an um diese lesen zu können.