hitachi air conditioning control with easyesp

[step3528]

Hi,

I have a Hitachi air conditioning that I would like to control with easyesp.

the irremoteesp8266 library has been modified to allow control, but when I use easyesp with the latest version of the library, I cannot control my air conditioning.

I think I must be using the wrong command, can someone help me on this?

and sorry for my english

thank you.

[Ath]

What build of ESPEasy do you have installed on your ESP? The exact name and version are on any page of the web UI at the bottom-right of the page, or in the Tools/Info page.

Best choice would be the minimal_IRext builds for ESP8266, any _IR_ build for ESP32, or a MAX build (that includes all features/plugins minus 1 (the Ping plugin doesn't work with ESP32 yet)).

[step3528]

I have installed several IR versions and at the moment I have the version ESP_Easy_mega_20231225_minimal_IRext_ESP8266_4M2M Dec 25 2023.

[Ath]

What model/protocol of Hitachi AC are you trying too use?
Most Hitachi AC devices are included but the Hitachi AC 264 and Hitachi AC 296 protocols are currently disabled, because of the .bin size limits, in the standard builds, available for download, but you could create a CustomIR build that includes them, if needed.

[step3528]

i use protocol hitachi AC 264.

how to create a custom version ? I don't find tutorial.
and what is the exact command to test in tools,
IRSEND .....

thank you

[bidrohini]

I am not sure but here is a quite big thread that you may find useful: viewtopic.php?t=1915&start=150

[Ath]

i use protocol hitachi AC 264.

how to create a custom version ? I don't find tutorial.

The documentation on creating a Custom build is quit scattered across the forum and documentation pages. I'll add a chapter to the ESPEasy Development guide soon.

For now I can build a Custom IR with these Hitachi protocols enabled, but we don't have a custom_IR for ESP8266 with 4M2M flash layout, so it will be a 4M1M version, and you'll have to either re-configure the device, or backup the configuration (config.dat) using the Save button on the Tools page, update to the Custom_IR build via Tools/Update Firmware and restore the config.dat from the backup (rename the downloaded file to config.dat and use the Load button on the Tools page).

ESP_Easy_mega_20240113_custom_IR_ESP8266_4M1M.zip

(1.32 MiB) Downloaded 46 times

(Custom build with enabled Hitachi AC 264 and AC 296 protocols)

NB: In any ESP32 MAX build, all IR protocols are enabled.

and what is the exact command to test in tools,
IRSEND .....

Sorry, can't help with that, don't have any of that equipment available. I think the 'trick' is to record the commands sent from an existing remote, and re-send that from ESPEasy.
The documentation for P035 - Communication - IR Transmit has a link to the supported protocols: https://github.com/crankyoldgit/IRremot ... otocols.md (but as said, some are disabled in ESPEasy)

[step3528]

thank you for you help.

your build custon IR work.

I tested with the command via Tools:
IRSEND,HITACHI_AC264,01100040BFFF00CC33926D13EC48B700FF00FF00FF00FF00FF46B9D12E00FF00FF,264

[Ath]

Great!

I'll see if we can include all IR protocols for ESP32 (all variants) IR builds, so you can use that, it will require you to replace the ESP8266 by an ESP32 model.

If module size is an issue, you can use an ESP32-C3 Mini board, that is about the same size as a Wemos D1 mini-clone (that has the same size and pinout as the Wemos clones, and some even smaller), but these do use a USB-C connector, instead of micro-USB.
If module size is not an issue, you could get an ESP32 with 8MB or 16MB Flash (that'll be an ESP32 or ESP32-S3, most other ESP32 boards come with 4MB Flash) and install the matching MAX build on it, that already has all IR protocols included.

Edit: Removed suggestion for ESP32-C2 boards, these are not suitable for IR sending as they don't have RMT support, used to generate the pwm signal.

[Ath]

I'll see if we can include all IR protocols for ESP32 (all variants) IR builds, so you can use that, it will require you to replace the ESP8266 by an ESP32 model.

I've started PR #4938 to enable that.

[Ath]

The PR has been merged, and will be included in the next release of ESPEasy.

[RBr]

i use protocol hitachi AC 264.

how to create a custom version ? I don't find tutorial.

The documentation on creating a Custom build is quit scattered across the forum and documentation pages. I'll add a chapter to the ESPEasy Development guide soon.

For now I can build a Custom IR with these Hitachi protocols enabled, but we don't have a custom_IR for ESP8266 with 4M2M flash layout, so it will be a 4M1M version, and you'll have to either re-configure the device, or backup the configuration (config.dat) using the Save button on the Tools page, update to the Custom_IR build via Tools/Update Firmware and restore the config.dat from the backup (rename the downloaded file to config.dat and use the Load button on the Tools page).
ESP_Easy_mega_20240113_custom_IR_ESP8266_4M1M.zip (Custom build with enabled Hitachi AC 264 and AC 296 protocols)

NB: In any ESP32 MAX build, all IR protocols are enabled.

and what is the exact command to test in tools,
IRSEND .....

Sorry, can't help with that, don't have any of that equipment available. I think the 'trick' is to record the commands sent from an existing remote, and re-send that from ESPEasy.
The documentation for P035 - Communication - IR Transmit has a link to the supported protocols: https://github.com/crankyoldgit/IRremot ... otocols.md (but as said, some are disabled in ESPEasy)

Hello, i saw this post and realized that probably i have the same issue. I am trying to read IR with this build ESP_Easy_mega_20231225_minimal_IRext_ESP8266_4M1M and it shows me UNKNOWN, but i tested with Arduino library https://github.com/crankyoldgit/IRremot ... otocols.md with dumpV3 and it reads IR just fine. I have " 3021203 RR03-S-Remote (CARRIER_AC84) ". It would be nice if you could add it to custom build, i was trying to do it my self, but without results...

[Ath]

The CARRIER_AC84 protocol is added quite recently to the IRremoteESP8266 library, and newer protocols are excluded by default in the ESPEasy ESP8266 IR builds (but not from the ESP32 IR builds).

You can create a Custom IR build by copying CustomIR-sample.h to CustomIR.h and commenting out the defines for DECODE_CARRIER_AC84 and SEND_CARRIER_AC84, around line 293, then execute a CustomIR build from VSCode/PlatformIO as documented here.

[RBr]

I understood right? Just need to rename the file, CustomIR-sample.h to CustomIR.h and comment out line where DECODE_CARRIER_AC84 and SEND_CARRIER_AC84 sits? I than just make build? I already setup PlatIO in VSCode i was falowing this guide https://www.youtube.com/watch?v=ArqwMcYSMsU, i it would be nice if someone could make some video guide for custom basic build step by step, i think it would help to many of beginners like me.. I was not able to find where i can enable IRremoteESP8266 library entry...

[Ath]

For that CustomIR.h file to be used, you must be build a CustomIR build from the list in PlatformIO. That means you can also control what plugins are to be included, either by working with a Custom.h file (described on the same page I linked), or by adjusting the pre_custom....py file (also explained on that page).

To be completely explicit: You must build a Custom build to have the Custom.h file implemented, and you must build a CustomIR build to have a Custom build with IR features included, that you can customize/fine-tune using the CustomIR.h file. (In most other ESP8266 builds the IR related libraries are explicitly excluded from the build to reduce .bin size)

[RBr]

For that CustomIR.h file to be used, you must be build a CustomIR build from the list in PlatformIO. That means you can also control what plugins are to be included, either by working with a Custom.h file (described on the same page I linked), or by adjusting the pre_custom....py file (also explained on that page).

To be completely explicit: You must build a Custom build to have the Custom.h file implemented, and you must build a CustomIR build to have a Custom build with IR features included, that you can customize/fine-tune using the CustomIR.h file. (In most other ESP8266 builds the IR related libraries are explicitly excluded from the build to reduce .bin size)

Basically you can use customIR.h or .py they will do the same in the end yes?

[TD-er]

What Ton tried to explain is that in PlatformIO you have several build environments.
In VS Code you can see this on the left panel when you select this alien-like symbol.

There are several build envs like "custom_274_ESP8266_4M1M" etc.
A few of those have "IR" in their env name like "custom_IR_ESP8266_4M1M"

Those with "custom" and "IR" in their name need the matching tools/pio/pre_custom_esp82xx_IR.py or CustomIR.h
And of course you need to use those environment entries in the PlatformIO tab.

[Ath]

No, the .py file is to be an alternative for Custom.h (mind the uppercase C), the CustomIR.h only defines the enabled/disabled IR protocols, and uses CustomIR-sample.h as a default if CustomIR.h is not found.

[RBr]

Just made build i think succesfuly. In VSCode build log showed *** CustomIR.h build detected. Create a clean build after changes to CustomIR.h *** .
So i guess it has added to build. Made custom build uncomented DECODE_CARRIER_AC84 and SEND_CARRIER_AC84, around line 293, but still showing in LOG entry UNKNOWN, if i check allow UNKNOWN, if not checked it shows RAW2 value.. What cloud be wrong? How i said i was able to decode with arduino IRRemote8266 library, which is included ir esp builds if i uderstod right..

This is what i get from IRRemote8266

Timestamp : 000080.211
Library : v2.8.6

Protocol : CARRIER_AC84
Code : 0x0C123332001200120013F6 (84 Bits)
uint16_t rawData[171] = {5894, 1100, 476, 1138, 476, 1142, 1208, 406, 1208, 408, 470, 1144, 1208, 406, 472, 1142, 472, 1142, 1212, 402, 476, 1138, 472, 1142, 472, 1142, 1212, 402, 1212, 404, 470, 1142, 476, 1138, 1212, 402, 1212, 402, 476, 1138, 476, 1138, 476, 1144, 1206, 408, 472, 1142, 472, 1142, 1208, 406, 1208, 408, 470, 1142, 472, 1142, 470, 1144, 472, 1142, 472, 1142, 472, 1142, 476, 1140, 476, 1138, 476, 1138, 476, 1138, 476, 1138, 1212, 402, 476, 1140, 474, 1138, 1212, 402, 476, 1138, 476, 1144, 470, 1142, 472, 1144, 472, 1142, 472, 1142, 472, 1142, 472, 1142, 472, 1138, 476, 1144, 472, 1138, 476, 1142, 1208, 406, 472, 1142, 472, 1142, 1208, 408, 470, 1144, 472, 1142, 472, 1142, 476, 1138, 476, 1138, 476, 1138, 476, 1138, 476, 1138, 476, 1142, 472, 1142, 472, 1142, 1186, 428, 1212, 402, 476, 1138, 476, 1138, 1212, 402, 476, 1138, 476, 1138, 476, 1138, 476, 1140, 1212, 402, 1212, 402, 476, 1138, 1212, 402, 1212, 402, 1212, 402, 1212, 402, 1208}; // CARRIER_AC84
uint8_t state[11] = {0x0C, 0x12, 0x33, 0x32, 0x00, 0x12, 0x00, 0x12, 0x00, 0x13, 0xF6};


Timestamp : 000094.661
Library : v2.8.6

Protocol : CARRIER_AC84
Code : 0x0C04333200120012011325 (84 Bits)
uint16_t rawData[171] = {5894, 1100, 472, 1142, 472, 1144, 1212, 402, 1208, 408, 470, 1144, 472, 1142, 1208, 408, 472, 1142, 472, 1142, 476, 1138, 476, 1138, 476, 1140, 1212, 402, 1212, 402, 476, 1138, 476, 1138, 1212, 402, 1212, 402, 476, 1138, 476, 1140, 476, 1138, 1212, 402, 474, 1144, 472, 1138, 1212, 402, 1212, 402, 476, 1140, 474, 1140, 476, 1138, 476, 1138, 476, 1138, 476, 1138, 476, 1140, 476, 1138, 476, 1140, 476, 1138, 476, 1138, 1212, 408, 470, 1144, 470, 1144, 1208, 406, 472, 1144, 472, 1138, 476, 1138, 476, 1138, 476, 1138, 476, 1138, 476, 1138, 476, 1140, 476, 1138, 476, 1138, 450, 1166, 472, 1138, 1212, 402, 476, 1142, 472, 1144, 1208, 402, 476, 1140, 476, 1138, 476, 1138, 1212, 402, 476, 1140, 474, 1140, 476, 1138, 472, 1140, 476, 1138, 476, 1138, 476, 1140, 1208, 402, 1212, 402, 476, 1138, 476, 1136, 1212, 402, 476, 1138, 476, 1134, 476, 1138, 1212, 402, 476, 1134, 1190, 424, 476, 1138, 476, 1138, 1212, 398, 476, 1140, 474, 1140, 1212}; // CARRIER_AC84
uint8_t state[11] = {0x0C, 0x04, 0x33, 0x32, 0x00, 0x12, 0x00, 0x12, 0x01, 0x13, 0x25};