tuya-homebridge
tuya-homebridge copied to clipboard
tuya
No 2-way synch? polling?
If a switch or dimmer switched is operated via tuya app or google, the change / state is not synchronised with home(bridge). Is there a standard polling time for this which can be changed?
Hi @paqpaqpaq ,Sorry for the late reply. The Tuya HB Plugin will update the Home App based on the MQTT service, Please check whether the Device Status Notification APIs are authorized. Please see https://github.com/tuya/tuya-homebridge/wiki/Tuya-IoT-Platform-Configuration-Guide-Using-Smart-Home-PaaS?_source=d8fba44feeef4757f7f22a14c2295f3f#create-a-project
Hi, I am in the same situation. Device status notification is subscribed, and sometimes it doesn’t works, sometimes yes…
I also have this problem for 'mcs' devices, the status of the devices updates every time Homebridge is restarted but never changes again in HomeKit despite the change being seen in the IoT Developer page and Tuya iOS app. Device Status Notification is subscribed and Authorised for my cloud project so everything seems correct as far as I can tell. With logging turned on, I never see any MQTT messages listed in the Homebridge logs so seems it is never getting any messages back through MQTT or periodically querying the device status.
Stale issue. we will close the issue soon. If this issue has not been resolved, please update the issue and contact us in time.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
Stale issue. we will close the issue soon. If this issue has not been resolved, please update the issue and contact us in time.
Stale issue. we will close the issue soon. If this issue has not been resolved, please update the issue and contact us in time.
Stale issue. we will close the issue soon. If this issue has not been resolved, please update the issue and contact us in time.
Stale issue. we will close the issue soon. If this issue has not been resolved, please update the issue and contact us in time.
Stale issue. we will close the issue soon. If this issue has not been resolved, please update the issue and contact us in time.
Stale issue. we will close the issue soon. If this issue has not been resolved, please update the issue and contact us in time.
BumpOn Mar 26, 2023, at 5:32 AM, github-actions[bot] @.***> wrote: Stale issue. we will close the issue soon. If this issue has not been resolved, please update the issue and contact us in time.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>
Stale issue. we will close the issue soon. If this issue has not been resolved, please update the issue and contact us in time.
BumpOn May 27, 2023, at 5:31 AM, github-actions[bot] @.***> wrote: Stale issue. we will close the issue soon. If this issue has not been resolved, please update the issue and contact us in time.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>
Stale issue. we will close the issue soon. If this issue has not been resolved, please update the issue and contact us in time.
BumpOn Jul 27, 2023, at 2:32 AM, github-actions[bot] @.***> wrote: Stale issue. we will close the issue soon. If this issue has not been resolved, please update the issue and contact us in time.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>
Stale issue. we will close the issue soon. If this issue has not been resolved, please update the issue and contact us in time.
BumpOn Sep 26, 2023, at 5:32 AM, github-actions[bot] @.***> wrote: Stale issue. we will close the issue soon. If this issue has not been resolved, please update the issue and contact us in time.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>
Stale issue. we will close the issue soon. If this issue has not been resolved, please update the issue and contact us in time.
BumpOn Nov 26, 2023, at 4:32 AM, github-actions[bot] @.***> wrote: Stale issue. we will close the issue soon. If this issue has not been resolved, please update the issue and contact us in time.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>
Stale issue. we will close the issue soon. If this issue has not been resolved, please update the issue and contact us in time.
BumpOn Jan 27, 2024, at 4:32 AM, github-actions[bot] @.***> wrote: Stale issue. we will close the issue soon. If this issue has not been resolved, please update the issue and contact us in time.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>
Stale issue. we will close the issue soon. If this issue has not been resolved, please update the issue and contact us in time.
BumpOn Mar 28, 2024, at 5:33 AM, github-actions[bot] @.***> wrote: Stale issue. we will close the issue soon. If this issue has not been resolved, please update the issue and contact us in time.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>