http://genmon.local:8000 not working #1149
-
Checklist
VersionV1.19.02 Have you submitted your log files from the About page? Note that outbound email must be working for logs to be submitted.I have submitted logs What is/are your question(s)?Why isn't the web interface working? Additional informationFor the life of me I cannot get this working. I have and older generac evolution. I ordered a new pi zero w, and the hat from: https://pintsize.me/store/ols/products/generator-hats-and-phat/v/PGI-PHAT I followed the instructions or genmon setup. The hat has constant blue light and it would appear the py scripts cannot communicate with it. In genmon.conf I tried both serial0 and serial1. /var/log/genmon.log: mark@genmon:/var/log $ cat genmon.log Granted, I do not have it plugged into the generator yet, I expected to see a UI before taking it outside. At least the videos linked from the wiki indicate it should have the web interface available. Any guidance, before I return everything and give up? I've tried two micro SD cards, reinstalled several times...same results every time. Thanks |
Beta Was this translation helpful? Give feedback.
Replies: 7 comments 15 replies
-
|
There isn't a wrong HAT, the hardware is the same for all supported controllers. Did you try the serial loopback test while setting up? |
Beta Was this translation helpful? Give feedback.
-
|
Juding only by the log output you show above it looks like you either have the wrong serial port selected, your serial port is not properly setup or your serial device is not responding. You mentioned that you have not connected this to a generator yet. In that case it may take a few minutes to load the UI as the web interface will not load until an attempt has been made to read the generator registers. If you are not connected to the generator then this will result in numerious timeout errrors so if you you are not connected to the generator it may take a couple of minutes to bring up the UI with this many timeout errors. I have not receveid any logs, I am guessing because you have not configured outbound email and can not pull up the web interface. In your message above you indicated that you did send logs so I am assuming that was unintentional. What is the output of this command on the pi? You wrote "I followed the instructions or genmon setup." Did you run the instructions here: https://github.com/jgyates/genmon/wiki/3.3--Setup-genmon-software The script ./genmonmaint.sh asks questions and setups the serial port based on your response. |
Beta Was this translation helpful? Give feedback.
-
|
mark@genmon:/var/log $ ls -la /dev/ser* ok. So loopback fails when run without jumping the pins. It succeeds when jumping them. Here is the startup: mark@genmon: Note: Genmon must NOT be running for this test to work properly. If Genmon is running this test will not function properly, Loopback testing for serial port /dev/serial0... Using python serial library V3.5b0 |
Beta Was this translation helpful? Give feedback.
-
|
Then serial0 is the correct port to use. |
Beta Was this translation helpful? Give feedback.
-
|
is there a way to try the loopback test without buying anything? |
Beta Was this translation helpful? Give feedback.
-
|
being able to use the URL genmon.local may be a function of your router, have you tried using the IP address of the pi instead of genmon.local? Here are alagotor clips: If you have something like this you can use it for a loopback test, however you may just want to try plugging it in to your controller first. So far you do not have any data that suggest your hardware is not working since you have not connected anything to the controller yet. The errors you are getting in your log are consistent with either selecting the wrong serial port and / or not having the pi connected to the controller. If you show the output of this command: we can validate the serial port is active and determine which port you should use (you mentioned changing it to serial1, which is probably not correct) The loopback test will only validate the serial port, it has nothing to do with the web interface. I would suggest the following:
https://github.com/jgyates/genmon/wiki/3.3--Setup-genmon-software
|
Beta Was this translation helpful? Give feedback.
-
|
I have found the scissors on a Swiss army knife work well for the loopback test as well. It is the two right pins on the top row directly on the HAT Molex plug. Do not do if barrel or Molex are connected. |
Beta Was this translation helpful? Give feedback.
-
|
so the serial seems to be working as the serialtest.py fails without jumpers and succeeds with it. I still cannot get anything in the browser. |
Beta Was this translation helpful? Give feedback.
-
|
And using the ipaddress does not work either: http://192.168.0.225:8000 |
Beta Was this translation helpful? Give feedback.
-
|
There might be an error in the install. It is installed to /home/mark/genmon as there was no /home/pi directory. |
Beta Was this translation helpful? Give feedback.
-
|
I linked /home/mark to /home/pi, so that should not be an issue now. This is all that is in the log: |
Beta Was this translation helpful? Give feedback.
-
|
It would appear there is no web server running: |
Beta Was this translation helpful? Give feedback.
-
|
did you run the install script genmonmaint.sh -i? This is the scrip that should be run before starting genmon. If you did not then the loader program genloader.py will attempt to load the missing libaries but it will take a LONG time. It is not recommended to run genmon without running gnemonmaint.sh first. When you do run genmonmaint.sh -i the install script will show any errors so if you are having an issue installing flask then this script will show the install errors. If you did run genmonmaint.sh -i before then show the output of both /var/log/genserv.log and /var/log/genloader.log |
Beta Was this translation helpful? Give feedback.
-
|
mark@genmon:~/genmon $ bash genmonmaint.sh -i |
Beta Was this translation helpful? Give feedback.
-
|
I ran it again, looks like everything was there. I do not have a /var/log/genserv.log |
Beta Was this translation helpful? Give feedback.
-
|
mark@genmon:~/genmon $ cat /etc/issue mark@genmon:~/genmon $ python --version |
Beta Was this translation helpful? Give feedback.
-
|
Trying to start the server directly yields this: mark@genmon: |
Beta Was this translation helpful? Give feedback.
-
|
ok got it. in requirements.txt change |
Beta Was this translation helpful? Give feedback.
-
|
I am glad it is working. Out of curiosity are you running a 32 or 64 bit version of the OS? I have a 64 bit that runs flask 3.0.0 and a test 32 bit system that is running Flask 2.0.3 with no issues. I know sometimes I have seen packages break for relatively short periods of time (before the maintiners can fix them) but usually switching from 32 to 64 or vice versa will correct the issue. The fix you provided will work just, just trying to get data incase this turns out to be an issue for others. |
Beta Was this translation helpful? Give feedback.
-
|
I did the 32 but image. Just kind of followed along the best I could with the YouTube video.
I’m excited to get it in the generator now.
Live, love, pick and strum,
-MrK
On Jul 23, 2024, at 7:03 PM, jgyates ***@***.***> wrote:
I am glad it is working. Out of curiosity are you running a 32 or 64 bit version of the OS?
I have a 64 bit that runs flask 3.0.0 and a test 32 bit system that is running Flask 2.0.3 with no issues. I know sometimes I have seen packages break for relatively short periods of time (before the maintiners can fix them) but usually switching from 32 to 64 or vice versa will correct the issue.
The fix you provided will work just, just trying to get data incase this turns out to be an issue for others.
—
Reply to this email directly, view it on GitHub<#1149 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ALMURDOOUBE2PU3EM24ZVVLZN3VNNAVCNFSM6AAAAABLKIUGFKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMJTGE4DSMI>.
You are receiving this because you modified the open/close state.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
ok got it. in requirements.txt change
Flask -> Flask>=2.2.2
and then everything started as normal