Unless you really need to use POST or PUT, I suggest you configure the Webhook Trigger to accept a GET request. Once you confirmed it works, you can optionally switch it back to PUT or POST but then you will need to use curl or some other means of producing a POST/PUT request.
I saw the ‘curl’ bit but I don’t understand how that can be used or embedded into a URL.
If it was a QR Code, how would a mobile device scan that and process it accordingly?
Webhooks support HTTP POST, PUT, HEAD, and GET requests; PUT requests are recommended. HTTP GET and HEAD requests are not enabled by default but can be enabled by adding them to the allowed_methods option.
That ‘kind of’ works, the automation gets triggered but also initiates a file download, while I appreciate this is likely to be part of the ‘GET’ process as it’s asking to get/retrieve information and the browser interprets this as a download or something, I can see this being a bit concerning to guests if they don’t know what it is.
Anyone know of how to get around this or a better way of achieving this?
Thanks very much
The idea is that a guest scans a QR Code to trigger the automation but I DON’T want people to have to install the companion app or login to anything just to trigger an automation.
If I could setup a dashboard with various things (turn heating on, change lights brightness etc) on it which could be interacted with without having to login, that might be another option.
If this was possible, I’d want to limit the max temperature that the heating could be set to.
This automation for the heating I want specifically as I don’t want the heating left on when guests leave so the automation will turn it off after X hours