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

Occasional zero values in my main panel power feed readings. #61

Closed
DabblerIOT opened this issue Feb 10, 2024 · 2 comments
Closed

Occasional zero values in my main panel power feed readings. #61

DabblerIOT opened this issue Feb 10, 2024 · 2 comments

Comments

@DabblerIOT
Copy link
Collaborator

A couple things. New to emporia as of a couple weeks ago. This isn't happening when I look at data on emporia side. 2 I am using another (insecure) api that is having the same problem. Stood up ha vm, on my nas with to test.

I believe the response from /getDeviceListUsages is returning a 1 length array (when array should be # of channels on a device or configured in request). Setting up a test to get debug info (capture the 1 length array with data response from the emporia energy API so I can share it later. Will patch my local copy to test. (Just have to sort out how to do that :)). This would match with only the mains having a 0 glitch every now and again. Every other device does not have the issue (as in short array will only mess up the main panel reading) and other data won't be updated.

Line #103 in pyemvue.py needs something to check response is valid, and not a length 1 valid data zero array. Believe we are going to find actual issue is with emporia api but considering it is unsupported.... for us.
"""if j.length != expected length (# of channels)-- retry request.."""

Thanks. Will post my fix and get it writing log or setup stand alone test with pyemvue to catch issue. And provide actual http response and headers to prove.

BTW - Thank you for doing your work and documenting the api. Really want to hit it directly with javascript / browser, but they have cors headers on the api which makes that a no-go for now / ever.

@webdeck
Copy link

webdeck commented Feb 10, 2024

Related to #39 ?

@DabblerIOT
Copy link
Collaborator Author

Yes :( I missed that when I was checking open issues. Should I just post my fix here or on 39 when I have it?

DabblerIOT added a commit to DabblerIOT/PyEmVue that referenced this issue Feb 12, 2024
…onse received from emporia (api internal bug)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants