Viomi. Error while adjusting timezone to UTC

DuBass858 commented 3 years ago

Describe the bug

All the time the robot cannot set the correct time zone, therefore the time is not correct.

To Reproduce

After reboot you can see all the time

Screenshots

Vacuum Model

ViomiV7

Valetudo Version

2021.09.1

Expected behavior

The robot must set the correct time

Additional context

[2021-07-28T19:24:26.339Z] [DEBUG] local request 5009 set_timezone timed out [2021-07-28T19:24:26.343Z] [DEBUG] >>> local: {"method":"set_timezone","params":[0],"id":7011} [2021-07-28T19:24:26.908Z] [DEBUG] local request 6010 set_timezone timed out [2021-07-28T19:24:26.918Z] [DEBUG] >>> local: {"method":"set_timezone","params":[0],"id":8012} [2021-09-27T18:40:46.002Z] [INFO] Successfully set the robot time via NTP to 2021-09-27T18:40:46.894Z [2021-09-27T18:40:48.444Z] [WARN] Token is okay, however we're unable to reach the vacuum { retries: 10, method: 'set_timezone', args: [ 0 ] } [2021-07-28T19:24:40.509Z] [INFO] Cloud message timed out. Assuming that we're not connected anymore [2021-07-28T19:24:40.511Z] [ERROR] RobotMQTTHandle: Error while polling the robots state MiioTimeoutError: request timed out:{"method":"get_prop","params":["run_state","mode","err_state","battary_life","box_type","mop_type","s_time","s_area","suction_grade","water_grade","remember_map","has_map","is_mop","has_newmap","timezone"],"id":13} at Timeout.timeout [as _onTimeout] (/snapshot/Valetudo/backend/lib/miio/MiioSocket.js:210:32) at listOnTimeout (node:internal/timers:557:17) at processTimers (node:internal/timers:500:7) [2021-07-28T19:24:44.017Z] [INFO] Cloud connected [2021-07-28T19:25:12.786Z] [WARN] Error while adjusting timezone to UTC

DuBass858 commented 3 years ago

Valetudo Version 2021.10.0

[2021-07-28T19:24:45.674Z] [DEBUG] Starting NTP Query for { server: 'pool.ntp.org', port: 123, timeout: 10000 } [2021-07-28T19:24:45.733Z] [DEBUG] Got Time from NTP Server: 2021-10-02T09:41:53.894Z [2021-10-02T09:41:53.002Z] [INFO] Successfully set the robot time via NTP to 2021-10-02T09:41:53.894Z [2021-10-02T09:41:53.005Z] [DEBUG] Next NTP sync in 28800000 ms [2021-07-28T19:24:48.704Z] [DEBUG] local request 10016 set_timezone timed out [2021-07-28T19:24:48.713Z] [DEBUG] >>> local: {"method":"set_timezone","params":[0],"id":13019} [2021-07-28T19:24:49.826Z] [DEBUG] >>> cloud: {"method":"set_timezone","params":[0],"id":8} [2021-07-28T19:24:50.166Z] [DEBUG] GC forced at 51634176 bytes RSS freed 1654784 bytes of memory. [2021-07-28T19:24:50.169Z] [DEBUG] local request 11017 set_timezone timed out [2021-07-28T19:24:50.175Z] [DEBUG] >>> local: {"method":"set_timezone","params":[0],"id":14020} [2021-07-28T19:24:50.944Z] [DEBUG] local request 12018 set_timezone timed out [2021-07-28T19:24:50.947Z] [DEBUG] >>> local: {"method":"set_timezone","params":[0],"id":15021}

nekromant commented 2 years ago

Seeing this as well. So far looks harmless if you use it with Home Assistant. I wonder if it's related to #1086

DuBass858 commented 2 years ago

I don't use home assistant. ioBroker one love)))

nando83 commented 2 years ago

Valetudo Version 2021.11.0

I have de same issue:

[2021-10-06T08:47:41.033Z] [INFO] MQTT configured [2021-10-06T08:47:46.246Z] [WARN] Error while adjusting timezone to UTC [2021-10-24T04:27:07.001Z] [INFO] Successfully set the robot time via NTP to 2021-10-24T12:27:07.895Z [2021-10-06T08:48:16.161Z] [WARN] Error while adjusting timezone to UTC [2021-10-06T08:48:46.161Z] [WARN] Error while adjusting timezone to UTC [2021-10-06T08:49:16.160Z] [WARN] Error while adjusting timezone to UTC [2021-10-06T08:49:46.160Z] [WARN] Error while adjusting timezone to UTC [2021-10-06T08:50:16.165Z] [WARN] Error while adjusting timezone to UTC [2021-10-06T08:50:46.160Z] [WARN] Error while adjusting timezone to UTC

I try to change via UI and doesn't works.

Hypfer commented 2 years ago

https://github.com/Hypfer/Valetudo/issues/1156#issuecomment-1001695151

nekromant commented 2 years ago

@Hypfer Thanks, deploying these hacks to my robots!

Hypfer / Valetudo