Better sensor naming support

The previous release(s) all had a bug in them that I'd left in from the beginning, where the code would expect to see a specific sensor ID and fail gracelessly (or output zeroes) if this wasn't found in HA.

It would also cause the tool to ignore the value for sensor_id in config.yaml.

That's now fixed ✅

Release faster

This is just a quick update to the release script to make it build everything in parallel, rather than in sequence.

Config and error handling fixes

What's Changed

** You will need to add sensor_id to your config.yaml to match your power consumption sensor, e.g. sensor.power_consumption, as configured in your Energy Config in HA.

✅ Features

• Power consumption sensor ID is now configurable. It was previously hard-coded, meaning this wouldn't work for anyone else.
• Initial config setup asks for sensor ID
  ⚠️ Bug fixes ⚠️
• Handle zero results from the API gracefully instead of panicking and dumping a stack trace.
• Notify user if sensor ID is not configured.

Full Changelog: v0.1.1...v0.1.2

v0.1.1

What's Changed

⚠️ Fix bug with websocket URL

The code wasn't:

1. Reading the base URL from the config file
2. Detecting whether we're using HTTP/HTTPS
3. Converting it into a usable ws:// URL for the dialer.

💪🏻 Improve user config input

Rather than using fmt.Scanln we can use a lightweight prompt library to hide things like the API key.

I also noticed that the code doesn't validate the URL that the user inputs so if they write some gibberish, it might not even work as a URL.

🔧 Added an insecure flag (-i | --insecure) to the app so that it can be run against Home Assistant instances which use a self-signed certificate

First release

First release. There are likely to be bugs.

New Contributors

• @poolski made their first contribution in #1

Full Changelog: https://github.com/poolski/powertracker/commits/v0.1.0