Question: Is the .env file format for custom measurements documented somewhere? #3259
Replies: 1 comment
-
@SirNoName2705 there is no dedicated section yet in documentation to further explain env variables.
Measure tool should ask to resume when script crashed or keyboard interrupted exactly as you expected. It will ask question like this: It will continue where it left.
These are |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi there 👋
I've been experimenting with the measurement script and the
.env
file that comes with it So far, most variables and comments seem self-explanatory, but I couldn’t find any formal documentation for this file – neither in the README nor the repo wiki/discussions.I'd like to ask a few questions to clarify behavior for certain variables:
1.
RESUME=true
Expected behavior:
I assumed this would resume a session that was interrupted earlier (e.g. due to a crash or KeyboardInterrupt), maybe by loading intermediate results?
Actual behavior:
When I set
RESUME=true
, the script still went through most steps again. It's unclear what gets reused or skipped, and no prior session seemed to be resumed. Am I misunderstanding what this flag does?2.
POWERMETER_ENTITY_ID
andVOLTAGEMETER_ENTITY_ID
I’m using Tasmota as power meter:
Question:
Do these entity ID variables (used for Home Assistant integration) have any effect when using
tasmota
as power meter?Or are they only relevant when
POWER_METER=hass
?✍️ Final Thoughts
I’ve successfully completed a few measurements and really appreciate how well this project works overall.
It would be super helpful to have a dedicated
.env
documentation section (maybe in the wiki or a table in the README), explaining which variables are required or optional for which meter/controller types.Thanks a lot for any clarification!
Beta Was this translation helpful? Give feedback.
All reactions