Welcome to today’s daily kōrero!

Anyone can make the thread, first in first served. If you are here on a day and there’s no daily thread, feel free to create it!

Anyway, it’s just a chance to talk about your day, what you have planned, what you have done, etc.

So, how’s it going?

  • Dave@lemmy.nzOPM
    link
    fedilink
    arrow-up
    3
    ·
    1 year ago

    @eagleeyedtiger@lemmy.nz I got my Arlec plug working with LocalTuya, thanks for the help!

    It looks like cumulative power use is still an issue - as in it can tell me how much power is being used right now, but can’t say how much has been used today so far. In the thread you linked they had the same issue, so perhaps this plug doesn’t support it.

    Does Home Assistant support some way of doing this manually? If we have the history, is there a template that can sum the history for a certain period or anything like that? I think because it’s poling it wouldn’t be super accurate but it might be something.

    • NoRamyunForYou@lemmy.nz
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      Just leaving a comment for future reference, as I want to get some Arlec gear up and running via Tuya on HA in the near future :)

      • Dave@lemmy.nzOPM
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        Check out this comment chain that has a lot more info.

        P.S. you can save posts. On the website, click the dots next to the reply to comment button, and there’s a star in there for saving. To find your saved posts, go to your profile page and there’s a tab for it (only visible to yourself).

        • NoRamyunForYou@lemmy.nz
          link
          fedilink
          arrow-up
          2
          ·
          1 year ago

          Ooh, didnt realise that was even available on Lemmy lol - Thank you for that, will come in handy :) And thank you for linking that other thread too

    • eagleeyedtiger@lemmy.nz
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      That’s great! From that thread, it sounds like the cloud based app integration does have that feature. I don’t have any of these devices so can’t play around with it.

      It looks like the Utility Meter integration is the way to go. But you could also setup your own Template sensors to sum it up, here’s a couple of threads that could lead you down the right track:

      https://community.home-assistant.io/t/how-to-sum-energy-and-power-sensors/172779

      https://community.home-assistant.io/t/power-consumption-sum-of-multiple-sensors-entities/266660

      I can’t be of more help than that, as I don’t use any power monitoring at the moment!

      • Dave@lemmy.nzOPM
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        Thanks for pointing out the Utility Meter integration. So much to learn!

        Unfortunately, I spoke a bit too soon. It seems to display current ok, but power just shows as 0W all the time, and voltage was previously showing ok but now is just constantly saying 1.0V. Gonna have to play around a bit more.

        • eagleeyedtiger@lemmy.nz
          link
          fedilink
          English
          arrow-up
          2
          ·
          1 year ago

          Maybe something to do with the polling? I notice under the documentation for LocalTuya in the section “Energy monitoring values”:

          On some devices, you may find that the energy values are not updating frequently enough by default. If so, set the scan interval (see above) to an appropriate value. Settings below 10 seconds may cause stability issues, 30 seconds is recommended.

          • Dave@lemmy.nzOPM
            link
            fedilink
            arrow-up
            2
            ·
            1 year ago

            Thanks, I’ll have another read of the docs. I’ve messed something up, values don’t seem to be updating anynore and turning it on/off doesn’t work, though it says it’s connected.

            I did work out I had the voltage set to the wrong sensor. So that got sorted once I fixed that.