Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IMILAB V1 Vacuuming Robot #2797

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

theundefined
Copy link
Contributor

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
Copy link
Owner

@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
Copy link
Contributor Author

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):
    image

next, after charging it look's like:
image

@theundefined
Copy link
Contributor Author

image
combination of battery level and power from shelly

@theundefined
Copy link
Contributor Author

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

image

@bramstroker
Copy link
Owner

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.

Screenshot 2024-12-15 at 10 54 45

@Macstar1601
Copy link
Contributor

Very interesting. Yesterday I took the measurements via the script for a Xiaomi X10+ vacuum robot and made the same observations.

I performed the suction of the base station manually at 80%. It is approx. 950 watts for 3 seconds during suction. I think you have to add this value at the end of the charge. (e.g. at 99%). If you add it at the beginning, e.g. at 5% charge, then it would never be added if the battery is not so far discharged.

In my model.json the value is calculated as 9.51 watt at 100%. The trickle charge calculation was performed for 1800 seconds.
In this phase, the consumption dropped from 20.9 to 5.3 watts and averaged 9.51 watts. The 5.3 watts were reached after approx. 11 minutes. The 5.3 watts also correspond to the standby consumption of the station when the robot is in the station or when it is vacuuming.
I would therefore say that you should not add the average value at 100%, but at 99%. Otherwise, the calculation for standby is too high when the robot is in the station and the battery is 100% charged.

What do you think?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants