How to Update the Telemetry Update Interval

[jibinbabuamakkattu]

I'm experiencing two issues with our modified firmware:

Telemetry Update Interval Issue:
Although I set the Environment Metrics Update Interval to 30 seconds in the Meshtastic app(connected to t1000e), after reconnecting the device the interval still shows as 1800 seconds. How can we force the firmware to accept a lower interval (e.g., 30s)?

Any guidance on bypassing the 30-minute minimum and ensuring each telemetry packet contains a fresh temperature reading would be greatly appreciated.

Thanks!

[fifieldt]

Hi @jibinbabuamakkattu , can you explain a bit more about your Telemetry use case? 30 second is very fast for these kind of low bandwidth networks.

[JibinBabu1]

I want to get the temperature data frequently, it's okay even if it's not 30s. But for testing i plan to use 30s. It's to get the temperature data of a package that is being transported.
Also i have a doubt on how to flash the transmitter with my custom generated firmware.
Is it by setting the env to t1000e using platformIO(vs code)?

[b8b8]

what preset are you using, longfast?

Would short_turbo work?

[JibinBabu1]

Yes i am currently using longfast.
Let me check with short_turbo

[fifieldt]

Are you using the SENSOR role: https://meshtastic.org/docs/configuration/radio/device/#roles ?

[JibinBabu1]

I have been using CLIENT role Jibin

…

On Sat, Mar 8, 2025 at 11:52 AM Tom Fifield ***@***.***> wrote: Are you using the SENSOR role: https://meshtastic.org/docs/configuration/radio/device/#roles ? — Reply to this email directly, view it on GitHub <#6264 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXF6KL72WXLODU7BKK2O4ZL2TKEDVAVCNFSM6AAAAABYSVFPB6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENBTGMYTGMY> . You are receiving this because you commented.Message ID: ***@***.***>

[fifieldt]

If you switch to Sensor, you'll be able to broadcast temperatures every 5 minutes. Note that this will disable a bunch of other functionality though :)

[jibinbabuamakkattu]

Okay thanks,Let me try it out

…

On Sat, Mar 8, 2025 at 11:59 AM Tom Fifield ***@***.***> wrote: If you switch to Sensor, you'll be able to broadcast temperatures every 5 minutes. Note that this will disable a bunch of other functionality though :) — Reply to this email directly, view it on GitHub <#6264 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A2G5GNHGSVMXRUIQBJT4MYL2TKE5HAVCNFSM6AAAAABYSVFPB6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENBTGMYTKNQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[JibinBabu1]

Tried it but the values in my csv remains the same. Even if its after 30mins or 5mins. Ill explain a bit more about my problem. I added an extra coloumn named temperature to the firmware generated csv in the rangetestmodule.cpp. But the problem is, from where should i get the temperature value so that it is updated with every packet? What i did was that i stored the temp value in the environmentTelemetry.cpp that was used to display it on the heltecv3’s screen to a global variable and used that in the rangetestmodule. But the problem with this was that the temperature keeps repeating and doesnt change( the temp displayed on the screen also doesnt change). So my main question is , how should i access the temperature so that it gets updated in the csv? The 5 mins i asked was for the easiness to debug, bu the temps not updating even after 30mins. So i think it has got to do something with how i access the temperature. From where?or how do i get the temperature values that updates frequently? Jibin On Sat, Mar 8, 2025 at 12:07 PM Jibin Babu Amakkattu < ***@***.***> wrote:

…

Okay thanks,Let me try it out On Sat, Mar 8, 2025 at 11:59 AM Tom Fifield ***@***.***> wrote: > If you switch to Sensor, you'll be able to broadcast temperatures every 5 > minutes. Note that this will disable a bunch of other functionality though > :) > > — > Reply to this email directly, view it on GitHub > < #6264 (reply in thread)>, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/A2G5GNHGSVMXRUIQBJT4MYL2TKE5HAVCNFSM6AAAAABYSVFPB6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENBTGMYTKNQ> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> > — Reply to this email directly, view it on GitHub <#6264 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXF6KLZJ3YSN3XBO3SWKHUT2TKFY5AVCNFSM6AAAAABYSVFPB6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENBTGMYTONI> . You are receiving this because you commented.Message ID: ***@***.***>

[fifieldt]

Do you have a second device? Perhaps plug it into a computer and use that to download the packets from the other device in real time?

You can use the python API eg https://github.com/fifieldt/meshtastic-map-backend/tree/main

[JibinBabu1]

Yes i have a heltecv3 as a reciever,and i am downloading the csv which is being stored in its flash memory from meshtastic.local/rangetest.csv Jibin

…

On Sat, Mar 8, 2025 at 2:22 PM Tom Fifield ***@***.***> wrote: Do you have a second device? Perhaps plug it into a computer and use that to download the packets from the other device in real time? You can use the python API eg https://github.com/fifieldt/meshtastic-map-backend/tree/main — Reply to this email directly, view it on GitHub <#6264 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXF6KL43ADWEEYDVNPOTD432TKVUPAVCNFSM6AAAAABYSVFPB6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENBTGM3DCNI> . You are receiving this because you commented.Message ID: ***@***.***>

[fifieldt]

Yeah, instead of storing in flash memory on the heltec, just write it out on the computer it's plugged into using the API :)