Connection to device succeeded but no datapoints found, please try again. Create a new issue and include debug logs if problem persists

[inventorematto]

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

[flattery103]

I am also having this problem

[Kingurus]

Same problem.

[yuriyb80]

i have same problem also , still no any solving ?

[Rekazm]

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.

[Idan37S]

Same issue for me, hope it gets resolved

[jstrat31]

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.

[jstrat31]

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.

[Rekazm]

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: @.***>

[koyaya]

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

[Fireball14]

Same issue here.

[isorensen]

+1

[hbaizer]

Same here.

[woempiej]

Same here with the Smart LSC PTZ camera. Light bulbs and LED strips working good.

No support on this for a year?!

[PedroNZ]

Same here with IR remote

[timnell]

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.

[DiegoDaza]

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.

[najamshah1]

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

[Railsimulatornet]

Same Problem with Gosund Bulb

[Rekazm]

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: @.***>

[koyaya]

tinytuya 1.7.1 already supports 3.4. protocol

[drkimlaw]

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?

[TruckeeAviator]

Same problem on a diffrent subnet

[deanfourie1]

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!

[najamshah1]

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

[deanfourie1]

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.

[najamshah1]

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: @.***>

[deanfourie1]

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

[deanfourie1]

This is the error and where I get stuck. Obviously, I am entering the local key.

[najamshah1]

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: @.***>

[tutor79]

Same issue here. no devices can be added using local Tuya. HA raspi

[TruckeeAviator]

So to confirm...

I was able to change the wifi to the same subnet as HA. The devices show up to localtuya right away. I was able to add them, change the wifi subnet back. Then edit each device to change the IP to the other subnet. Takes time but it works.

So this is a different subnet problem. My firewall was set to allow all between VLANs for testing, this still wouldn't work. So maybe we are looking at broadcast packets? Just a guess at this point.

[pedronunesbr]

Same issue here. Same VLAN. I have two Teckin SP22 smart switches, 1 of them works fine but I'm getting the same error with the second one.

Connection to device succeeded but no datapoints found, please try again. Create a new issue and include debug logs if problem persists.

Any clues? Both are in the same room and connected to the same WIFI router.

[TruckeeAviator]

Same issue here. Same VLAN. I have two Teckin SP22 smart switches, 1 of them works fine but I'm getting the same error with the second one.

Connection to device succeeded but no datapoints found, please try again. Create a new issue and include debug logs if problem persists.

Any clues? Both are in the same room and connected to the same WIFI router.

I also had this problem with one of my devices even after I had everything on the same VLAN.

What I did to solve it was:

1. Make sure tuya app was closed.
2. I shut off the internet so nothing could make a connection to the cloud server. (might not be necessary)
3. Rebooted the tuya device (light bulb).
4. Once it joined the network I was able to run the localtuya wizard without the above error.

[pedronunesbr]

Hi guys, I solved the problem as follows:

No success steps: 1) Unplug/plug/unplug the device (…) 2) Pause the device's internet (from the router) 3) Close the Smartlife App on all connected devices 4) Restart Home Assistant

Success steps: 1) Delete the device from the SmartLife App (I saw that the timezone of this device was different from my working device) 2) Add a new device in Smartlife App (smart wifi switch in my scenario) 3) Get the new Local Key (device ID kept unchanged) 4) Add the new Device in Local Tuya with the new Local Key 5) Bingo. 

FFI: Now, the device is set with the right Timezone.

[deanfourie1]

Look what I just found.

Will test it tomorrow.

[RastopchinSS]

Привет, ребята, я решил проблему следующим образом:

Никаких шагов успеха:

1. Отключите / подключите / отключите устройство (...)
2. Приостановите доступ к интернету устройства (от маршрутизатора)
3. Закройте приложение Smartlife на всех подключенных устройствах
4. Перезапустите Home Assistant

Шаги успеха:

1. Удалите устройство из приложения SmartLife (я увидел, что часовой пояс этого устройства отличается от моего рабочего устройства)
2. Добавьте новое устройство в приложение Smartlife (smart wifi switch в моем сценарии)
3. Получите новый локальный ключ (идентификатор устройства остался неизменным)
4. Добавьте новое устройство в локальную Tuya с новым локальным ключом
5. Бинго.

FFI: теперь на устройстве установлен правильный часовой пояс.

Мне Ваш способ не помог. Есть кто решил эту проблему?

[TruckeeAviator]

Привет, ребята, я решил проблему следующим образом: Никаких шагов успеха:

1. Отключите / подключите / отключите устройство (...)
2. Приостановите доступ к интернету устройства (от маршрутизатора)
3. Закройте приложение Smartlife на всех подключенных устройствах
4. Перезапустите Home Assistant

Шаги успеха:

1. Удалите устройство из приложения SmartLife (я увидел, что часовой пояс этого устройства отличается от моего рабочего устройства)
2. Добавьте новое устройство в приложение Smartlife (smart wifi switch в моем сценарии)
3. Получите новый локальный ключ (идентификатор устройства остался неизменным)
4. Добавьте новое устройство в локальную Tuya с новым локальным ключом
5. Бинго.

FFI: теперь на устройстве установлен правильный часовой пояс.

Мне Ваш способ не помог. Есть кто решил эту проблему?

Did you change the devices to the same subnet? I had to do this first to get it to work. This seems to be the fix for now. After you change the VLAN and add them to Localtuya, change the VLAN back and edit each device's IP in Localtuya.

[RastopchinSS]

Привет, ребята, я решил проблему следующим образом: Никаких шагов успеха:

1. Отключите / подключите / отключите устройство (...)
2. Приостановите доступ к интернету устройства (от маршрутизатора)
3. Закройте приложение Smartlife на всех подключенных устройствах
4. Перезапустите Home Assistant

Шаги успеха:

1. Удалите устройство из приложения SmartLife (я увидел, что часовой пояс этого устройства отличается от моего рабочего устройства)
2. Добавьте новое устройство в приложение Smartlife (smart wifi switch в моем сценарии)
3. Получите новый локальный ключ (идентификатор устройства остался неизменным)
4. Добавьте новое устройство в локальную Tuya с новым локальным ключом
5. Бинго.

FFI: теперь на устройстве установлен правильный часовой пояс.

Мне Ваш способ не помог. Есть кто решил эту проблему?

Вы переключили устройства на ту же подсеть? Я должен был сделать это первым, чтобы заставить его работать. Похоже, на данный момент это исправление. После изменения VLAN и добавления их в Localtuya измените VLAN обратно и отредактируйте IP каждого устройства в Localtuya.

Сервер и устройства в одной подсети. VLAN у меня не используется.

[pedronunesbr]

Привет, ребята, я решил проблему следующим образом: Никаких шагов успеха:

1. Отключите / подключите / отключите устройство (...)
2. Приостановите доступ к интернету устройства (от маршрутизатора)
3. Закройте приложение Smartlife на всех подключенных устройствах
4. Перезапустите Home Assistant

Шаги успеха:

1. Удалите устройство из приложения SmartLife (я увидел, что часовой пояс этого устройства отличается от моего рабочего устройства)
2. Добавьте новое устройство в приложение Smartlife (smart wifi switch в моем сценарии)
3. Получите новый локальный ключ (идентификатор устройства остался неизменным)
4. Добавьте новое устройство в локальную Tuya с новым локальным ключом
5. Бинго.

FFI: теперь на устройстве установлен правильный часовой пояс.

Мне Ваш способ не помог. Есть кто решил эту проблему?

Вы переключили устройства на ту же подсеть? Я должен был сделать это первым, чтобы заставить его работать. Похоже, на данный момент это исправление. После изменения VLAN и добавления их в Localtuya измените VLAN обратно и отредактируйте IP каждого устройства в Localtuya.

Сервер и устройства в одной подсети. VLAN у меня не используется.

Could you share detailed info? What are you trying to do?

[RastopchinSS]

Привет, ребята, я решил проблему следующим образом: Никаких шагов успеха:

1. Отключите / подключите / отключите устройство (...)
2. Приостановите доступ к интернету устройства (от маршрутизатора)
3. Закройте приложение Smartlife на всех подключенных устройствах
4. Перезапустите Home Assistant

Шаги успеха:

1. Удалите устройство из приложения SmartLife (я увидел, что часовой пояс этого устройства отличается от моего рабочего устройства)
2. Добавьте новое устройство в приложение Smartlife (smart wifi switch в моем сценарии)
3. Получите новый локальный ключ (идентификатор устройства остался неизменным)
4. Добавьте новое устройство в локальную Tuya с новым локальным ключом
5. Бинго.

FFI: теперь на устройстве установлен правильный часовой пояс.

Мне Ваш способ не помог. Есть кто решил эту проблему?

Вы переключили устройства на ту же подсеть? Я должен был сделать это первым, чтобы заставить его работать. Похоже, на данный момент это исправление. После изменения VLAN и добавления их в Localtuya измените VLAN обратно и отредактируйте IP каждого устройства в Localtuya.

Сервер и устройства в одной подсети. VLAN у меня не используется.

Не могли бы вы поделиться подробной информацией? Что вы пытаетесь сделать?

Я пытаюсь добавить устройство в Localtuya. HA его обнаруживает, IP и идентификатор определяется. Далее делаю все по инструкции, но получаю ошибку: "Connection to device succeeded but no datapoints found, please try again. Create a new issue and include debug logs if problem persists". Пробовал сделать как Вы описали выше, но результат тот же.

[pedronunesbr]

When you remove and add the device again, is the LocalID attribute changed? In my tests, the Local ID changed to a new one and with this new one, I was able to set it into Local Tuya.

[RastopchinSS]

Когда вы удаляете и добавляете устройство снова, изменяется ли атрибут localID? В моих тестах локальный идентификатор был изменен на новый, и с помощью этого нового идентификатора я смог установить его в Local Tuya.

Да, localID меняется. Я ввожу идентификатор устройства и новый localID, ошибка повторяется.

[KRiZ-R]

Same problem here. I am trying to add 6 lights. 3 lamps work without problems, and with the other 3, I get the error above. I noticed, that the 3 working bulbs have firmware version 1.2.16 and the non working have firmware version 1.3.21

[RastopchinSS]

У меня 2 устройства:

1. Переключатель с версией прошивки v1.2.1
2. Шлюз ZigBee v1.15.0

Тоже думаю, что дело в прошивках. На моих устройствах они последние.

[pickonedev]

Same issue here

[bored-mind]

same issue here. my devices are on a diferent ip range. homeassistant is on 168.168.1.xx and devices are on 192.168.86.xx any help????

[TruckeeAviator]

same issue here. my devices are on a diferent ip range. homeassistant is on 168.168.1.xx and devices are on 192.168.86.xx any help????

Did you try any of the solutions above?

Changing the ips to the same subnet. Adding it to localtuya. Then change back to the desired subnet worked for me.

Just need to edit the decives under local tuya after.

[bored-mind]

I just tried to connect it to 192.168.1.xx and it works fine. Then I edited the device, changed local key and IP . and it doesn't do anything, the device is unavailable.

[vgomenyuk]

The same issue with "ATORCH-Temperature Controller (S1TW)"

[drdrei]

I also ran into this issue and managed to resolve it after a lot of troubleshooting. Steps:

• close Tuya Smart app
• reboot the device you're trying to connect
• connect the device to localtuya (should work now)
• if the device doesn't work properly in localtuya, reboot the device again
• you should now be able to control the device via localtuya