ROUTER_LATE should be treated as an impolite telemetry role like ROUTER, responding to multi-hop broadcast requests and using aggressive send timing without channel utilization checks. Co-authored-by: Ben Meadors <benmmeadors@gmail.com>
16 lines
408 B
C++
16 lines
408 B
C++
#pragma once
|
|
|
|
#include "NodeDB.h"
|
|
#include "configuration.h"
|
|
|
|
class BaseTelemetryModule
|
|
{
|
|
protected:
|
|
bool isSensorOrRouterRole() const
|
|
{
|
|
return config.device.role == meshtastic_Config_DeviceConfig_Role_SENSOR ||
|
|
config.device.role == meshtastic_Config_DeviceConfig_Role_ROUTER ||
|
|
config.device.role == meshtastic_Config_DeviceConfig_Role_ROUTER_LATE;
|
|
}
|
|
};
|