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

Alarm notifications not specific #218

Closed
jcherney opened this issue Dec 18, 2018 · 2 comments
Closed

Alarm notifications not specific #218

jcherney opened this issue Dec 18, 2018 · 2 comments
Labels

Comments

@jcherney
Copy link

Hi,

Received an alarm (email and text) this morning, showing as UNKNOWN. Upon logging into the system, the software was showing INSPECT AIR FILTER. I sent logs and registers to you just now- but it seems that the notifications don't (in this case) show the actual alarm problem.

@jcherney
Copy link
Author

Current Alarm: UNKNOWN ALARM: 00000010
System In Alarm: 0001:00000010

@jgyates
Copy link
Owner

jgyates commented Dec 18, 2018

@jcherney

This is expected behavior. The controller status register 0001 outputs unique values for various conditions (switch state, current alarm, etc). These contents of this register is not documented by Generac. Alarm E-Codes are documented by Generac and are used by the alarm a log (the software stores these in ALARMS.txt). The software can only know the values of all of the conditions or register 0001 based on user feedback, which you are providing. I have updated the code 00000010 to correspond to Inspect Air Filter (V1.12.0).

More info on this topic is here:
https://github.com/jgyates/genmon/wiki/Appendix-4-Known-Issues
#13

@jgyates jgyates closed this as completed Dec 18, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants