-
Notifications
You must be signed in to change notification settings - Fork 4
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
Archive this repository? #10
Comments
I second this, I migrated today and honestly I am quite impressed with what they've put out with opower. I'll be honest I didn't expect us to be amongst the first to get this, but for those on the fence give it a shot! Honestly super impressed with the amount of data that was pulled in as quick as it was. |
Has anyone compared this to opower in terms of delay? The opower integration says data is delayed 48 hours. Is that the case with this integration as well or is the data more recent with this? |
Opower is delayed by up to 24-48 hours but highly accurate down to the hour data. Looking at mine right now at 00:21 8/7 I can see data as of 11:59:59 8/5 I had this integration set up on a service call every hour which would update a running total for the day so I’d get 3 to 5 updates a day. Also opower pulls in historical data where this integration never did that I saw. I was happy enough to make a complete switch because of the historical data Sent from my iPhoneOn Aug 6, 2023, at 11:02 PM, Trevor ***@***.***> wrote:
Has anyone compared this to opower in terms of delay? The opower integration says data is delayed 48 hours. Is that the case with this integration as well or is the data more recent with this?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
Copying this from lawrencefoley#37 since it's relevant here as well.
2023.8 will introduce an official integration for Evergy using the new opower API: https://rc.home-assistant.io/integrations/evergy. I tested it out and, while a little slow, it did work. I think this custom integration can also probably be archived with a note pointing users to the new official integration.
The text was updated successfully, but these errors were encountered: