Open Sparoney opened 1 year ago
there's no need to add all schema into the config, just keep those you want to modify. mode
is the fallback of work_status
, its okay without it. Can you describe how it didn't work?
I added the other schema in the config as I wanted to change the temperature min/max values as I only use celsius.
The issue I'm having is that after making the custom schema it still says that mode
is missing from the schema. The aircon also doesn't appear in the list of HomeBridge Accessories and in HomeKit it says Not Supported.
I am wondering if my custom schema might just be getting ignored, as it seems like it should work?
after switch to dp mode, did you restart the homebridge? from your device info json, there's still missing mode
.
Yeah I was restarting it everytime I changed the config but it appears to be working now, its properly registering as DP mode and after overriding Power
to switch
.
Now I have two new issues:
[09/01/2023, 01:27:10] [TuyaPlatform] [Portable Air Conditioner] Invalid mode range for TargetHeaterCoolerState: [ 'COOL', 'FAN', 'DRY' ]
but I can ignore this as it still works.
In the HomeKit app or on the HomeBridge Accessories page, after turning on the air conditioner, about two seconds later it'll appear as offline and just display the current room temprature. (Could this be because I had to change Power DP to switch?)
The fan modes in HomeKit also show as "OFF, COOL, HEAT, AUTO" instead of "COOL, DRY, FAN". Are these modes able to be changed or is that a limitation by the HomeKit app? My Air Conditioner is for cooling only, it doesn't do heating as well.
Thanks!!
Please post your original mode
schema. your config of these part:
{
"oldCode": "mode",
"code": "mode",
"type": "Enum",
"property": {
"range": [
"COOL",
"FAN",
"DRY"
]
}
}
is useless and invalid. Here you can find the AC schema definition: https://developer.tuya.com/cn/docs/iot/f?id=K9gf46qujdmwb
Everytime you editing deviceOverrides
, better clean the accessory cache. If a AC have cooling only, fan and dehumidifier won't appear then.
The original mode
schema is the exact same.
{
"code": "mode",
"mode": "rw",
"type": "Enum",
"property": {
"range": [
"COOL",
"FAN",
"DRY"
]
}
},
Which is invalid.
I have overridden it to:
{
"oldCode": "mode",
"code": "mode",
"type": "Enum",
"property": {
"range": [
"cold",
"wind",
"wet"
]
}
}
After clearing cashe and restarting this then shows no mode options in HomeKit and shows 2 power buttons and a slider (for fan speed) with a power button in it.
The AC has cooling, fan, and dehumidifer modes (COOL, FAN, DRY)
@Sparoney hello,
Can you please help me how to change device code on Tuya. I can not find any detailed information on google.
Edit: I changed device type as "DP instruction" from Tuya Iot platform. But I can not find how to change the code.
Thank you!!
Hi, I recently I got this Portable Air Conditioner from Kogan.
In HomeBridge, I get a message saying I am missing the schema for
mode
andwork_status
.So I went to the Tuya website and set it from Standard Instruction to DP Instruction. These are the available options it gives me:
With DP Instruction mode selected
With Standard Instruction mode selected
I added mode to my schema override but there is no option for "work_status".
Here is the device info from MQTT/Logs:
Using Debug in Homebridge I noticed that when changing between the three modes (Dry, Cool, and Fan) it sends this:
And here is my override schema I created (hoping it is correct!):
I had also set work_status to be the same as mode but that didn't work. I still get the message that both mode and work_status are missing from the schema.
Was wondering if you could assist in how I can fix this? Or is this something that needs to be changed in the plugin? I'm unsure if there's a way in the Tuya API to get all the DP instruction modes and their values.
Thanks!