Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Start & Transfer after x dropouts in a period of time #353

Closed
JMVS opened this issue Feb 3, 2020 · 3 comments
Closed
Labels
enhancement request for new features question

Comments

@JMVS
Copy link

JMVS commented Feb 3, 2020

Hi @jgyates.

I know this might be an isolated/edge case but it would be nice if you could implement it.
The electrical service in Argentina is really degraded and in summertime we experience low voltage. I have an autotransformer to cope with that but even sometimes it not enough and we experience short outages as the autotransformer cuts the power when is below the minimum threshold. In turn the generator kicks in and shortly after the voltage comes back to a value the autotransformer can stabilize (it waits for 1 minute before restoring the line power) and the generator goes into cooling down mode and then off. Moments later the same process starts all over again. What I do in these cases is manually start & transfer the gen via genmon's web interface whilst monitoring the utility line status.
Can this process be automated somehow? Like if there are "x" amount of short outages for certain period of time, start & transfer the generator and then wait until the utility power is above a defined level for an "y" amount of time, transfer back to utility, cool down, stop and restart the counter. I know...easier said than done...

This also might be doable with something like Home Assistant (that I have running along with genmon's MQTT). Do we have access to Stop/Start/Start & Transfer via MQTT messages? If possible, anyone care to share a possible setup?

Thanks in advance.

@jgyates jgyates added enhancement request for new features question labels Feb 4, 2020
@jgyates
Copy link
Owner

jgyates commented Feb 4, 2020

@JMVS

Let me think on this. One issue that would need to be thought about is the implementation of the timing: determine how long a low line voltage would need to be low before doing anything. Off the top of my head the parameters could be:

  1. Threshold Voltage - If Utility drops below this value then we pay attention
  2. Pickup Voltage - If Utility if above this it is normal
  3. Minimum Brownout Time - Utility must be below threshold for this period of time to be considered an outage
  4. Minimum Restore Time - Utility must be above the pickup voltage for this period of time to be considered an end of an outage
  5. Number of Outages- Number of outages before "Start and Transfer" is issued
  6. Amount of time without an outage that has to pass before stopping a previous "Start and Transfer"

Does this sound like what you are talking about?

@JMVS
Copy link
Author

JMVS commented Feb 4, 2020

@jgyates Yup. That pretty much covers it.
In my case if in the span of an hour I get 3-4 short outages* I then trasfer to gen's power for an hour (I'm obviously not constantly monitoring the utiliy voltage) and then back to utility power. Fuel consumption should be accounted for.

EDIT: FWIW these short outages show up as 12 secs outages in genmon's log.

*short outages: Please note that this is due to my setup. If I remove the autotransformer from the equation, what I would experiencie would be a dangerous dropout in voltage and not an actual outage.

@jgyates
Copy link
Owner

jgyates commented Sep 29, 2020

I am tracking the feature request list here: https://github.com/jgyates/genmon/blob/master/feature_requests.md

I will be closing this thread for now but the request is still on the master request list.

@jgyates jgyates closed this as completed Sep 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement request for new features question
Projects
None yet
Development

No branches or pull requests

2 participants