-
Notifications
You must be signed in to change notification settings - Fork 36
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
How to get In/out to grid kWh #51
Comments
I don't have solar so those don't come up for me but I believe you can get them from the If you use a call like Note that if you just want the daily data you can get on the main page of the app, that call will get the data for every device and channel in just one call, rather than making separate calls to the get_chart_usage endpoint. The get_chart_usage endpoint is good if you want data over a time range since it unsurprisingly corresponds to the "Graphs" page in the app. |
Thanks a ton Mike for leading me down the right path. I'm finding Emporia's internals quite confusing, with terms like "channel" overloaded to mean different things depending on the context. As you point out, PS: I am cognizant of the high query rate concerns that you may be alluding to. I am building a simple command line tool that I intend to query once/month to reconcile my utility bill with Emporia's measurements, so it shouldn't put any non trivial load on their servers. Thanks again |
First, thank you for creating this API. I have had great success with it. Among other things, I am using get_chart_usage() to fetch daily energy usage for various circuits.
For the main panel, I can retrieve the net energy flow for the day. We have solar, so power flows in both directions and this number can be positive or negative. However, I'd like to separately query "In from Grid" and "Out to Grid" kWh (what I'm getting is essentially a difference of the two). This should be possible since the Emporia UI shows those numbers separately for durations >= DAY, but I can't figure out how to do that with this API.
The text was updated successfully, but these errors were encountered: