You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there, I have been stuck on this problem for a while.
The tuya water valves for typical garden hoses are exceptional value but can't be controlled with arduino. I have sniffed the tuya app to device ble communications and they are definitely encrypted. This is pretty sad if you intend to use the project as a means of watering your garden.
This project is the closest as it actually uses your local device to talk with the device. The workflow has the pi grab the local key and from that point on it communicates with the device. LocalTuya works on TCP and it stores the local key to allow for it to communicate with wifi devices without tuya involved.
Does this mean that if an Arduino contains the local key, and uses code similar to whats in this project, that it could pair to the device and start to toggle the device on and off? Are the local keys valid forever?
The text was updated successfully, but these errors were encountered:
Hi there, I have been stuck on this problem for a while.
The tuya water valves for typical garden hoses are exceptional value but can't be controlled with arduino. I have sniffed the tuya app to device ble communications and they are definitely encrypted. This is pretty sad if you intend to use the project as a means of watering your garden.
This project is the closest as it actually uses your local device to talk with the device. The workflow has the pi grab the local key and from that point on it communicates with the device. LocalTuya works on TCP and it stores the local key to allow for it to communicate with wifi devices without tuya involved.
Does this mean that if an Arduino contains the local key, and uses code similar to whats in this project, that it could pair to the device and start to toggle the device on and off? Are the local keys valid forever?
The text was updated successfully, but these errors were encountered: