lol yes exactly, the “measurement” state_class you mentioned is the vague memory I had from months ago when I did this 
I should be able to make the integration set this for you. This was something I did locally but since no one ever asked about this later I never bothered to do anything about it
Would definitely make things more beginner friendly. But do as you please, for me it works well with editing the configuration.yaml 
My bad if I misrepresented anything.
No worries, I appreciate knowing that someone else is getting use out of this integration. I made it for myself back in July or August and it has been silently working without issues while I’ve been incredibly busy on my actual day job and neglecting my grow and esp32 work.
I planned to come back and make this integration installable via HACS but never took the time. I’ll try to circle back and give this project some love again soon and maybe do that.
@monstermash no worries I didn’t assume it was intentional. I just didn’t want it to seem like it was officially endorsed, supported or created by the Pulse folks since they won’t want to deal with support emails asking about something I broke with it 
Also @blackhatgarden if you can clarify any friction points you had in getting things setup the first time, I can update the readme if needed to make it easier for others in the future. Lmk. But if I make it installable via HACS I assume that would be simpler for everyone and make it easier to update/distribute updates.
Sure if I find time I will write down some points. If I remember correctly it was only related to AppDaemon as I never used it before. So finding the right Folders and messing with configuration to load the missing plugin.MQTT for AppDaemon.
I can imagine that a HACS installable version would clearly help, as there are supposed to be people who are not familiar with yaml, shell or reading logfiles. 