Hi – friend and I were looking at ours and troubleshooting here in Denver. It appears as if the meter goes into powersave/sleep mode very quickly, which we’re guessing is why it often shows as disconnected on Xcel’s website.
In the documentation, it looked as if there are references to url’s that function as a ‘keep alive’ url
This is how me and my buddy made this work in Homeassistant:
The steps highlighted by pdubs10 helped a lot. But it seemed like the generated certificate was not compatible with our meters. We took a shortcut and used a cert/key provided as an example on the Xcel SDK site. We have been successfully polling our meter for the past few days, without any issues.
Here are the steps to pull data into HA:
Add the following LFDI on your utilities website: 58F371CB4CF0FC393B459559576904D1F7E338EE
To test if the cert and key are able to communicate with your meter, open the HA ssh addon.
5a) run the following command: curl --ciphers ECDHE-ECDSA-AES128-CCM8 --insecure -v --url https://HOST_IP:8081/upt --cert /FILE_PATH/cert.pem --key /FILE_PATH/key.pem
5b) < HTTP/1.1 200 OK response means it worked, you can follow the HREF chain to find data based on your meter version.
where do the cert and key files get saved in HA? is there a specific file path/folder where they would need to be? Can they be created through the file editor in HA? Thank you for any help.
Got this to work finally. I’m running on a Raspberry Pi, so might be some differences. The command_line sensor command wouldn’t work for me with the “grep -oPm1”, as “P” wasn’t recognized. I had to change me command to the following:
I used the above to pull into the Energy Dashboard, and for some reason comparing hourly consumption with the Xcel website my numbers (energy dashboard) were all double what was reported on the Xcel site.
Yeah. I used the utility helper. My understanding is after that I needed to create an automation which would change the “select.UtilityMeter” helper to the right tariff at the right time… then create another variable that changes the price at the same time… At this point, when the utility meter helper produces the different tariff meters, and then loading those into the energy monitor, I most likely could have gotten away with a static price for each tariff, but all the guides said I needed a variable price sensor. It certainly wasn’t very clear.
For the life of me I cannot get a curl command to return anything other than a 404 Not Found.
Connection accepted, TLS handshake negotiated, but…can’t find anything at reasonably known resource locations documented in GitLab documentation or posted in this thread…
The Bash prompt is from command line on my Ubuntu box (running Docker version of HA, so no Terminal add-on). It’s where I’m finding the HTTP/1.1 404 Not Found error.
Also getting 404 with /upt.
I used self-signed cert creation / LFDI as @pdubs10 noted above.
Input that LFDI on Xcel’s site.
At first I was getting a connection refused, as was expected, until the Meter was updated with LFDI.
Days later I started to be able to connect using the cert, but I’ve only gotten the 404 error on response. Looks like handshake is fine / cert recognized … just doesn’t appear to be a resource.
Can someone post sample output that is what should be expected from this curl command?
Supposed to get the Itron smart meter in a month, and I have rooftop solar, so I’m very interested in an HA integration. I’m a former dev, but significantly out of date, so although I’ve done a little Python that Github project scared me off. By the time I could conceivably figure it all out, surely someone will have a working integration.
Does this “pending” status eventually change or do I have to do something manually? My Itron smart meter was installed four days ago in Minneapolis. Thanks!
Just so we’re all clear the solutions you’re referring to is in the 65 by SergeantScar and the post he quoted, correct? I have one of these meters in Denver hooked up to wifi and a Pi so may complete this soon. Will post results.
See the post above by @sss2400 that walks through step-by-step, he took the time to lay it out. Works great, I’ve been running it since early Jan with no interruptions and the reporting is within 99% of what Xcel reports.
If someone wants to take the time to make this into an integration and figure out a better way to dynamically create a certificate that works, by all means please do. But in the interim I can tell you with certainty that this works. The latest update to HA allows you to select an energy conversion for watts to kilowatt hours so there is now no need to create a separate template sensor.
I’m unable to get sensors working so I can monitor Xcel Smart Meter Energy readings for W and kWh.
I enrolled in Xcel Energy Launchpad and have LFDI 58F371CB4CF0FC393B459559576904D1F7E338EE installed and working with these cURL commands to extract kWh and Watts.
I ssh into home assistant to execute these commands to get watts and kWh.