question and issue

[iotEFFIX]

Hello,

i just had a couple of questions. So if i am right i don't have to implement any of the .cpp or .h files into esphome to work because we all get them extern via:
external_components:

• source: github://Omniflux/esphome-fujitsu-halcyon
• source: github://Omniflux/esphome-tzsp
  If this is correct, and i just have to copy and paste the yaml file and change some names where needed.
  but than how to find this file:
  packages:
  wifi: !include common/wifi.yaml
  because this file can't be found and is not delivered in this repository i think.

[Omniflux]

Correct, external_components now takes care of the .cpp, and .h files.

Packages are explained here https://esphome.io/components/packages.html

If you are not using packages, just replace that section with the wifi or ethernet section from your existing yaml.

You probably also need to change the pins set in the uart section. The example yaml showing tx 13 rx 14 is probably not correct for your device.

If you are using an Atom Lite + FOSV's Fuji-Atom-Interface it would be

uart:
tx_pin: GPIO22
rx_pin: GPIO19

The circuit in Aaron Zhang's original post I believe uses

uart:
tx_pin: GPIO17
rx_pin: GPIO16

[iotEFFIX]

Thank you for the answer!
Now i have working yaml file that is downloadable. I can also upload it to my esp32 feather and it confirms is has been installed correctly. I just can't get life into it for some reason, no climate template and no acces to the local acces to the site of the esphome project. Do i miss something or is something wrong?
Here is my .yaml file:

substitutions:
  name: airco-jd-test
  friendly_name: Airco Jürgen & Davy
  halcyon_name: aircoj&d
  esp_board: featheresp32


external_components:
  - source: github://Omniflux/esphome-fujitsu-halcyon
  - source: github://Omniflux/esphome-tzsp

esphome:
  name: ${name}
  friendly_name: ${friendly_name}

esp32:
  board: ${esp_board}
  framework:
    type: esp-idf

api:
  password: ""

web_server:
  port: 80

ota:
  platform: esphome
  password: !secret esphome_ota_password

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password

  ap:
    ssid: "Fujitsu"
    password: !secret hotspot_password


sensor:
- platform: uptime
  name: "Uptime"

button:
- platform: restart
  name: Restart device
- platform: safe_mode
  name: Safe Mode Boot

#logger:
#  level: DEBUG

uart:
  tx_pin: GPIO17  # Device dependent
  rx_pin: GPIO16  # Device dependent
  baud_rate: 500
  parity: EVEN

climate:
- platform: fujitsu-halcyon
  name: ${halcyon_name}
  # Fujitsu devices use 0 and 1, but 2-15 should also work. Must not skip addresses
  controller_address: 1  # 0=Primary, 1=Secondary
  #temperature_controller_address: 0  # Fujitsu controller address to read temperature from
  #temperature_sensor_id: my_temp_sensor  # ESPHome sensor to read temperature from
  #ignore_lock: true  # Ignore feature lock

  # To capture communications for debugging / analysis
  # Use Wireshark with https://github.com/Omniflux/fujitsu-airstage-h-dissector
#  tzsp:
#    ip: 192.168.1.20
#    protocol: 255

[Omniflux]

Nothing looks obviously wrong with your configuration.

I would remove the external_component, uart, and climate sections and see if local access works.
If it does, I would suspect uart pins are incorrect. If not, esp_board or wifi settings.

[iotEFFIX]

Yes, when i delete the things you said here above i can enter the local site with the buttons that are in the yaml file still. The GPIO pins should be correct since i came here to your project because of Aaron Zhang's. I checked this myself to. It seems to work i think with the edited yaml file but only to turn it on and off not the settings like fan speed, mode ect on the template:

substitutions:
  name: airco-jd-test
  friendly_name: Airco Jürgen & Davy
  halcyon_name: aircoj&d
  esp_board: featheresp32

external_components:
  - source: github://Omniflux/esphome-fujitsu-halcyon
  - source: github://Omniflux/esphome-tzsp

esphome:
  name: ${name}
  friendly_name: ${friendly_name}

esp32:
  board: ${esp_board}
  framework:
    type: esp-idf


api:
  password: ""


web_server:
  port: 80


ota:
  platform: esphome
  password: !secret esphome_ota_password


wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password
  fast_connect: true  


  ap:
    ssid: "Fujitsu"
    password: !secret hotspot_password
    ap_timeout: 300s  

logger:
  level: INFO

# Sensors
sensor:
  - platform: uptime
    name: "Uptime"


button:
  - platform: restart
    name: "Restart Device"
  - platform: safe_mode
    name: "Safe Mode Boot"


uart:
  tx_pin: GPIO17  # Verify based on hardware
  rx_pin: GPIO16  # Verify based on hardware
  baud_rate: 500  # Adjust if needed
  parity: EVEN

# Fujitsu Halcyon Climate Control
climate:
  - platform: fujitsu-halcyon
    name: ${halcyon_name}
    controller_address: 1  # 0=Primary, 1=Secondary

    # Optional settings (uncomment if needed)
    #temperature_controller_address: 0  
    #temperature_sensor_id: my_temp_sensor  
    #ignore_lock: true  

    # Debugging / Traffic Capture (Uncomment to use)
    # tzsp:
    #   ip: 192.168.1.20
    #   protocol: 255

Is this normal?? It seems to be working but when i connect it to the controller it falls into an error the controller. I think it is stuck in some sort of boot loop.

[Omniflux]

Could you set your logger level to debug and post about 10 seconds of the log?

It should contain lines like these, among other things

[20:44:21][D][fujitsu-halcyon:071][UART_Event]: RX: 00 A0 00 0B 16 A0 03 20
[20:44:22][D][fujitsu-halcyon:071][UART_Event]: RX: 20 A1 00 0B 16 00 42 00
[20:44:22][D][fujitsu-halcyon:071][UART_Event]: TX: 21 81 00 0B 16 20 00 00
[20:44:22][D][fujitsu_halcyon_controller::Controller:096][UART_Event]: UART break!

Then set controller_address to 2 and post about 10 seconds of the log again. If set to 2, it should remain in read only mode, and not put your primary controller into an error state.

It would be great if the log covered the period when the Fujitsu unit first powers on, but should be helpful even if you can't get that.

[iotEFFIX]

Hey, sorry for the late answer. I only work on the project on 3 days a week. when i set it to debug it is giving me this:

INFO ESPHome 2025.3.2
INFO Reading configuration /config/esphome/aircojd2.yaml...
INFO Starting log output from [redacted] using esphome API
INFO Successfully connected to [redacted] in 0.064s
INFO Successful handshake with [redacted] in 0.012s
[09:41:41][I][app:100]: ESPHome version 2025.3.2 compiled on Mar 31 2025, 09:36:22
[09:41:41][C][wifi:600]: WiFi:
[09:41:41][C][wifi:428]: Local MAC: [redacted]
[09:41:41][C][wifi:433]: SSID: [redacted]
[09:41:41][C][wifi:436]: IP Address: [redacted]
[09:41:41][C][wifi:439]: BSSID: [redacted]
[09:41:41][C][wifi:441]: Hostname: [redacted]
[09:41:41][C][wifi:443]: Signal strength: -74 dB ▂▄▆█
[09:41:41][C][wifi:447]: Channel: 1
[09:41:41][C][wifi:448]: Subnet: [redacted]
[09:41:41][C][wifi:449]: Gateway: [redacted]
[09:41:41][C][wifi:450]: DNS1: [redacted]
[09:41:41][C][wifi:451]: DNS2: [redacted]
[09:41:41][C][logger:177]: Logger:
[09:41:41][C][logger:178]: Max Level: DEBUG
[09:41:41][C][logger:179]: Initial Level: DEBUG
[09:41:41][C][logger:181]: Log Baud Rate: 115200
[09:41:41][C][logger:182]: Hardware UART: UART0
[09:41:41][C][uart.idf:159]: UART Bus 1:
[09:41:41][C][uart.idf:160]: TX Pin: GPIO17
[09:41:41][C][uart.idf:161]: RX Pin: GPIO16
[09:41:41][C][uart.idf:163]: RX Buffer Size: 256
[09:41:41][C][uart.idf:165]: Baud Rate: 500 baud
[09:41:41][C][uart.idf:166]: Data Bits: 8
[09:41:41][C][uart.idf:167]: Parity: EVEN
[09:41:41][C][uart.idf:168]: Stop bits: 1
[09:41:41][C][uptime.sensor:033]: Uptime Sensor 'Uptime'
[09:41:41][C][uptime.sensor:033]: Device Class: 'duration'
[09:41:41][C][uptime.sensor:033]: State Class: 'total_increasing'
[09:41:41][C][uptime.sensor:033]: Unit of Measurement: 's'
[09:41:41][C][uptime.sensor:033]: Accuracy Decimals: 0
[09:41:41][C][uptime.sensor:033]: Icon: 'mdi:timer-outline'
[09:41:41][C][uptime.sensor:034]: Type: Seconds
[09:41:41][C][restart.button:017]: Restart Button 'Restart Device'
[09:41:41][C][restart.button:017]: Icon: 'mdi:restart'
[09:41:41][C][safe_mode.button:024]: Safe Mode Button 'Safe Mode Boot'
[09:41:41][C][safe_mode.button:024]: Icon: 'mdi:restart-alert'
[09:41:41][C][fujitsu-halcyon:075]: FujitsuHalcyonController:
[09:41:41][C][fujitsu-halcyon:076]: Controller Address: 1 (Secondary)
[09:41:41][C][fujitsu-halcyon:077]: Remote Temperature Controller Address: 0 (Primary)
[09:41:41][C][fujitsu-halcyon:078]: Remote Temperature Controller Sensor 'Remote Temperature Sensor'
[09:41:41][C][fujitsu-halcyon:078]: Device Class: 'temperature'
[09:41:41][C][fujitsu-halcyon:078]: State Class: 'measurement'
[09:41:41][C][fujitsu-halcyon:078]: Unit of Measurement: '°C'
[09:41:41][C][fujitsu-halcyon:078]: Accuracy Decimals: 0
[09:41:41][C][fujitsu-halcyon:080]: Use Sensor: NO
[09:41:41][C][fujitsu-halcyon:081]: Ignore Lock: NO
[09:41:41][C][web_server:285]: Web Server:
[09:41:41][C][web_server:286]: Address: [redacted]
[09:41:41][C][mdns:116]: mDNS:
[09:41:41][C][mdns:117]: Hostname: [redacted]
[09:41:41][C][esphome.ota:073]: Over-The-Air updates:
[09:41:41][C][esphome.ota:074]: Address: [redacted]
[09:41:41][C][esphome.ota:075]: Version: 2
[09:41:41][C][esphome.ota:078]: Password configured
[09:41:41][C][safe_mode:018]: Safe Mode:
[09:41:41][C][safe_mode:019]: Boot considered successful after 60 seconds
[09:41:41][C][safe_mode:021]: Invoke after 10 boot attempts
[09:41:41][C][safe_mode:022]: Remain in safe mode for 300 seconds
[09:41:41][C][api:140]: API Server:
[09:41:41][C][api:141]: Address: [redacted]
[09:41:41][C][api:145]: Using noise encryption: NO
[09:41:43][I][safe_mode:041]: Boot seems successful; resetting boot loop counter
[09:41:43][D][esp32.preferences:114]: Saving 1 preferences to flash...
[09:41:43][D][esp32.preferences:142]: Saving 1 preferences to flash: 0 cached, 1 written, 0 failed
[09:42:25][D][sensor:093]: 'Uptime': Sending state 102.23700 s with 0 decimals of accuracy

I redacted every sensetive information obviously.

When i set the controller adress to 2 i get the same.

[Omniflux]

This does not show it receiving any data from the Fujitsu unit, so probably uart pins or something is disconnected. Is this a Feather V2? It looks like the V2 uses pins 7(rx) and 8(tx). There are a lot of Feather models and many of them use different pins...

[iotEFFIX]

I use the adafruit esp32 feather.
link for example: https://www.adafruit.com/product/3405

[Omniflux]

Not sure where to go from here, there should have been a UART_Event in the log if anything had been received on the serial port, even bad data.