search

milo526 / homebridge-tuya-web

Hoobs and Homebridge plugin for Tuya devices using Home Assistant Tuya Web Api
MIT License
220 stars 96 forks source link

Change how cover accessories are handled to match observed behavior o… #618

Open Tomcraft1980 opened 2 months ago

Tomcraft1980 commented 2 months ago

…f real hardware.

prettier

64Spaces commented 1 month ago

AFAIK, these type of RF cover devices do not provide feedback to HomeKit. But once they are in sync, they work fine for automations and such. If they ever get out of sync, they have to be adjusted.

milo526 commented 1 month ago

AFAIK, these type of RF cover devices do not provide feedback to HomeKit. But once they are in sync, they work fine for automations and such. If they ever get out of sync, they have to be adjusted.

Tuya is the creator of many different appliances; not all devices that are considered "cover devices" are RF; The non-RF devices should be able to report their state back, that also what the current implementation was built for. Sadly not all tuya devices behave the same; but that's also why I cannot blindly accept an untested PR made by someone else when it is unclear what it's effect is on the current userbase.

64Spaces commented 1 month ago

Thank you. That makes sense. I’m very interested in the Issue with Zemismart Cover RF devices getting stuck showing opening/closing or not reacting unless the command is sent two or three times. It’s interesting that Zigbee2MQTT has the same issue with Zemismart Cover RF devices. I’m not sure how the Fork in question solves this problem. Maybe the RF USB Stick “goes to sleep” or something. The logs do not show any data on the first “click”.

dannyuk1982 commented 1 month ago

I've got a QUOYA MC11 Blind, opens/closes via Homekit fine, but Homekit always says "opening" or "closing". Just in case that is of any use towards working out this PR.