Building my own custom device integration with yaml files- without a support/pull request #1235
-
Hello- I truly hate to bother you as I see you are swamped with requests and discussions. I don't want to add to your work loc So I poured over you Python Code and Yaml files to find out when a place a new YAML file in the custom_components\Tuya_local\Devices folder its not picked up by the integration. Your Python code seems like it scans the directory and determines if there's a match, I don't see what else I need to do place to get the integration to pick it up. I'm still getting the: "Sorry, there is no support for this device." Message. Is the file name itself that important? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
Only the yaml extension is important. More likely you have made your config from iot.tuya.com docs, but it is not exactly matching the actual data that the device is sending. There should be a log message showing a list of dps along with that "Sorry there is no support for this device" popup, and you can compare the types with the types in your config, and look for any that are missing from the log, which need to be marked |
Beta Was this translation helpful? Give feedback.
-
Fixed by reviewing the log and adding the missing DPs in the Yaml file for the new entity. |
Beta Was this translation helpful? Give feedback.
Fixed by reviewing the log and adding the missing DPs in the Yaml file for the new entity.