-
Notifications
You must be signed in to change notification settings - Fork 474
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
Holman WX1 Tap Timer won't Add to configuration #1951
Comments
Allow the config to proceed even when local network scan throws an error. Issue #1951
You seem to be getting the same error from tinytuya standalone as you are getting from this integration. |
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 Logs
Then I try adding the hub with the sub device on the WX1 (ending in
Then I try adding the WX1 as the main device without the hub:
|
Never got it to work. Be interested in how others have successfully integrated this into a local tuya setup. |
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. |
Would anyone be able to suggest next steps for debugging here? |
Allow the config to proceed even when local network scan throws an error. Issue make-all#1951
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 #1309
If the bug involves a device, then please include device diagnostics from
Settings / Devices & Services / Tuya Local (your device) / "1 device"
Please check if there are messages from Tuya Local in the Home
Assistant log (Settings / System / Logs), and include those too.
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.
The text was updated successfully, but these errors were encountered: