-
Notifications
You must be signed in to change notification settings - Fork 183
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No 2-way synch? polling? #117
Comments
Hi @paqpaqpaq ,Sorry for the late reply. |
Hi, I am in the same situation. |
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. |
Bump! |
Stale issue. we will close the issue soon. If this issue has not been resolved, please update the issue and contact us in time. |
Bump |
Stale issue. we will close the issue soon. If this issue has not been resolved, please update the issue and contact us in time. |
bump |
Stale issue. we will close the issue soon. If this issue has not been resolved, please update the issue and contact us in time. |
Bump |
I see similar issue on the garage opener as well. Any other solution? |
Stale issue. we will close the issue soon. If this issue has not been resolved, please update the issue and contact us in time. |
Bump |
Stale issue. we will close the issue soon. If this issue has not been resolved, please update the issue and contact us in time. |
bump |
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: ***@***.***>
|
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 28, 2024, 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 Jul 29, 2024, 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. |
Bump
|
Outstanding perseverance from @reidcooper here 👏🏻 |
@tomharvey Bump! 😂 |
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?
The text was updated successfully, but these errors were encountered: