I recently discovered that my HTTP GET requests are not executing despite the log files claiming they are.
I have some RM rules that incorporate GET requests on my C-7. I set these up some time ago and they had been running fine. I discovered this past week, though, they no longer appear to be working, although I can't say precisely when they stopped. The logs show the respective rules are being triggered as desired and the GET request is activating with no warnings or errors, but I don't see the results of those GET requests anywhere.
My primary use case is that I have a Flic hub with an attached IR blaster. A GET request to the hub fires an IR beam to a dumb air purifier to turn it on. The IR blaster still works when run manually, and a GET request through a browser activates it as well. (I can see it activated through their SDK in addition to the physical result of the air purifier turning on.) On the chance that it was a communication issue to the Flic hub and/or that particular address, I have tested other addresses of unrelated devices -- even using some local end points on the HE itself -- with the same non-result. They work when sent from a browser, but not from HE.
I also thought that it might be an issue with that specific rule where that Flic hub was called. I added a GET request to other existing rules (even a couple RM Legacy rules) and created an entirely new one with the GET request being the only action. All of the logs indicate when the rules are triggered, that the actions are run properly, and that there are no warnings or errors but the GET never seems to be actually sent.
I also thought it might be an issue with the latest platform version since that was updated fairly recently. But I've tried rolling back several iterations and I get the same non-result on 2.3.9.180, 2.3.9.177, 2.3.9.174, and 2.3.8.140.
I'm at a bit of a loss on what other troubleshooting I can do at this point. I'd welcome any suggestions on what else I can look at.
