meshtastic
[Bug]: No signal on SenseCap Indicator
Category
Hardware Compatibility, Other
Hardware
Other
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.6.4.b89355f Beta
Description
I got no signal after this and node online came to 1 its mine!
and it stays in this state forever, I need to manually restart the device! And I usually have about 20 active nodes around me! and it shows me them after restart!
Update: it hapens in steps: nodes online goes from 22-16-12-7-4-2-1-No signal
I made a restart and all 20-22 nodes are back online!
meshtastic-log-2025-04-26T10-06-31.040Z.log
meshtastic-log-2025-04-25T18-16-25.581Z.log
Relevant log output
INFO | 19:25:35 132227 [Router] Received Admin from=0x0, id=0xfd59cc43, portnum=6, payloadlen=3
INFO | 19:25:35 132227 [Router] Handle admin payload 16
INFO | 19:25:35 132227 [Router] Client got device connection status
DEBUG | 19:25:35 132227 [Router] Set admin key to 34 3b 07 a1 ab 9e 8e a5
DEBUG | 19:25:35 132227 [Router] Partially randomized packet id 2436675652
INFO | 19:25:35 132227 [Router] Asked module 'Admin' to send a response
DEBUG | 19:25:35 132227 [Router] Module 'neighborinfo' wantsPacket=1
INFO | 19:25:35 132227 [Router] Received neighborinfo from=0x0, id=0xfd59cc43, portnum=6, payloadlen=3
DEBUG | 19:25:35 132227 [Router] Module 'neighborinfo' considered
DEBUG | 1900 fr=0x00000000 to=0xda7522d8, WantAck=1, HopLim=0 Ch=0x0 Portnum=6 WANTRESP)
DEBUG | 21:14:15 138747 [PacketAPI] Partially randomized packet id 3366513010
DEBUG | 21:14:15 138747 [PacketAPI] Enqueued local (id=0xc8a8e972 fr=0x00000000 to=0xda7522d8, WantAck=1, HopLim=0 Ch=0x0 Portnum=6 WANTRESP rxtime=1745604855)
DEBUG | 21:14:15 138747 [Router] Add packet record fr=0x0, id=0xc8a8e972
DEBUG | 21:14:15 138747 [Router] handleReceived(REMOTE) (id=0xc8a8e972 fr=0x00000000 to=0xda7522d8, WantAck=1, HopLim=0 Ch=0x0 Portnum=6 WANTRESP rxtime=1745604855)
DEBUG | 21:14:15 138747 [Router] Module 'Admin' wantsPacket=1
INFO | 21:14:15 138747 [Router] Received Admin from=0x0, id=0xc8a8e972, portnum=6, payloadlen=3
INFO | 21:14:15 138747 [Router] Handle admin payload 16
INFO | 21:14:15 138747 [Router] Client got device connection status
DEBUG | 21:14:15 138747 [Router] Set admin key to 93 45 a2 2e 63 00 ae 69
This is not a bug. You lost connection to all other nodes, so it goes to state "no signal".
Ok. but it stay in this state forever, I need to manualy restart the device! and I usualy have about 20 active nodes around me! and it shows me them after restart!
Hi Manuel! Ok. but it stays in this state forever, I need to manually restart the device! And I usually have about 20 active nodes around me! and it shows me them after restart!
On Fri, 25 Apr 2025 at 23:04, Manuel @.***> wrote:
mverch67 left a comment (meshtastic/firmware#6672) https://github.com/meshtastic/firmware/issues/6672#issuecomment-2831331712
This is not a bug. You lost connection to all other nodes, so it goes to state "no signal".
— Reply to this email directly, view it on GitHub https://github.com/meshtastic/firmware/issues/6672#issuecomment-2831331712, or unsubscribe https://github.com/notifications/unsubscribe-auth/BHRZUB2X2N45QN5VV7H6L2L23KILXAVCNFSM6AAAAAB34HYJ3CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMZRGMZTCNZRGI . You are receiving this because you authored the thread.Message ID: @.***>
I suggest you update the description in your bug report. It wasn't clear what you meant.
After restart an d few minutes I got back lots of Online nodes.
meshtastic-log-2025-04-26T10-22-24.026Z.log
last update: 28 minutes uptime and I got almost all nodes online it just cant be that in some random time they all went offline!
and after 50 minutes uptime i got as usuall about 22-25 online
I dont know is it a coincidence or what, got a new antenna, now always positive SNR and no more No signal! Will test longer but now 3 days online!
Q) when did you buy your device? I heard that some very early models had an issue but don't know any details...
Already return my first purchase and got new version about a month ago! First one was with a restart problem! every 10-30 minutes
I want to report I'm having the same issue with one of these. Works for between 2 and 24 hours, then stops receiving/transmitting packets.
I was purchased a month ago, not the old batch that had issues (I have two of those as well, which oddly DON'T have this issue, but only will send big packets on faster spread factors)
Does it only happen when wifi/mqtt is enabled as displayed in the pictures? Also, if you don't have a GPS module attached (and the proper firmware loaded on the rp2040) I would try to disable GPS.
In my case with wifi and MQTT off and on too. As I say before now with different antena it happens twice a week!
I've got the same issue with MQTT and wifi on. I've not tested MQTT and wifi off yet.
I've only just contacted Seeed Studio support, and they've yet to examine my logs, but they've suggested that the issue may be that I have a lot of nodes around me (usually around 90 out of 170), and if they're sending messages to each other it may cause a memory overflow.
I've only just contacted Seeed Studio support, and they've yet to examine my logs, but they've suggested that the issue may be that I have a lot of nodes around me (usually around 90 out of 170), and if they're sending messages to each other it may cause a memory overflow.
I doubt that it's because out-of-memory due to number of nodes. It should work fine also with 250 nodes, just before old nodes get purged from the list (to avoid out-of-memory issue). Also when it's low on memory the node would reboot and not just keep running and ignoring RF traffic.
What can cause out-out-memory for LVGL PSRAM memory (see very last entry on home screen) is the number of messages received and stored. Above ~3000 stored messages this could cause an issue and old chats should be removed manually. However, this is also not related to the RF issue, the firmware also does not use PSRAM.
Hi all, I seemed to also have this issue – but only with Wifi enabled. With wifi off and only connecting via bluetooth, it seems to work happily.
Hi all, I have this some issue with Wifi enabled, GPS enabled, about 250 nodes in DB. I will make step test:
- tomorrow with disabled WiFi
- next - disabled Wifi and GPS I have 3 another (different) nodes which work 2-3 weeks without any issues or freezing.
After numerous tests, I have come to the conclusion that this is a memory-related issue in Indicator.
Actions I have tested:
- updates to the latest versions, including 2.7.7 alpha
- installation with or without Meshtastic UI
- configuration with or without GPS
- configuration with or without Wi-Fi.
- UDP Broadcasting enabled or disabled
- configuration with or without Bluetooth.
- MQTT enabled or disabled
- telemetry enabled or disabled
- power saving enabled or disabled
- power supply from a USB power adapter or USB PowerBank, monitored, very stable power supply.
It may be important to note that there are many nodes in my environment (approx. 300), which can significantly burden the device's memory.
All these actions did not bring clear results, they only improved performance for a few hours.
The only action that brought a longer improvement, for several hours, was reinstalling the firmware.
After reinstallation, the device worked properly for several hours. After several hours, the first “no signal” problem occurred, and then it got worse and worse.
After subsequent restarts (regardless of whether via the ‘shutdown’ function or by disconnecting the power supply):
- subsequent functions were disabled: GPS, Wi-Fi, “no signal”- the device saw the Lora Signal, was able to send messages, but was unable to receive them
- despite attempts to activate the functions that had turned off automatically, e.g., Wi-Fi or GPS (clicking the icon or changing the parameters via client.meshtastic.org), there was no improvement. The functions remained inactive.
Therefore, I conclude that the problem is a faulty device memory that damages data over time. I will request a replacement device from seeedstudio.
My Seeed SenseCAP Indicator model: DIL Z4T-D1-A S/N: 114993532251300209
Final test:
- update to meshtastic 2.7.8 alpha
- test with and without GPS, Wifi, MQTT - no influence, "no signal" after 2-24h
I asked seeedstudio for replecement.