I use reeftronics to log data from my ReefAngel for longer terms and also to provide a nice quick status and graph. I have been getting periodic "unable to connect" messages that say
"HTTP/1.1 401 Access Denied"
even though Reeftronics uses the /sa URL to bypass authentication in a read-only way.
Russ at Reeftronics also reports that he sometimes sees something like this in the response to /sa which looks to me like the GET request that should be talking to the portal.
GET /status/submitp.aspx?t1=800&t2=0&t3=0&ph=254&id=neuro&em=0&em1=0&rem=1&key=&af=1&sf=0&atohigh=0&atolow=0&r=55&ron=0&roff=2
The RA should definitely be sending GET requests as a response to an HTTP request. Is something odd going on with the WiFi libs when auth is turned on perhaps? I never started getting as many ReefTronics disconnects as when I enabled WiFi authentication.
I use reeftronics to log data from my ReefAngel for longer terms and also to provide a nice quick status and graph. I have been getting periodic "unable to connect" messages that say
"HTTP/1.1 401 Access Denied"
even though Reeftronics uses the /sa URL to bypass authentication in a read-only way.
Russ at Reeftronics also reports that he sometimes sees something like this in the response to /sa which looks to me like the GET request that should be talking to the portal.
GET /status/submitp.aspx?t1=800&t2=0&t3=0&ph=254&id=neuro&em=0&em1=0&rem=1&key=&af=1&sf=0&atohigh=0&atolow=0&r=55&ron=0&roff=2
The RA should definitely be sending GET requests as a response to an HTTP request. Is something odd going on with the WiFi libs when auth is turned on perhaps? I never started getting as many ReefTronics disconnects as when I enabled WiFi authentication.