[NonNASA] F1/F2 users

[lanwin]

I you are have a non NASA System and use the connection between outdoor and indoor units (F1/F2) then please let me know here.

My plan is to have a list of users who are willing to give feedback or test if something works.

[TCB13]

Count me in!

[matthias882]

Here I am, an non-NASA user on F1/F2 Bus :)

[ukw6]

+1

[Goaheadz]

Able to help and test progress.
RJ100F5HXBA - Non-NASA - 5 splits outdoor able (only using 3 at the moment)

RX is working ok (I can see changes in HA) when pressing remote.

Would like to see data out in log window (TX led does not blink), to be sure it is connected properly before moving frwd.
I do have:
debug: direction: TX dummy_receiver: false after: delimiter: "\n" sequence: - lambda: UARTDebug::log_string(direction, bytes);

@ukw6 I have the same HW setup as you (ESP+TTL->RS485).
Do you see TX led blinking when sending HA commands? or do I have a connection problem?

[TCB13]

(12V to 5V very expensive module

Mine also runs on a very expensive module ... https://www.aliexpress.com/item/1005005393995240.html 😆

[Goaheadz]

I just use what I have laying around...overkill!

https://www.digikey.pt/en/products/detail/delta-electronics/DCL12S0A0S20NFA/4318401
(I know I can change it to 3.3V, just dont have the correct resistor to config trim)
14€ and 20A capable xD

[TCB13]

Oh yes, that's a decent module indeed but the fact that is surface mount makes me cry.

[Goaheadz]

Not related to this subject, but may help others:
Reading some documentation:
TTL-RS485

D1 Mini:

Pin-out:

The issue related to my d1 mini not booting when tx is connected is due to:
D8 must be pull-down at boot, and TTL-RS485 board has a pull-up build-in. (10K up and 10K down is half voltage)

As soon as I get home, I will try to use D3, D1 or D2, D1 pins for TX and RX.

(And yes I cannot use build in uart GPIO1 GPIO3 cause it fails when I connect RX side...Gremlin's hidden)

[matthias882]

For power supply I use this cheap power supply shield for wemos d1 Mini

DC Power Shield V1.1.0 for wemos D1 mini development board DC power supply screen module
https://a.aliexpress.com/_ExMSBov

[Goaheadz]

Now back to the non-NASA.

It works!!! finally.(even with no tx led ligth)

I can control , power, mode, temp and fan speed. for 3 diferent spliters attached to one outdoor machine.
I think last changes you guys did to the code, solve it. thx guys.

Only thing missing is blade direction option, but not very important at the moment.

I will focus now in the HW (also waiting for a esp32 from aliexpress)
I need to solve the non boot when tx is connected.

yuipy!!!

[TCB13]

Blade movement discussion here: #76

[buzurk26]

Yep, Non-nasa here and from last changes it all works

[matthias882]

made the PR #86
there are many fancy values from outdoor unit decoded:

state 4way valve
state hot gas bypass
state compressor
state ac fan
state bldc fan
outdoor temp
discharge temp
condenser mid temp
sump temp
some error-codes and -bits
inverter order frequency
inverter target frequency
inverter current frequency
and the values of the EEVs (don't know the unit, but in my system a value of 480 is fully open, 0 is fully closed)

for now the values are only shown in the log, connection to the esphome-api is tbd

[Rebem13]

I'm a non-NASA user and happy to help with testing.

Strangely yesterday's updates have broken my AC control. It was working really well up until I updated about 18 hours ago and now the controls are still there but actioning anything has no effect on the unit. I'm still working through the issue but it's odd that the change that fixed others has broken mine.

[TCB13]

it's odd that the change that fixed others has broken mine.

I'm not sure mine isn't broken if I use the latest version. More: #87 (comment)

[Goaheadz]

Any news regarding outside temperature sensor being made available for Home Assistant?
I think would be usefull for everyone, since it can be used for other automations.

[lanwin]

Can you please create a separate feature request issue. Its hard to keep track otherwise.

[dansck]

+1

[zombie4000]

non-NASA user here as well with F1/F2

[jszkiela72]

I have a non-Nasa AC: Outdoor AJ100FCJ5EH Indoor: 4xAR09HSFSBWKNZE + 1xAR12HSSDBWKNEU
Works:
Mode selection, off, oemperature change.
Does not work:
Fan speed, swinging.

[LorenzoBastianello]

Here a non-NASA AC owner!
I have a 2019 AR12NXFHBWKNEU (idk internal/external part number, they have both the same code I write here)
I'm using main branch code

How I connect to F1/F2:
I'm using a M5 atom lite + atom rs485, A -> F1 and B -> F2, 9600 baud
To power esp32 I find out my AC internal unit have a unused flat with +12V and GND (probably for a wifi card)

What works:

• on/off
• change standard mode (fan only/cool/dry/heat/..)
• temperature setpoint write
• target temperature read

What doesn't works:

• swing (my internal unit has only vertical one)
• custom mode (single user aka economy, comfort, fast, ..)
• fan speed
• every thing I don't mention in above section

Strange behaviours:

• if I plug-in esp32 when AC is in some custom mode, I get swing freeze and logs abount "Unsupported alt_mode 0"
• if I send a command via esp32, swing freeze (if it was swinging)
• I get a lot "Component samsung_ac took a long time for an operation" but I think it's ok
• since I connected esp32 it seems internal AC unit fan have some "burst" and speeds up for a second before return to normal speed (I get this problem also with no esp32 connected, i'm investigating)

Thank you all for this project, I'm here to help with testing!

[tfoutfou]

Non-NASA here too

slim duct 14Kw unit

indoor AC140HBMDKH
outdoor AC140HCADKH

i can happily help , exchange with you on whatsapp or anything if needed

i can even share a private acces to a computer that is directly connected to the Non-NASA network to do some test and sniff packet

can also connect ESP to that machine for test flashing code on it

[mitchsmi]

Working on outdoor model AC140HCAFKH NonNASA

[tech2urdoor]

Working perfectly on outdoor midel AC090HCAFKH NonNASA

[tristone-cz]

Works quite fine on outdoor model AJ040NCJ2EG ... once registered.
Startup issue to be handled, #191 . Related pull request #209.

EDIT:
Today I get to my second unit and it seems our numbering understanding is getting into troubles 😢
This second unit is simple split one, not multi-split system. It is using the same indoor unit as my first multi-split AC mentioned above.
And the bad thing - the outdoor unit shares the model number with the indoor one - AR09RXWXCWKX
According to current knowledge it shall not be supported but it work fine, NonNASA. Expected as the same indoor units work on NonNASA protocol with the multi-split outdoor one.

[omerfaruk-aran]

Hello everyone,

Thank you for volunteering to test the latest Non-NASA implementation. I have made significant code optimizations, focusing on memory management and comprehensive data logging. It is crucial that we verify all functionalities, including sensors, triggers, power on/off actions, temperature adjustments, and more.

For your testing:

• Please test all sensors and actions, such as turning the AC on/off, increasing/decreasing temperature, and more.
• Include the additional sensors for outdoor temperature and energy monitoring that were added in the example YAML.
• Use the provided YAML configuration to integrate these sensors:

external_components:
  - source: github://omerfaruk-aran/esphome_samsung_hvac_bus@add-outdoor-sensors 
    components: [samsung_ac]
    refresh: 0s

      #[NASA or NonNASA]  
      outdoor_temperature: # Should be used with the outdoor device address
        name: "Outdoor temperature"

      # [NASA or NonNASA] Measures the instantaneous power consumption of the outdoor unit in Watts.
      outdoor_instantaneous_power:
        name: "Outdoor Instantaneous Power"

      # [NASA or NonNASA] Records the cumulative energy consumption of the outdoor unit in kWh.
      outdoor_cumulative_energy:
        name: "Outdoor Cumulative Energy"

      # [NASA or NonNASA] Measures the current drawn by the outdoor unit in Amperes.
      outdoor_current:
        name: "Outdoor Current"

      # [NASA or NonNASA] Tracks the voltage supplied to the outdoor unit in Volts.
      outdoor_voltage:
        name: "Outdoor Voltage"

After completing your tests, please share the following details with me:

• YAML examples used during testing.
• Log dumps capturing all relevant data.
• Device connection information.

Your feedback and testing insights will help me plan the next steps more effectively. Thank you all for your support and dedication!

---

Participants:
@zombie4000
@TCB13
@Goaheadz
@tfoutfou
@matthias882
@buzurk26
@tristone-cz
@Rebem13
@tech2urdoor
@mitchsmi
@LorenzoBastianello
@dansck
@jszkiela72
@ukw6

Thank you!

[maddogrvo]

Hey Guys,

I`ve just discovered this project and wanted to have an attempt at this too.

I`m using M5Stack atom lite with RS485 Base
Outdoor unit is a AJ052FCJ3EH/EU
Indoor units(3) are AR07HSFNBWKN

After the initial problems caused by the connector of the Atom RS-485 (soldered the wired directly on the board now) I can report everything seems to be working for all three AC`s.

Tested different HVAC Modes, temperature and fan settings. Everything is updated correctly.
(Missing Horizontal / Vertical swing but not sure if i need to fix something in my config but i`ll report back on that later)

Also checked the parameters for the outdoor unit and i`m seeing some strange values

• Current is 0,59 Amps which seems to low
• Instant power is correct (2 KW at the moment)
• Voltage 324V (Which could be correct if the unit has some electronics to increase it above net levels (240V))
• Outdoor temperature 7C (Also correct value)
• Outdoor Cumulative is incorrect, it started at 0.004 kWh and is currently 0.0002 kWh and still dropping

All in all a great success, thanks to everyone that has contributed to this project, ill check if im able to do some contributions myself, but that depends on if im able to learn the C++ syntax (im a C# developer)

[maddogrvo]

Ahh i read that one, but i will try again and turn off the power to the AC (i never turned off the AC power)

[maddogrvo]

Unfortunately still no luck (did not manage to detect anything again, despite using usb power or switching F1 / F2 around)

I did remove the device configuration in the hope that it would detect anything again but even then no luck, also moving the Atom lite to another indoor unit did not work

[tech2urdoor]

Did you try the main repo rather than this add outdoor sensors one? Maybe see if it works with that first. Can you post your yaml and I'll see if I can help.

[omerfaruk-aran]

Could you please open this issue as a separate ‘Issue’ so that we can track it more effectively and document potential solutions? This way, we can keep this discussion focused on feedback and the test user list.

[maddogrvo]

Ahh sorry for that, i think i found out my issue, the default connector supplied with the Atom RS-485 seems faulty, if i push on it i sometimes see all the communication working (including real messages). So with that count me in as a tester (After i fix the connector problem)

[christianjl]

Hi,

Thanks for this great project and the work everyone has done!
I have a different AC unit number than what I mostly see here, so thought I'd add my testing.
(This is my first time using ESPHome, so sorry if i messed anything up in the testing)

AC details:

• Split unit ducted reverse cycle
• Outdoor unit: RC100DHXEH
• Indoor Unit: NS100HHXEH
• Wired remote control unit: MWR-WE13N (F3/F4 connection)

The protocol check returned "Other", but it seems Non-NASA works.
I used the default example yaml.
M5STACK ATOM Lite & M5STACK ATOM RS-485 Base
Installation is on the indoor unit, F1/F2 & V1/V2 for power

Unit addresses were returned immediately and I have the below functions working;

• Turn on/off
• Mode select: Auto, heat, cool, fan
• Increase/decrease temperature

The "Current temperature" is very different than the current temperature on the Samsung indoor controller.
Edited after further testing; The Current temperature is taken from the indoor unit air intake, which makes sense. The wall mounted controller has its own temperature reading, but i assume it is not used for the control.

Would there be any way to use this reading from the wall mounted controller on F3/F4 and have that as an output? Since my indoor unit is located in the ceiling, the temperature is very different than the house temperature when the AC is not working.

Outdoor sensors testing:

• Outdoor temperature - Showing temperature
• Outdoor Instantaneous Power - Only showing 0.0 W
• Outdoor Cumulative Energy - Showing a value but seems really low (see current reading)
• Outdoor Current - Highest value it showed was 0.41A - seems really low - left in heating mode for ~5min with a high target temp.
• Outdoor Voltage - Only showed 0.0 V

I'm located in Australia, if that has any relevance maybe to the power readings

logs_esphome-web-9fbd2c_run2.txt

[christianjl]

@tech2urdoor The controller is a MWR-WE13N i believe. That makes sense that the temperature reading is from the air intake. I am hoping there is a way to report the temperature reading from the controller in ESPHome.
The zones aren't controlled through the samsung controller, just simple wall mounted switches.

[tech2urdoor]

Looks the same as mine. https://youtu.be/jEy2tXQC-ag?si=S-pMk2SzU0I3pLcw follow these instructions and you should be able to change it to pickup the sensor in the controller. My zones aren't controlled through the controller either. Seperate zonemaster.

[christianjl]

Thanks a lot! That worked, the controller temperature is now showing as the current temperature

[tech2urdoor]

You're welcome! Glad I could help. When I bought my house this was all installed previously. They had a wifi kit next to the controller. MIM-H02. I was struggling to connect it up to my wifi. I managed to get it connected to my wifi but it wasn't talking to the controller. Did a lot of research and turns out the controller had to be configured to allow the wifi kit to talk to it. Obviously the previous owner was sold this system, installers installed it without actually knowing how to configure it. The previous owners must have never actually even tried to use the wifi kit otherwise it would have been configured. In my research I discovered the temp sensor change as well. Then Samsung decided to cease support for the app I was using to control the wifi kit and that's what led me here. I'm so thankful for everyone's hard work on this project.

[omerfaruk-aran]

Is this issue resolved? If not, could you please open it as a separate ‘Issue’ so that we can track it more effectively and document potential solutions? This way, we can keep this discussion focused on feedback and the test user list.

[brentk7]

Got this working on an (Australian) AR4500 split system using both the @stable branch or the @add-outdoor-sensors branch.
Only sensor from the @add-outdoor-sensors branch which works is Outdoor temperature - this appears to match the sensors I see on S-NET pro. @main branch does not work.
AR09KSFTAWQNSA - Indoor unit
AR09KSFTAWQXSA -Outdoor unit

[Goaheadz]

Still big lag, and some times missing using source: github://omerfaruk-aran/esphome_samsung_hvac_bus@add-outdoor-sensors

This one: source: github://tristone-cz/esphome_samsung_hvac_bus@patch-slow-registration was a bit better but still missing some key press.

With the first one, I see messages like:
"Took 78ms and sould be a max of 30ms"

Commands like C1,F0 and F1 should be removed. We dont need commands that we do not know what they do at this stage.
Less information flowing and less processor trying to decode commands.

[Goaheadz]

All other parameters are ok (outdoor temperature, watts, voltage etc), and the indoor data still also works fine, and updating when something changes in indoor units.

I am only suferring from commands not getting into indoor machines from HA.

[tech2urdoor]

Everything is functioning except the voltage and power sensors, which aren't updating. The current sensor is much lower than it should be.

logs_atom_run.txt