merdok / homebridge-miot

Homebridge plugin for devices supporting the Xiaomi miot protocol
MIT License
371 stars 62 forks source link

Dreame Robot Vacuum: Total clean time is wrong - minutes are interpreted as hours #458

Closed ufkel closed 1 year ago

ufkel commented 1 year ago

Describe the bug Fresh install of a Dreame vacuum robot. The robot did its very first test run, which took about 10 minutes. The Xiaomi Home App shows a total runtime of 10 minutes. All is good so far. During restart of Homebridge, the Log tells "Total clean time: 10 hours." instead of 10 minutes.

Expected behavior The Homebridge Log should correctly report "Total clean time: 10 minutes."

Your config.json { "name": "NAME", "ip": "192.168.178.200", "token": "TOKEN", "deviceId": "ID", "model": "dreame.vacuum.r2228o", "pollingInterval": 10, "deepDebugLog": false, "buzzerControl": true, "ledControl": true, "childLockControl": true, "modeControl": false } Debug log [3/23/2023, 10:20:12 AM] [homebridge-miot] [NAME] Device found! Setting up miot device from local connection! [3/23/2023, 10:20:12 AM] [homebridge-miot] [NAME] Connected to device: dreame.vacuum.r2228o [3/23/2023, 10:20:12 AM] [homebridge-miot] [NAME] Doing initial property fetch. [3/23/2023, 10:20:12 AM] [homebridge-miot] [NAME] Main brush left time: 299 hours. [3/23/2023, 10:20:12 AM] [homebridge-miot] [NAME] Main brush life level: 99%. [3/23/2023, 10:20:12 AM] [homebridge-miot] [NAME] Filter life level: 99%. [3/23/2023, 10:20:12 AM] [homebridge-miot] [NAME] Total clean time: 10 hours. [3/23/2023, 10:20:12 AM] [homebridge-miot] [NAME] Total cleaned: 1 times. [3/23/2023, 10:20:12 AM] [homebridge-miot] [NAME] Total clean area: 10 m2. [3/23/2023, 10:20:12 AM] [homebridge-miot] [NAME] Starting property polling.

merdok commented 1 year ago

Thanks for reporting, will check that out. The unit detection might have a bug...

ufkel commented 1 year ago

Great! If there is anything I can do to assist you, just let me know.

merdok commented 1 year ago

Thanks, but it should be a straight forward fix!

merdok commented 1 year ago

Should be fixed in 1.6.0

ufkel commented 1 year ago

Yep. It is fixed in 1.6.0. Thank you for the very fast reaction.