-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Daikin A/C remote control (Panasonic protocol) #3423
Comments
I'm not sure that Panasonic HVAC is supported yet - I tried using it on a Defy HVAC which I know has a Panasonic board in it and got the same result as you. Would be interesting to see how one would make it work. |
@iz3man You can check the following excellent work on reverse engineering the Daikin A/C protocol: https://github.com/blafois/Daikin-IR-Reverse The code is in Java, but that shouldn't be a problem to understand how it works. |
Excellent. Thank you! |
I wonder if its Daikin specific, or if the same will work with other ones identified as Panasonic... and of course someone will need to port the code :| |
What is the model of your Daikin Remote ? |
Copied from #3228 :
|
Just a short follow-up on this, there is an excellent work done on IR and HVAC at https://github.com/ToniA/arduino-heatpumpir |
Hello I have the exact same problem but with a Panasonic TV, I am using a D1 mini with an IR shield I can see the codes from my Panasonic TV remote, however when I send the codes via console or MQTT nothing happens. Did you found a solution? |
@Jason2866 Posted some interesting info on Tasmota Chat but I have not been able to test it yet. |
I tried to integrate the arduino-heatpumpir in Tasmota, and, after while I bought the first problem and first success. Briefly, I detected a problem that does not allow the integration of arduino-heatpumpir lib in Tasmota, the problem consists in an alreay used definition of the identifiers POWER_ON and POWER_OFF; I described the problem in bullet 1 of this post. In the mean while, in my development enviroment, I bypassed the problem described in the post renaming the duplicated identifiers used in arduino-heatpumpir. So, to intengrate the arduino-heatpumpir in Tasmota, we need to follow the following main steps:
I attach my preliminary working version of xdrv_05_irremote.ino In my version of xdrv_05_irremote.ino I commented the old unused source code. In my opinion the next steps for a full integrations are:
Gregorio |
Take a look here: |
Hi, Thanks a lot for sharing your ideas. As Tasmota can't handle ALL possible IR protocols, due to flash size restrictions, we should be better implementing a RAW IR send/receive as requested at #2116. Please, if you have further questions or ideas, do not hesitate on contacting us in the Tasmota Discord Chat. Thanks. |
There’s no need to include hearpumpir. |
Sound great, i will try asap!!! Even though it's time to turn on the heating and not A/C ;) |
i installed tasmota 6.1.1 on one of my nodemcu, as they have enough exploited i/o pins.
connected an IR receiver to D2 and an IR transmitter to D4, and set IrSend and IrReceive accordingly.
all seems to work, and when i press buttons on my Daikin's A/C remote control, i can receive the commands, which are identified as PANASONIC protocol.
as this seems hex code to me, i then tried to send the exact same code to the A/C to turn it on/off, or get some reaction at all.
so in console i sent:
IRsend {"Protocol":"PANASONIC","Bits":48,"Data":"0xE4000090"}
and received
17:15:20 MQT: tele/sonoff/RESULT = {"IrReceived":{"Protocol":"PANASONIC","Bits":48,"Data":"E4000090"}}
exactly the same as what i received when i pressed the button on the remote. but nothing happens. by being able to send/receive commands on the nodemcu directly, i guess i can rule out any wiring issues.
i even moved the IR led very close to the IR receiver of the A/C just to be sure.
any idea what's going on here, and how to trouble shoot it? i'd really love to add my A/C together with automated shades and temperature sensor to home-assistant.
thanks
The text was updated successfully, but these errors were encountered: