Communication Problems

[T-C123]

Checklist

• I made sure that there are no existing issues or discussions - open issues,closed issues,open discussion, closed discussion - which may answer my question or that I could contribute my information to.
• I have read the Known Issues Wiki Page and my question / issue is not listed.
• I have provided the version of the software and the operating system in my post.
• If I have an issue with genmon not communicating with the controller, I have read and followed the serial troubleshooting guide.
• I have included the generator make and model in my submission.

Version

Latest

Have you submitted your log files from the About page? Note that outbound email must be working for logs to be submitted.

I have not submitted logs

What is/are your question(s)?

Sorry I can't get all system details due to the problem I'm having.

I got an email message that my Generac 18 kW generator was exercising and I opened my browser to see the status. I was unable to connect to the generator. IP address was correct, router shows no problems. I'm still getting emails and can send email commands to Genmon to request a status report. Just not able to see the Genmon screen. Tried different browsers and VNC - no help. Running on a Raspberry Pi 4.

It's about 10 degrees out now so I won't be able to look further until the weather warms up, but what should I be looking for?

Thanks much!

To

Additional information

No response

[jgyates]

You mentione that you can not connect to the browser. What response do you get in the browser? timeout, blocked, etc?

Can you ping the pi?
Are you using a static or dynamic IP address?
Do you have an ASUS router (they are known to block some local web servers)?

[jgyates]

Can you access you pi via VNC or SSH?

[T-C123]

Browser returnc "The connection has timed out"
Ping returns "Destination host unreachable"
I'm using a static IP address on a TP-Link router. It has been working without issues for months then lost communication.
VNC returns "Timed out waiting for a response from the computer"
SSH returns "Connection timed out"

Thanks!

[jgyates]

as a test you could change the generator from auto to off, wait about 15 seconds and then set it back to auto. If the pi is still up and genmon operational, you should get emails on the state change of the generator.

If you don't get the emails and you can log in via ssh then the only recourse would be to reboot.

[jgyates]

I agree with @skipfire about the SD card. It also could be a power / ground issue.

[T-C123]

I am getting status updates by email as well as being able to send email commands ("generator: status") to Genmon. SSH & VNC not working. Waiting for the snow to stop.

[T-C123]

I sent log and register files in case you want to see what's going on.

[jgyates]

I do not see anything that would cause a system disruption. There are a couple of errors but they deal with MQTT input add on and an error related to not loading a gauge that may be related to that. Check to make sure all of your external sensors are working (temp or anything imported as an input to genmon via MQTT. Other that that, everything looks good.

[T-C123]

Working now! Walking past my router and on a whim I decided to power off, reboot. When it came back on communication with the Pi was restored. I don't know if the reboot fixed something in the router or triggered the Pi to reset. Previously, all settings in the router looked good and it showed a reserved, permanent IP address for the Pi. All other connections through the router were working normally. Still don't know what caused the issue.

Thanks to everyone for their help and suggestions!

[skipfire]

That brings 2 likely problem causes that can be fixed with the same thing.

If the router is also your wifi, then the Pi likely dropped wifi and reacquired which triggered a DHCP call and refresh. Your Pi may have somehow gotten the wrong IP at some point.

Second (and I'm guessing more likely), perhaps the name resolution or the routing tables in the router was borked and rebooting cleared garbage out of RAM and rebuilt correctly when it came back up.

In either case, I'm glad you are working again, especially without having had to touch anything on the Pi.