Open jeeshofone opened 4 months ago
You seem to be getting the same error from tinytuya standalone as you are getting from this integration. Most likely it is a problem with the configuration parameters you are using. The details are slightly different for a hub.
Hi @make-all - thanks for that - what information of the configuration parameters can I provide to assist.
I first try only adding only the hub ending in vcvd
:
Logs
2024-05-27 09:13:59.059 WARNING (SyncWorker_10) [custom_components.tuya_local.device] Test protocol error 900: Invalid JSON Response from Device
Then I try adding the hub with the sub device on the WX1 (ending in izo5
):
2024-05-27 09:14:47.747 WARNING (SyncWorker_50) [custom_components.tuya_local.device] Test protocol error 900: Invalid JSON Response from Device
Then I try adding the WX1 as the main device without the hub:
2024-05-27 09:15:19.927 ERROR (MainThread) [custom_components.tuya_local.device] Failed to refresh device state for Test.
Never got it to work. Be interested in how others have successfully integrated this into a local tuya setup.
@Brazen00 added it in https://github.com/make-all/tuya-local/pull/979 - I wonder if they could help us out?
Based on what is tested in the new config flow, device id should be the device id of your hub, and sub device id should be the uuid of the sub device.
Based on what is tested in the new config flow, device id should be the device id of your hub, and sub device id should be the uuid of the sub device.
That was one method I tried in the above troubleshooting description
I have tried it again tonight and found that with the latest version, the process never finishes (I let it go for 5min)
This is the only relevant line in the logs
2024-06-04 01:02:15.398 INFO (MainThread) [custom_components.tuya_local.device] Setting protocol version for Test to 3.3
I used the UUID
of the sub device (same as the sub device id
for the sub device id and the device id as the id of the hub. The hub also has a switched outlet device in it. I tested it again the same way with identical results. Also made sure the Tuya app was closed.
The device does work when testing in the Tuya app alone.
Would anyone be able to suggest next steps for debugging here?
Describe the bug When adding the WX1 Tap Timer to Home Assistant via either cloud or manual mechanisms the device does not add. I am adding the device via the hub after it is paired to Tuya. I can control the device with Tuya Cloud App. I am not leaving the IP address blank. To Reproduce Steps to reproduce the behavior including the device the issue was observed with:
python -m tinytuya wizard
to get devicespython -m tinytuya scan
to get device details (device id, IP(static mapped in Opnsense), local key, versionReceive error:
',"_{
etcExpected behavior A clear and concise description of what you expected to happen.
Additional context Add any other context about the problem here. Discussed in https://github.com/make-all/tuya-local/discussions/1309
If the bug involves a device, then please include device diagnostics from Settings / Devices & Services / Tuya Local (your device) / "1 device"
Additionally:
however this issue is with the cloud add is gone once i uninstalled rospogrigio/localtuya
If applicable, add screenshots to help explain your problem.