homebridge-tuya-platform
homebridge-tuya-platform copied to clipboard
2 heaters, item shows, but no parameters shown
Prerequisite
- [X] Yes, I've read the readme completely.
Cache
- [X] Yes, I've cleaned accessory cache and the issue still exists.
Version
1.7.0-beta.51
Device Infomation JSON File
is attached, otherwise too big (max is 65536 characters
Device Control Mode
None
Logs
No response
Other Infomations
expect to see some details, even on/off... is totally blank.
can toggle on off by pressing on the left part of the device where all the devices in a room are listed, but that is all.
it's about these two devices:
[10/14/2023, 10:07:39 PM] [@0x5e/homebridge-tuya-platform] Restoring existing accessory from cache: Panel heater [10/14/2023, 10:07:39 PM] [@0x5e/homebridge-tuya-platform] Restoring existing accessory from cache: LSC IR Panel Heater
Have 2 different small appliance heaters - nothing displays within the home app for device settings TuyaDeviceList.eu1650895720019C93IQ.json empty panel with no attributes or parameters.pdf
I have the same issue, no control options when clicking on a panel heater tile in the Home app - iPhone 14 Pro iOS 17.1.
Strangely, when using the macOS app (Ventura 13.6), the controls show up as expected...
interesting... on macOS Sonoma 14.1, it's the same as on the iPhone and iPad, no controls
Unfortuntaley I can't upgrade to Sonoma, Macbook isn't (officially) supported, so not able to see if that would be the same for me. Seems maybe it's an issue with the latest Home app?
In the plugin settings change category: "qn" (heater) to catergory: "wk" (thermostat).
This is working for me until this bug is fixed.
Yes! That's worked Bat-Maniac, cheers.
I tried this, but no change. I removed from cache, restarted...
"deviceOverrides": [ { "id": "global", "schema": [ { "code": "qn", "newCode": "wk" } ] } ],
@DolmensDude,
wrong code.
Try this:
"deviceOverrides": [
{
"id": "device_ID",
"category": "wk"
}
]
Or simply change category in plugin device settings:
thanks. I saw global override and thought it would work... workaround does work using the actual ID :-)