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

Initial support of Hitachi A/C messages. #445

Merged
merged 2 commits into from
Apr 7, 2018
Merged

Initial support of Hitachi A/C messages. #445

merged 2 commits into from
Apr 7, 2018

Conversation

crankyoldgit
Copy link
Owner

  • Add send and decode routines for Hitachi A/C protocol.
  • There is no interpretation of the message as yet. i.e. Just dumb decoding.
  • Unit tests for sendHitachiAC() and decodeHitachiAC()
  • Add needed changes to example & tool code.
  • Change new maximum state size to HITACHI_AC_STATE_LENGTH (28 bytes)

[Note] Assuming that this is a 38kHz protocol. Can't test as I don't have a device.
Ref: Issue #417
FYI @matkappert

* Add send and decode routines for Hitachi A/C protocol.
* There is no interpretation of the message as yet. i.e. Just dumb decoding.
* Unit tests for sendHitachiAC() and decodeHitachiAC()
* Add needed changes to example & tool code.
* Change new maximum state size to HITACHI_AC_STATE_LENGTH (28 bytes)

[Note] Assuming that this is a 38kHz protocol. Can't test as I don't have a device.
Ref: Issue #417
Copy link
Collaborator

@markszabo markszabo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Apart from the comment it looks good to me 👍

#if (DECODE_ARGO || DECODE_DAIKIN || DECODE_FUJITSU_AC || DECODE_GREE || \
DECODE_KELVINATOR || DECODE_MITSUBISHI_AC || DECODE_TOSHIBA_AC || \
DECODE_TROTEC || DECODE_HAIER_AC)
DECODE_TROTEC || DECODE_HAIER_AC | DECODE_HITACHI_AC)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was | (bitwise or) intentional, or should it be || (logical or) as before?

@crankyoldgit
Copy link
Owner Author

@markszabo Very nice catch. Thanks for the review!

@crankyoldgit crankyoldgit merged commit 5fcd9fe into master Apr 7, 2018
@crankyoldgit crankyoldgit deleted the hitachi_ac branch April 9, 2018 07:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants