- only works if we don't have a phone connected, but that is probably dsired
- this will send a copy of device-originating text messgaes to a connected phone. Breaking change.
- this will iterate the tophone queue by deconstructing and reconstructing it every time we look for an ID. Probably also mangles the queue oder since it aborts when a ID is found.
- Can we navigate the packet pool instead? If so, how?
- Let's keep this in draft state for now
* Add interested portnums to TextMessageModule
* Send Detection Sensor Module messages on its own portnum
* Add to Ext. Notification and consolidate logic
* RANGE_TEST_APP portnum for RangeTestModule
* Yank mqtt service envelope queue
* trybuildfix mqtt system
* removed too much
* no excessive heap debugging on release builds
* send QueueStatus messages
The QueueStatus message is sent as a response to the attempt to queue
an outgoing MeshPacket and contains statuses of the last queue
attempt, TX Queue space and capacity and MeshPacket.id that was
queued.
When TX Queue changes status from completely full to at least
a single slot free a QueueStatus message is also sent to notify
that user can queue more messages.
Signed-off-by: Pavel Boldin <pavel.b@techspark.engineering>
* WIP: update protobufs
Signed-off-by: Pavel Boldin <pavel.b@techspark.engineering>
* update protobufs
* regen protos
Signed-off-by: Pavel Boldin <pavel.b@techspark.engineering>
Co-authored-by: Ben Meadors <benmmeadors@gmail.com>
Co-authored-by: Thomas Göttgens <tgoettgens@gmail.com>
Co-authored-by: Sacha Weatherstone <sachaw100@hotmail.com>
@professr I noticed you added a "newStatus" observable to the GPS class.
Do you remember why you didn't remove the old GPS status (which seemed
to be dumber). Is it just because you didn't want to risk breaking
MeshService? (I assume) In this change I removed the old Observable
and all seems well (just using newStatus everywhere).
