-
Notifications
You must be signed in to change notification settings - Fork 2
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
Issue Summary: AC Unit Commands Sent but Not Executed by Airton PAC #5
Comments
@sgmckay25 : check on your remote that the wifi is enabled, there is a dedicated button for that, i had numerous times the issue of thinking that my board was no more working and in fact it was just someone had pressed the wifi button and disabled it. |
Hi @ouinouin, I'm receiving the bytes correctly, which confirms that the RX and TX connections are good. I checked the remote, and the Wi-Fi is indeed enabled. I also tried toggling it on and off, but it doesn’t make a difference. Here’s an example log where I request the unit to turn on at 31 degrees. We can see that it recognizes the internal temperature via Example log: 12:01:31.361 function GetFrametype : valid message from AC unit : bytes('7A7AD521220000A30A0A170000440500C8000000000464008A44423131353130B4F6')
12:01:31.363 function GetACmode : ACmodeString = off
12:01:31.366 function GetFanSpeed : FanModeString = medium-high
12:01:31.367 function GetOscillationMode : OscillationModeString = off
12:01:31.370 function GetInternalTemperature : internal unit temperature: 23
12:01:31.372 function GetTemperatureSetpoint : TemperatureSetpoint retrieved from persistent memory : 31
12:01:31.374 function PublishFeedback : got all needed value, publishing in mqtt topics
12:01:31.379 MQT: tele/Newclim/mode/get = off
12:01:31.381 MQT: tele/Newclim/fan/get = medium-high
12:01:31.383 MQT: tele/Newclim/swing/get = off
12:01:31.385 MQT: tele/Newclim/Actualtemp/get = 23
12:01:31.387 MQT: tele/Newclim/Actualsetpoint/get = 31 Then I send the command to switch to "heat" mode and set the temperature to 31 degrees: 12:03:09.783 function MQTTSubscribeDispatcher : message received from mqtt
12:03:09.785 function MQTTSubscribeDispatcher : actual ACmode = heat
12:03:09.786 function MQTTSubscribeDispatcher : actual FanSpeedSetpoint = medium
12:03:09.788 function MQTTSubscribeDispatcher : actual OscillationModeSetpoint = low
12:03:09.790 function MQTTSubscribeDispatcher : actual TemperatureSetpoint = 31
12:03:09.792 function MQTTSubscribeDispatcher : received ACmode = heat
12:03:09.796 MQT: tele/Newclim/mode/get = heat
12:03:09.797 function MQTTSubscribeDispatcher : publishing immediately ACmode
12:03:09.801 function forgepayload : Register 13 ,temperature setpoint -16 : 1
12:03:09.823 function MQTTSubscribeDispatcher : sending frame to AC unit: bytes('7A7A21D5180000A1000000003C0106980000000000000EEA') Despite this, the unit doesn’t activate. Any ideas on how to resolve this? Thanks in advance! |
@sgmckay25 did you get something new on this topic ? you could maybe get a cheap logic analyser to see if you really receive some serial frames. |
Hi |
Just for you to know, I solved the issue by using a shift level. Maybe the signal voltage was a bit too weak to be understand by the AC unit at 3,3v |
I've tested the Berryton project by connecting via TX/RX and an external power supply. The Airton PAC receives the commands, but it does not activate. In the logs, the data appears to be sent as expected. Here’s the full log for reference:
I reversed the TX and RX connections to double-check, and as expected, I stopped receiving data. This suggests that the TX/RX wiring is correct. Despite this, the AC unit still doesn’t respond to the commands sent.
I’ve tested with the PAC both on and off and with
internalThermostat
set to0
and1
, but it remains unresponsive. Could there be specific settings or configurations needed to resolve this? Any insights or suggestions would be greatly appreciated.The text was updated successfully, but these errors were encountered: