Going to move this issue out here in its own thread so hopefully it will not get buried. I have done some very novice poking around. I have tried uninstalling and reinstalling meshtasticd and meshtastic-mui. I have tried resetting meshtasticd and restarting it. The only thing maybe of significance that I found is when trying to manually start meshtasticd it complained of a portduino error.
I’ll take a look at it tomorrow and see what’s going on.
can you post the full error messages? that usually helps diagnose issues.
1 Like
Sounds Good!! Thanks Rex, appreciate your hard work.
Portduino is starting, VFS root at /home/xxxx/.portduino/default
Using /etc/meshtasticd/config.yaml as config file
MAC ADDRESS: xx:xx:xx:xx:xx:xx
Initializing GPIO26 on chip gpiochip0
meshtasticd: pio/packages/framework-portduino/cores/portduino/linux/gpio/LinuxGPIOPin.cpp:249: gpiod_line_request* LinuxGPIOPin::getLine(const char*, int): Assertion `0’ failed.
Aborted
Forgot to mention that this is an AIO v1.
1 Like
I’m using a v2 board and can confirm the same error message. Ran as root and as myself with the same results.
The odd thing is that Meshtastic appears to be intermittently running on the uConsole despite the error messages and not being able to connect. My roof top node picked it up yesterday when I was messing with it. It just seems to be some sort of conflict between MUI , the browers based client and Trixie.
Ran sudo systemctl status meshtasticd recived following:
:~ $ sudo systemctl status meshtasticd
Ă— meshtasticd.service - Meshtastic Daemon
Loaded: loaded (/usr/lib/systemd/system/meshtasticd.service; enabled; pres>
Active: failed (Result: start-limit-hit) since Mon 2026-07-20 20:35:05 CDT>
Duration: 49ms
Invocation: 3151cea6d127462ab8a1b7c2ae4511df
Process: 5978 ExecStart=/usr/bin/meshtasticd-start.sh (code=exited, status>
Main PID: 5978 (code=exited, status=0/SUCCESS)
Jul 20 20:35:05 clockworkpi systemd[1]: meshtasticd.service: Scheduled restart >
Jul 20 20:35:05 clockworkpi systemd[1]: meshtasticd.service: Start request repe>
Jul 20 20:35:05 clockworkpi systemd[1]: meshtasticd.service: Failed with result>
Jul 20 20:35:05 clockworkpi systemd[1]: Failed to start meshtasticd.service - M>
lines 1-12/12 (END)
Ă— meshtasticd.service - Meshtastic Daemon
Loaded: loaded (/usr/lib/systemd/system/meshtasticd.service; enabled; preset: enable>
Active: failed (Result: start-limit-hit) since Mon 2026-07-20 20:35:05 CDT; 15s ago
Duration: 49ms
Invocation: 3151cea6d127462ab8a1b7c2ae4511df
Process: 5978 ExecStart=/usr/bin/meshtasticd-start.sh (code=exited, status=0/SUCCESS)
Main PID: 5978 (code=exited, status=0/SUCCESS)
Jul 20 20:35:05 clockworkpi systemd[1]: meshtasticd.service: Scheduled restart job, resta>
Jul 20 20:35:05 clockworkpi systemd[1]: meshtasticd.service: Start request repeated too q>
Jul 20 20:35:05 clockworkpi systemd[1]: meshtasticd.service: Failed with result 'start-li>
Jul 20 20:35:05 clockworkpi systemd[1]: Failed to start meshtasticd.service - Meshtastic >
~
~
~
~
~
~
~
~
~
~
lines 1-12/12 (END)
I have Meshtastic working again on uConsole, Trixie, AIO V1. I will test for a while and make sure it stays up and running. Thanks to hamphun post for getting my mind moving in the correct direction.
I am learning as I am trying to figure things out. I am not sure if what I did was 100% the correct way to fix this problem, but it worked for me. Try at Your own risk. maybe one of the more experienced forum members can decipher this and find an easier way to accomplish this.
sudo nano /etc/meshtasticd/config.yaml
added gpiochip: 15 at bottom of lora section. ctrl s ctrl x
sudo systemctl reset-failed meshtasticd
sudo systemctl restart meshtasticd
sudo systemctl status meshtasticd
did not recieve above error when manually restarting meshtasticd
I had to do the following since I had been poking around and changing things
uninstalled meshtasticd
rebooted
reinstalled meshtasticd
Tried mui and web app are working.
1 Like
Hey hey, that worked! I didn’t have to remove and reinstall meshtasticd because I didn’t poke around and change things. I waited for someone else to do that and here you are! Thanks so much for taking one for the team!
1 Like
Just seeing this now… I replaced the meshtastic ui menu item with a bash script that activated the chip, waited, restarted meshtasticd, waited and then opened meshtasticui…
You can’t restart.. sorry.. you have to stop and start it because of that error.. that was one of the things
Hey, have you found a fix to this? I have installed your Dragon OS and have installed the complete v2 package and when I try to open Meshtatsic web I get the “unable to connect” then when i open the Meshtastic app I get the “Connection failed” and won’t proceed to open.
Did you turn on the lora radio then stop and start meshtasticd cd with systemctl? Because on the V2 the radios are off by default you have to activate it then start the meshtasticd service.
How do I turn it on? Forgive me as I’m new to the uconsole world.
Hey, I figured how to make sure its set on and then I restarted meshtastic by the command and I am still getting the meshtastic failed to connect and the ui site is stating site cant be reached. The website address is just localhost. I did get PyGPS to work.
did you stop and start or just restart the service?
I finally got it running. I completely uninstalled it, uninstalled the aiov2 ctr and then installed the aiov2 ctr and then reinstalled the meshtastic by itself and reboot it and now it’s fully working. Thanks for getting back to me.