Ken, this is a very old post, and since then the time on the website has local UTC setting. When looking at the data on http://www.uradmonitor.com it will now show it in your local timezone.

Years ago, there was server generated charts with hardcoded timezones.

Hello Ken, thanks for the detailed observations.

Given all the above and your other posts, it seems that there is an issue that we still don’t clearly understand. Please keep in mind that the FW running on your unit is stable and there are multiple other units using it with no reported issues. This is why I would like you do run another test, and connect your unit to a separate network . Either give it to a friend, or create a small separate network (via GSM, etc). Please connect it to this separate setup to rule out this direction. Yes, I fully understand that you have other devices using it, but it is important to understand more.

If the unit reboots frequently, it can impact the CO2’s sensor autocalibration that runs on an internal timer.. I’d try to get the A3 to run stable first.

Not sure what happened, but thanks for taking the time to explain everything again. This is actually extremely helpful . Here is what I know from you:

– device starts and connects to your WIFI router, following your initial SSID+WIFI KEY configuration
– device presents it’s internal webpage , accessible via the LAN IP (this is what we call the router allocated IP in your local network)
– the device reboots

This information tells me the following:
– device connectivity works
– device sensors work (as you saw the data on the internal webpage)
This is consistent with my expectations, as the device was tested prior to being shipped to you. Also since it is a digital device, partial failures are impossible. All device functionality is ok.

The problem:
– the device reboots

The solution:
The problem is caused by the device internal watchdog. This is a special kind of timer, displayed in the local web interface as “WDT” . You will see it gradually increase to a top limit where the reboot happens. The watchdog itself needs to be periodically reset (petting the dog), to prevent it from rebooting.
It’s role is to protect the correct functionality of automated devices and trigger reboots when such hardware is in a deadlock or any other unrecoverable state, to limit human intervention and maintenance.

The reason for why the watchdog is not reset and it eventually reaches the top limit and resets is related to the successful sending of the data. The data simply doesn’t reach the server . The server will not send an acknoledgement . The watchdog will see no successful response and will continue to increase until reboot when the entire things starts over. On the internal webpage you will see a “Stats” field, with the number of succesful data sends / total data sends. First will most likely be 0 in your case.

Why this happens is related to the security settings in your network. You’ll need to connect to your router and rule out anything that might be blocking the A3 communication. A3 sends data by doing simple HTTP Posts, equivalent to a browser opening a webpage. The destination is port 80 on data.uradmonitor.com , make sure your router allows this.
You will also need to do a separate test, where you create a Wifi hotspot on your phone, and have the A3 connected to that, to rule out any other problems created by your main WIFI Router.

Again, your A3 has all its modules operational (sensors + wifi) , yet it keeps on rebooting and the data it sends is blocked.

Waiting for your results!

Hi! Yes, the older units didn’t offer an USB port . So for them you would need to flash a new firmware to do any changes : https://www.uradmonitor.com/firmware-upgrade-guide/

No, the 2 units are demo units so everyone can try out the API / Data access , including those that have no units.

But I can add two other units of your choice to your account, manually, just let me know the IDs.

Thanks

hi Ken,

This might be caused by some security settings on your router.

Please try one of the following:
– enable DMZ for your A3 on your router
– connect the A3 to a different network / router to see if this happens again.

From what you are saying it seems that the unit reboots periodically (triggered by the internal watchdog) due to network communication errors.

Radu