-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Today I had a power failure, and luckily everything came back up when I fixed it. However, a while later, I wondered if the probe had too, and it had not. The status page said it was up, but it hadn't reported data for about 6 hours (grey graphs). I assume I hit one of the problems in the FAQ: - --- Technical background: the probe tries to get current time indication using NTP upon booting, which sometimes fails. This causes the probe to think the curent date is November 1999, which confuses it a lot; it doesn't register properly or it sends measurement data for the twentieth century which is immediately discarded by the system. We plan to convince the probe to insist on vaild NTP or acquire some other time indication. The fix will be deployed in a firmware update. - --- Since the probe boots a lot faster than my gateway, I guess it never retried NTP. Powercycle fixed it indeed. So the lesson here is (at least until there is an update that retries ntpdate, or something), if the machine that provides your Internet connection takes a while to boot up, and they are both powered on at the same time, you may need to powercycle your probe. Jelte -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkz4HX0ACgkQ4nZCKsdOncVlXgCfZe+3FbLdTWTxCvXYZFrmaXjd TsEAn3vqmfjbUmWfueVcziCi2a3Hs6jF =zqNQ -----END PGP SIGNATURE-----