meteohub.de

I can get to other tabs of the application but the sensor page is solid white. Any clues?

FishAlaska wrote:I can get to other tabs of the application but the sensor page is solid white. Any clues?

Have you checked the meteohub log (&/or used Inspect Data to see if data is being recorded)?

If meteohub is having difficulty starting logging it prevent the sensors page from showing.

Try stopping logging (on the Maintenance page). Can you then see the Sensors page? If so, 'sanity check' the sensor settings, then if/when all is well try restarting logging.

Does that help?

I have a similar problem. In my case the maintenance page stays white. All other pages and functions are working. So, I am also open for suggestions

Tried to stop logging and no different. I can not access the sensor page. All data must be working becasue my wunderground page is working fine.

Maybe it is not working right. Here is the latest from the meteohub log under log files.

I thought the update was to fix logging?

logger (04.06.2009 15:31:31): station 0 (WMR-200), wrong checksum (0701 vs computed 02ce) for sensor model d7 in byte sequence: d7 10 2e 08 06 01 07 01 7c d4 16 2e 08 06 01 07
logger (04.06.2009 15:47:35): station 0 (WMR-200), wrong checksum (0701 vs computed 0200) for sensor model d3 in byte sequence: d3 10 02 09 06 01 07 00 0c d7 10 02 09 06 01 07
logger (04.06.2009 15:48:21): station 0 (WMR-200), wrong checksum (0701 vs computed 0330) for sensor model d7 in byte sequence: d7 10 03 09 06 01 07 40 fa d3 10 03 09 06 01 07
logger (04.06.2009 16:03:25): station 0 (WMR-200), wrong checksum (10d7 vs computed 039a) for sensor model d7 in byte sequence: d7 10 12 09 06 01 07 81 6b 01 06 46 80 d1 d7 10
logger (04.06.2009 16:04:27): station 0 (WMR-200), wrong checksum (0701 vs computed 034a) for sensor model d7 in byte sequence: d7 10 13 09 06 01 07 40 f4 d3 10 13 09 06 01 07
logger (04.06.2009 16:14:15): station 0 (WMR-200), wrong checksum (d732 vs computed 0132) for sensor model d4 in byte sequence: d4 16 1c 09 06 01 07 00 00 00 00 00 00 00 00 00 0c 01 01 07 32 d7
logger (04.06.2009 16:30:15): station 0 (WMR-200), wrong checksum (0701 vs computed 0243) for sensor model d6 in byte sequence: d6 0d 2d 09 06 01 d7 10 2d 09 06 01 07
logger (04.06.2009 17:00:25): station 0 (WMR-200), wrong checksum (0032 vs computed 0373) for sensor model d4 in byte sequence: d4 16 0f 0a 06 01 07 00 00 d7 10 0f 0a 06 01 07 40 f8 00 1c 32 00
logger (04.06.2009 17:22:45): station 0 (WMR-200), wrong checksum (0000 vs computed 020a) for sensor model d3 in byte sequence: d3 10 d4 16 25 0a 06 01 07 00 00 00 00 00 00 00
logger (04.06.2009 17:37:15): station 0 (WMR-200), wrong checksum (10d7 vs computed 0307) for sensor model d7 in byte sequence: d7 10 33 0a 06 01 07 80 fc 00 1d 3c 00 00 d7 10
logger (04.06.2009 17:39:05): station 0 (WMR-200), wrong checksum (8007 vs computed 020d) for sensor model d5 in byte sequence: d5 0a d7 10 36 0a 06 01 07 80
logger (04.06.2009 17:40:21): station 0 (WMR-200), wrong checksum (0000 vs computed 02f5) for sensor model d4 in byte sequence: d4 16 37 0a 06 01 07 00 00 d3 10 37 0a 06 01 07 08 0c 06 70 00 00
logger (04.06.2009 17:41:31): station 0 (WMR-200), wrong checksum (0c07 vs computed 026a) for sensor model d7 in byte sequence: d7 10 38 0a 06 01 07 d3 10 38 0a 06 01 07 07 0c
logger (04.06.2009 17:42:25): station 0 (WMR-200), wrong checksum (3910 vs computed 03f0) for sensor model d7 in byte sequence: d7 10 d1 d5 0a 39 0a 06 01 07 00 30 01 d7 10 39

I went ack to an older version and the settings page is fine now but here is my meteo log. It say WMR928 and I have a WMR200. What does all this mean? I cloned my stick to a new stick and am using the new stick.




wmr928eval (04.06.2009 19:03:25): illegal data record in line 73819 while reading from file /data/weather/200904/raw: hour1_uv0_index 6.8
wmr928eval (04.06.2009 19:03:25): illegal data record in line 73820 while reading from file /data/weather/200904/raw: hour1_uv0_indexmax_time 20090604120628
wmr928eval (04.06.2009 19:03:26): illegal data record in line 73821 while reading from file /data/weather/200904/raw: hour1_uv0_indexmax 8.0
wmr928eval (04.06.2009 19:03:26): illegal data record in line 73822 while reading from file /data/weather/200904/raw: wmr928eval (04.06.2009 19:03:26): illegal data record in line 73823 while reading from file /data/weather/200904/raw: seqmin1_th2_humidex_c 16.3_16.3_16.4_16.6_16.6_16.6_16.6_16.6_16.6_16.6_16.6_16.6_16.6_16.6_16.7_16.8_16.8_16.8_16.8_17.0_16.8_16.7_16.7_17.0_17.0_17.0_17.0_17.0_16.8_16.8_16.8_17.0_16.8_17.0_17.0_17.0_17.0_17.0_17.0_17.0_17.0_17.0_17.0_17.1_17.1_17.0_17.0_17.0_17.2_17.2_17.2_17.2_17.2_17.2_17.2_17.2_17.2_17.2_17.2_17.2_-_
wmr928eval (04.06.2009 19:03:26): illegal data record in line 73824 while reading from file /data/weather/200904/raw: seqmin1_uv0_index 0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_0.0_-_
wmr928eval (04.06.2009 19:03:26): illegal data record in line 73825 while reading from file /data/weather/200904/raw: wmr928eval (04.06.2009 19:03:26): illegal data record in line 74095 while reading from file /data/weather/200904/raw: 2009040505200020090325192000 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 4.7 0.0 3.3 0.0 0.0 0.0 0.0
wmr928eval (04.06.2009 19:03:27): illegal data record in line 77705 while reading from file /data/weather/200904/raw: 20090408067.1 867.0 868.0 1014.9 1014.7 1016.1 22.0 22.0 22.0 19.5 19.5 19.5
wmr928eval (04.06.2009 19:03:27): illegal data record in line 77950 while reading from file /data/weather/200904/raw: 200904050650A�

FishAlaska wrote:It say WMR928 and I have a WMR200.

wmr928eval is the name of one of the parts of Meteohub. The name is that way for "historical" reasons. Noawadays it gets used for much more than the WMR928, so the log entries that mention it are not strange in themselves.

FishAlaska wrote:I cloned my stick to a new stick and am using the new stick.

The error messages show corruption in the April 2009 raw data file and could have been carried across from the old stick by the cloning. and They might indicate that the old stick was starting to have problems (hopefully the new stick is fine!). The Cleanup Dataon the Inspect Data is a tool for repairing badly formatted raw data.

Borrowing and slightly adapting something Boris wrote a few days ago, here's a recipe:

1) stop data logging
2) goto "inspect data" page
3) select troubled month (2009-04)
4) press "cleanup data"
5) wait till finished
6) start data logging again
7) start recomputation