Page 1 of 1

Incorrect time showing

Posted: 05 Jul 2020, 14:32
by RobNor
From about 11am this morning the time on MyNetatmo dashboard is about 1.5hrs behind. I have checked that my station is set to London time and it’s correct. I have checked other UK stations on the map and most are at the correct time but a number are around 1.5 hrs behind. Data is being recorded and updated it’s just the time that is wrong

Re: Incorrect time showing

Posted: 05 Jul 2020, 14:54
by whitesnuf
You are not alone, happens to many stations at the moment

Re: Incorrect time showing

Posted: 05 Jul 2020, 15:03
by RobNor
Where are you?

Re: Incorrect time showing

Posted: 05 Jul 2020, 16:51
by whitesnuf
Southern Germany

Re: Incorrect time showing

Posted: 05 Jul 2020, 17:14
by vegard@engen.priv.no
Is this data that is lagging with update or is it data that is there but with timestamp wrong?

I have the same issue.

This is a raw getstationdata call (in a python structure):

Code: Select all

'_id': '70:ee:50:64:25:56', 'station_name': 'KlauvsteinenAV', 'date_setup': 1592315736, 'last_setup': 1592315736, 'type': 'NAMain', 'last_status_store': 1593961553, 'module_name': 'Indoor', 'firmware': 178, 'wifi_status': 33, 'reachable': True, 'co2_calibrating': False, 'data_type': ['Temperature', 'CO2', 'Humidity', 'Noise', 'Pressure'], 'place': {'altitude': 170, 'city': 'Bergen', 'country': 'NO', 'timezone': 'Europe/Oslo', 'location': [5.306777220438363, 60.371132509556816]}, 'dashboard_data': {'time_utc': 1593959134, 'Temperature': 25.8, 'CO2': 910, 'Humidity': 57, 'Noise': 69, 'Pressure': 985.6, 'AbsolutePressure': 965.9, 'min_temp': 23.5, 'max_temp': 25.8, 'date_max_temp': 1593959134, 'date_min_temp': 1593936468, 'pressure_trend': 'down'}, 'modules': [{'_id': '02:00:00:64:1c:62', 'type': 'NAModule1', 'module_name': 'Outdoor', 'last_setup': 1592315740, 'data_type': ['Temperature', 'Humidity'], 'battery_percent': 100, 'reachable': True, 'firmware': 50, 'last_message': 1593961548, 'last_seen': 1593961542, 'rf_status': 70, 'battery_vp': 6074, 'dashboard_data': {'time_utc': 1593959132, 'Temperature': 12.6, 'Humidity': 94, 'min_temp': 11.5, 'max_temp': 12.8, 'date_max_temp': 1593924372, 'date_min_temp': 1593907709}}, {'_id': '05:00:00:07:3b:be', 'type': 'NAModule3', 'module_name': 'Regnmåler', 'last_setup': 1592914803, 'data_type': ['Rain'], 'battery_percent': 100, 'reachable': True, 'firmware': 12, 'last_message': 1593961548, 'last_seen': 1593961548, 'rf_status': 82, 'battery_vp': 6162, 'dashboard_data': {'time_utc': 1593959126, 'Rain': 0.202, 'sum_rain_1': 0.6060000000000001, 'sum_rain_24': 22.6}}]}
Notice that time_utc on the various dashboard_data entries are way behind last seen. time_utc updates, though, over time, and I get new data.

Re: Incorrect time showing

Posted: 05 Jul 2020, 17:18
by RobNor
vegard@engen.priv.no wrote:
05 Jul 2020, 17:14
Is this data that is lagging with update or is it data that is there but with timestamp wrong?

I have the same issue.

This is a raw getstationdata call (in a python structure):

Code: Select all

'_id': '70:ee:50:64:25:56', 'station_name': 'KlauvsteinenAV', 'date_setup': 1592315736, 'last_setup': 1592315736, 'type': 'NAMain', 'last_status_store': 1593961553, 'module_name': 'Indoor', 'firmware': 178, 'wifi_status': 33, 'reachable': True, 'co2_calibrating': False, 'data_type': ['Temperature', 'CO2', 'Humidity', 'Noise', 'Pressure'], 'place': {'altitude': 170, 'city': 'Bergen', 'country': 'NO', 'timezone': 'Europe/Oslo', 'location': [5.306777220438363, 60.371132509556816]}, 'dashboard_data': {'time_utc': 1593959134, 'Temperature': 25.8, 'CO2': 910, 'Humidity': 57, 'Noise': 69, 'Pressure': 985.6, 'AbsolutePressure': 965.9, 'min_temp': 23.5, 'max_temp': 25.8, 'date_max_temp': 1593959134, 'date_min_temp': 1593936468, 'pressure_trend': 'down'}, 'modules': [{'_id': '02:00:00:64:1c:62', 'type': 'NAModule1', 'module_name': 'Outdoor', 'last_setup': 1592315740, 'data_type': ['Temperature', 'Humidity'], 'battery_percent': 100, 'reachable': True, 'firmware': 50, 'last_message': 1593961548, 'last_seen': 1593961542, 'rf_status': 70, 'battery_vp': 6074, 'dashboard_data': {'time_utc': 1593959132, 'Temperature': 12.6, 'Humidity': 94, 'min_temp': 11.5, 'max_temp': 12.8, 'date_max_temp': 1593924372, 'date_min_temp': 1593907709}}, {'_id': '05:00:00:07:3b:be', 'type': 'NAModule3', 'module_name': 'Regnmåler', 'last_setup': 1592914803, 'data_type': ['Rain'], 'battery_percent': 100, 'reachable': True, 'firmware': 12, 'last_message': 1593961548, 'last_seen': 1593961548, 'rf_status': 82, 'battery_vp': 6162, 'dashboard_data': {'time_utc': 1593959126, 'Rain': 0.202, 'sum_rain_1': 0.6060000000000001, 'sum_rain_24': 22.6}}]}
Notice that time_utc on the various dashboard_data entries are way behind last seen. time_utc updates, though, over time, and I get new data.
It’s the time stamp that’s behind although it’s catching up, it’s now only 45mins behind rather than 90mins

Re: Incorrect time showing

Posted: 05 Jul 2020, 18:40
by whitesnuf
For me the same, my station is at the moment approximately 30 minutes behind

Re: Data lagging behind for long periods of time

Posted: 09 Aug 2020, 16:00
by palsoft
It's lagging again. The data are almost 2 hours behind. I've experienced this problem for the first time

Re: Incorrect time showing

Posted: 09 Aug 2020, 19:09
by paulvanraven
Same over here 1 hour behind in the IOS app. Time in the andriod App is OK. Started 9-8-2020

Time 1 hour behind

Posted: 09 Aug 2020, 19:11
by paulvanraven
The time is constantly 1 hour behind related to the measurements. Timezone is Amsterdam, however measurement timings are minus 1 hour.