Get Started with Indicator for Meshtastic | Seeed Studio Wiki

[giscus[bot]]

Get Started with Indicator for Meshtastic | Seeed Studio Wiki

Get Started with SenseCAP Indicator for Meshtastic

https://wiki.seeedstudio.com/sensecap_indicator_meshtastic/

[kd7eir]

This does NOT install the nice graphical interface that Seeed keeps showing people. I smell a rat, at least deceptive advertising!

[yNosGR]

The Fancy-UI is not released yet. You can build it and flash it yourself, but there is not an official build available yet. Here is a howto for the t-deck, the process is not much different for the Indicator. To flash it, use the meshtastic flasher, select the indicator, click the folder icon next to the firmware selector, choose firmware.bin, upload like normal.

[yNosGR]

I was able to build the firmware at gitpod with the following commands.
Remember - this is not supported - so don't go whining in the discord about broken functionality. They know. They are working on it. It'll be done, eventually.

git switch tft-gui-work
git submodule update --init
pio run -e seeed-sensecap-indicator

[kd7eir]

Thank you for that, and I fully understand this is solely POC.

[kd7eir]

I guess I'm just too daft to follow three simple steps because each time I compile and upload, following these steps:

git switch tft-gui-work
git submodule update --init
pio run -e seeed-sensecap-indicator

I end up with the regular non-FancyUI.

I do appreciate your efforts to assist me immensely, though. I'll wait for an official release.

[yNosGR]

My node hasn't landed yet, I'm still waiting on shipping. I'll update after I get it.

[TechMindsYT]

I also confirm that the standard firmware gets built using the above commands, however:

I believe you need to use:

pio run -e seeed-sensecap-indicator-tft

But currently there seems to be an error while compiling.

[yNosGR]

I was able to get it to compile by changing src/mesh//generated/meshtastic/mesh.pb.h line 611 to typedef PB_BYTES_ARRAY_T(237) meshtastic_Data_payload_t;. I don't have a node to test on yet, but at least it compiles.

[kd7eir]

I'll try that later and let you know how it goes. Thank you for the tip.

[TechMindsYT]

Cheers yNosGR, I just changed the code as per your suggestion and it compiled! I have also installed the firmware on to the Indicator and so far, so good. It loads and runs and detects local nodes. Thanks!

[yNosGR]

Glad to be of help, and thanks for making great content!

[PaulSchulz]

I can confirm that this fix works for me as well - 66101bc9
Change 233 -> 237
src/mesh//generated/meshtastic/mesh.pb.h:611 typedef PB_BYTES_ARRAY_T(237) meshtastic_Data_payload_t;

The following is for my own information.

Compiles on Ubuntu 24.10

  git clone https://github.com/meshtastic/firmware meshtastic-firmware
  cd meshtastic-firmware
  python -m venv venv
   . venv/bin/activate
  pip install platformio
  pip install esptool

Make sure everything builds and installs:

  ./bin/build-esp32.sh seeed-sensecap-indicator
  esptool.py write_flash 0x0 .pio/build/seeed-sensecap-indicator/firmware.factory.bin

Build TFT firmware and install:

  git checkout tft-gui-work
  git submodule update --init .
  pio run -e seeed-sensecap-indicator-tft
  esptool.py write_flash 0x0 .pio/build/seeed-sensecap-indicator-tft/firmware.factory.bin

[kd7eir]

Here are my steps:

1. Full erase and install 2.5.15.79da236 Alpha - Indicator boots into meshtastic just fine
2. In gitpod I edit src/mesh/generated/meshtastic/mesh.pb.h line 611 to typedef PB_BYTES_ARRAY_T(237) meshtastic_Data_payload_t;. It compiles with no errors.
3. Download firmware.factory.bin from Gitpod
4. In meshtastic I select SenseCap Indicator, select firmware.factory.bin click on Flash - I do not have the full erase and install option, only Update.
5. Flash firmware - Indicator is left at a blank screen
6. I have repeated the above steps using firmware.bin and get the same results.

Any suggestions other than surrender?

[TechMindsYT]

If you have the firmware.factory.bin file, then I used https://espressif.github.io/esptool-js/ to flash the firmware.

You can use that tool to also erase the flash. I also set the flash address to 0x0000 before pressing the program button.

Hope that helps.

[kd7eir]

I just recompiled, and it looks like there have been no updates yet.

[brothercorvo]

I just recompile all and now get an error
src/mesh/api/PacketAPI.h:4:10: fatal error: comms/PacketServer.h: No such file or directory
any idea?

[kd7eir]

@TechMindsYT That was the answer! Thank you so much.

[psteckler]

If you have the GPS module installed, how can you use the GPS data? Can you send automated messages with your coordinates?

[nfs0619]

Thanks for reaching out! We recommend contacting our technical support team at [email protected]. They will be able to provide you with more detailed guidance on your setup.

[psteckler]

I don't yet have an Indicator device. I was looking for information about use cases for the GPS module, if I should decide to buy one.

[rpwhite3]

Got my sensecap this week, today I tried to update the firmware and it connects and gets to about 20% then stops and the pc looses connection (windows, I get the ding the device disconnected) then nothing. I left it for a few mins but nothings... I can re-start the process but gets to about the same place and noting.. I have tried multiple cables, to both usb c ports, same thing... Any ideas? Thanks!

[rpwhite3]

Yes winblows doesn't even recognize it now, something happened with the power circuit if I had to guess. When I plug in power and then the USB I get a power issue on the USB side... so it's trying to power via the USB power it seems but failing.. dead...oh well, guess I will wait for the new one. And see if Tech Support answers my email ;)...tried the reset button then apply power and nothing.

[Zeke5579]

Can you guys see indicator serial port in the device manager of your computer? Try to following this URL a couple more times: https://wiki.seeedstudio.com/sensecap_indicator_meshtastic/#flash-firmware

[kd7eir]

When I plug in power and then the USB I get a power issue on the USB side

Are you plugging in both USB ports? That is not recommended and is most assuredly the cause of your USB issue with Windows. You can program through either USB port; I use whichever one is most convenient, depending on how I am using that particular Indicator.

[rpwhite3]

Ok to clarify, I don't need USB power when programming the device. I can plug in 1 USB cable to either USB C port and the power from the PC (Windows) should be able to power the device and program it. I will give that a try, but I have a feeling it won't work. I am also being told by SS via email to try to FLASH the bootloader on the device. The issue I have is when plug in the USB C cable from windows it doesn't recognize it at all, but will try again and report back here.

[rpwhite3]

Nothing, I give up, it's dead, got 22% thru flashing and just gave up the ghost. Oh well, wanted to start to learn about Meshtastic but guess I won't be doing that right now... will wait for new updated sensecap indictor... thanks everyone for the help.. I am also discussing with seeed support, to see what my options are if any. :(

[brothercorvo]

It seems that the Meshastic/MeshtasticUI build fails. If you want to fix it yourself you can edit line 493 in ViewController.cpp from

bytes[232], bytes[233], bytes[234], bytes[235], bytes[236]}},
to
bytes[232]}},

however, then I got the error In file included from src/main.cpp:119:
src/mesh/api/PacketAPI.h:4:10: fatal error: comms/PacketServer.h: No such file or directory
#include "comms/PacketServer.h"
the file PacketServer.h in not in the source

[Psycardis]

After reviewing some of the recent changes, I was able to get it working. The comms/PacketServer.h error is the first of a few, here are my notes:

1. changed main.cpp:119 to “PacketServer.h”
2. changed src/mesh/api/PacketAPI.h:4 to “PacketServer.h”
3. changed main.cpp:120 to “PacketClient.h”
4. changed main.cpp:122 to “DeviceScreen.h”
5. changed main.cpp:123 to “DisplayDriverConfig.h"

I then used https://esp.huhn.me to flash the firmware.factory.bin to address 0x0000.

[brothercorvo]

works! thank you @Psycardis great indications

[lhloftin47]

I am looking in main.cpp, but I don't see anything that is labeled 119.
So, what does - changed main.cpp:119 to “PacketServer.h” mean?
I am really stumped, but would like to get the "fancy" interface working for the SenseCAP.

[brothercorvo]

119 is the line number in the file main.ccp.
If you don't know this, probably should wait for the official release

[bl4ck4dd3r]

Mine works up to the point where a large message is received , then it reboots.
No answer from the support email address yet , after 4 days. Sent another copy.
Device is pretty much useless if it reboots every 5 minutes or so.

[Jessie219-web]

Hi there, sorry for the delay, could you help to provide the serial logs to [email protected], then I will check it and get back to you.

[bl4ck4dd3r]

done

[lhloftin47]

Thanks, Corvo, I thought that was the meaning, however, the replacement data did not seem to be relevant. I believe now I was in the wrong file. Another look this morning made more sense. There are certain a lot of files that go into the making of a program.

…

On Jan 24, 2025, at 5:41 AM, Corvo ***@***.***> wrote: 119 is the line number in the file main.ccp. If you don't know this, probably should wait for the official release — Reply to this email directly, view it on GitHub <#1867 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIVC3PBCVKNOHR6I7FPYIEL2MIRIJAVCNFSM6AAAAABRM6JPRGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOJUGI2DENA>. You are receiving this because you commented.

[lhloftin47]

Made a number of changes today, as suggested in comments above. Still get error messages.
Too bad I never really learned programming, :-)
I'll keep checking to see when a viable version is released. Looking forward to it.
Les, WD5BYQ

[carlotech]

mine comes with an alarm clock like. with same model. if i flash it with web flasher it does not looks like one advertised, anyone have 2.5.12 fw sensecap indicator stock firmware pls share?

[lhloftin47]

Carlotech,
The "fancy UI" is not available as yet, except for those whose programming skills are good.
Others of us will have to wait for Seeed to finalize the software. That being said, the comments above can be a guide to seeing program on GitPod and trying to compile it. I was successful in altering the code to remove some error messages, but only more errors appeared.
Hope this helps.

[carlotech]

i have seen few in youtube saying preloaded mestastic fw. even unboxing and power with fw 2.5.12 dont know how that means to you.

[lhloftin47]

The YouTube videos I have seen (two) both say the firmware is beta. The official Seeed Studio website says, "The Fancy-UI firmware has not been officially released yet, it's recommended to flash the Classic-UI firmware described in this wiki."
As far as I know from reading this thread that we post on, the only ones running the fancy ui and those who were able to get the code and modify it to run on their SenseCAP Indicators. I like you, am still wanting for an official release of the firmware.

[kd7eir]

This is correct. I'm one of those who modified and flashed the code using Gitpod. Subsequently, I returned to the Classic UI because the Fancy UI is missing far too many features to be workable. If they ever get it all worked out, it will be great, but until then, it's just a novelty that limits what you can do with your node.

[zano112]

Is there any certain date for official release ?

[kd7eir]

Unfortunately, no.

[bl4ck4dd3r]

Mine is still rebooting on any official firmware.
Unpredictable when it will do it , sometimes several times over an hour and sometimes can go for many hours without issue.
The longest I am aware of that it has run , is 27 or so hours . Currently at 4 Hours. I have 2 Heltec's and 2 Lilygo that don't do this.
It is perhaps as well that by design , the mesh is resilient, still , it is annoying that the SenseCap has a much bigger screen but is pretty much an ornament at the moment.

[carlotech]

the screen has no use at all.

[Jessie219-web]

which firmware version are you using? can you help flash it to the latest version and share the serial monitor log with [email protected]?

[lhloftin47]

SEEED STAFF: The SenseCAP Indicator for Meshtastic is a nice looking device, however, without the newer "Fancy UI" shown in the wiki, I am better off just running my old HeltecV3. Is or when will the updated firmware be available? I have the SenseCAP, but it is not the all-in-one unit I hoped for when I ordered it. Still have to pair with a smartphone or tablet is not what was wanted.

[kd7eir]

I just compiled the Fancy-UI on GitPod with no errors. I thought I had the same reboot errors that others reported, but it is running strong after a few power cycles.

It does not connect to WiFi, and there is no Bluetooth option. It does pick up nodes; it just doesn't provide any manner to interact with them.

Still not a functional product. Back to the standard interface.

[lhloftin47]

Did you have to make any corrections on the code or did it just compile correctly?

[kd7eir]

No changes whatsoever.

git switch tft-gui-work
git submodule update --init
pio run -e seeed-sensecap-indicator-tft

It compiled perfectly.

[lhloftin47]

Complied the code and loaded it to the SenseCAP. However, device would not boot and the serial screen keep repeating this message:
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x3 (RTC_SW_SYS_RST),boot:0x8 (SPI_FAST_FLASH_BOOT)
Saved PC:0x403cdb0a
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fce3808,len:0x4bc
load:0x403c9700,len:0xbd8
load:0x403cc700,len:0x2a0c
entry 0x403c98d0

[kd7eir]

You can use that tool to also erase the flash. I also set the flash address to 0x0000 before pressing the program button. Perhaps one or both of these at a time can help you.

[lhloftin47]

I did them together, but not separate. I may give that a try tomorrow. Thanks.

[lhloftin47]

Used the ESP Tool this morning. Tried without erasing the flash and with erasing the flash. Code seemed to load just fine, but at the end the serial monitor read "Hard resetting via RTS pin..." and then stopped. Tried pushing the green button on top of the device and the pinhole button on the bottom and met with no success. Reloaded a standard Meshtastic using the Web Flasher and returned to the standard interface.
??

[kd7eir]

Mine did that. I just unplugged the USB cable and plugged it back in, and it started normally.

[lhloftin47]

No joy here. Tried plugging and unplugging numerous times. Thanks for the help. Guess I will keep waiting for China to do something.

…

On Feb 13, 2025, at 1:24 PM, kd7eir ***@***.***> wrote: Mine did that. I just unplugged the USB cable and plugged it back in, and it started normally. — Reply to this email directly, view it on GitHub <#1867 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIVC3PA4NZGMWOY73MFLNOD2PTWOFAVCNFSM6AAAAABRM6JPRGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMJZGE4TIMQ>. You are receiving this because you commented.

[etimothyd]

Any updates?

[TechGyver7]

https://meshtastic.org/blog/meshtastic-2-6-preview/?utm_source=Bazaar&utm_campaign=d3d210d176-Bazaar_2_27_25&utm_medium=email&utm_term=0_4b071a49e3-d3d210d176-478229349&goal=0_4b071a49e3-d3d210d176-478229349&mc_cid=d3d210d176&mc_eid=4db1323ac7

[Coopersmith-24601]

Hello! It's May 7th, 2025.

Just curious how the rest of the firmware is coming along so Meshtastic users can have access to the SD card slot, Maps, buzzer, and rest of IO besides simply the GPS?

[Zeke5579]

What you see in the video is the Classic UI, which is the firmware we use in our factory production process. After you received the device, you flashed MUI, which is another set of firmware adapted by Meshtastic for the indicator.

[kd7eir]

The video clearly showed the MUI, including the large keyboard.

The pictures labeled "Desktop Node" and "Car Node" on your page right now show the MUI. The video on your page right now, showing sending and receiving messages between the Indicator and a phone, also shows the MUI.

You forgot to scrub those, huh?

Just who are you trying to gaslight here?

[Zeke5579]

The large keyboard with a black background is another Meshtastic firmware called Classic UI, not MUI. Both can be used on Indicator.

[WJ4IoT]

I am new to the Indicator (freshly received this week) and notice that my previous remark stirred up this discussion. However I am missing any tips on my question: Does the icon appear when a properly formatted CD card is inserted (and device is rebooted)??? on Meshtastic 2.7.0.

But in the meantime after deleting all your replies in my mailbox I got this "beautiful" answer from Seeed:

Currently, Meshtastic does not support development for the RP2040, so you cannot use the RP2040 at this time.
There are also no firmware updates available for the RP2040 at this time.
The open-source community relies on contributions from everyone, so please be patient as Meshtastic continues its development efforts.

All the Best,
Zeke Cai
Field Application Engineer

But Craig @yNosGR claimed he got the maps working on a latest 2.6 build; perhaps he is able to share with us which one exactly.

[yNosGR]

My apologies, I got my threads mixed up. I should delete or strike that
comment.

[WJ4IoT]

No worries, notice you employed already the strikeout which is better than a delete, thanks for that.

Based upon a tiny bit of knowledge I know that an external device can interact with the Meshtastic software, if maps are a bridge to far I wonder if a GPS or other type of sensor can already interact between RP2040 and the ESP of the SenseCap Indicator; they only explicit say something about the Buzzer:（Not developed yet) MLT-8530, Resonant Frequency：2700Hz, about the SD card they say it is supported up to 32GB, sensors are left a bit in the dark (I do not have any so I am fishing now).

However they blame the open-source community it is not developed yet; come you (read Seeed) but a odd combination and say it works with Meshtastic.

Back to a GPS sensor; looking at the picture I was a bit LMPO (aka Laughing My Pants Out) with this sensor bungling at the back and antenna fixed at the top of the Indicator. Most likely they also expect that 3D enthusiasts will create an add-on box.

[WJ4IoT]

Just for your information:

I also replied on Seeed's reaction and expressed my opinion:
If I understand you correctly Seeed put a product on the market with an odd but potential great combination with a RP2040.
They advertise it as a Meshtastic product, but anything working over the RP2040 is not properly developed.
So no maps, no sensors including GPS and no buzzer is working yet, is this assumption correct?
Seeed does not take the lead on this but thinks this is the responsibility of the open-source community, is this assumption correct?
What kind of tools does Seeed do supply us?
Does the present firmware already includes the interaction between the ESP and RP2040 (despite some parts are not working)?
I like the product and realize I need to do a lot more of RTFM but based upon information given by your company I expected a more mature product.

Seeed's reaction:
Thank you for your feedback—we appreciate your patience as we work through the stages of this product.
You’re correct that some features (like maps, GPS, buzzer on MUI) aren’t fully implemented yet. This is a joint effort between Seeed and Meshtastic: we handle the hardware while they lead the open-source firmware development. We’re still refining functionality together with the community. We’re committed to improving this over time and will share updates as they’re ready.
Thanks again for your support and understanding.
All the Best,

Can anyone already share something?

[EsEnZeT]

@WJ4IoT telemetry also didn't work 😂, if only that.

[PWDesign-create]

I recently bought the SenseCAP Inidcator D1 to use with Meshtastic. Once it generates a code for me to pair the app, the firmware keeps getting stuck on the programming page. The only way to get the firmware off of the programming page is to hold and press the Bluetooth icon which then causes it to reboot and disconnects it from the app. I have done a wipe and clean install of several different versions of the firmware to no avail. I have made sure to forget the device in my phone's Bluetooth. I have made sure my phone is not running a VPN. I am pairing it wiith an Iphone 16 Plus. I am not sure if it is a firmware problem or a problem with the SesesCAP. Any suggestions would be welcome.