You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
The text was updated successfully, but these errors were encountered:
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".
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.
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.
The text was updated successfully, but these errors were encountered: