I have no experience with the Hubitat or the Hydrawise, but ideally the response for an auth issue should be a 401 or 403 and not the 404 that you're seeing.? A 404 is supposed to indicate an issue in the URL string.? However, it could be worth a try to leave off the access_token URL parameter (and/or supply a bogus value) on the Crestron call and see if a 404 is still returned.? If the response changes to a 401 or 403 then you have some confidence that you're not dealing with an auth issue with your access_token.? Also, may want to try the browser calling the URL without the access_token and compare that with Crestron calling the URL without access_token to see if there's a difference in response/behavior between the two in that scenario.??

I've seen some equipment that needed certain headers before playing nice, so another suggestion would be adding some of the headers that aren't currently being sent from the Crestron call.? To help with issues like this I tend to use the curl command from a command prompt instead of the browser when troubleshooting.? If a basic curl command with no headers works, then I would suspect something in how the Crestron program is formatting the command and at that point you could try comparing the curl call vs the Crestron call (with the webhooks site or wireshark) without the noise of the additional headers that the browser introduced.? If curl also fails when you use it without headers, then could try adding the headers one by one that the web browser is sending.??

Good luck!

On Sunday, August 1, 2021, 08:58:36 AM CDT, Wyatt J <wyatt@...> wrote:

I have been messing with some HTTP stuff recently myself.? I've found the best thing is to run wireshark on the system with the browser and see what the traffic back and forth looks like.? In my case the device was doing digest authentication, which is impossible to deal with without S#.