Meshtasticd on Rpi with a SX1262 and BT iOS?

Support
1

I ordered a sx1262 xxxm board from waveshare(sku: 24654). I have it plugged into a Rpi 4. I followed the directions on “Meshtastic on Linux-Native Devices | Meshtastic”

I think I followed the directions correctly, I installed “meshtasticd_2.3.10.d19607b_arm64.deb” on a clean version of Rpi OS Debian Bookworm.

It DOES appear to be working I can send and receive messages via the web interface but I have somethings I do not understand.
The first question is, when I look at the journalctl output for meshtasticd(see below). I am getting “No I2C device configured, skipping.” and “No I2C devices found”, is this normal? Isn’t the sx1262 xxxm on the i2c bus? Also when I do a “i2cdetect -y 1” I don’t see any devices/addresses just “–”. Shouldn’t the Rpi see something on the i2c bus? Sorry I know very little about how i2c works.

Also…

I thought I read somewhere that you can not use the iOS Meshtastic app to configure/use meshtasticd when running on the Rpi, is this correct? I am not seeing it the in the app or it being advertised/discoverable via bluetooth. I thought I would just ask here before I went down that rabbit hole/troubleshooting that issue.

Thank you for any help people can give.

Jun 02 04:17:51 monitor systemd[1]: Started meshtasticd.service - Meshtastic Daemon.

Jun 02 04:17:51 monitor meshtasticd[771]: Portduino is starting, HWID=1, VFS root at /root/.portduino/default

Jun 02 04:17:51 monitor meshtasticd[771]: Setting up Meshtastic on Portduino…

Jun 02 04:17:51 monitor meshtasticd[771]: Using /etc/meshtasticd/config.yaml as config file

Jun 02 18:09:25 monitor meshtasticd[771]: INFO | ??:??:?? 0

Jun 02 18:09:25 monitor meshtasticd[771]:

Jun 02 18:09:25 monitor meshtasticd[771]: //\ E S H T /\ S T / C

Jun 02 18:09:25 monitor meshtasticd[771]:

Jun 02 18:09:25 monitor meshtasticd[771]: INFO | ??:??:?? 0 No I2C device configured, skipping.

Jun 02 18:09:25 monitor meshtasticd[771]: INFO | ??:??:?? 0 No I2C devices found

Jun 02 18:09:25 monitor meshtasticd[771]: INFO | ??:??:?? 0 Meshtastic hwvendor=37, swver=2.3.10.d19607b

Jun 02 18:09:25 monitor meshtasticd[771]: INFO | ??:??:?? 0 Initializing NodeDB

Jun 02 18:09:25 monitor meshtasticd[771]: INFO | ??:??:?? 0 Loading /prefs/db.proto

Jun 02 18:09:25 monitor meshtasticd[771]: INFO | ??:??:?? 0 Loaded /prefs/db.proto successfully

Jun 02 18:09:25 monitor meshtasticd[771]: INFO | ??:??:?? 0 Loaded saved devicestate version 22, with nodecount: 9

2

I have only had luck using python cli and the web interface to connect

3

What I²C device are you expecting to see? The SX1262 XXXM board uses SPI to for communication with the radio module and UART to communicate with the GPS (if present). There is no I²C device on the HAT.

You could connect the classic I²C 0.96" 128x64 OLED display to the Pi I²C pins and it would behave the same as your regular ESP32/nRF etc. Meshtastic boards, but it’s not necessary.

In other words, unless you have some other I²C device that you’re expecting to see, your configuration is correct :slight_smile:

My Android Meshtastic app didn’t see the Meshtastic instance on the Pi initially. I was however able to enter the IP manually and manage it from the app.

Then I realized the service was advertised over mDNS / DNS-SD, so I created the following service file for avahi-daemon (in /etc/avahi/services/meshtastic.service):

<service-group>
 <name replace-wildcards="yes">Meshtastic</name>
 <service>
   <type>_https._tcp</type>
   <port>443</port>
  </service>
</service-group>

Then I restarted avahi-daemon (sudo systemctl restart avahi-daemon) and voilà - the instance showed up in the app :slight_smile:

4

The Bluetooth is not working yet