Replies: 5 comments 2 replies
-
what do you mean that it doesn't auto discover it? If you setup the cloud-api with localtuya you can find the device data inside the entry diagnostics try to add it manually and try each protocol version on it's own. |
Beta Was this translation helpful? Give feedback.
-
How can I add it manually if there is no local key discovered? I have two devices that are not auto discovered even though I certainly have the cloud-api setup properly. They show up without anything to identify them besides a number string and the ip. |
Beta Was this translation helpful? Give feedback.
-
I am confused about where to download the entry diagnostics. |
Beta Was this translation helpful? Give feedback.
-
In the drop down menu after I click to add a device it usually has the name of the device populated and a check box below about automatic import. For this and one other device this is what I see: |
Beta Was this translation helpful? Give feedback.
-
OK so for anyone else that has a slight stroke like myself over this issue. I finally tried to resetup the cloud integration and it gave me the error I needed to jog my memory: "Failed to retrieve device list. Error 28841002: No permissions. Your subscription to cloud development plan has expired." It would be nice if we could be informed within Home Assistant about this being the problem, as I don't believe I saw anything in the logs that would have let me know otherwise. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello;
I bought one of these:
https://www.ebay.ca/itm/276856577450
It works within the normal tuya integration, however is not auto discovered by localtuya.
I've attached the diagnostics from the default tuya.
tuya-01JHDY4X8SDH1E5WCTPFMQZB5Q-Water Temp 2-f3996ea0b66f9956d10187c4a07f058d.json
Beta Was this translation helpful? Give feedback.
All reactions