Error messages in system log

Ok - I'm not sure what I did or if this is significant -
I'm getting the following error messages in the system log,
the daemon.err uhttpd[367] repeat a gazillion times, any ideas on how to remedy that?

on Apr 17 18:24:23 2017 kern.notice kernel: [ 16.908064] random: crng init done
Mon Apr 17 18:24:23 2017 user.err : RRD error: /tmp/hm.rrd: converting '' to float: Invalid argument
Mon Apr 17 18:26:05 2017 user.warn : New -1 peak @1492467964=697.9 half=0 per=0 amp=0.0 gain=0.0
Mon Apr 17 18:26:10 2017 user.warn : New 1 peak @1492467966=758.7 half=2 per=0 amp=60.8 gain=0.0
Mon Apr 17 18:30:12 2017 daemon.err uhttpd[367]: wc: /proc/net/nf_conntrack: No such file or directory
Mon Apr 17 18:30:12 2017 daemon.err uhttpd[367]: sysctl: error: 'net.nf_conntrack_max' is an unknown key

That's because something is polling the status page (the page you get to if you click the Status tab in the webui). The status page tries to see what "outgoing" connections are currently active, because the firmware is designed around being an internet router. HeaterMeter doesn't do NAT routing for connected clients, it is a client itself, so there are no connections to track. If you don't leave your browser on the status page, then you won't get the error.

Thanks for explaining Bryan!

There is some text in there from heatermeter though
HeaterMeter is constantly analyzing the data coming in and looking for trends. These are new peaks (the first is a low, the second is a high) with their corresponding temperatures, periods, half-periods (if the period is non-symmetrical) as well as the peak-to-peak amplitude and gain compared to the previous full period. If there is enough of a trend, PID coefficients are also calculated.

Use this to do PID tuning by setting I=0 and D=0 and picking a P value and following the instructions on the PID tuning page. You're looking for peaks with 0 gains and an amplitude of at least 5 degrees. Once you hit that proper P, just use the calculated I and D values and you're done! Theoretically. In practice I don't think it works all that well which is why there is no UI for it and also because it can take an hour or two given the slow reaction time of a smoker.