new-device.yaml 2.5 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667
  1. name: New Device
  2. description: Report an unsupported device
  3. title: Request support for <productname>
  4. labels: ["new device"]
  5. body:
  6. - type: markdown
  7. attributes:
  8. value: |
  9. This form is for reporting a **New Device**. If you are looking for
  10. general help, including cases where you do not see anything in the log,
  11. see [Discussions](https://github.com/make-all/tuya-local/discussions).
  12. Thank you for reporting your unsupported device. Please provide as
  13. much information as you can. Because the developers are busy, new
  14. device requests will be prioritised as follows:
  15. 1. Pull requests
  16. 2. Issues with logs and QueryThingsDataModel API results or equivalent
  17. 3. Issues with logs and enough dps info to make a useful config.
  18. 4. Issues with logs and a tested config
  19. - type: textarea
  20. id: log
  21. attributes:
  22. label: Log message
  23. description: |
  24. Please paste the Warning level log message containing a dps list
  25. which is output when you attempt to add the device and are presented
  26. with a list of non-matching devices.
  27. placeholder: Reports without logs will be immediately closed
  28. render: text
  29. validations:
  30. required: true
  31. - type: textarea
  32. id: data_model
  33. attributes:
  34. label: DPS information
  35. description: |
  36. Preferred data is QueryThingsDataModel API result from iot.tuya.com
  37. If you do not have access to iot.tuya.com, but have other ways of
  38. obtaining dps information, the minimum info required is the numeric
  39. dp id, name/description, data type, and for settable dps, the range
  40. for numeric dps, and the list of possible values for enum dps.
  41. render: text
  42. validations:
  43. required: true
  44. - type: input
  45. id: productid
  46. attributes:
  47. label: Product ID
  48. description: |
  49. The product ID or productKey for the device. You can get this
  50. from the same iot.tuya.com API functions that provide the local key
  51. or from `tinytuya scan` or other tools doing local discovery
  52. - type: input
  53. id: productname
  54. attributes:
  55. label: Product Name
  56. description: The product name (usually brand and model name/number)
  57. - type: textarea
  58. id: info
  59. attributes:
  60. label: Information about how the device functions
  61. description: |
  62. Put any additional information here. Remember the developers are not
  63. familiar with your device, so any explanations of how it functions,
  64. links to manuals or even marketing webpages are useful.