-
Notifications
You must be signed in to change notification settings - Fork 569
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
Connection to device succeeded but no datapoints found, please try again. Create a new issue and include debug logs if problem persists. #183
Comments
Another one of these devices that works in a different way... Would it be possible for me to get access to it somehow, so I can try to run some commands? |
Adding in config manual works.
|
Then it's just the datapoint detection that doesn't work. I would love to know why that is, but it's hard to troubleshoot. Let's see if I can resurrect my brute force-branch and try that. |
Same problem with "Smart Floor Light 2.4G WIFI" |
I had the same problem with a E14 RGB bulb from LSC. My 3 E27 RGB LSC bulbs work fine though. The only difference I see between the E14 and E27 versions is the E14 is ESP based and E27 is the realtek chip I believe. Adding them in YAML works, however with each command to the E14 light in on state, first switches off before going to the commanded state. For example: if brightness is 100% and command is send to go to 20%, the light will do 100%->0% (off state)->20%. I'm not sure if this is fully related. The [822...e7a] @ 192.168.1.65 in the following log is the E14 bulb. It shows connected, disconnected, connected, but it will still react to commands.
|
I had this error on a plug and found that it would actually map If i did the find quickly after connecting it to electric. Going to leave it a few hours now to see if it goes away again. --edit-- So far hasnt gone away again. I've noticed that strange things happen if you try and query tuyapi at the same time as having the tuya/smart life app open. |
Same problem with Zigbee gateway |
thx. Solved when app is closed |
Here is the output of my log
The text was updated successfully, but these errors were encountered: