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

Midea VRF Support #453

Closed
manunited10 opened this issue Jan 9, 2025 · 4 comments
Closed

Midea VRF Support #453

manunited10 opened this issue Jan 9, 2025 · 4 comments

Comments

@manunited10
Copy link

Device type and model (or SN)

WDC3-120T

The detail description of new feature

[Transferred from georgezhao2010/midea_ac_lan]

We recently installed a Midea MDV-V200WN1 system, which includes one outdoor unit and several indoor units (IDU). Additionally, we added a Wi-Fi wall controller (WDC3-120T), connected to one of the indoor units. The indoor units (IDUs) are linked to each other in a chain configuration (wifi controller is connected to IDU1, IDU1 is connected to IDU2, IDU2 is connected to IDU3 and so on; See 2nd figure below).

I successfully added the Wi-Fi controller to the SmartHome app, and it works fine. However, I dislike relying on online solutions, and I haven’t been able to connect it to my Home Assistant. I tried using this repository, but it doesn’t work with the Wi-Fi controller. In fact, none of its ports appear to be open.

Any advice would be greatly appreciated. I've attached some photos for reference.

Wifi controller:
wdc3-120t

Wifi controller wiring to IDUs:
Screenshot 2025-01-10 at 9 45 58 AM

Indoor and outdoor unit example:
midea-vrf

SmartHome app:
midea-mshome

Thank you in advance.

@manunited10 manunited10 added the enhancement New feature or request label Jan 9, 2025
@Issues-translate-bot
Copy link

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿


Title: Midea VRF Support

@wuwentao
Copy link
Owner

@manunited10
First of all, you should install currrent integration and discover your device, confirm the result in debug log and the discover result. if your device don't response to discover message, we can do nothing for it with this integration, as we don't know your device communication protocol.
if you device can response to discover message, we can check the detail and supported info with your device SN.

@manunited10
Copy link
Author

Thank you for your quick response.
Unfortunately, as of my tries, this integration is not able to do anything. I think this integration is trying to connect to port 6xxx (I forgot the exact port number) but that wall controller has no open port. I did some sniffing once, and looks like it opens a port (probably random) and establishes a connection to the remote. I have to verify what I said though.

@wuwentao
Copy link
Owner

wuwentao commented Jan 10, 2025

@manunited10 so we can confirm your device NOT support current protocol.
we can't use this integration for your device, as it using a unknown device protocol, we can't control or decode it.

if you want to control or communicate with your device, you should have a valid device protocol to do it, this is the root cause.

I will close this issue as current integration NOT support it. sorry

anyway, if there is any new progress and updates, we still can add comments in a closed issue.
thanks!

@wuwentao wuwentao added not_support and removed enhancement New feature or request labels Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants