Home Assistant OS

[defaultuser8]

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

Ubuntu 26.04.1 LTS
Genmon 2.02
Generac 22kw
Evolution

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)?

I finally succeeded in getting Genmon to run on a Beelink T4 Pro using Ubuntu Server, I had previously tried Debian Standard and Alpine Standard with no success. I have a Home Assistant server running on another T4 Pro and was wondering if the HAOS buildroot environment would be enough to add Genmon to that same device instead of having 2 devices. And yes I know I could just run them in Docker but that's not how I want to build out my home server setup. I have a freeNAS 4 bay box running OMV for my "root" home services for my family, and would like to run Home Assistant and Genmon on that one device if possible. Just thought I'd ask before I go to experimenting with my current fully functional setup

Additional information

No response

[jgyates]

Hi @defaultuser8

Unfortunately I do not know much about the HAOS environment. Genmon needs a file system, network access, a serail port (optional) and a python environment that you can load libraries. If you go down this road let me know how it works out or if you run into issues.

Thanks
@jgyates

[defaultuser8]

WOW, ask and you shall receive. Trying it out now, I was going to investigate building my own addon this weekend.

UP and running, just waiting on my esp32 to come in, I have a RS485 converter, but I also need wire and I need molex pins. I'll report back once I get it connected!
Thanks MichaleB2018!

[MichaelB2018]

Hi @defaultuser8 — thanks so much for jumping on this so quickly.

A few tips for when the ESP32 and the Molex pins show up:

• App Configuration tab: turn on Use serial over TCP, put the ESP32's IP address in Serial TCP address, and set Serial TCP port to whatever port your ESP32 firmware listens on (8899 is common for serial bridges). Values you set there get applied to genmon each time the app starts, so that tab is the best place for them.
• Modbus TCP: leave this off unless your ESP32 firmware actually converts to Modbus TCP (that usually runs on port 502). Most ESP32 serial bridges just pass the raw serial data through, and that's what genmon expects with Modbus TCP off.
• Serial settings on the ESP32 side: for an Evolution controller use 9600 baud, 8N1.
• Once genmon is talking to the controller, the genmon-ha integration brings all the generator sensors into Home Assistant.

If anything in the docs is unclear, or something acts up once you're wired in, just let us know here or open an issue on genmon-ha-addon. Feedback from a real setup is exactly what we need right now. Looking forward to hearing how it goes. Good luck with the crimping! 🔧

Michael

[dennis48755]

Thanks @jgyates & @MichaelB2018 for doing this.

Installing into my RPi 5 (with Raspberry Pi M.2 HAT & 512 GB SSD) HA was easy & successful.

I haven't configured the GPIO serial port or moved my GPIO to max3232 board connectors yet. I'm a RPi rookie so I want to follow the configuration instructions carefully.

Also, how can the Outage Logs and Service Journal be copied over. Genmon has been running on my RPi 3B since 2019 so I have significant data I don't want to loose.

Thanks again,
Dennis

[MichaelB2018]

Hi @dennis48755, glad the install went smoothly on the Pi 5!

Good news: you don't have to copy anything by hand. Genmon's About page has Export Configuration and Import Configuration buttons under Actions, and the export bundles the whole genmon config folder (/etc/genmon/ on your 3B). That folder holds more than settings:

• outage.txt: your Outage Log
• maintlog.json: your Service Journal
• kwlog.txt and fuellog.txt: power and fuel history
• sensordata/, plus all the .conf files for genmon and its add-ons

To move everything over:

1. On the RPi 3B: About → Export Configuration. This downloads genmon_backup.tar.gz.
2. On the HA app: open the genmon web UI → About → Import Configuration and pick that file. Genmon restores it into the app's data folder and restarts itself.
3. Check that your Outage and Service Journal pages show your history.

A few things to know:

• Serial port: the import also brings over the 3B's serial settings (probably /dev/serial0). If that port doesn't exist on the Pi 5 under HA OS, the app falls back to a placeholder port so the UI still loads. Just set the right port afterward, preferably in the app's Configuration tab, since those values are applied each time the app starts and take priority.
• Older genmon on the 3B: if you don't see the Export button, either update genmon on the 3B first, or SSH in and run sudo ~/genmon/genmonmaint.sh -b. That creates the same genmon_backup.tar.gz in the genmon folder.
• Size limit: the import accepts files up to 10 MB. Even six years of logs compress well, so you should be fine. If you do hit the limit, let us know and we'll sort it out.
• Keep the 3B as it is until the HA side is wired up and talking to the controller, so you have a fallback.

Let us know how it goes!

Michael

[MichaelB2018]

Hi @dennis48755,

About the GPIO serial board: your max3232 board will work from the app. It uses the Pi's hardware UART on GPIO 14/15, which the app can access like any other serial port. On a Pi 5 under HA OS:

1. Edit config.txt on the HAOS boot partition (put the SSD in a PC, or use an SSH app with protection mode off: /mnt/boot/config.txt) and add dtparam=uart0=on, then reboot.
2. In the app's Configuration tab, set Serial port to /dev/ttyAMA0. Don't use /dev/ttyAMA10; on the Pi 5 that's the separate debug connector, not the GPIO pins.

This is also covered step by step, with settings for each Pi model, in the README, section "Raspberry Pi GPIO serial port (pins 14/15)".

One caveat: the genmon GPIO add-ons (status LEDs / GPIO inputs) aren't supported in the app, so those won't carry over from the 3B.

[dennis48755]

@MichaelB2018 thank you for your information, I will pursue this later this afternoon, after running some errands.

One thing I forgot about, on my RPi 3B in 2022, I installed a PintSize.Me from @skipfire Sensor HAT (current transformers & temp sensor). I wonder if this HAT can work with the RPi 5? If not, I will probably just do without it's sensors.

Dennis

[skipfire]

I can't think of any reason it would not continue to work. Just make sure you enable the SPI the same as you did on the Pi 3B.

[dennis48755]

Great, thanks Jon.

Dennis.

[dennis48755]

I'm having problems editing the config.txt file for the serial port.
I don't have a Linux machine.
Using a StarTech NVMe Dock on my PC, the dock is recognized but no drive is available. This is the same dock I used to put the HA OS image on this M.2 NVMe SSD card.

Additionally, I have Samba installed in the HA OS, can this be used?

[skipfire]

Sorry, missed some of the important context that makes my answer pointless.

Windows cannot edit Linux partitions, but you can install WSL and Ubuntu to have Linux on your PC as well (not a VM but basically a VM) and I've had success mounting and manipulating Linux drives that way.

Is the drive for the Pi 5? If so, you can connect to the Pi directly and edit on the Pi from the OS UI/CLI or via SSH if enabled. A samba share could work, but sharing those key folders may not be a good idea, a network blip while editing or saving while unlikely could kill the system.

[MichaelB2018]

Hi @dennis48755,

Sorry, my earlier instructions were partly wrong: the SSH app can't see /mnt/boot directly. Here's why your dock shows no drive and two ways that do work.

Why Windows shows no drive: on a Pi 5, Home Assistant OS formats the disk as GPT and marks the small boot partition (hassos-boot) as an "EFI System Partition". Windows never assigns a drive letter to those automatically. The partition itself is plain FAT32, so Windows can edit it once you give it a letter. No Linux is needed, although WSL as @skipfire suggested works too. (Pi 3/4 images use the older MBR layout, which is why they show up normally.)

Option 1 – on your PC (SSD in the dock):

1. Open Command Prompt as administrator and run diskpart.
2. list disk → find the ~512 GB disk, then select disk N (N = its number).
3. list partition → select partition 1 (the small ~64 MB one).
4. assign letter=Z, then exit.
5. Open Notepad as administrator (Explorer may say "access denied" on this partition; that's normal), open Z:\config.txt and add this as the last line, below the final [all]:

   dtparam=uart0=on
   

   Save.
6. Back in diskpart: select disk N, select partition 1, remove letter=Z, exit. Eject the dock safely, put the SSD back in the Pi and boot.

Option 2 – on the Pi itself, without removing the SSD, using the Advanced SSH & Web Terminal app:

1. On the app's Info tab, turn Protection mode off.
2. Open its terminal and run:

   docker run --rm -v /mnt/boot:/boot alpine sh -c 'grep -qx "dtparam=uart0=on" /boot/config.txt || echo "dtparam=uart0=on" >> /boot/config.txt; tail -n 3 /boot/config.txt'
   

   The last lines shown should end with dtparam=uart0=on.
3. Reboot the host: ha host reboot.
4. Turn Protection mode back on.

Samba won't help here, by the way: it only shares the Home Assistant folders (config, share, backup, …), not the boot partition.

After the reboot, set Serial port to /dev/ttyAMA0 in the genmon app's Configuration tab and restart the app. The app log lists the serial devices it can see; /dev/ttyAMA0 should now be among them. (Not /dev/ttyAMA10: on a Pi 5 that's the separate debug connector, not GPIO 14/15.)

The change survives Home Assistant OS updates. Let us know how it goes!

Michael

[dennis48755]

System is ready! Use browser or app to configure.
➜ ~ docker run --rm -v /mnt/boot:/boot alpine sh -c 'grep -qx "dtparam=uart0=on" /boot/config.txt || echo "dtparam=uart0=on" >> /boot/config.txt; tail -n 3 /boot/config.txt'
Unable to find image 'alpine:latest' locally
latest: Pulling from library/alpine
36c38f094eae: Download complete
ec67817084c6: Download complete
Digest: sha256:294b683cb724975bec92580e1e685676bd4b50bda910ddb8c51d4cabeaec77e6
Status: Downloaded newer image for alpine:latest
[all]

dtparam=uart0=on
➜ ~

[MichaelB2018]

All good. Nothing needs fixing, and the output is exactly what it should be.

The only thing left is to reboot so the change takes effect: ha host reboot.

One condition: this line is for a Pi 5. If your Pi is a 3 or 4, it needs enable_uart=1 and dtoverlay=disable-bt instead.

[dennis48755]

Also, my logs (outage, Service Journal, etc.) did not import. They exported properly as I can access them in the tar file. Some configurations did import like my settings.
Note: I am not connected yet. I need to transfer my max3232 jumpers over to the RPi 5.

Dennis

[MichaelB2018]

Hi @dennis48755,

Thanks for reporting this. You found a real bug in the app. Your import did work: the outage log and service journal were copied into the app's settings folder. But genmon looks for those files in a different folder, so they don't show up. The same problem means new outages and journal entries would be lost whenever the app restarts.

The fix is in app version 0.1.11, which I've sent to Jason to check in. Once Home Assistant shows the update on the Genmon app page:

1. Click Update.
2. Open the Outage and Service Journal pages. Your history from the 3B should be there. No need to import again, since the files are already in place.

Let us know if the history doesn't show up after the update.

Michael

[dennis48755]

Thanks @MichaelB2018 I will let you know when I get it upgraded.

I'm curious about how maintenance & upgrades will work in the future, not being familiar with github or HA Apps.

Does Jason @jgyates have to maintain two versions of Genmon?

If he updates the Genmon software does it then have to go to you @MichaelB2018 to update the HA App?

If you update the HA App, apparently, it goes to Jason?

Besides being the developer of this incredible program (Genmon) @jgyates is further appreciated for his quick resolution to problems and/or the opportunity to quickly test fixes. Is this process hindered for users of the HA App?

Thanks again
Dennis

[jgyates]

The updates from @MichaelB2018 are in the repository now.

@dennis48755

Only one version of genmon is maintained. New repository only has HA container specific details so as new features are added to genmon no additional changes should be needed to the HA container add on.

The new repository is relatively small so any addition maintenance will likely not be an issue. Also, @MichaelB2018 and I have worked together for many years on genmon. He is the main force behind the web interface of the main genmon project.

[MichaelB2018]

This is simply a wrapper that allows Genmon to be deployed as a Home Assistant app. It pulls Genmon directly from the official repository, so you’ll continue to receive future updates and improvements as they are released upstream.

[dennis48755]

Thanks @jgyates,

Just to be clear, I meant no disrespect towards @MichaelB2018, his work is also greatly appreciated, I was aware he did the web interface work. Also, he has been instrumental in helping me with this project.

I'm just not familiar with how any of this works.

Thanks,
Dennis

[jgyates]

No worries, I did not it that way. All questions are good.

[dennis48755]

@MichaelB2018 fantastic, your fix brought up my logs.

However I have a new hardware problem I could use suggestions with. I went to swap over my GPIO to max3232 board jumpers or even my PintSize.me Sensor HAT and find that the Raspberry m2 HAT is blocking access to the header pins. See attached pics.

[dennis48755]

Hurray, after reading that the M2 HAT doesn't use the header connections, just it's own ribbon cable, I flipped it out of the way and was able to connect the Max3232.

Not only do I have my Outage logs and Journal, I have connection to my generator. It is working nicely.

I could still use suggestions for the above issue. And how to insert the PintSize.me Sensor HAT.

Thanks,
Dennis

[dennis48755]

Could someone help me with how to enable SP1 under the HA OS. For Support of the Raspberry pi HAT with CTs from PintSize.me and the External Current Transformer (CT) Sensors Add-on.

[jgyates]

Hi @dennis48755

SPI (Serial Peripheral Interface) can be enabled with the raspi-config program. If you log in via ssh, from a terminal window type:

 sudo raspi-config

This will run the raspberry pi config tool. It has a text based menu and is used to enabled various features of the pi hardware.

Use the arrow / dirction keys on your keyboard to select "Interface Options", then select SPI, it will prompt to enable or disable SPI. You can exit the program and reboot with the reboot command.

sudo reboot

When the system comes back up SPI will be enabled.

[MichaelB2018]

Try this. It's the same approach we used yesterday for the UART, just with the SPI line instead.

Enable SPI

1. In the Advanced SSH & Web Terminal app, turn Protection mode off on the Info tab.
2. Open its terminal and run:

   docker run --rm -v /mnt/boot:/boot alpine sh -c 'grep -qx "dtparam=spi=on" /boot/config.txt || echo "dtparam=spi=on" >> /boot/config.txt; tail -n 3 /boot/config.txt'

The output should end with dtparam=spi=on, just below your dtparam=uart0=on line.
3. Reboot the host:

   ha host reboot

Check that SPI is enabled

After the reboot, open the terminal again (Protection mode still off) and run:

docker run --rm --privileged alpine sh -c 'ls -l /dev/spidev*'

You should see /dev/spidev0.0 and /dev/spidev0.1. If you get "No such file or directory," SPI isn't enabled yet. Run the first command again and check that dtparam=spi=on is the last line.

Once it's confirmed, turn Protection mode back on.

Note: raspi-config and sudo reboot don't exist on HA OS, which is why you got "command not found" earlier.

Michael

[dennis48755]

Thanks @jgyates I tried that from you Add-On instructions, but I get command not found under the HA OS.

Dennis

[jgyates]

OK, you should be able to do one of the following:

Method 1: Editing via your Computer (Easiest)

1. Shut down your Home Assistant server safely via the web interface (Settings > System > Hardware > Shut Down).

2. Unplug the power and remove the SD card or SSD from the Raspberry Pi.

3. Insert the card/drive into your computer.

4. Open the drive volume labeled boot (or boot/firmware).

5. Locate the file named config.txt and open it with a plain text editor (like Notepad or TextEdit).

6. Scroll to the very bottom of the file and add the following line on its own new line:text

   dtparam=spi=on

7. Save the file and safely eject the card/drive from your computer.

8. Put it back into your Raspberry Pi and power it back up.

Method 2: Editing via Host SSH

If you have already configured debugging SSH access to the HA OS host (operating on port 22222, not the standard web terminal add-on)

1. SSH into your host system.

2. Open the system boot configuration file by running

   nano /mnt/boot/config.txt
   

3. Use the arrow keys to scroll to the bottom and add:text
   dtparam=spi=on

4. Press Ctrl + O then Enter to save, and Ctrl + X to exit.

5. Reboot your system to apply the changes

   sudo reboot

[dennis48755]

Worked perfectly.

I'm all set, everything appears to be working.

I was able to flip the Raspberry M2 HAT so it was mounted under the RPi 5 instead of above it. So I was then able to add the PintSize.me Sensor Hat above and add my Max3232 Board jumpers. Just as they were with my RPi 3B

@MichaelB2018 thank you so much for your help.

Dennis

[MichaelB2018]

Hi @dennis48755,

Perfect, great to hear it's all working, logs and generator connection included!

I'd like to update the documentation with what actually worked for you. Could you let me know which of the commands/steps you ran?

• Serial port (config.txt): did you end up using Option 1 (SSD in the dock + diskpart on Windows) or Option 2 (the docker run ... alpine command from the Advanced SSH & Web Terminal app)? Did you add anything besides dtparam=uart0=on?
• Serial port setting: which port did you set in the app's Configuration tab (/dev/ttyAMA0?)
• Logs: did the Outage Log and Service Journal show up after updating the app to 0.1.11, or did you do anything else?

The tip about flipping the M.2 HAT out of the way to reach the GPIO header is a good one too, I'll add that as well.

Thanks!
Michael

[dennis48755]

G'morn @MichaelB2018.

For the Serial port (config.txt) I followed your suggestion to install the Advanced SSH & Web Terminal App and run the command you provided...
docker run --rm -v /mnt/boot:/boot alpine sh -c 'grep -qx "dtparam=uart0=on" /boot/config.txt || echo "dtparam=uart0=on" >> /boot/config.txt; tail -n 3 /boot/config.txt'

When the NVMe M.2 SSD card was in the dock I looked at it with Windows Disk Manager and it had 8 partitions some looked similar in size. So, I was uncomfortable using diskpart for fear of selecting the wrong partition.

dtparam=uart0=on was the only thing I added at that time.

Near the end of my installation, you helped me add dtparam=spi=on but that was only needed because I have @skipfire PintSize.me Sensor HAT with current transformers. I believe that HAT is now discontinued.

/dev/ttyAMA0 was the Serial port I entered in the app's Configuration tab.

Sorry I'm not sure what I did regarding the logs apperaring. I was impatient and unsure how the 0.1.11 update would be installed. Sure enough soon latter the notification appeared next to the "Settings" menu.

I believe they were accessible right after Genmon restarted.

I do have a problem where not all of the available Outage Log entries are displayed. The outage.txt file is complete, but the listing is truncated. However, I find this same issue with my standalone Genmon setup, so I will submit a separate ticket to @jgyates.

Attached are a couple images of my stacked RPi 5. Even with out the PintSize.me HAT, the header pins were inaccessible with the Raspberry Pi M.2 HAT.

Without the Sensor HAT, one could probably use a GPIO stacking header with longer pins between the RPi 5 and the M.2 HAT. The HAT comes with a 16 mm GPIO stacking header. This would allow access to the header pins for the GPIO Serial Port.

I may pursue other stacking header options as I'm not sure the NVMe M.2 SSD card has enough cooling at the bottom of the stack.

[MichaelB2018]

Hi @dennis48755,

Thanks a lot for the detailed answers, and for the photos! Based on your feedback I've updated the main documentation (README, released as app version 0.1.12):

• New section Moving from an existing genmon install: Export/Import Configuration, then restart the app and set the serial port.
• The diskpart steps now say which partition to pick. A Home Assistant OS disk has 8 partitions, and the boot partition is always partition 1 (64 MB, type System). If you're unsure, use the SSH option instead, like you did.
• A tip for the Pi 5 with the M.2 HAT+: it connects only through its ribbon cable, so you can mount it underneath the Pi to free the GPIO header, as you did.
• An FAQ entry explaining that raspi-config / sudo reboot don't exist on HA OS, plus one on how genmon updates reach the app.

One question about your PintSize.me CT HAT: do the External Current / External Power gauges actually show plausible values in the genmon running in the app?

I'm asking because, as far as I can tell from the Home Assistant and genmon code, it shouldn't work yet:

1. The app only gets access to serial and USB devices. The SPI device is visible inside the app but can't be opened, so the CT add-on would fail with Error on opening SPI device.
2. dtparam=spi=on only enables SPI bus 0. The CT add-on reads bus 1 (/dev/spidev1.0), which the genmon wiki enables with an extra line, dtoverlay=spi1-1cs.

You can check point 2 in the Advanced SSH & Web Terminal app (Protection mode off):

docker run --rm --privileged alpine sh -c 'ls -l /dev/spidev*'

If only spidev0.0 and spidev0.1 show up, bus 1 isn't enabled.

For now the README lists SPI add-ons as not supported in the app. If the gauges stay empty, I can add SPI access in the next app version. You would then only need to add dtoverlay=spi1-1cs the same way you added the SPI line. Your result will tell us which way to go.

Michael

[dennis48755]

Hi @MichaelB2018,

Here are the results from your command...
crw------- 1 root root 153, 0 Oct 8 23:29 /dev/spidev0.0
crw------- 1 root root 153, 2 Oct 8 23:29 /dev/spidev0.1
crw------- 1 root root 153, 1 Oct 8 23:29 /dev/spidev10.0

At this time the CT's are connected to my generator output, so without an outage the graphs are null. I've thought about moving them to the circuit breaker panel feed, but that's kind of a pain.

Michael, I'm concerned about Genmon's internal "Update Software" (About page) not functioning under HA. As much as I really, really like Genmon running under HA, this is a game-changer for me.

I'm afraid that if that is the way it will always be, I will be resorting back to my standalone RPi and Genmon.

Dennis

[dennis48755]

@MichaelB2018 I missed you mentions of the update process, this sounds promissing. I will give it a try.

[MichaelB2018]

@dennis48755: Did you manage to test whether the updates are now working? I'm keen to close this thread too.

[dennis48755]

@MichaelB2018, I don't have a problem with closing this thread.

I upgraded the Genmon App to 0.1.13, but I don't believe I can test the Rebuild function until @jgyates updates the version number or makes a change I can verify/test.

Also, I'm having second thoughts about suggesting to others about moving the Raspberry M.2 HAT off of the header connections. Mine has been working flawlessly for three days, but I have come across mentions from others that the HAT does indeed connect to some header pins. I'm going to try to find a stacking header with longer pins and test them.

Dennis

[MichaelB2018]

genmon-ha-addon 0.1.14 (Home Assistant app): bug fix for genmon's Update button

This is about the Home Assistant app/add-on genmon-ha-addon, not a normal genmon install on a Pi.

In the Home Assistant app, genmon's About → Update Software button didn't work: genmon restarted but stayed on the old version (for example 2.0.2 after 2.0.3 was released).

This is fixed in genmon-ha-addon 0.1.14. To get it, go to Settings → Apps → App store → ⋮ → Check for updates in Home Assistant and install the Genmon app update. That update also brings genmon 2.0.3.

From then on, genmon's Update button works in the app. It takes a few minutes, and genmon is unavailable during that time. Your settings and logs are kept.

[dennis48755]

@MichaelB2018, This is terrific news, thanks so much.

Dennis

[defaultuser8]

Got my ESP32 setup this morning, put the ip address and port into genmon and logs say the esp is sending data but genmon isn't seeing it, does it take a few minutes, or should I be looking for something else?

[defaultuser8]

give me a minute, i'll log in and try it right now, I replaced my MAX board before i left for work. BRB.
So I"m getting this when i run sockettest.py
python3 sockettest.py -a 10.33.40.143 -p 6638

Loopback testing for TCP serial port at 10.33.40.143:6638...

write data: sent test string
waiting to received data....
error communicating...: timed out

I'm running ./startgenmon.sh stop before I run sockettest.py but the webpage is still loading, is that right? If I"m stopping Genmon shouldn't I NOT be able to load the webpage?

last enrty in myserialtcp.log:
2026-10-10 22:47:06,404 : Error in SerialTCPDevice:Write : [Errno 32] Broken pipe : myserialtcp.py:224

last entry in mymodbus.log:
2026-10-10 22:48:11,767 : Error: timeout receiving slave packet for register 002b Buffer: 0, sequence 37

2026-10-10 22:52:43,350 : Generator Monitor Shutdown

ran sockettest.py:
python3 sockettest.py -a 10.33.40.143 -p 6638

Loopback testing for TCP serial port at 10.33.40.143:6638...

write data: sent test string
waiting to received data....
error communicating...: timed out

[22:53:39] ERROR: genmon.py is not running - see /data/log/genmon.log. Retrying...
[22:53:39] INFO: Generator connection: TCP 10.33.40.143:6638
[22:53:39] INFO: Starting genmon...
Starting....
Starting /genmon/genmon.py
2026-10-10 22:53:41,967 : Selected Controller: generac_evo_nexus
2026-10-10 22:53:42,505 : GenMon Loaded for site: McCrory Home using python 3.11: VEnv: False
Starting /genmon/genserv.py
Starting /genmon/addon/genhalink.py
==> /data/log/genserv.log <==
2026-10-10 22:53:46,165 : Starting /genmon/genserv.py, Port:8000, Secure HTTP: False, SelfSignedCert: selfsigned, UseMFA:False, OS:linux, Config:/data/genmon/
==> /data/log/genmon.log <==
2026-10-10 22:54:14,756 : WARNING: Initialization not complete after 30 seconds, possible communication failure. Check cabling.

UPDATE:
(Hopefully the last!)

Finally got a successful loop back test!!!!!!!!!!!!!!!!!!
Sloppy soldering on my part was the culprit, or buying cheap MAX3232 boards off Aliexpress (solder pad had come off the board) either way it's showing a good loop back test.
So, now I just need to move it from the workbench to the generator, hopefully all will go well on the transition.

Thank you both so much for your work!

[defaultuser8]

So got my serial bridge to finally do a proper loop back test, moved it to the generator today but still no joy.
Entries in myserialtcp.log:
2026-10-12 15:15:08,204 : Error: Connect : timed out
2026-10-12 15:30:16,868 : Error in SerialTCPDevice:Write : [Errno 32] Broken pipe : myserialtcp.py:224
2026-10-12 15:45:25,826 : Error in SerialTCPDevice:Read socket error: [Errno 104] Connection reset by peer : myserialtcp.py:199
2026-10-12 16:00:21,642 : Error in SerialTCPDevice:Write : [Errno 32] Broken pipe : myserialtcp.py:224
2026-10-12 16:00:21,642 : Error in SerialTCPDevice:Read socket error: [Errno 9] Bad file descriptor : myserialtcp.py:199
2026-10-12 16:15:21,471 : Error in SerialTCPDevice:Read socket error: [Errno 9] Bad file descriptor : myserialtcp.py:199
2026-10-12 16:15:21,471 : Error in SerialTCPDevice:Write : [Errno 32] Broken pipe : myserialtcp.py:224
2026-10-12 16:30:26,351 : Error in SerialTCPDevice:Read socket error: [Errno 9] Bad file descriptor : myserialtcp.py:199
2026-10-12 16:30:26,351 : Error in SerialTCPDevice:Write : [Errno 32] Broken pipe : myserialtcp.py:224
2026-10-12 16:45:21,202 : Error in SerialTCPDevice:Write : [Errno 32] Broken pipe : myserialtcp.py:224
2026-10-12 17:00:21,056 : Error in SerialTCPDevice:Read socket error: [Errno 9] Bad file descriptor : myserialtcp.py:199
2026-10-12 17:00:21,056 : Error in SerialTCPDevice:Write : [Errno 32] Broken pipe : myserialtcp.py:224
2026-10-12 17:15:25,983 : Error in SerialTCPDevice:Write : [Errno 32] Broken pipe : myserialtcp.py:224
2026-10-12 17:30:25,808 : Error in SerialTCPDevice:Write : [Errno 32] Broken pipe : myserialtcp.py:224
2026-10-12 17:30:25,808 : Error in SerialTCPDevice:Read socket error: [Errno 9] Bad file descriptor : myserialtcp.py:199
2026-10-12 17:45:37,841 : Error in SerialTCPDevice:Write : [Errno 32] Broken pipe : myserialtcp.py:224
2026-10-12 18:00:27,767 : Error in SerialTCPDevice:Write : [Errno 32] Broken pipe : myserialtcp.py:224
2026-10-12 18:15:37,677 : Error in SerialTCPDevice:Write : [Errno 32] Broken pipe : myserialtcp.py:224
2026-10-12 18:15:37,677 : Error in SerialTCPDevice:Read socket error: [Errno 9] Bad file descriptor : myserialtcp.py:199
2026-10-12 18:30:17,434 : Error in SerialTCPDevice:Read socket error: [Errno 104] Connection reset by peer : myserialtcp.py:199
2026-10-12 18:30:18,436 : Error: Connect : timed out
2026-10-12 18:45:27,338 : Error in SerialTCPDevice:Write : [Errno 32] Broken pipe : myserialtcp.py:224
2026-10-12 18:45:27,338 : Error in SerialTCPDevice:Read socket error: [Errno 9] Bad file descriptor : myserialtcp.py:199
2026-10-12 19:00:25,401 : Error in SerialTCPDevice:Read socket error: [Errno 104] Connection reset by peer : myserialtcp.py:199
2026-10-12 19:15:52,127 : Error in SerialTCPDevice:Write : [Errno 32] Broken pipe : myserialtcp.py:224
2026-10-12 19:15:52,127 : Error in SerialTCPDevice:Read socket error: [Errno 9] Bad file descriptor : myserialtcp.py:199
2026-10-12 19:30:31,898 : Error in SerialTCPDevice:Write : [Errno 32] Broken pipe : myserialtcp.py:224

[jgyates]

The errors in your log imply that it is a network connection issue on the TCP side of things. Specifically the "Error: Connect : timed out" means that genmon attempted to establish a TCP socket but it was not accepted by the remote end. If you can use the loopback socket test I would validate the IP address and socket used on the command line match the IP and socket on the Settings -> Communications page in the web interface.

[defaultuser8]

I finally got it working after trying my fourth MAX3232 RS232 converter I guess I finally got one that worked.

[jgyates]

interesting. Thanks for updating the thread with the end result.