- This topic has 3 replies, 2 voices, and was last updated 8 years, 7 months ago by .
Viewing 4 posts - 1 through 4 (of 4 total)
Viewing 4 posts - 1 through 4 (of 4 total)
- You must be logged in to reply to this topic.
When casually checking in on the status of my uradmonitor unit, i saw it’s been offline for nearly a month!
However, it was running just fine locally.
After cycling the power, the webinterface showed:
uRADMonitor 1200003F
type:1 hw:108 sw:110 SI-29BGradiation:0CPM
average:0.00CPM
temperature:9.50C
voltage:380V (29%)
uptime:25s
wdt:22s
ip:10.16.8.2
server:0.0.0.0
http:0
The “0.0.0.0” was bugging me.
After a bit of looking around in the logs, i found the issue.
Even though the unit has access to uradmonitor.com, data.uradmonitor.com and 8.8.8.8, i’ve recently added a line above that one in my firewall configuration explicitly blocking all DNS requests to any server outsite of my network.
TLDR: Let the device use the DNS server provided via DHCP, do not set it fixed to Google’s DNS servers. Thanks!
Also: 9.5 °C shown in webinterface but around 2.43 °C on website, the latter being the correct value. What’s going on?
Also: search function on forum redirects to a page showing the latest blog post.
Thanks for the excellent suggestions!
For the temperature, the components in your model A generate some extra heating. The server has a calibration / compensation layer , common across the various hardware models. This layer is adaptive. The correct value is the one returned by the server, this is why I encourage everyone to use the API for data access.
Very well.
Should’ve been something for me to be aware of.
As always, thank you for responding.
(can’t edit previous post)
Another option: add a DNAT rule to your router, changing any request to Google’s DNS servers into one to the local DNS server. The uradmonitor device will be none the wiser.