No change, it still says “Pending” two weeks after the meter was installed. When I visit Xcel’s Usage page the meter is reporting usage in 15-minute increments. Lmk if you figure out how to update it.
Mine was pending for more than a month.
1 Like
How long did it take peole for the meter to get an IP address?
Started a new repo for this project. Its VERY rough currently, but the idea is to poll the meter and convert that to MQTT to send to home assistant. So far I have mDNS working, it finds my meter and uses that IP address for making HTTPS requests to. Now I’m working on programmatically breaking the response down into the different endpoints from the meter. Once that’s done I can convert the responses to MQTT messages and send those off!
Feel free to contribute, make suggestions, etc.
3 Likes
I e-mailed [email protected] and they told me to go to here to see if I was enrolled:
https://my.xcelenergy.com/MyAccount/s/meters-and-devices/
I guess I wasn’t.
I did that, added WiFi details and its Ready to Go and I can see it on my network.
Haven’t done anything else at this point, but probably will tomorrow.
1 Like
Still not joined to my network…
Mined added and popped up on my network within a few minutes when I entered in the WiFi info the other day.
Maybe its something with your WiFi network.
I saw that the WiFi name entered is case sensitive.
I have 5 and 2.4 networks split… using the 2.4 for just IoT stuff.
In my situation, one of my IoT devices doesn’t support special characters for some odd reason, so my 2.4 network’s password is only letters and numbers.
Not sure if the ITron has the same limitations.
Also I had a device have issues joining to a hidden network, so if yours is hidden, that would be something to look into.
Hope you find a solution.
I must have fat fingered something. Put the credentials in again and it joined in seconds.
Am I missing a step between running the first openssl and getting the cert.pem and key.pem files? Are they located in a specific folder within HA? I’ve check /etc/ssl and /ssl and don’t see either.
Using you first post, I created the files and pasted in your text, but get “Failed to connect to IP_ADD port 8081 after XXXms.” after running
curl --ciphers ECDHE-ECDSA-AES128-CCM8 --insecure -v --url https://IP_ADD:8081/upt --cert /config/xcelcerts/cert.pem --key /config/xcelcerts/key.pem
You probably need to replace IP_ADD with the IP Address of the device on your network.
I have the IP of my meter in my actual script. This was for reference only, like the original posts.
Alright, my Xcel Meter 2 Itron Repo is ready! I think?
I’ve just finished it and it automates most of the process. Hope the README covers how to get this up and running (assuming the meter is already on your network).
I will add some more docs about the previous steps of adding the meter to your wifi network through Xcel’s site etc, but for now, those who already have that bit working try this out and let me know what happens.
2 Likes
I need to figure out how to get this built on unraid.
I was able to output the certificate and key text from my self generated cert and add the LFDI to xcel devices. However, I continue to get:
➜ ~ curl --ciphers ECDHE-ECDSA-AES128-CCM8 --insecure -v --url https://192.168.251.105:8081/upt --cert /config/xcelcerts/cert.pem --key /config/xcelcerts/key.pem
* Trying 192.168.251.105:8081...
* connect to 192.168.251.105 port 8081 failed: Connection refused
* Failed to connect to 192.168.251.105 port 8081 after 223 ms: Couldn't connect to server
* Closing connection 0
curl: (7) Failed to connect to 192.168.251.105 port 8081 after 223 ms: Couldn't connect to server
Any input would be greatly appreciated.
Device is connected to my IoT 2.4GHz network and I can see its IP, as input. Added allow external directories to homeassistant config.
homeassistant:
allowlist_external_dirs:
- "/config/xcelcerts"
It took my meter a few days to start responding after setting up the LFDI on Xcel’s site
2 Likes
Great to know, thank you!
If you want to test all your other stuff, you could just just the example cert provided at the top of the thread from the Xcel documentation— The cert posted by @sss2400 on 1/3/2023 above. I had used that and it worked near instantly. Maybe try that to make sure all is working then add the complexity after you’ve got everything else working?
I’ve tried it with both and still get “Connection Refused.” Not sure where I’m going wrong. Even tried moving to a different 2.4 network without any special characters. I can connect via the Xcel site, see it on my network, IP updated. At a loss.
1 Like
Have mine up and running but am noticing pretty material discrepancies between what the meter is reporting and what Xcel is reporting. Typically, my consumption is substantially higher than what is being reported by Xcel.
For example, yesterday I recorded ~60kWh but actual consumption recorded by Xcel was ~45kWh. Sometimes the discrepancy isn’t as wide, but nonetheless, the reading from the meter are typically higher.
Using the following in config for command:
command: "/usr/bin/curl --ciphers ECDHE-ECDSA-AES128-CCM8 --insecure --url https://xxx.xxx.xxx.xxx:8081/upt/1/mr/3/r --cert /config/itron/cert.pem --key /config/itron/key.pem 2>&1 |
grep -o '<value>.*</value>' | grep -Eo '[0-9]+'"
value_template: "{{ value | multiply(0.001) | round(3)}}"
Anyone else seeing discrepancies in what they’re reading from the meter and what is being reported on Xcel’s usage website?