peterder72
commented
3 years ago I am getting the same issue. Tuya developer documentation clearly states the order and types for all available datapoints and in theory matches plugin's expectations. However, for reasons unknown to me some ACs have different order and even data format for some datapoints.
By trial and error I was able to fix some data mappings and get most of the functions working properly with the exception of fan speed (might require changes to Homebridge similar to the ones in #148). Apple Home, however, is still unstable and can sometimes have issues with getting current state of the device (on/off), though basic functions like turning on/off and changing temperature are working.
To fix the issue completely, first the nature of those differences between signatures must be determined; only after that a solid solution can replace a quickfix that I have set up on my system.
As for your issue, when booting up Homebridge, the plugin dumps all available data to logs. Could you post those here? The line should look like this:
[TuyaLan] Ready to handle AC (AirConditioner:3.3) with signature {"1":true,"2":"auto","3":"low","4":0,"5":18,"6":false,"7":false,"8":22,"9":0,"12":true,"13":false,"14":false,"15":0}
conradb08
I've installed the plugin on homebridge that is running on my Raspberry Pi3. I've successfully added the AC that is registered in my Tuya app and it also shows in my Apple Home App. The functions however are not working correctly. The AC will be on but it will show it is off in the Apple Home App. And when I try to change the temp when it shows on in the Apple Home App, it will jump to the highest setting (32degrees celsius).
[homebridge-tuya] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 220 exceeded maximum of 100. See https://git.io/JtMGR for more info.
Could you please help, I'm not a developer and don't understand coding. I only got so far by Googling and watching tutorials.
Regards.
Conrad