-
Notifications
You must be signed in to change notification settings - Fork 24
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
Device with 3.5 protocole #579
Comments
Currently protocol 3.5 is not supported. |
This needs to be implemented. However, it's hard to do without a device. Do you know how to use Wireshark and do you use the SmartLife app? |
I ran this script to confirm that I have a proper connection with the device. Yes, I use the SmartLife app, but I have never used Wireshark. I installed Wireshark few minutes ago, but I don't see the IP address to which the device is connected in the monitoring list. When I scanned my connection by running the script above again, I still don't see any communication with the device, even though the Python script prints a response - so connection exist. I do not know how may i help better 🤔 |
This Python repository has partial support for protocol 3.5 implemented. https://github.com/jasonacox/tinytuya But it doesn't support my device. |
I am correcting my entry - the device actually works on protocol 3.5. So there is a starting point to implement protocol 3.5 😄 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Keep open |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
My device is switching offline/offline on each protocole version.
From json I know it uses protocole 3.5
On trace Level
The text was updated successfully, but these errors were encountered: