I don't like how ConEd represents electricity usage data, and want something that appeals to me visually.
I've used The Elastic Stack for this in the past and have containerized it before, so that seems easy.
Then, you can populate a ./.credentials.env file like:
[email protected]
LOGIN_PASSWORD=password
LOGIN_TOTP_SECRET=JBSWY3DPEHPK3PXP
ACCOUNT_UUID=b6a7954a-f9a0-46bf-92a5-2ccc8e50a755
METER_NUMBER=123456890
COST_PER_KWH=0.30
This will feed data to the ConEd Collector container.
It's not great, but there is a Make function for testing your ConEd credentials. The biggest limitation is that the output is noisy and a bit unclear. In brief if you don't see documents get pushed to Elasticsearch, you didn't successfully pull data from ConEd's website. If you didn't get data from ConEd's website, your .credentials.env file probably has an error.
make test_coned_creds
The output of a succesful run of this test command is here.
Dependencies:
- Aforementioned setup for ConEd interaction
docker-composemake, if you want any semblance of security
Recommended way to start this up is to run:
make start
That will generate unique password for Elasticsearch and Kibana.
Note: even in this configuration there will be a user viewer and password password; but it lacks privilege to do anything destructive.
You technically can just run docker-compose up but it will use the passwords that have been comitted into the public repo. Whether or not this really matters depends on the level of network exposure for the endpoints.