Skip to content
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

Device stopped working on January update #2922

Open
4 of 5 tasks
kap-Gun opened this issue Feb 6, 2025 · 2 comments
Open
4 of 5 tasks

Device stopped working on January update #2922

kap-Gun opened this issue Feb 6, 2025 · 2 comments
Labels
bug Something isn't working device behaviour The device itself causes this behaviour

Comments

@kap-Gun
Copy link

kap-Gun commented Feb 6, 2025

Description

I have an ATORCH Smart Energy Meter (GR2PW).
It was working fine until January update.
Tuya plugs are still working, only this device has stopped.

Steps to reproduce

I used the add new device via the smartlife app.
Upon choosing the device in the drop down, I get a new screen asking for the IP address to be inserted manually.
Doing so will bring up a new window on the type of device.
The device type is not present.

Image

Image

Expected behaviour

The device to continue working as before the update or the ability to recognise device type to be added after a reset.

Additional context

No response

Confirmation

  • I am sure this is a bug or improvement, that is well enough described that it can be implemented.

  • This report is for tuya-local, not for localtuya.

  • If this is for a specific device, the device config is mentioned above, or diagnostics are included.

  • Log messages or diagnostics relevant to the issue are included.

  • This is not requesting addition of a new device.

@kap-Gun kap-Gun added the bug Something isn't working label Feb 6, 2025
@make-all
Copy link
Owner

make-all commented Feb 6, 2025

It is likely that your device is a "device22" device, and needs to use the newly added "3.22" protocol version instead of "3.3". Other users have also seen this problem when "3.4" devices are misdetected as "3.3".

@make-all make-all added device behaviour The device itself causes this behaviour and removed bug Something isn't working labels Feb 6, 2025
@kap-Gun
Copy link
Author

kap-Gun commented Feb 6, 2025

Choosing '3.22' protocol, or any '3.2' , '3.3' or even auto gives the same result.

@make-all make-all added the bug Something isn't working label Feb 7, 2025
@make-all make-all moved this to 🏗 Stalled in Tuya Local Feb 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working device behaviour The device itself causes this behaviour
Projects
Status: 🏗 Stalled
Development

No branches or pull requests

2 participants