Non-fruity mesh device disconnects immediately a short while after connection

[PriyeshNema]

Hi team,

I'm trying to connect a non-fruity mesh device (ble peripheral) with a fruity mesh device (as ble central). Peripheral device mandates pairing/bonding here.

I created a module to filter the advertising packets and initiate connection using BleGapConnect(), connection happens, but it immediately disconnects. From the logs, looks like from

ConnectionManager.cpp -> GapConnectionConnectedHandler() -> logt("WARNING", "No pending Connection");

fruityMesh disconnects the connections which are non-fruityMesh.

Is there a way to safely handle this situation? Please suggest

Thanks,

[siretty]

Hello @PriyeshNema,

in order for your 'custom' connection to be recognized you will have to implement a connection class (as an example you can take a look at the MeshAccessConnection) and especially implement the ConnTypeResolver (https://www.bluerange.io/docs/fruitymesh/Connections.html) which can select and instanciate the correct connection type.

Kind regards Daniel

[siretty]

You will also have to reference your resolver function in a special section of the binary. For the MeshAccessConnection this is done via the following line

uint32_t meshAccessConnTypeResolver __attribute__((section(".ConnTypeResolvers"), used)) = (u32)MeshAccessConnection::ConnTypeResolver;

in the beginning of the MeshAccessConnection.cpp file. The function MeshAccessConnection::ConnTypeResolver is static (i.e. has no implicit this parameter).

[siretty]

This issue is being closed after 14 days of inactivity. Please feel free to re-open it!