It does look normal, but the header is missing. This results in the 400 Error code. The image shows a dash on each row. For other units there’s the user agent there.

What’s strange is that a few days ago, 11000016 was working fine . Did anything change in the network setup?

For Rick’s unit, 11000009 the problem was from the beginning.

But both units worked perfectly here, while running the tests.

Good idea. Support forum created and this topic moved.

Regarding the problem, I have investigated things further. Must say this seems to be an elusive bug and I have wasted a few hours to track it already.

Apparently the two units get to the server with their User Agent info stripped. Probably other parts of the packages are changed as well. Also the source IP is null. I don’t know what on their route changes their HTTP headers. Local tests didn’t show this issue, and it is impossible to consider a malfunction of any kind.

I can only assume a firewall would be able to have this intrusive result.

With the User Agent info removed and no source IP, the server denies the packages with a HTTP 400 Error code (Bad request).

I will see what I can do about this.

• This reply was modified 8 years, 9 months ago by uRADMonitor.

Here is a snapshot of the access log. Because the packets are not landing on data.uradmonitor.com, the server issues a HTTP 400.

As the unit is unable to get a valid reply, it auto-resets after 5 minutes. See the ts parameter, which is the local time of the unit in seconds, it never goes over 240 (=4×60 seconds, on the fifth it resets).

Two units are currently having this problem, 11000016 and 11000009 . I will find out why.

So I am correct in assuming that on routers that send it we have a problem, on those that don’t we’re fine.

I think you’re right Ben. And this makes it strange: to get inconsistent behaviour depending on the network!

I have a router that I know was causing some problems with uRADMonitor units. I’ll need to find it and run some tests before I can report back.

The DHCP code was mainly written by me, and in the last revision I added the hostname option (in the form uRADMonitor-). Previously you would only see the MAC, the allocated IP and no hostname. I might have done something wrong so hopefully things will clarify.

Another option is checking it against the Arduino implementation, but I find that complicated with all the Arduino libs and custom I/O code.

Looks great, Peter! Congrats on the nice installation.

I’m afraid there were no updates. So the change must have been local. Yes, currently there are several IP used. The one for data is correct: 23.239.13.18.

Lars, just as a note, I don’t think this is physical, nevertheless if you are unable to find the problem, you can send the unit back anytime to get a replacement.