Keeping up with community standards

So... it was said in the "insights" of this small project that the community standards should be upheld. And so i did.
This feature adds the bureaucratic suggestions made by GitHub adding enough fluff for you to read, just in case you have nothing better to do, but adding ABSOLUTELY no extra executable code, fixing any issue or adding any new functionality.
And life goes on...

Keeping up with the variables

No longer supporting MQTT.

Remade all the code.

The one who uses can now configure the variables they are looking for in Tasmota.

Adding some secrets segregation

Added the call to a external file where all secrets will be configured so you can add it to .gitignore and not share it by mistake.

Just create a file secrets.sh at the same level you added the EnergyMeter.sh and copy the configuration with your variables there.

The one that does to much

This is the first release of the code. It does exactly what it was supposed to do, but it misses the point: less configuration work.

This version uses both a one shot per start-up function and one that adds state values to a REST sensor.

• Adding EnergyMeter.sh -m to your Home-assistant startup adds the variables to the MQTT via Home-Assistant MQTT discovery.
• Adding EnergyMeter.sh -e to your crontab -e (add this line with the correct path */1 * * * * /myscripts/EnergyMeter.sh -e > /dev/null 2>&1), or some other scheduler, will send the new sensor values (states) to your Home-assistant via REST sensor.
• Running EnergyMeter.sh -d will show you the data being sent to MQTT or REST sensor.