[Bug]: Custom Build can only see other custom built boards or Heltec V3 (Official Release)

[LagoESP]

Category

Hardware Compatibility

Hardware

DIY

Is this bug report about any UI component firmware like InkHUD or Meshtatic UI (MUI)?

• Meshtastic UI aka MUI colorTFT
• InkHUD ePaper
• OLED slide UI on any display

Firmware Version

2.7.13

Description

I have a custom build, and I am using at home for over a year as a home base the LIlyGo TBeam, and I am unable to see it in my node list. Funny enough, I can see my custom node from the TBeam list, but of course the traceroute doesn't work.

When I manually share the node details via QR Code into my custom node, and I send a message, the message gets received perfectly in my TBeam, but there is no chance that I get the message ACK or any message back to my DIY Node.

When I introduce a Heltec V3 into the equation, regardless if the firmware is manually built from master or using the release on web flasher, then I can see the Heltec V3, traceroute it, message it, and not only that, I can traceroute my home node (TBeam) through the Heltec V3.

The traceroute goes: DIY->TBeam (Direct) | TBeam->Heltec V3->DIY (1 hop). Using the V3 I can see pretty much the rest of the nodes on my area (+100 nodes). The code for this DIY was not changed over the last months, and I can confirm that it used to ping perfectly fine the TBeam, but I can't seem to get this mystery solved.

Any hint?

Relevant log output

[korbinianbauer]

What radio does that mysterious DIY node use?
What Role are the nodes set to?
What channels are configured as primary on each of the nodes?

What does the Debug panel say when you're connected to the DIY node and try to DM the T-Beam?

Have you tried deleting your DIY node from the T-Beams NodeDB?

Have you tried unpairing your DIY node from your phone, restarting the App and pairing it again?

[github-actions[bot]]

This issue has not had any comment or update in the last month. If it is still relevant, please post update comments. If no comments are made, this issue will be closed automagically in 7 days.