xZetsubou
commented
2 months ago "0" isn't meant to be used this way, have you tried to fully turn off and on the device? 3.4 has some weird issue were devices stops accepting any connection sometimes.
Closed gounry closed 1 month ago
xZetsubou
commented
2 months ago "0" isn't meant to be used this way, have you tried to fully turn off and on the device? 3.4 has some weird issue were devices stops accepting any connection sometimes.
AleksanderGPL
commented
2 months ago I am experiencing the same issue with a Tuya Smart Sprinkler Controller (also protocol 3.4). The device became available again after physically replugging it, although this is likely not a permanent fix.
gounry
commented
2 months ago I removed all fuses from house to be sure it was complety power off (power clamp), And tried, same error.
xZetsubou
commented
2 months ago I am experiencing the same issue with a Tuya Smart Sprinkler Controller (also protocol 3.4). The device became available again after physically replugging it, although this is likely not a permanent fix.
I also sometimes bump into the issue tho I don't know what actually triggers it.. Unlike @gounry issue your issue is fixed if you reboot the device but his device not.
@gounry Did the device got discovered automatically by localtuya or you manually add it? If your device is not running on batteries then 0 shouldn't be used on the device. Can you do long ping with the device IP to ensure that it's not low-power device?
ping -t 192.168.1.239
gounry
commented
2 months ago the device is discovered automatically, pince ampermetrique, 192.168.1.139
i done a cmd with your line ping, i got that
xZetsubou
commented
2 months ago Have you test if the device may works on another protocol version? for example try "auto" it will test all supported protocol versions.
gounry
commented
2 months ago I tried each choice in protocol version, included auto.
Every time I got Connection to device succeeded but no datapoints could be found. Please try set-up again. If problem persists, create a new issue (including debug logs).
fabianosan
commented
2 months ago I tried each choice in protocol version, included auto.
Every time I got Connection to device succeeded but no datapoints could be found. Please try set-up again. If problem persists, create a new issue (including debug logs).
When I have this issue, I put 0 in the "(optional) Manual DPS's ..." and click send and it pass to the next step and I can add the device (setting up manually).
gounry
commented
2 months ago Yes i done that in my first post. But unlucky, It doesn't work
gounry
commented
2 months ago No idea? I tried a lot of thing but still not working.
xZetsubou
commented
2 months ago Not sure to be honest what happen with your device judging by the logs it may be local key issue but I think since you used cloud setup so I guess not.
Can you post the product link if you have it?
You may also want to test the port state. Windows PS: # change the IP to your device IP address.
Test-NetConnection -ComputerName 192.168.1.103 -Port 6668A success message:
ComputerName : 192.168.1.103
RemoteAddress : 192.168.1.103
RemotePort : 6668
InterfaceAlias : Ethernet
SourceAddress : 192.168.1.18
TcpTestSucceeded : True
github-actions[bot]
commented
1 month ago This issue is stale because it has been open 14 days with no activity. Remove stale label or comment or this will be closed in 5 days.
LocalTuya Version
2024.7.0
Home Assistant Version
2024.8.1
Environment
What happened?
hello, i'm trying to add power clamp in local tuya but, i got that error
"Connection to device succeeded but no datapoints could be found. Please try set-up again. If problem persists, create a new issue (including debug logs)"
after saw on another thread i add "0" in Manual DPS's and i jump to the next page, "configure devices entities".
-if i press "discover device entities automatically" i got error "An error occurred: Couldn't find the data for your device category: zndb.. If reason isn't showing, check logs."
-If i press "configure device entities manually", it ask me to choose the entity type, then i choose "sensor" now in DP ID area it show all the DP ID with value, so i choose the first one and set all area.
now when i go to see the entity i have a red dot writed "unavailable"
Steps to reproduce.
Relevant log output
Diagnostics information.
localtuya-01J53WH2S6ETEF6PD48W6REFGR-Pince Ampermetrique-6d79fabc419826aef9d1ee3a36768196 (1).json