Hi, did you get any replies on XYE or none? Can you make some photos of your unit? maybe you have an addressing issue - my controller seems to sweep adresses.
With the XYE interface, I get good replies on 0xC0 (Query) and 0xC3 (Set Command). For the extend set of commands 0xC4 (Query) and 0xC6 (Set/FollowMe) the replies have 0x00 or 0xFF in the data portions.
You will see on the motherboard that XYE is a valid connector/populated, just not responding in “extended mode”. As I would like follow me to work and get some other info like outside temp and current to name a few, I might have to dig into your UART interface with the display board.
There are a number of connectors that are not populated and 1 that is populated label CN19 (5 wire). I can seem to find any documentation/git/whatever that outlines these connectors. I’m assuming the labeling is pretty consistent across products/motherboard. Anyone have this documentation?
John
Hello,
would/could you provide full data samples of your requests and responses (full logs).
Then i may use some AI and transform then into my wireshark format to analyze it further.
Do you know if there is a compatible room controller for your device. Has you display another connector too?
Hey folks, I’m trying to get this going with my Carrier rebrand. Got my Atom S3 hooked up and been running a few different yamls with varying success but when trying to flash the one from github://mdrobnak/esphome@delays_updated
I get this error back:
Could not find __init__.py file for component midea_xye. Please check the component is defined by this source (search path: /data/external_components/b8c74471/esphome/components/midea_xye/__init__.py).
- midea_xye
refresh: 0s
Any idea what I’m doing wrong?
I have seen this with my version, do you have another thermostat connected to the system, if so, I suggest you disconnect it, otherwise the system will start getting conflitinc follow me requests.
Given that my system does not implement auto mode natively (it is implemented in the thermostat) and if both the ESp32 and the thermostat are connected, then follow me will start to get conflicting reports, I added a native Smart Thermostat implemented in HACS, so that I get the auto functionaly and presets all natively in home assistant: Release v0.0.2 · HomeOps/HASS-Smart-Climate
Do you have another Midea thermostat connected to the system?
@4SeasonsGuy : My installer gave me a HA/HB tstat that I am not using, my plan was to use it to reverse engineer the HA/HB protocol. DM me directly, I would gladly send my tstat for you to play with this.
I do but I have follow me turned off. I’m not actually having any issues with the setup anymore. I prefer to leave the OEM tstat “in the loop,” so to speak, because the Midea AC LAN integration has access to some stuff that these esphome projects do not, specifically the aux switch. I also like having an additional view into the system as a backup in case I run into weird issues with the esphome.
Also FWIW, my issues were not from the controllers squabbling over control, I think my main issue was actually just wifi signal strength. I added an antenna to my esp32 and most of the crazy temp fluctuations stopped. They only returned when I was on a stale version of the firmware from mdrobnak.
Hello people, I am trying to collect all the missing issues so that we can have a unified implmentation. I have collected all the issues here: Issues · HomeOps/ESPHome-Midea-XYE · GitHub
Can you all check them, let me know if you are missing something. It will help a lot if you could comment to see which ones should be solved first.
Thanks….
I do have a KJR-120N wired controller set up to the system via HA/HB. It does have a XYE 4 wire connector, however there is no 12v DC available on the motherboard of the air handler. The XYE connector on the motherboard is a screw connector so it does not appear to support (or want to support) a XYE interface in an extended mode. Base Set and Query commands are supported and other commands just return a “blank” or “default” response.
So no need for your controller. Thanks again though
John
I’ve been away and will get something to you soon in the next day or so.
John
Hello everyone. I am struggling for weeks now. All I do is reading and trying.
Can someone verify where my xye terminal is or if there is any other terminal to possibly use?
No wired controller. Trying with esp32+ max485 module and also tried with atom lite + 485 tail.
Nothing worked.
Model is hydronic fan coil unit midea mkt3-600g12-cl
Thank you
See where i has the and X and Y in brackets. thats it. Make sure the power to the unit is off before going near that board.
Thank you for your reply. I assume you mean D1(X) and D2(Y) and E at the CN2 terminal.
This is what I use. Tried all possible baudrates, swapping A and B etc but I can’t get it working. I get no responses at all.
AI says the unit needs a handshake to wake up which can only done with a wire controller connected.
I see here
that xye and pqe in ducted fcu’s are connected to a additional fcu kit as accessory and then this kit connects to the ducted unit, while in all other units pqe and xye are wired directly to the unit
The packet sequence are below. They are not EspHome data as right now im using my own esp32 firmware to test, play, experiment. It’s much faster for testing.
Set
16:01:49.088 1:3fcc0214 D (57504) *: 0x3fcb5990 aa c0 00 00 80 00 00 00 00 00 00 00 00 3f 81 55 |…?.U|
16:01:49.213 1:3fcbfbf0 D (57630) *: 0x3fcbf4e9 aa c0 80 00 00 00 40 14 84 84 46 47 59 ff 2e ff |…@…FGY…|
16:01:49.213 1:3fcbfbf0 D (57639) *: 0x3fcbf4f9 00 00 00 01 00 00 00 00 00 00 00 00 00 00 51 55 |…QU|
Query
16:02:19.115 1:3fcc0214 D (87523) *: 0x3fcb594c aa c3 00 00 00 00 84 84 45 00 00 00 00 3c b4 55 |…E…<.U|
16:02:19.253 1:3fcbfbf0 D (87681) *: 0x3fcbf4e9 aa c3 00 00 00 00 40 14 84 84 45 47 59 ff 2e ff |…@…EGY…|
16:02:19.253 1:3fcbfbf0 D (87681) *: 0x3fcbf4f9 00 00 00 01 00 00 00 00 00 00 00 00 00 00 cf 55 |…U|
Query - Extended
16:04:04.038 1:3fcc0214 D (192454) *: 0x3fcb5990 aa c4 00 00 80 00 00 00 00 00 00 00 00 3b 81 55 |…;.U|
16:04:04.176 1:3fcc0214 D (192603) *: 0x3fcbf4e9 aa c4 80 00 00 00 00 00 00 00 00 ff ff ff ff ff |…|
16:04:04.176 1:3fcc0214 D (192604) *: 0x3fcbf4f9 ff ff ff 00 00 00 00 00 00 00 00 ff 00 00 c5 55 |…U|
Sent you a private message - frames seems to be valid, but the response indicates issues. CRCs valid too 