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

[Bug]: Current from PC191HA incorrectly detected as A instead of mA #223

Closed
1 of 3 tasks
NotActuallyTerry opened this issue May 5, 2024 · 5 comments
Closed
1 of 3 tasks
Labels
bug Something isn't working

Comments

@NotActuallyTerry
Copy link

LocalTuya Version

3.2.5

Home Assistant Version

2024.3.0

Environment

  • Does the device work using the Home Assistant Tuya Cloud component?
  • Is this device connected to another local integration, including Home Assistant and any other tools?
  • The devices are within the same HA subnet, and they get discovered automatically when I add them

What happened?

The PC191HA (Arlec Grid Connect Smart Plug with Energy Meter) is automatically detected as reporting Current in A instead of mA

Steps to reproduce.

  1. Allowed LocalTuya to run auto-detection

Relevant log output

No response

Diagnostics information.

localtuya-2e03f8338f7ce09008a6e66a705e6b31-Office Desk-9bd18a1146c171251ab8ecd759655f68.json

@NotActuallyTerry NotActuallyTerry added the bug Something isn't working label May 5, 2024
@xZetsubou
Copy link
Owner

I think it may be better if we converted mA "same as official Home Assistant do with sensors unit` but I guess let goes this. usually I would take the measure of units from Tuya cloud data however it seems Home Assistant doesn't recognizes all Tuya units so it will require a convert function from Tuya -> HA if I decided to go with cloud data units. 😩

@xZetsubou xZetsubou added the master/next-release Fixed in master branch, Will be ready in the next release label May 5, 2024
Copy link

This issue was closed because it was resolved on the release:

@github-actions github-actions bot added stale and removed master/next-release Fixed in master branch, Will be ready in the next release stale labels May 26, 2024
@kazango
Copy link

kazango commented May 27, 2024

Is this actually fixed? It doesn't appear to be fixed on my instance after updating for my smart plugs with energy meters. Still showing the incorrect A instead of mA. Do I need to remove and re-add the devices?

@xZetsubou
Copy link
Owner

xZetsubou commented May 27, 2024

Do I need to remove and re-add the devices

Yes, usually I don't migrate the changes unless it critical one, However "auto configure entities" it just a helper feature I add, to make set-up entities easier and it only works on "set-up step".

Note that if you don't want to re-add the device you can just choose "re-configure device" and manually change the unit of temperature of the entities.

@kazango
Copy link

kazango commented May 28, 2024

Do I need to remove and re-add the devices

Yes, usually I don't migrate the changes unless it critical one, However "auto configure entities" it just a helper feature I add, to make set-up entities easier and it only works on "set-up step".

Note that if you don't want to re-add the device you can just choose "re-configure device" and manually change the unit of temperature of the entities.

Can confirm that works, thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants