IMILAB V1 Vacuuming Robot

[theundefined]

Device information

https://home.miot-spec.com/s/chuangmi.vacuum.hmi707

Home Assistant Device information

chuangmi.vacuum.hmi707
producent: chuangmi
oprogramowanie: 0.2.7_2510 (lan)

Checklist

• I have created a single PR per device. When you have multiple submissions please create separate PR's.
• For lights - I have only included the gzipped files (*.gz), not the raw CSV files.
• For lights - I have provided a CSV file per supported color mode. Look that up in Developer Tools -> States

Additional info

combined with two measurment - during first one power measure script did exception (and in normal use it's very hard to empty battery)

[bramstroker]

@theundefined cool, thanks for the contribution.

Do you have some graphs from HA entities both the vacuum and power sensor?
Similar as shared here: #639

Interested in how the vacuum is behaving after fully charged. And if the profile correctly represents that.

[theundefined]

Hello! I'ts more complicated here. There are two things missing in profile:

1. vacuum when goes to base every few dockings (not every time!) suck dust from robot to base. In that moment it increase own power for few seconds. It's directly after docking, and every 2-3 cleanings (depends on configuration):
   

next, after charging it look's like:

[theundefined]

combination of battery level and power from shelly

[theundefined]

hm. now when i look at it - it's more and more complicated:

• during cleanup phase - it take about 0.5-0.7W (robot it's not docked)
• when docking and sucking it takes ~700-800W (for about 10 seconds) - but only when suck. I don't see any changes in home assistant in that phase
• when docked and charging it takes ~20W
• After charging it slowly decrease taken power from 20W do ~3W for 40 minutes

[bramstroker]

Hmmm yes, it's complicated.

See my thoughts in the chart.
Sleep_power as referenced is used here: https://github.com/bramstroker/homeassistant-powercalc/blob/master/profile_library/harman%20kardon/HK%20Citation%20MultiBeam%20700/model.json#L27

It's not usable currently but might be a direction we can investigate.

For the sucking phase after dock I need to think about that, no obvious solution yet.
Might need to have a look at supporting composite strategy in model.json, that would provide much flexibility combining different strategies and conditions when a certain strategy applies.
Might also add some delay or duration stuff there, but that won't be an easy development.