-
-
Notifications
You must be signed in to change notification settings - Fork 20
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
AC changes mac address?? #306
Comments
Hi there.
That's interesting. Can you run the discover command with the
This could be caused by a few things. One thing to try is the Can't say anything about the MAC addresses. That's an odd one for sure. |
Thanks for taking a look. Sure:
I tried tuning the |
This is the bigger problem. Try setting a different cloud region or using another username & password. |
Not sure is it is the same problem, but my "Midea" airconditioners stop woking a couple of days ago: they became not available (it happened a week ago too, and I thought it was because the IP addresses changed: I deleted them from HA integration, rediscoverd and they worked again) and, after deleted them, I cannot add anymore: Midea Smart AC HACS integration found them, but I receive the message "unable to connect".
It finds 2 units, but they are 3 (yes, the third one is connected and available on the local network) This is the output with --debug option:
|
Hi, I've got a Midea AC unit and I've used this integration with mixed results. However, that is not due to this integration, but rather my AC unit I believe.
So why am I posting here? Because I hope that someone can help me with a solution..
This is my situation:
msmart-ng discover
always discovers my device and gives the following output:{'ip': '192.168.1.138', 'port': 6444, 'id': 208......, 'online': False, 'supported': False, 'type': <DeviceType.AIR_CONDITIONER: 172>, 'name': 'net_ac_F714', 'sn': '000000P0000000Q1502DBB58F7140000', 'key': None, 'token': None}
It says
'supported': False
. I am not sure why it says that, because the integration works fine when it finds my device.msmart-ng discover
and checking the contents ofhome-assistant-config/.storage/core.config_entries
. Sometimes this was a different IP address than whatmsmart-ng
reported. Changing the IP and restarting HA would make the device work again.Anyhow.. Has anyone encountered this issue before?
Or does anyone have any advice?
Unfortunately I cannot map 2 MAC addresses to the same IP..
Finally, apologies if this is not the place for my troubles. I can always close the issue, but any help or thoughts would be appreciated regardless.
The text was updated successfully, but these errors were encountered: