Since it was my post, I will quote it. 
It's in the beta area. Have to be in the beta program to access.
does it work? I havent been able to get it to. what am im missing?
it works if i put it in the browser, but not in the rule.
You need to use port 8080. So:
Sent GET to: 192.168.1.82:8080/hub/.......(etc).
Because the hub can't send and receive on the same port (80) at the same time.
1 Like
of course
1 Like
@aaiyar still didn't work though. any other ideas?
Nope - I'm out of thoughts.
You might consider escaping the ampersands (so \& instead of &).
It probably won't work if you have hub security enabled, as RM had no way to send the auth cookie
1 Like
Yes. Just in case the & is throwing something off.
Correct. Although @BorrisTheCat mentioned he had it working via a browser URL, so I'm thinking he doesn't have hub authentication enabled.
http://...
?
1 Like
i have it enabled but it still worked in the browser. 
1 Like
Already tried that one. 
The browser has the auth cookie saved from a previous login, so it still works. @tony.fleisher had it nailed in his analysis.
3 Likes
Bruce said he was looking into a possible solution when I raised this previously :
3 Likes
I don't believe freeOSMemoryStatus exists anymore. However /hub/advanced/freeOSMemoryHistory may have replaced it.
2 Likes
I see it on my hubs....
404 Here.
1 Like
