-
Notifications
You must be signed in to change notification settings - Fork 14
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
get_15min does not handle 'consumption' data #136
Comments
Looks like this func doesn't parse the returned data correctly. The line
Looking at the SMT.com JS, It seems this get_15min func only handles the situation where you generate surplus, and not also handling consumption. |
I was able to update the function to support RT="C".
|
This is something I've been working on as well, I essentially re-wrote the I added a couple of properties that I thought might be useful, an example can be found here. Would love to see this upstream but I also don't generate surplus so have no idea what it looks like for those that both consume and generate, I assume those with solar panels have that generation ability. It might be useful to have another property for "net consumption." Handling that in the data frame output would also be nice so there aren't duplicate entries for the same interval e.g. each interval would have a column like "CONSUMPTION_KWH", "SURPLUS_GENERATION_KWH", and "NET_CONSUMPTION_KWH", where NET would be negative if you generated more than used. The issue is I have no idea what the output looks like for those with generation and no way of testing it unless I had a raw JSON output from the At least with what I've currently implemented, the output from the example looks like this, which is just a slightly nicer version of SMT's "Export My Report":
|
Description
I'm using the example get_meter_reading.py, except I changed line 36 to
await meter.get_15min(client)
and addedprint(f"{meter.read_15min}")
. This is the output:After 5 minutes of seeing that same output, I did ctrl-c to stop it.
Is there an update to this aspect? Different API endpoint? Or do you have a working example?
The text was updated successfully, but these errors were encountered: