Airton air conditioner serial protocol decoding

[ouinouin]

Hi,
i ll use this discussion to try to reverse the protocol of airton internal air conditioning units, i hooked up a setup to sniff the frames , and was disappointed to not see the tuya headers , since the module is a WR1 module by tuya.
the module has 4 pins : 12V , GND and TX AND RX (wich are mislabeled from the point of view of the module since tx is going to the rx pin of the wr1 module)... the serial signal coming from the air conditioner is 5volts, then in the module two small transistors rectifies signal to the 3.3v supported by the WR1 module.
some big test poitns are available on the boards : wifi tx wifi rx , corresponding to pin 2 and 3 of the module, and log tx ang log rx , corresponding with pins of the same name (supposedly for debugind purposes, it seems to replicate all frames passing by the module).

frames looks like this : (thanks to tasmota serial bridge function).
7A7AD5211C0000A60A0A00000000000000000000000000000000520B
7A7AD1210D0000A40A0A002525
7A7AD521220000A30A0A12000004400088000000000464004744423131333730C56C

first something is clear, the protocol starts with a 7A7A header.
second thing, the protocol ends with a CRC16 , endianness being little endian (thanks : https://www.scadacore.com/tools/programming-calculators/online-checksum-calculator/).
third, most likely on one ot thos frames will appear the setpoint : 16 degres Celcius, and the actual value : 18.
actual value can show on the app a 0,5 degres step , so expect to have a trick like value multiplied by 10 , or value multiplied by two.
edit : found the actual temperature position :
on the below frame the actual temp is represented by 1905 the decoding is : 0x19 = 25 the trailing 05 means 0,5 , 1B00 would mean 27 , 1B05 would mean 27,5
7A7A D521 2200 00A3 0A0A 1905 000C 4F00 9800 0000 0004 6400 5744 4231 3133 3730 951E

on the same frame, at 4F00 , the F represents the value of 31°C , the air conditionner can only be set from 16°C to 31°C so the values are mapped one to one : 0x0 = 16°C 0xF =31°C

if everyone wants to add his two cents on this subject, it might look having nothing to do with tasmota but first , i decided to use tasmota as my serial debug solution.
pictures of the setup might come

[ouinouin]

got some progress, i managed to decode most of the info coming from and to the unit , i made a spreadsheet to summarize some captured frames, here attached. i first took the approach to make a serial to tcp brigde , i f i get time and knowledge i ll integrate airton wifi protocol somewhere in tasmota.
airton decode.ods

[TheMiNuS]

@extazy173 , I worked yesterday with @ouinouin on the sniffed frames that both of us did on our respective units. We have done some good progress and now I'm crossing this information with the content of your file that is giving some hints on the missing elements. The frames are structured in a different way between your file and the Airton protocol but both use some common configuration bytes.

We will get there. I already have an ESP connected to my unit and I manage to send commands to it so now I can verify that everything work fine.

I'm working on documenting the protocol and after that I will jump on the keyboard to code something.
My goal is to build an ESP8266 firmware to interface with an MQTT server.

[extazy173]

@TheMiNuS @ouinouin You are the best. I'd love to help, but it's beyond my skill. I can try to get other documents from the manufacturers. Thanks for the new information and good luck

[TheMiNuS]

@extazy173 The more you have the best it is.
Don't hesitate to share any information you may have (protocol, hw, electronic,...).

[TheMiNuS]

@extazy173 OuinOuin and I would like also to investigate on the infrared protocol as there also some interesting features hidden in it.

If you can manage to have some docs it could be awesome.

[nagius]

Look like this guys already decoded and implemented the IR protocol : crankyoldgit/IRremoteESP8266#1670

[tompointexe]

Hey, did anyone try the ESPHome Tuya MCU / Tuya climate components to see if thoes would work ?

Does anyone know at what logical voltages are the TX and RX outputs ?

[ouinouin]

i did sniff the serial frames and they dont have tuya headers, see attached ods sheet. Le 3 décembre 2023 19:46:18 GMT+01:00, "Tom.exe" ***@***.***> a écrit :

…

Hey, dyd anyone try the ESPHome Tuya MCU / Tuya climate components to see if thoes would work ? -- Reply to this email directly or view it on GitHub: #17328 (comment) You are receiving this because you were mentioned. Message ID: ***@***.***>

[tompointexe]

That's sad :(

[ouinouin]

hi, not yet, just made a small update on the excel shhet i ll post it while back home. i expext to have some time during my december time off to begin programming something in berry, actually i found a code snippet to make the crc calculation, and i stopped there. Le 16 décembre 2023 19:50:15 GMT+01:00, extazy173 ***@***.***> a écrit :

…

Hi, do you have any progress? -- Reply to this email directly or view it on GitHub: #17328 (reply in thread) You are receiving this because you were mentioned. Message ID: ***@***.***>

[TheMiNuS]

Let me know when you are back I will spend some time on coding so if you have the full protocol analyse it will save my time.

[ouinouin]

[airton.decode.ods](https://github.com/arendst/Tasmota/files/13716973/airton.decode.ods) hi, back home now. i ll be available for help if you want. the only things i have are on the excel file. Le 19 décembre 2023 15:27:04 GMT+01:00, TheMiNuS ***@***.***> a écrit :

…

Let me know when you are back I will spend some time on coding so if you have the full protocol analyse it will save my time. -- Reply to this email directly or view it on GitHub: #17328 (reply in thread) You are receiving this because you were mentioned. Message ID: ***@***.***>

[TheMiNuS]

Today I have done a couple of scan of frames from the Remote and the Wifi module. I start to see the structure of frames. If you want I can put the file on a Nextcloud share to work together on it. Just give me a way to reach out to you.

[ouinouin]

couldnt find any way to PM or find your mail, tu peux me contacter [edit , removed mail adress] a plus. you can put the file on nexctloud no issue,

[ouinouin]

some update on this subject, with @TheMiNuS we had a decoding sessions that was completing the initial job based on tests and guessings, we ll soon be able to bring to life the definition of the protocol . @TheMiNuS is coding a monolithic system to drive the AC unit with MQTT from an esp8266 and a dedicaded OS , from my side i choose to stay on the Tasmota side of the force , and i coded a berry script that works. first version is attached in this comment. ill try to publish this on github. coments welcome , i m not a coder at all so its very far from being perfect but at least if it could attract some people around this subject.
the functionalities are limited to : change the mode (heat , cool , dry , fan ...) change the fan speed mode and change louvres height or oscillation.
the system driving this is homeassistant with this config :
note that the thermostat driving the show in this setup is an external one, so you might need to set an offset in the code to get something to work correctly in heat mode. (ongoing).

the homeassistan setup :

  climate:
    - name: NewAirton
      unique_id: climate.NewAirton
      max_temp: 31.0
      min_temp: 16.0
      modes:
        - "auto"
        - "off"
        - "cool"
        - "heat"
        - "dry"
        - "fan_only"
      swing_modes:
        - "on"
        - "off"
       # - "lowest"
        - "low"
        - "medium-low"
        - "medium"
        - "medium-high"
        - "high"
       # - "higher"
       # - "highest"
      fan_modes:
        - "turbo"
        - "high"
        - "medium-high"
        - "medium"
        - "low-medium"
        - "low"
        - "quiet"
        - "auto"
      #initial: 21
      current_temperature_topic : "nodered/temp-salon"
      power_command_topic: "cmnd/Newclim/power/set"
      mode_command_topic: "cmnd/Newclim/mode/set"
      temperature_command_topic: "cmnd/Newclim/temperature/set"
      fan_mode_command_topic: "cmnd/Newclim/fan/set"
      swing_mode_command_topic: "cmnd/Newclim/swing/set"
      
      fan_mode_state_topic: "tele/Newclim/fan/get"
      swing_mode_state_topic: "tele/Newclim/swing/get"
      mode_state_topic: "tele/Newclim/mode/get"
      temperature_state_topic: "tele/Newclim/Actualsetpoint/get"
      precision: 0.1 

the berry code

#airton prtocol from me and brice (pingus.org)
#todo : implement quiet mode on the fan mode
#todo : check boost mode on the fan mode
# crc snippet from  https://github.com/peepshow-21/ns-flash/blob/master/berry/nxpanel.be
import string
import mqtt

var topicprefix = "cmnd/Newclim/"
var FeedbackTopicPrefix = "tele/Newclim/"
var FanSpeedSetpoint 
var OscillationModeSetpoint
var TemperatureSetpoint
var ACmode
var incomingpayload = bytes()
print("mqtt topics", topicprefix , FeedbackTopicPrefix )
# serial communications (pin 26 TX , PIN 32 RX)
ser = serial(32, 26, 9600, serial.SERIAL_8N1)


def modcrc16(data, poly)
      if !poly  poly = 0xA001 end
      # CRC-16 MODBUS HASHING ALGORITHM
      var crc = 0xFFFF
      for i:0..size(data)-1
        crc = crc ^ data[i]
        for j:0..7
          if crc & 1
            crc = (crc >> 1) ^ poly
          else
            crc = crc >> 1
          end
        end
      end
      return crc
    end

def CheckMessage(payload)
   print(payload.size()) #debug
   var MsgCalCrc = modcrc16(payload[0..payload.size()-3])
   var MsgCrc = payload.get(payload.size()-2,-2) # last -2 param means endianness swap
   #print("calculated message = " , MsgCalCrc , "crc of payload = ", MsgCrc) #debug
   if MsgCalCrc == MsgCalCrc
	 return 1
   else
	 return 0
   end
end






	
	def GetACmode(payload) # available modes are : "auto","cool","dry","fan_only","heat"
		var ACmodelist = ["auto","cool","dry","fan_only","heat","off",]
		var ACmodeString = "auto"
		var AConOffState = 0
	    print("byte 13 : 0x" ,string.hex(payload[13]), " ACmode 3 bits value :", payload.getbits(106,1), payload.getbits(105,1), payload.getbits(104,1), " AC unit on/off state :", payload.getbits(107,1) ) #debug
	    AConOffState = payload.getbits(107,1)
	    if AConOffState == 1 
	    ACmodeString = ACmodelist[payload.getbits(104,3)]
	    else
	    ACmodeString = ACmodelist[5]    
	    end
	    print(" ACmodeString = " , ACmodeString ) #debug
	    return ACmodeString
	end

	def GetFanSpeed(payload)
	    var TurboModeState = 0
	    var FanModeString = "auto"
		var FanModeList = ["auto","low","low-medium","medium","medium-high","high","stepless","turbo"]
		#print("byte 13 : 0x" ,string.hex(payload[13]), " FanSpeedMode 3 bits value :", payload.getbits(110,1), payload.getbits(109,1), payload.getbits(108,1), " mode turbo :", payload.getbits(111,1) ) #debug
		if TurboModeState == 0
		FanModeString = FanModeList[payload.getbits(108,3)]
		else
		FanModeString = FanModeList[7]
		end
		print( "FanModeString = " , FanModeString)
		return FanModeString
	end
	
	def GetOscillationMode(payload)
		var OscillationModeList = ["off", "on" ,"high","medium-high","medium","medium-low","low","sweep 3-5","sweep 3-5","sweep 2-5","sweep2-4","sweep1-4","sweep 1-3","sweep 4-6"]
		print("byte 15 : 0x" ,string.hex(payload[15]), " Oscillation mode up/down 4 bits value :",payload.getbits(123,1), payload.getbits(122,1), payload.getbits(121,1), payload.getbits(120,1)) #debug
		var OscillationModeString = OscillationModeList[payload.getbits(120,4)]
		print ("OscillationModeString = ", OscillationModeString)
		return OscillationModeString
	end
	
	def GetTemperature(payload)
	    var temperature = 0
	    #print("byte 10 , ambient temperature integer part : " , payload.get(10,1) , "byte 11, ambient temperature decimal part: " , payload.get(11,1)   ) #debug
		temperature = real(payload.get(10,1)) + real(payload.get(11,1)) /10
		print("decoded temperature: ", temperature)
		return temperature
	end
	
	def GetTemperatureSetpoint(payload)
		var TemperatureSetpoint = 20
		#print("byte 14 , setpoint temperature: " ,payload.getbits(115,1),payload.getbits(114,1), payload.getbits(113,1), payload.getbits(112,1) ) #debug
		TemperatureSetpoint = payload.getbits(112,4) +16
		print("TemperatureSetpoint = ", TemperatureSetpoint)
		return TemperatureSetpoint
	end
	

	def PublishFeedback(payload)
		var MyACmode = GetACmode(payload)
		var MyFanSpeed = GetFanSpeed(payload)
		var MyOscillationMode = GetOscillationMode(payload)
		var MyTemperature = str(GetTemperature(payload))
		var MyTemperatureSetpoint = str(GetTemperatureSetpoint(payload))
		
		#initialize sttings value with first feedback from AC unit to manage restart conditions
		if FanSpeedSetpoint == nil FanSpeedSetpoint = MyFanSpeed  print("recovered FanSpeedSetpoint : " , FanSpeedSetpoint) end
		if OscillationModeSetpoint == nil OscillationModeSetpoint = MyOscillationMode print("recovered OscillationModeSetpoint : ", OscillationModeSetpoint) end
		if TemperatureSetpoint == nil TemperatureSetpoint = MyTemperature print("recovered TemperatureSetpoint : ", TemperatureSetpoint) end
		if ACmode == nil ACmode = MyACmode print("recovered ACmode : ", ACmode) end
		
		
		print("got all needed value, publishing in mqtt topics")
		
		mqtt.publish(FeedbackTopicPrefix + "mode/get" , MyACmode)
		#print("published FanSpeedFeedback")
		
		mqtt.publish(FeedbackTopicPrefix + "fan/get" , MyFanSpeed)
		#print("published FanSpeedFeedback")
		
		mqtt.publish(FeedbackTopicPrefix + "swing/get" , MyOscillationMode)
		#print("published OscillationModeFeedback")
		
		mqtt.publish(FeedbackTopicPrefix + "Actualtemp/get" , MyTemperature)
		#print("published TemperatureFeedback")
		
		mqtt.publish(FeedbackTopicPrefix + "Actualsetpoint/get" , MyTemperatureSetpoint)
		#print("published Temperature_setpointFeedback")
		
	end
	
	def GetFrametype(payload)
		var FrameTypeString = "NONE" #frame A3 = feedback from AC unit to wifi module
	    if CheckMessage(payload) == 1
	        if payload.size() == 34
				print("byte 7 : 0x" ,string.hex(payload[7]) ) #debug	
				if string.hex(payload[7]) == "A3"
					print("frame type A3 : AC unit is giving back useful feedback")
					FrameTypeString = "ACFeedback"
					PublishFeedback(payload)
					return FrameTypeString
				else 
					print("frame is not A3 type")
					return "INVALID_FRAME"
				end	
			print("frame is not 34 bytes legnth")
			end
			
		else	
			print("CRC seems invalid, incomplete buffer ?")
			return "BADCRC"
		end	
		
	end	




	
	def forgepayload(Acmode,FanSpeed,OscillationMode,TemperatureSP)
	    var frame = bytes("7A7A21D5180000A100000000" + "00000000" + "000000000000")
	    #print("empty frame= " ,frame)
		var ACmodeValues = {"auto": 0x00 , "cool" : 0x01 , "dry" : 0x02 , "fan_only" : 0x03 , "heat": 0x04 , "off" : 0x08}
		var FanModeValues = {"auto" : 0x00 ,"low" : 0x10 , "low-medium" : 0x20 ,"medium" : 0x30 , "medium-high" : 0x40 , "high" : 0x50 ,"stepless" : 0x60  ,"turbo" : 0x70 }
		var OscillationModeValues = {"off" : 0x00 , "on" : 0x01 ,"high" : 0x02 ,"medium-high" : 0x03 ,"medium" : 0x04 ,"medium-low" : 0x05 ,"low" : 0x06 ,"sweep 1-5" : 0x07 ,"sweep 2-5" : 0x08 ,"sweep2-4" : 0x09 ,"sweep1-4" : 0x0A ,"sweep 1-3" : 0x0B ,"sweep 4-6" : 0x0C ,"sweep 3-5": 0X0D}

		#setting ACmode on register 12 of the frame
		var Reg12 = 0x00
		var Reg13 = 0x00
		var Reg14 = 0x00
		var Reg15 = 0x98 #config word
		if Acmode != "off"
			Reg12= ACmodeValues[Acmode] | 0x08
		elif Acmode == "off"
			Reg12=  0x00
		end	
		
		#setting FanSpeed on register 12 of the frame
		if Acmode != "turbo"
			Reg12 = Reg12 |	FanModeValues[FanSpeed]
		elif Acmode == "turbo" #todo , check if its worth it to separate turbo mode
			Reg12 = Reg12 |	FanModeValues[FanSpeed]
		end	
		
		#setting swing mode (oscillation ouf louvres ) on register 14 of the frame
		Reg14 = Reg14 |	OscillationModeValues[OscillationMode]
		
		#setting temperature setpoint on register 13
		Reg13 = number(TemperatureSP) - 16
		#print("type reg13" , type(Reg13))
					
		#print("register 12 , AC mode and fanspeed :", string.hex(Reg12))
		#print("register 13 , temperature setpoint :", string.hex(Reg13))
		#print("register 14 , OscillationMode      :", string.hex(Reg14))
		#print("register 15 , ConfigWord (todo)    :", string.hex(Reg15))
		#setting all the calculated parameters into the frame		
		frame.set(12,Reg12)
		frame.set(13,Reg13)
		frame.set(14,Reg14)
		frame.set(15,Reg15)	
		#print("filled frame= " ,frame)
		
		#appending CRC
		modcrc16(frame)
		#print(modcrc16(frame))
		frame.add(modcrc16(frame),-2)
		#print("filled frame with crc = " ,frame)
		return frame
	end

	def f(topic, idx, payload_s, payload_b)
	  print("message received from mqtt")
	  print("actual ACmode = ", ACmode)
	  print("actual FanSpeedSetpoint = ", FanSpeedSetpoint)
	  print("actual OscillationModeSetpoint = ", OscillationModeSetpoint)
	  print("actual TemperatureSetpoint = ", TemperatureSetpoint)
	 
	  #we send back gratuitous feedback upon reception to ensure homeassistant gets immediate feedback and sets correctly its values (why doesnt Homeassistant have time setting for the feedback ? )
	  if topic == (topicprefix + "mode/set")
	    ACmode = payload_s
	    print("received ACmode = ", ACmode)
	    
	    mqtt.publish(FeedbackTopicPrefix + "mode/get" , ACmode)
		print("publishing immediately ACmode")
		
	  elif topic == (topicprefix + "fan/set")
		FanSpeedSetpoint = payload_s
		print("received FanSpeedSetpoint = ", FanSpeedSetpoint)
		mqtt.publish(FeedbackTopicPrefix + "fan/get" , FanSpeedSetpoint)
		print("publishing immediately FanSpeedSetpoint")
		
	  elif topic == (topicprefix + "swing/set")
		OscillationModeSetpoint = payload_s
		print("received OscillationModeSetpoint = ", OscillationModeSetpoint)
		mqtt.publish(FeedbackTopicPrefix + "swing/get" , OscillationModeSetpoint)
		print("publishing immediately OscillationModeSetpoint")
	  elif topic == (topicprefix + "temperature/set")
	  
		TemperatureSetpoint = int(number((payload_s)))
		print("received TemperatureSetpoint = ", TemperatureSetpoint)
		print("debug point 1")
		mqtt.publish(FeedbackTopicPrefix + "Actualsetpoint/get" , payload_s)
		print("publishing immediately TemperatureSetpoint")
	  
	  #used for debugging over mqtt
	  elif topic == "testsclim/payloadfromclim"
	  incomingpayload = payload_b
	  print("incomingpayload" ,incomingpayload)
	  print("type de payload = ", type(incomingpayload))
	  GetFrametype(incomingpayload)
	  
	  return true
	  end
	  print("debug point 2")
	  #print("topic", topic)
	  #print("forging payload")
	  var frametosend = forgepayload(ACmode,FanSpeedSetpoint,OscillationModeSetpoint,TemperatureSetpoint)
	  print("sending frame to mqtt for debug: ", frametosend)
	  mqtt.publish("testsclim/rawpayload" , frametosend)
	  print("sending frame to AC unit: ", frametosend)
	  ser.write(frametosend)
	  return true
	end
	
	mqtt.subscribe(topicprefix + "mode/set",f)
	mqtt.subscribe(topicprefix + "fan/set",f)
	mqtt.subscribe(topicprefix + "swing/set",f)
	mqtt.subscribe(topicprefix + "temperature/set",f)
	mqtt.subscribe("testsclim/payloadfromclim",f)
	



def getfromserial()
	var avail = ser.available()
	if avail != 0
	    var msg = ser.read()
	    ser.flush()
	    if msg[0..1] == bytes("7A7A") && avail == msg.get(4,1)
			#print("buffer filled with :", avail , " bytes")
			#print ("message length :", msg.get(4,1))
			print("message from AC :", msg.tostring(60))
		
		elif msg[0..1] == bytes("7A7A") && avail > msg.get(4,1)
			#print ("buffer is bigger than frame, cutting frame")
			var msg2 = msg[msg.get(4,1)..size(msg)-1]
			msg = msg[0..msg.get(4,1)-1]
			print("message from AC :", msg.tostring(60))
			print("remaining msg   :", msg2.tostring(60)) #toto , implement a buffer of frames.
			#print("calling publishfeedback")
			PublishFeedback(msg)
		end	
	else 
	#	print ("nothing in the buffer")
	end
end

def loopme()
  getfromserial()
  tasmota.set_timer(200, loopme, 1)
end
loopme()

[psailleko]

Hi, do you have a test repository ? :)

[TheMiNuS]

Yes I do but not available for now.
Sorry I'm running late with the publication of the code but I'm quite busy at work and I struggle to code after a long day.
I do my best to release asap.

[psailleko]

Hi, sorry to bug you again,
Could you please tell us that this project is not a dead-end ^^

And sorry to OuinOuin (t'es pas un François à tout hasard toi ^^), but i have plenty esp8266 to use for this kind of project.

[TheMiNuS]

It's not a dead end, it's just that I do that on spare time and for now I'm quite busy.

The code works for me since few weeks but some features are still missing before I can publish. Just wait a bit.

[psailleko]

Thanks for your reply :)

for me , the fact that this project is not a "dead-end" is the onnly thing i want to know ^^
Sorry if i seems a bit arsh, as many of us, US is not my main langage ... so ..... :)

[ouinouin]

hi all, the berryton (berry+airton) code is published here :-)

https://github.com/ouinouin/Berryton

[ouinouin]

no, its not , its running nice since this winter and i have motivation to improve the code and give / recieve comments. for berryton you shall use esp32 to leverage the berry language available only on esp32 builds of tasmota. (and yes since airton is a franch rebrand , je suis français, its a bit much like some topics about the linky, the risk of seing french users is high :-) Le 28 février 2024 20:22:37 GMT+01:00, psailleko ***@***.***> a écrit :

…

Hi, sorry to bug you again, Could you please tell us that this project is not a dead-end ^^ And sorry to OuinOuin (t'es pas un François à tout hasard toi ^^), but i have plenty esp8266 to use for this kind of project. -- Reply to this email directly or view it on GitHub: #17328 (reply in thread) You are receiving this because you were mentioned. Message ID: ***@***.***>

[psailleko]

Thanks for providing this really cool code for our Airton AC brand o7
(dur-dur d'écrire en US sans passer pour un sale type, clairement merci à toi OuinOuin, ton code fonctionne super bien je l'ai testé avec les Berry Script et c'est top, mais comme j'ai tenté de l'expliquer maladroitement vu que j'ai plein de esp8266 à utiliser je me dit que pour gérer une clim ça ira largement ^^, j'ai un peu le cul entre deux chaises, m'en veut pas si je pollue pour un autre projet que le tien)

[ouinouin]

pas de soucis. habe also a look to pingus project when it will be published. dont hesitate to open issues on berryton. i m happy to see one user of my code :-). dont worry for english, keep the topic in english as it can be valuable for some other skyworth variants users. regards. Le 28 février 2024 20:39:01 GMT+01:00, psailleko ***@***.***> a écrit :

…

Thanks for providing this really cool code for our Aitron AC brand o7 (dur-dur d'écrire en US sans passer pour un sale type, clairement merci à toi OuinOuin, ton code fonctionne super bien et c'est top, mais comme j'ai tenté de l'expliquer maladroitement vu que j'ai plein de esp8266 à utiliser ^^, j'ai un peu le cul entre deux chaises, m'en veut pas si je pollue pour un autre projet que le tien) -- Reply to this email directly or view it on GitHub: #17328 (reply in thread) You are receiving this because you were mentioned. Message ID: ***@***.***>

[julien8913]

Hello, I am a French user, I have an Airton AC and I use homey pro to manage my home.
I see that Tasmota seems compatible, but I'm not familiar with how MQTT works.

Do you think it would be possible to add management via HTTP API to your code, which would make your work automatically compatible with all boxes?
Do you have the possibility of posting a short tutorial in the readme with the wiring you've done and the method used to flash the module with tasmota?
I understand of course that all this takes a lot of time.
Thank you in advance for all the work you've already put in.

[s-hadinger]

Many things are possible via HTTP, basically you can send any Tasmota command via HTTP, and get the result. There are some limitations since you can't receive any notification (contrary to MQTT).

[ouinouin]

@julien8913 : its effectively a good idea to describe the connections done to the AC unit, i ll edit the readme.md on github to show the connections.
actually my code is not implemented as a driver, so there is no direct tasmota commands, indeed mqtt is quite simple to handle , this would be a nice addition, like this this would allow to directly send commands through http i ll try to implement it as a driver if there is interrest in doing so , if i can count on you as a regular tester it would motivate me to update the code . another plan is to add the mqtt message for the unit to self describe itself to homeassistant.
@s-hadinger am I right that i should transform my code as being packed into an object , for the functions of the object to be available as commands in tasmota ?
i ll have a deeper look while back home withing 5-6 days.

[julien8913]

Thank you for your reply

@s-hadinger
The problem is that my home automation box is a man pro and although tasmota is an app available to manage in Mqtt, the cards available are few and therefore do not allow to exploit the berryton code.
https://homey.app/fr-fr/app/com.paveld.tasmota/Tasmota-MQTT/

@ouinouin
I can make myself available and will be delighted to test your code.

First of all, I'll use the scripts available in the homey pro 2023, which allow you to match commands directly with the thermostat.
Then I'll try (I don't know how to develop, but tutorials exist) to create a HOMEY app based on your work.
As mentioned, the HOMEY PRO 2023 has a TASMOTA MQTT app, but the cards available are very limited.
An API would allow me to use your code directly via the HOMEY flows.
I use a WEMOS D1 ( ESP8266 ESP-12F 4mo) Wifi.
Have a good day .

[ouinouin]

@julien8913 , i m beginning the "objectification" of my code, then i ll be working on making a command set directly available through http.
feel free to continue this discussion by openin an issue on the berryton repository.

[julien8913]

Hi, there,
After several searches I think I can finally use your code in MQTT via script on homey so I'll test that in parallel.

[EricBerdah]

Hi,there
i m trying your script on a esp32-C3
the air conditioner seems to connect well because I receive frames from the AC, but I cannot send a command.
for example if I send to the tasmota console: publish cmnd/Newclim/temperature/set 21

I have feedback that the script was well received. but nothing happens. (Temperaturesetpoint stay at NIL)
berrylog.txt

on the other hand if I put the thermostat function off (internal

thermostat = 0) , the script stops with an error
ErrorLog.txt

any idea to make it all work?

Thanks for your help

[ouinouin]

thanks for your trial, first the esp32 must wait some frame from the unit to know all the state of the unit. ( seems to be the vase here but just keep this in mind). as per the attached log, the esp32 received the temperature setpoint, but i guess the unit cannot receive a setpoint while its in off mode. try to change the mode to heat or cool and then the setpoint. i would like to have the homeassistant ac panel to send all the values at once but unfortunately its noth the behavior of the mqtt ac component which is a shame but i alreadey discussed this with ha maintainer and they couldnt understand the need for sending all the values at once just like in an ac unit remote. for the thermostat off nil error, i ll have a look. Le 20 juin 2024 00:15:22 GMT+02:00, EricBerdah ***@***.***> a écrit :

…

Hi,there i m trying your script on a esp32-C3 the air conditioner seems to connect well because I receive frames from the AC, but I cannot send a command. for example if I send to the tasmota console: publish cmnd/Newclim/temperature/set 21 I have feedback that the script was well received. but nothing happens. (Temperaturesetpoint stay at NIL) [berrylog.txt](https://github.com/user-attachments/files/15906274/berrylog.txt) on the other hand if I put the thermostat function off (internal thermostat = 0) , the script stops with an error [ErrorLog.txt](https://github.com/user-attachments/files/15906333/ErrorLog.txt) any idea to make it all work? Thanks for your help -- Reply to this email directly or view it on GitHub: #17328 (comment) You are receiving this because you were mentioned. Message ID: ***@***.***>

[EricBerdah]

hello, thanks for your rapid answer,
This morning I did some new tests. It seems that the air conditioner frame is well decoded with the exception of tempsetpoint which always remains at nil.
I made a more complete log where we see the changes in state of the air conditioner with the remote control
Berrytonlog.txt

[EricBerdah]

i think i have find the problem
the test :

ensure we received a fisrt feedback from the AC unit

if ACmode == nil || FanSpeedSetpoint == nil || OscillationModeSetpoint == nil || TemperatureSetpoint == nil
print("function MQTTSubscribeDispatcher : Some of the variables are not yet received , escaping")

return

end

if you don't have previous value in the flash crash the script in mode thermostat 0 and and does not allow mqtt commands to be taken into account.
for it to work I had to comment out this portion, then restart the esp32 and everything was back to normal.
after the first launch I uncommented the test and it worked perfectly

Thank you very much for your work

[ouinouin]

hi, thnaks for digging, just to be sure you use the latest version, pull the script from berryton on github. <https://github.com/ouinouin/Berryton> the main has been updated to support heat and cool mode with internal thermosat and several issues fixed. feel free to post issues there, its more than welcome. you can also try the object branch, but its yet untested. Le 20 juin 2024 12:07:54 GMT+02:00, EricBerdah ***@***.***> a écrit :

…

i think i have find the problem the test : # ensure we received a fisrt feedback from the AC unit if ACmode == nil || FanSpeedSetpoint == nil || OscillationModeSetpoint == nil || TemperatureSetpoint == nil print("function MQTTSubscribeDispatcher : Some of the variables are not yet received , escaping") return end if you don't have previous value in the flash crash the script in mode thermostat 0 and and does not allow mqtt commands to be taken into account. for it to work I had to comment out this portion, then restart the esp32 and everything was back to normal. after the first launch I uncommented the test and it worked perfectly Thank you very much for your work -- Reply to this email directly or view it on GitHub: #17328 (comment) You are receiving this because you were mentioned. Message ID: ***@***.***>

[EricBerdah]

yes it's the last version , i have downloaded it from your GitHub repo

[ouinouin]

good catch, there is a typo line 164, if the setpoint is not initialized :
if TemperatureSetpoint == nil TemperatureSetpoint = print("recovered TemperatureSetpoint : ", TemperatureSetpoint) end
and also in the eprsistance initialisation, the value put in the temperaturesetpoint couldnt be initialized i think.

@EricBerdah : can you wipe your persistance file and give a try with the latest i just pushed ?

[ouinouin]

just try to give feedback directly on berryton by opening an issue

[EricBerdah]

Hello,
the updated release doesn't run

00:00:04.924 RUL: SYSTEM#BOOT performs 'br load('Berryton.be')'
00:00:05.029 BRY: failed to load '/Berryton.be' (syntax_error - /Berryton.be:435: expected 'end' before 'EOS')
00:00:05.032 MQT: CHAUFFAGE/SALON_ANNEXE/stat/RESULT = {"Br":"false"}

[ouinouin]

i ll check that, but please let the discussion be on an issue on the berryton repo

[ouinouin]

i corrected the error , can you check again ?