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.

Sign up for GitHub

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

Jump to bottom

Dehumidifier tank status unknown #235

Open
Vetti52 opened this issue Jul 13, 2024 · 8 comments
Open

Dehumidifier tank status unknown #235

Vetti52 opened this issue Jul 13, 2024 · 8 comments
Labels
bug Something isn't working good first issue Good for newcomers

Comments

@Vetti52
Copy link

Vetti52 commented Jul 13, 2024

HA core version

2024.2.2

Current integration version

0.5.3

Last known working integration version

None

Device type and model

Dehumidifier 00000Q1A (161)

Working mobile app

Home Assistant

The description of problem

When looking into binary_sensor.DEVICE-ID_tank_full, I always see status „problem“, when the tank is full or „unknown“, when the tank is empty. Anyway, the status remained as „problem“ in both cases.
Therefore I currently ignore this binary sensor and use sensor.DEVICE-ID_tank instead, which gives at least 0%, or 100%, when full.
This was already the case, when I used the version of georgezhao. But, as I now realized, that you indeed continue to maintain this integration, I decided to mention it. Maybe, you will have a look at it.
Thanks.

The logs

Nothing to debug, no logs written
@Vetti52 Vetti52 added the bug Something isn't working label Jul 13, 2024
@chemelli74
Copy link
Collaborator

@Vetti52 thank you for reporting. Can you please join HomeAssistant on Discord and then contact me: chemelli74#2180

@chemelli74 chemelli74 added the good first issue Good for newcomers label Jul 13, 2024
@wuwentao wuwentao mentioned this issue Aug 16, 2024
Closed
@wuwentao
Copy link
Owner

just checked with the A1 device source code, tank_full result should based on tank and water_level_set, if you tank works well and water_level_set also works well, it should be works.

so why you not add any debug log for it?
please enable debug log based on README and attach the detail debug log.
thanks!

@Vetti52
Copy link
Author

Vetti52 commented Aug 20, 2024 via email

@chemelli74
Copy link
Collaborator

chemelli74 commented Aug 20, 2024 •
edited
Loading

Always attach logs and not paste the content otherwise it's hard to read them

@wuwentao
Copy link
Owner

thanks , please upload the log as file to current issue in future and not paste it.

in fact, just checked with your paste log line by line, I found your tank result is always 0.

and in this time, you may change the water_level from default 50% to 0, I'm not sure the reason, you have manual changed it ? the log and time as your log:

2024-08-20 18:00:22.156 DEBUG (Luftentfeuchter) [midealocal.devices.a1] Device - tank: 0, tank_full: False,                                      water_level: 50, tank_full_calculated: False
2024-08-20 18:00:22.156 DEBUG (Luftentfeuchter) [midealocal.devices.a1] Device after - new_status: {'tank_full': False, 'power': False, 'child_lock': False, 'mode': 'Auto', 'fan_speed': 'Medium', 'swing': False, 'target_humidity': 55, 'anion': False, 'tank': 0}, tank_full: False
2024-08-20 18:00:22.156 DEBUG (Luftentfeuchter) [midealocal.devices.a1] Device - tank: 0, tank_full: False,                                      water_level: 0, tank_full_calculated: False

after find out the water_level changed reason, we still need to check your tank value, as it always 0.
you should provide both log file to use:

  • log file and app info requirement 1: when tank_full is false, check the tank/water_level/tank_full value from midea app and share midea_ac_lan debug log to us.

  • log file and app info requirement 2: when tank_full is true, and also check the tank/water_level/tank_full value from midea app and share midea_ac_lan debug log to us

@wuwentao
Copy link
Owner

wuwentao commented Aug 28, 2024 •
edited
Loading

@Vetti52 any updates for this issue and debug log file ?
or you can directly provide us your device SN?

@Vetti52
Copy link
Author

Vetti52 commented Sep 19, 2024

Sorry, I did not follow this issue, because I was in contact with @chemelli74 at Discord, where he provided a solution for this issue. This solution seems to be included in the latest update. At least, the solution still works after updating to v0.5.7

@wuwentao
Copy link
Owner

@Vetti52 thanks, so we can consider there is no error exist with the latest version v0.5.7?
if yes, we will close this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working good first issue Good for newcomers
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@wuwentao @Vetti52 @chemelli74