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

DPs for energy consumptions are not selectable #688

Closed
codingcatgirl opened this issue Jan 2, 2022 · 6 comments
Closed

DPs for energy consumptions are not selectable #688

codingcatgirl opened this issue Jan 2, 2022 · 6 comments
Labels
bug Something isn't working

Comments

@codingcatgirl
Copy link

codingcatgirl commented Jan 2, 2022

The problem

Now that the lack of updates on the energy confumption DPs was fixed, i decided to give loyaltuya another go.

Sadly, when setting up, i now can't even select the energy consumption DPs. When i add one of my smart plugs with energy monitoring with todays new update, only two DPs show up. The ones that would contain the energy consumption information are missing. When i tried localtuya for the first time a few months ago, a lot more DPS would show up (and provide data as long as the app was running).

Environment

  • Localtuya version: 3.3.0
  • Home Assistant Core version: 2021.12.7
  • [] Are you using the Home Assistant Tuya Cloud component ?
  • [] Are you using the Tuya App in parallel ?

Steps to reproduce

  1. Click "Add Integration"
  2. Setup a tuya smart plug with energy consumption feature.
  3. The DPs for energy consumption can't be selected.

Configuration configuration.yaml or config_flow

image

DP dump

TuyaDebug (Tuya DPs dump) [1.0.0]

Device bf08d3a7087ecab2c7uxpp at 192.168.178.99 key xxxxxxxxxx protocol 3.3 dev_type type_0a:
    DPS [1] VALUE [True] 
    DPS [9] VALUE [0] 

Provide Home Assistant taceback/logs

I'd like to set the log level to debug, but the method described in the issue template does not work for me. There seems to be no service named logger.set_level.

Additional information

I tried to set the DPs using the YAML configuration and discovered another bug that prevented me from doing so: #687

@codingcatgirl codingcatgirl added the bug Something isn't working label Jan 2, 2022
@codingcatgirl codingcatgirl changed the title DPS for energy consumptions are not selectable DPs for energy consumptions are not selectable Jan 2, 2022
@vmartinv
Copy link

vmartinv commented Jan 2, 2022

Did you have DPs for this initially and they disappeared or you have never seen them? Are you sure your plugs actually have the DPs? Maybe try adding the plug with the app open after rebooting home assistant, that way it can detect the dps being reported

@codingcatgirl
Copy link
Author

Did you have DPs for this initially and they disappeared or you have never seen them?

Like i said: "When i tried localtuya for the first time a few months ago, a lot more DPS would show up (and provide data as long as the app was running)."

Are you sure your plugs actually have the DPs?

Well, since i got data from them previously while the app was open – yes.

Maybe try adding the plug with the app open after rebooting home assistant, that way it can detect the dps being reported

I'm aware that this might be a workaround, but the entire point of #549 included in the last update was that you don't need the app to be open and this should not be needed to get localtuya working. Also, i have to assume that even with this workaround it might reset at some point again.

@vmartinv
Copy link

vmartinv commented Jan 2, 2022

I'm aware that this might be a workaround, but the entire point of #549 included in the last update was that you don't need the app to be open and this should not be needed to get localtuya working. Also, i have to assume that even with this workaround it might reset at some point again.

can you test if the workaround works first ? We need to be able to detect the DPs

@codingcatgirl
Copy link
Author

I can, but it will be a while until i have the time to tinker around with the app again

@codingcatgirl
Copy link
Author

@Elendilon just explained here that it is a zombie issue they have fixed with #491 – so once that PR is merged, the issue should hopefully disappear.

@codingcatgirl
Copy link
Author

This has been fixed for me since the last update, though i had to remove all localtuya devices and set them up anew. But now it works! Including Power Consumption! Awesome! Thanks!

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

2 participants