Meshtastic wish list

Development
1

Hi everyone !

First, thanks to all the great devs for such a nice piece of software, very useful and fun!

Here is my wish list for Meshtastic’s Santa Claus.
Features and bug fixes I would love to see implemented (I’m using firmware 2.3.12)

WEB CLIENT

  • implement all Android app settings (fixed GPS settings, licensed ham setting, …)

ANDROID APP

  • allow a single application to easily manage several devices (with tabs, for example)
  • allow all setting changes to be sent together, so that there is only one reboot
  • improve the stability of the connection to devices
  • adapt settings to suit the hardware, and hide irrelevant settings (e.g. store and forward, when the right memory does not exist)
  • be able to manage android notifications (for example, only receive direct messages, but not notify new devices discovered)
  • tool for visualising mesh topology and the quality of links between nodes
  • improve channel management (delete, add, modify)
  • improve conversations (“reply to” mode)

DEVICES/FIRMWARE

  • Allow several clients to be connected to the same device, and for messages received or sent to be synchronised between all the clients.
  • debug the traceroute tool, which most of the time doesn’t work (perhaps linked to MQTT)
  • add a simple PING utility, with display of response time

Thanks again for the hard work

3 Likes
2

  1. I will ask for integration with reticulum.network. Web interface possible much simpler than a website. Or pipe interface.

  2. I need a integrate between band. For example ham operator should be able to transmit data to meshtastic and read back.
    The meshtastic from 433MHz should forward packets to 868MHz, etc.

3

I’m not sure I understand your point, but it is possible to create a gateway between the 868 and 433 networks simply by adding a node connected with MQTT.

4

How connect band without internet?
Why not glue devices? using any i2c or other interface or serial usb?
MQTT is not this same than normal message meshtastic, no encryption (or different encryption)

5

And choice your own Notification Sound for the iOS App👍🏻

6

You can use tiny RPi as hotspot without internet to run a MQTT server.

7

How about a super cut down firmware for trackers and sensors. No receive functionality, just simple sleep or deep sleep options, transmit at set times.

Have been playing with the heltec capsule and would like to get decent battery life from it.

8

This is what the sensor role does already if you turn on power saving

9

Sensor mode is doing that … sleep … wakeup … messure + send data … sleep

“Every role except for the … SENSOR roles are capable of traditional sleep behavior using the power.is_power_saving setting.”

10

Maybe it’s just the hardware I have then. They don’t sleep correctly. The heltec HT-CT62 and heltec capsule sensor.

They still receive messages in sensor and tracker role with power saver enabled which is trick at they don’t give the option in the app but managed to get it enabled. The capsule appears to just reboot constantly when power saving is enabled.

Will see how it goes when the RAK wireless hard turns up. I know the documentation makes sensor or tracker mode sound great but just hasn’t worked for me yet.

11

i have devices Rak 19003 4631
some running in tracker
and some in sensor mode. (my energy saving option when solar routers battery is almost empty)
that works perfectly “out of the box”

i wish my capsule would :slight_smile:

12

These are devices that have had partial support for like a month.

13

Just doing some further testing in the ht-ct62 with some modded firmware to get it working with a sensor and get power saving mode accessible like I did for the capsule sensor.
However as soon as it’s hit the 300 second light sleep limit I get a new reading so I think it’s rebooting from the deep sleep signal.

I didn’t realise these were very new and barely support modules until I already had a few. I’ll try reach out to I think it was Aaron from heltec who got us a variant setup for the capsule and see if he can help with the deep sleep reboot issue.

14

TLoRa2.1-1.6 run 3 month with sensor update every hour at 3x AAA battery.

15

That’s more like the battery life I want. But also want it super tiny and light as it’s for a cat collar. 250mah battery and would like 7 days with 10minutes gps transmissions. Looks technically possible but just have to get the right hardware combo and software working

16

Reliable firmware updates via BT or IP from the Andriod app. :slightly_smiling_face:

2 Likes
17

could you please detail how you managed to enable the power saving for heltec capsule? it’s driving me nuts. thanks!

18

uplad newest firmware ! in original /older firmware , pwer saving does not work

19

i am on 2.5.4.8d288d5 and the power saving mode does not really seem to work.

20

ok, standard settings,
then:
power saving on
role: tracker,
gps position boradcast intervall something longer like 300 or 3000 …
then it should sleep betweeen fixes.
but it needs to get a fix ! so put it outside for testing. (or give gps data by phone)

my capsule is on 2.5.3 alpha and its working…
nevertheless runtime is still not very good… some days only.