search

tnmendes / watt

iOS App for TP-Link Devices (Kasa Smart & Tapo) | Support page for issues related to Watt iOS App
48 stars 4 forks source link

No historic power consumption data from KP125M #142

Open slads11 opened 1 month ago

slads11 commented 1 month ago

I see its on your supported list and it does connect but... While it shows current power consumption there is no historic data hence empty graphs. I have attached screenshots showing this. Cheers Simon Lucas

IMG_7501 IMG_0023 IMG_0022 2 IMG_0024 IMG_0026

tnmendes commented 1 month ago

Hey Simon, thanks for the warning, I have to investigate the reason for the problem

tnmendes commented 1 month ago

Hey @slads11 what is the Firmware Version of your KP125M? Is newer or older than 1.2.3 Build 240624?

slads11 commented 1 month ago

Firmware Version 1.2.3 Build 240624 Rel.154806 Hardware Version 1.0Sent from my iPadOn Aug 13, 2024, at 14:23, Tiago Mendes @.***> wrote: Hey @slads11 what is the Firmware Version of your KP125M? Is newer or older than 1.2.3 Build 240624?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

tnmendes commented 2 days ago

On versoo 5.2.10 of watt I did some fixes related to KP125M devices but still, I judge that will solve. Did you buy the device at 60+ days? Is working now? This is just a theory that I still haven't managed to confirm, I think this problem happens when the device is less than 60 days and I am making a request for the last 60 days' consumption results.

KP125M is a Kasa brand device but they are not using Kasa API but the API of Tapo, but it doesn't always have the same behavior as a Tapo :-/

slads11 commented 1 day ago

Thanks for following up.. look like it is downloading ok now. I have about a month of data now. Sent from my iPadOn Sep 13, 2024, at 00:15, Tiago Mendes @.***> wrote: On versoo 5.2.10 of watt I did some fixes related to KP125M devices but still, I judge that will solve. Did you buy the device at 60+ days? Is working now? This is just a theory that I still haven't managed to confirm, I think this problem happens when the device is less than 60 days and I am making a request for the last 60 days' consumption results. KP125M is a Kasa brand device but they are not using Kasa API but the API of Tapo, but it doesn't always have the same behavior as a Tapo :-/

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>