<RA>
<ID>ReefingHavoc</ID>
<T1>0</T1>
<T2>0</T2>
<T3>0</T3>
<PH>852</PH>
<R>0</R>
<RON>0</RON>
<ROFF>255</ROFF>
<R1>144</R1>
<RON1>0</RON1>
<ROFF1>255</ROFF1>
<R2>0</R2>
<RON2>0</RON2>
<ROFF2>255</ROFF2>
<R3>0</R3>
<RON3>0</RON3>
<ROFF3>255</ROFF3>
<R4>0</R4>
<RON4>0</RON4>
<ROFF4>255</ROFF4>
<R5>0</R5>
<RON5>0</RON5>
<ROFF5>255</ROFF5>
<R6>0</R6>
<RON6>0</RON6>
<ROFF6>255</ROFF6>
<R7>0</R7>
<RON7>0</RON7>
<ROFF7>255</ROFF7>
<R8>0</R8>
<RON8>0</RON8>
<ROFF8>255</ROFF8>
<ATOLOW>0</ATOLOW>
<ATOHIGH>0</ATOHIGH>
<EM>1</EM>
<EM1>6</EM1>
<REM>1</REM>
<BID>4</BID>
<AF>0</AF>
<SF>0</SF>
<PWMA>0</PWMA>
<PWMD>80</PWMD>
<PWMAO>255</PWMAO>
<PWMDO>255</PWMDO>
<PWMA2>0</PWMA2>
<PWMD2>0</PWMD2>
<PWMA2O>255</PWMA2O>
<PWMD2O>255</PWMD2O>
<DCM>4</DCM>
<DCS>80</DCS>
<DCD>100</DCD>
<DCT>30</DCT>
<LEAK>0</LEAK>
<ALARM>0</ALARM>
<PWME0>0</PWME0>
<PWME0O>255</PWME0O>
<PWME1>0</PWME1>
<PWME1O>255</PWME1O>
<PWME2>0</PWME2>
<PWME2O>255</PWME2O>
<PWME3>0</PWME3>
<PWME3O>255</PWME3O>
<PWME4>0</PWME4>
<PWME4O>255</PWME4O>
<PWME5>0</PWME5>
<PWME5O>255</PWME5O>
</RA>

More came through on the monitor:

Portal Call
Data Sent
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: text/html; charset=utf-8
Server: Microsoft-IIS/8.5
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
Date: Wed, 12 Sep 2018 00:19:33 GMT
Connection: close
Content-Length: 4

DoneDisconnected
Connecting...
Connected
HTTP/1.1 200 OK
Content-Type: text/html; charset=UTF-8
Server: Microsoft-IIS/8.5
X-Powered-By: PHP/5.6.24
Date: Wed, 12 Sep 2018 00:19:33 GMT
Connection: close
Content-Length: 0

Data: 0
Header: 0
Disconnected

Ok, so whatever you did a while ago made the controller connect to the portal.
status/chart.aspx?id=ReefingHavoc&filter=ph
You can see that it started sending data about half hour ago.
So, you should be able to set your email alerts now.
Try doing the remote upload again.

Thought I'd close the loop on this. I had my connection running through a patch panel that was connected to a AT&T U-verse router. I did some troubleshooting to determine where the problem was as when I connected the RA* directly to a Netgear router, everything seemed to work. Patch panel and all connections turned out to be fine. Tried running the patch panel to the Netgear instead of U-verse and miraculously I'm able to able to now upload remotely and updates hitting the portal. Strange...

ReefingHavoc wrote:Thought I'd close the loop on this. I had my connection running through a patch panel that was connected to a AT&T U-verse router. I did some troubleshooting to determine where the problem was as when I connected the RA* directly to a Netgear router, everything seemed to work. Patch panel and all connections turned out to be fine. Tried running the patch panel to the Netgear instead of U-verse and miraculously I'm able to able to now upload remotely and updates hitting the portal. Strange...

I guess it was too good to be true. I haven't touched the RA* since Sunday, but it looks like it stopped communicating yesterday (see attached)

Any thoughts on what is going on? The unit will connect for short periods of time and all of a sudden stop updating to the portal (still shows connected on the unit). I've tried swapping out power cables, ethernet cables, connecting to different routers, observing traffic through a serial monitor. Just today the unit had a black screen and unresponsive to touch. I had to reboot it by unplugging and when it did, saw that the temperature in the tank dropped by 3 degrees. The RA+ was rock solid for years; not sure why I'm having so many issues.

When you were watching the monitor, what did you get when it was not communicating?

rimai wrote:When you were watching the monitor, what did you get when it was not communicating?

I had it connected to a monitor for a couple hours and did not see issues, but when I plugged it back in to the power supply it stopped updating shortly after. I'll run a monitor on it for 24hrs to see what happens. The problem has been that my tank is in the basement and my PC is on the first floor so I have to disconnect the RA* from my system to monitor. I'll figure out how to keep it connected to the system with monitoring in place.

Thanks for the follow up

Mike

rimai wrote:When you were watching the monitor, what did you get when it was not communicating?

I ran the monitor for 24 hours and did capture a 400 error at the time the Portal stopped being updated.


Data: 0
Header: 0
Disconnected
Portal Call
Data Sent
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: text/html; charset=utf-8
Server: Microsoft-IIS/8.5
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
Date: Sun, 23 Sep 2018 14:20:17 GMT - This is the time when Portal last updated
Connection: close
Content-Length: 4

DoneDisconnected
Connecting...
Connected
HTTP/1.1 200 OK
Content-Type: text/html; charset=UTF-8
Server: Microsoft-IIS/8.5
X-Powered-By: PHP/5.6.24
Date: Sun, 23 Sep 2018 14:20:18 GMT
Connection: close
Content-Length: 0

Data: 0
Header: 0
Disconnected
Portal Call
Actinic 2Data Sent
Actinic 2HTTP/1.1 400 Bad Request
Content-Type: text/html; charset=us-ascii
Server: Microsoft-HTTPAPI/2.0
Date: Sun, 23 Sep 2018 14:25:18 GMT
Connection: close
Content-Length: 311

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd">
<HTML><HEAD><TITLE>Bad Request</TITLE>
<META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii"></HEAD>
<BODY><h2>Bad Request</h2>
<hr><p>HTTP Error 400. The request is badly formed.</p>
</BODY></HTML>
ÿDisconnected
Actinic 2Connecting...
Actinic 2Connected
Actinic 2HTTP/1.1 400 Bad Request
Content-Type: text/html; charset=us-ascii
Server: Microsoft-HTTPAPI/2.0
Date: Sun, 23 Sep 2018 14:25:19 GMT
Connection: close
Content-Length: 339

Data: 339
Actinic 2Header: 0
Actinic 2Disconnected
Actinic 2Portal Call
Actinic 2Data Sent
Actinic 2HTTP/1.1 400 Bad Request
Content-Type: text/html; charset=us-ascii
Server: Microsoft-HTTPAPI/2.0
Date: Sun, 23 Sep 2018 14:30:19 GMT
Connection: close
Content-Length: 311

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd">
<HTML><HEAD><TITLE>Bad Request</TITLE>
<META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii"></HEAD>
<BODY><h2>Bad Request</h2>
<hr><p>HTTP Error 400. The request is badly formed.</p>
</BODY></HTML>
ÿDisconnected
Actinic 2Connecting...
Actinic 2Connected
Actinic 2HTTP/1.1 400 Bad Request
Content-Type: text/html; charset=us-ascii
Server: Microsoft-HTTPAPI/2.0
Date: Sun, 23 Sep 2018 14:30:20 GMT
Connection: close
Content-Length: 339

Data: 339
Actinic 2Header: 0
Actinic 2Disconnected
Actinic 2Portal Call
Actinic 2Data Sent
Actinic 2HTTP/1.1 400 Bad Request
Content-Type: text/html; charset=us-ascii
Server: Microsoft-HTTPAPI/2.0
Date: Sun, 23 Sep 2018 14:35:20 GMT
Connection: close
Content-Length: 311

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd">
<HTML><HEAD><TITLE>Bad Request</TITLE>
<META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii"></HEAD>
<BODY><h2>Bad Request</h2>
<hr><p>HTTP Error 400. The request is badly formed.</p>
</BODY></HTML>
ÿDisconnected
Actinic 2Connecting...
Actinic 2Connected
Actinic 2HTTP/1.1 400 Bad Request
Content-Type: text/html; charset=us-ascii
Server: Microsoft-HTTPAPI/2.0
Date: Sun, 23 Sep 2018 14:35:21 GMT
Connection: close
Content-Length: 339

Data: 339
Actinic 2Header: 0
Actinic 2Disconnected
Actinic 2Portal Call
Actinic 2Data Sent
Actinic 2HTTP/1.1 400 Bad Request
Content-Type: text/html; charset=us-ascii
Server: Microsoft-HTTPAPI/2.0
Date: Sun, 23 Sep 2018 14:40:21 GMT
Connection: close
Content-Length: 311

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd">
<HTML><HEAD><TITLE>Bad Request</TITLE>
<META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii"></HEAD>
<BODY><h2>Bad Request</h2>
<hr><p>HTTP Error 400. The request is badly formed.</p>
</BODY></HTML>
ÿDisconnected
Actinic 2Connecting...
Actinic 2Connected
Actinic 2HTTP/1.1 400 Bad Request
Content-Type: text/html; charset=us-ascii
Server: Microsoft-HTTPAPI/2.0
Date: Sun, 23 Sep 2018 14:40:22 GMT
Connection: close
Content-Length: 339




The 400 error captured repeats until 6 PM EST when I disconnected the monitor

Any thoughts on the 400 error?