localtuya
localtuya copied to clipboard
rospogrigio
Connection to device succeeded but no datapoints found, please try again. Create a new issue and include debug logs if problem persists
Hello folks, i'm facing this error but i don't know why...
"Connection to device succeeded but no datapoints found, please try again. Create a new issue and include debug logs if problem persists."
Here some details of my setup:
i'm currenty running my hassio istance in a cloud VM hosted in contabo DC. The istance is a docker container updated al the latest possible version as the custom component Localtuya. Everything at network level just works as it should. Form IoT network i can reach hassio and viceversa.
IoT net 10.60.3.0/24 Contabo private net 10.60.0.0/24
i'm tring to add this gateway and this switch
- https://www.amazon.it/gp/product/B08FHZV7GC/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1
- https://www.amazon.it/gp/product/B08DKKSCLP/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1
No matter what i've tried i can't get out of this situation.
All info (Device ID, Local Key, Host) are 100% correct and retrivered from tuya dev account using APIs.
Packet Monitor of PFSense
19:20:43.663072 IP 10.60.0.35.53328 > 10.60.3.158.6668: tcp 0 19:20:43.664771 IP 10.60.3.158.6668 > 10.60.0.35.53328: tcp 0 19:20:43.688124 IP 10.60.0.35.53328 > 10.60.3.158.6668: tcp 0 19:20:43.695384 IP 10.60.0.35.53328 > 10.60.3.158.6668: tcp 55 19:20:43.695488 IP 10.60.0.35.53328 > 10.60.3.158.6668: tcp 104 19:20:43.697563 IP 10.60.3.158.6668 > 10.60.0.35.53328: tcp 0 19:20:43.699005 IP 10.60.3.158.6668 > 10.60.0.35.53328: tcp 28 19:20:43.722464 IP 10.60.0.35.53328 > 10.60.3.158.6668: tcp 0 19:20:43.724794 IP 10.60.3.158.6668 > 10.60.0.35.53328: tcp 60
Hope someone can help me😊
Kind Reguards
Mirco
I am also having this problem. It was working before but now I cannot add them without this issue:
Other plugs are working fine, just two bulbs.
I'm having this same issue as well now. The power switch was flipped for my 4 Tuya light bulbs and now they won't respond or let me add them again after removing. I've verified none of the IP's have changed.
I'm having this same issue as well now. The power switch was flipped for my 4 Tuya light bulbs and now they won't respond or let me add them again after removing. I've verified none of the IP's have changed.
Just to note: I had my "Local Tuya" lights on a VLAN that has the internet blocked. Once I re-enabled firewall and NAT rules to enable outside access, the lights started working fine again. I then disabled internet access and they're still working as expected. Sounds like the Local Tuya setup needs internet for at least some initial connection.
I gave it that though then removed it but once the devices reboot they don't like it and stop responding. I was just going to use the official tuya integration for these 2 and localtuya for the rest ---- On Thu, 27 Jan 2022 15:21:11 +0000 @.*** wrote ----
I'm having this same issue as well now. The power switch was flipped for my 4 Tuya light bulbs and now they won't respond or let me add them again after removing. I've verified none of the IP's have changed.
Just to note: I had my "Local Tuya" lights on a VLAN that has the internet blocked. Once I re-enabled firewall and NAT rules to enable outside access, the lights started working fine again. I then disabled internet access and they're still working as expected. Sounds like the Local Tuya setup needs internet for at least some initial connection.
—Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you commented.Message ID: @.***>
same for me happens for
device works in smart life app
in localtuya says Connection to device succeeded but no datapoints found, please try again. Create a new issue and include debug logs if problem persists.
probably it is not supported protocol version or something
Same here with the Smart LSC PTZ camera. Light bulbs and LED strips working good.
No support on this for a year?!
I have the same issue but the really weird thing is I have 4 devices setup and working. This error is on second air purifier but I had no problem with the first.
I though it might be because it is similar device but I also have 2 identical door controllers and they are work fine.
I have tried many things.
I have the same problem, I got the MOES wireless gateway with two curtain motor, but this message appear:
Connection to device succeeded but no datapoints found, please try again. Create a new issue and include debug logs if problem persists.
Someone already solved it.
I have the same issue with Lenovo Smart Filament bulb, however it happens because bulb was joinedin a different network ( VLAN). I have reachibility and firewall rules any any, its just a separate network. if i join the bulb to the same network as HASS with local tuya, then no issue. I do not know how to pass this issue, i want to keep smart things in a different network with others
Is everybody here using HA on a different VLAN or same vlans? ---- On Sat, 01 Oct 2022 13:43:49 +0100 @.*** wrote ---- Same Problem with Gosund Bulb
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>
I try to Add AVTTO TYWB 4ch a Tuya switch devices with 4 isolated relays. It works with Tuya Cloud integration in HA but does not work in Local Tuya. I got the same message "Connection to device succeeded but no datapoints found, please try again", how do I resolve this?
I have the same issue with Lenovo Smart Filament bulb, however it happens because bulb was joinedin a different network ( VLAN). I have reachibility and firewall rules any any, its just a separate network. if i join the bulb to the same network as HASS with local tuya, then no issue. I do not know how to pass this issue, i want to keep smart things in a different network with others
Exactly same scenario for me. I have a VLAN in a different subnet with no internet and im getting this error. I have one interface on HA for internet and one for the devices on a different subnet with no internet, so its finding the device on the VLAN without internet and is unable to add it.
We need a fix for this ASAP. I really hate how everything is so cloud based these days! Love my trusty and easy ESPHome stuff I wish we could just reflash this stuff with ESPHome!
I have the same issue with Lenovo Smart Filament bulb, however it happens because bulb was joinedin a different network ( VLAN). I have reachibility and firewall rules any any, its just a separate network. if i join the bulb to the same network as HASS with local tuya, then no issue. I do not know how to pass this issue, i want to keep smart things in a different network with others
Exactly same scenario for me. I have a VLAN in a different subnet with no internet and im getting this error. I have one interface on HA for internet and one for the devices on a different subnet with no internet, so its finding the device on the VLAN without internet and is unable to add it.
We need a fix for this ASAP. I really hate how everything is so cloud based these days! Love my trusty and easy ESPHome stuff I wish we could just reflash this stuff with ESPHome
I took a very unsual and very in-efficient way to solve it. I joined it to the main VLAN/SSID, and then added it to local tuya. After that I removed it from my main VLAN/SSID and joined to my other VLAN/SSID. I went into the tuya IOT portal and got the new IP/and unique ID and keys. I then edited the core config file in HA , edited the section with the device and changed IP/ and other options, restarted HA and it can now control it on a diff VLAN
I have the same issue with Lenovo Smart Filament bulb, however it happens because bulb was joinedin a different network ( VLAN). I have reachibility and firewall rules any any, its just a separate network. if i join the bulb to the same network as HASS with local tuya, then no issue. I do not know how to pass this issue, i want to keep smart things in a different network with others
Exactly same scenario for me. I have a VLAN in a different subnet with no internet and im getting this error. I have one interface on HA for internet and one for the devices on a different subnet with no internet, so its finding the device on the VLAN without internet and is unable to add it. We need a fix for this ASAP. I really hate how everything is so cloud based these days! Love my trusty and easy ESPHome stuff I wish we could just reflash this stuff with ESPHome
I took a very unsual and very in-efficient way to solve it. I joined it to the main VLAN/SSID, and then added it to local tuya. After that I removed it from my main VLAN/SSID and joined to my other VLAN/SSID. I went into the tuya IOT portal and got the new IP/and unique ID and keys. I then edited the core config file in HA , edited the section with the device and changed IP/ and other options, restarted HA and it can now control it on a diff VLAN
Yea nice, I don't think that will work for me as my IoT VLAN has no internet.
I'm pretty sure I've exhausted all options.
I created a SSID with the same SSID as my IoT VLAN on tether from my phone, that way it will auto connect to the IoT network when the phone Hotspot is no longer on,
Then, when connected to the phone, I added to Tyua app and got all the details local key etc,
But when trying to add it in HA, it does not like it. It must need to initially talk to Tuya cloud to get some information or something, and being on the IoT VLAN with no internet, it cannot do this and throws a error.
It finds the device and everything, just won't connect, says something about unable to find endpoints.
I don't think there are any other ways for me to get it working.
I wish I could do a video.I had the same issue. You have to add it to the same VLAN as your HA not the IOT VLAN to start with, also you have to add endpoint information manually. This video explains adding endpoints manually
https://www.youtube.com/watch?v=2kfv0W80NYk
On Mon, Oct 24, 2022 at 10:44 AM deanfourie1 @.***> wrote:
I have the same issue with Lenovo Smart Filament bulb, however it happens because bulb was joinedin a different network ( VLAN). I have reachibility and firewall rules any any, its just a separate network. if i join the bulb to the same network as HASS with local tuya, then no issue. I do not know how to pass this issue, i want to keep smart things in a different network with others
Exactly same scenario for me. I have a VLAN in a different subnet with no internet and im getting this error. I have one interface on HA for internet and one for the devices on a different subnet with no internet, so its finding the device on the VLAN without internet and is unable to add it. We need a fix for this ASAP. I really hate how everything is so cloud based these days! Love my trusty and easy ESPHome stuff I wish we could just reflash this stuff with ESPHome
I took a very unsual and very in-efficient way to solve it. I joined it to the main VLAN/SSID, and then added it to local tuya. After that I removed it from my main VLAN/SSID and joined to my other VLAN/SSID. I went into the tuya IOT portal and got the new IP/and unique ID and keys. I then edited the core config file in HA , edited the section with the device and changed IP/ and other options, restarted HA and it can now control it on a diff VLAN
Yea nice, I don't think that will work for me as my IoT VLAN has no internet.
I'm pretty sure I've exhausted all options.
I created a SSID with the same SSID as my IoT VLAN on tether from my phone, that way it will auto connect to the IoT network when the phone Hotspot is no longer on,
Then, when connected to the phone, I added to Tyua app and got all the details local key etc,
But when trying to add it in HA, it does not like it. It must need to initially talk to Tuya cloud to get some information or something, and being on the IoT VLAN with no internet, it cannot do this and throws a error.
It finds the device and everything, just won't connect, says something about unable to find endpoints.
I don't think there are any other ways for me to get it working.
— Reply to this email directly, view it on GitHub https://github.com/rospogrigio/localtuya/issues/543#issuecomment-1288233729, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASX35HNHVG7CJCYXHH45SQ3WEXEXHANCNFSM5CO3ZY3A . You are receiving this because you commented.Message ID: @.***>
I wish I could do a video.I had the same issue. You have to add it to the same VLAN as your HA not the IOT VLAN to start with, also you have to add endpoint information manually. This video explains adding endpoints manually https://www.youtube.com/watch?v=2kfv0W80NYk … On Mon, Oct 24, 2022 at 10:44 AM deanfourie1 @.> wrote: I have the same issue with Lenovo Smart Filament bulb, however it happens because bulb was joinedin a different network ( VLAN). I have reachibility and firewall rules any any, its just a separate network. if i join the bulb to the same network as HASS with local tuya, then no issue. I do not know how to pass this issue, i want to keep smart things in a different network with others Exactly same scenario for me. I have a VLAN in a different subnet with no internet and im getting this error. I have one interface on HA for internet and one for the devices on a different subnet with no internet, so its finding the device on the VLAN without internet and is unable to add it. We need a fix for this ASAP. I really hate how everything is so cloud based these days! Love my trusty and easy ESPHome stuff I wish we could just reflash this stuff with ESPHome I took a very unsual and very in-efficient way to solve it. I joined it to the main VLAN/SSID, and then added it to local tuya. After that I removed it from my main VLAN/SSID and joined to my other VLAN/SSID. I went into the tuya IOT portal and got the new IP/and unique ID and keys. I then edited the core config file in HA , edited the section with the device and changed IP/ and other options, restarted HA and it can now control it on a diff VLAN Yea nice, I don't think that will work for me as my IoT VLAN has no internet. I'm pretty sure I've exhausted all options. I created a SSID with the same SSID as my IoT VLAN on tether from my phone, that way it will auto connect to the IoT network when the phone Hotspot is no longer on, Then, when connected to the phone, I added to Tyua app and got all the details local key etc, But when trying to add it in HA, it does not like it. It must need to initially talk to Tuya cloud to get some information or something, and being on the IoT VLAN with no internet, it cannot do this and throws a error. It finds the device and everything, just won't connect, says something about unable to find endpoints. I don't think there are any other ways for me to get it working. — Reply to this email directly, view it on GitHub <#543 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASX35HNHVG7CJCYXHH45SQ3WEXEXHANCNFSM5CO3ZY3A . You are receiving this because you commented.Message ID: @.>
Excellent, thanks ill check it out. You should do a video too.
The other thing I noticed was when I added the device in local tuya, I was adding it as a "light" as it is a light. But it would auto fill it as a switch.
When I added it as a light, the entity would be unavailable straight after adding it.
If I added it as a switch, I was able to atleast turn it on and off
This is the error and where I get stuck. Obviously, I am entering the local key.
Exactly my problem when I connect my devices to a separate network, HA fails to connect properly.
I am trying to put together few screenshots
On Mon, Oct 24, 2022 at 9:42 PM deanfourie1 @.***> wrote:
This is the error and where I get stuck
[image: Capturet] https://user-images.githubusercontent.com/71812804/197508350-095fd6f9-dfb8-423c-8c97-e0b68dcae07f.PNG
— Reply to this email directly, view it on GitHub https://github.com/rospogrigio/localtuya/issues/543#issuecomment-1288826419, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASX35HKESO4WLWEDLBFVE6DWEZRY7ANCNFSM5CO3ZY3A . You are receiving this because you commented.Message ID: @.***>
