make-all
Make it easier to collect info for new devices
Description
Now that an iot.tuya.com account is no longer needed to get local keys, users do not have a good source of info for dps info for new devices. This has led to a regression in quality of reports, which often don't contain the needed enum/integer range info, and sometimes not even dp ids, making the report useless.
Steps to reproduce
- Login with QR code method
- Try to add a device which is unsupported
- Try to gather what info you can without a Tuya developer account
Expected behaviour
Now that cloud functionality is available, we could try to pull in all the info needed and log it, so we just need to send users to the log file for gathering info.
Additional context
No response
Confirmation
-
[X] I am sure this is a bug, or improvement that is well enough described that it can be implemented
-
[x] If this is for a specific device, the device config is mentioned above, or diagnostics are included.
-
[X] This is not requesting addition of a new device
