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

Warning message from HA suggesting alternative call #216

Open
ryanandres opened this issue Jul 15, 2023 · 10 comments
Open

Warning message from HA suggesting alternative call #216

ryanandres opened this issue Jul 15, 2023 · 10 comments

Comments

@ryanandres
Copy link

**Describe the bug **
Warning message from HA suggesting alternative call

**Screenshots / Logs / Pcap File **
Logger: homeassistant.helpers.entity
Source: helpers/entity.py:565
First occurred: 10:24:17 AM (1 occurrences)
Last logged: 10:24:17 AM

Entity climate.garage_ac (<class 'custom_components.midea_ac.climate.MideaClimateACDevice'>) is using self.async_update_ha_state(), without enabling force_update. Instead it should use self.async_write_ha_state(), please report it to the custom integration author.

Versions (版本信息)

  • Home Assistant version: 2023.6.3
  • Midea msmart version: 0.2.3
@mill1000
Copy link

This issue is resolved in my updated fork mill1000/midea-ac-py

@ryanandres
Copy link
Author

Excellent! I just switched over. Thank you!

@mill1000
Copy link

mill1000 commented Jul 15, 2023

Make sure you update msmart as well to get all the features.

e.g. In your HA system/container/env

pip install git+https://github.com/mill1000/midea-msmart.git

@ryanandres
Copy link
Author

Make sure you update msmart as well to get all the features.

e.g. In your HA system/container/env

pip install git+https://github.com/mill1000/midea-msmart.git@future

I did this and now my cool mode is not an option in the drop down

SmartSelect_20230715_120542_Home Assistant.jpg

@mill1000
Copy link

Ah, that can happen if (for some reason) the device doesn't report the correct capabilities.

You can work around this by manually adding the cool mode in the integration configuration like so
image

@ryanandres
Copy link
Author

That worked! And no warnings or errors in my logs.

Off topic, but have you fixed the issue with devices being unresponsive due to having multiple client instances?

In my case I'm using Carrier's app and HA... #95 (comment)

@mill1000
Copy link

Unfortunately, most of the underlying network code is unchanged so this will probably still be an issue

What are you using the carrier app for that this extension can't do?

@ryanandres
Copy link
Author

I'm using it to configure schedules and I'm not aware of this extension supporting it.

@ryanandres
Copy link
Author

I know that sounds idiotic considering I can use HA to automate my own schedules. Now I'm trying to recall exactly why I relied on the carrier app... I think a while ago the extension or my system was not reliable so I depended on carrier's cloud service. I need to reconsider this

@mill1000
Copy link

| I'm using it to configure schedules and I'm not aware of this extension supporting it.
...
| I know that sounds idiotic considering I can use HA to automate my own schedules. Now I'm trying to recall exactly why I relied on the carrier app... I think a while ago the extension or my system was not reliable so I depended on carrier's cloud service. I need to reconsider this

Hahaha that's alright. Might be worth ditching the Carrier app for a little bit just to see if it makes the integration more reliable. If its still flaky then the integration won't be of much use will it.

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

No branches or pull requests

2 participants