FWIW: I considered a custom integration vs the addon I made. The precise SSL setup is tricky to keep working as OpenSSL versions tick up, the meters themselves can be temperamental, etc. I decided the addon was the best way to isolate things to maximize reliability.
I think an integration should likely target full IEEE 2030.5 compatibility so it could work with things beyond Xcel’s meters.
I’m able to get the Itron device connected to my network and I see that it has an IP address. I used nmap to find that there is only port 8081 responding. That port is closed, however, and my attempts at telnet ... 8081 are failing. I think that telnet ought to work, even if I don’t have ssh credentials or whatever, right?
To potentially help others with the issue that landed me here today…
I had this working quite well for over a year until I started trying to get fancy with my MQTT setup and bricked my energy setup (the subtleties of MQTT remain voodoo to me).
The issue for me was that, while the Xcel iTron MQTT Addon would start, connect, and transmit to Mosquitto/MQTT Integration, the sensors would appear in the Xcel Itron device, but the usage numbers stayed constant and were obviously incorrect.
After a bunch of frantic reconfiguring, including deleting the Xcel Addon, Mosquitto, removing the devices and entities from the core config files, and setting it all up from scratch… I still observed the same behavior.
Fortunately/unfortunately, I was not able to isolate the final step(s) that got things working again, but I am reasonably confident it was 1 of 2 things:
I had a somewhat complex Utility Meter Helper setup to track energy consumption/return (solar panels) in the various TOU categories.
I disabled these helper devices and went through the delete/disable/re-enable process again for the Xcel Itron device and addon, potentially with a restart of HA thrown in for good measure.
Before determining whether the above made a difference, I also setup the Xcel My Energy Connection mobile app, which created a new device in the Xcel Energy Launchpad for my account on their site.
Upon setting up the app, I saw that the provided readings appeared to be correct, so I checked back in on HA and… it was working again as expected.
My suspicion is that it was the second bit with the Xcel app that made the difference, and my wild guess is that it triggered a restart of the meter, or at least the API endpoint. This aligns with others’ experience above, wherein contacting/emailing Xcel for a meter restart fixed their issues.
Hope this helps someone out there to avoid the days of frustration!
I have been seeing a very similar issue as well (I also have a solar installation too)- I setup the My Energy Connection app as well, but that didn’t seem to have much effect.
The one thing that did finally work was connecting to the mqtt broker via MQTT Explorer. It seems like it had just gotten stuck a couple weeks ago and connecting that was enough to fix things – no clue why.