54L15 MESH-packet loss

RE: 54L15 MESH-packet loss

Edvin — Mon, 02 Nov 2026 14:35:19 GMT

What kind of HW are you testing this on? Are you using DKs, or custom PCBs? If it is a custom PCB, did you submit your design for a review?

Best regards,

Edvin

RE: 54L15 MESH-packet loss

Nathan — Fri, 30 Oct 2026 09:20:02 GMT

Dear Edvin，

Thanks for you reply.

At present, it is only a pure mesh network without any other BLE connections. After testing 1-2 times for 20 times, there will be 1 to 2 packet losses (instructions to turn on and off the lights), but there will be no packet loss problem in the shielded room.

Compared with competitors who use 52840, we have 54l15. Therefore, I would like to ask what operations can be modified and added to the software to reduce packet loss rate or increase the probability of receiving.

Many thanks,

Nathan

RE: 54L15 MESH-packet loss

Edvin — Thu, 29 Oct 2026 13:56:08 GMT

Tell me, are your other mesh nodes (the ones that are not the EnOcean switch) doing anything other than Bluetooth Mesh? Are they all proxy nodes, for example? Are they using the radio for anything else?

And how many nodes are within radio range of the EnOcean device?

If they are in e.g. a Bluetooth connection, try keeping the connection interval long, and the connection event length short. This is to provide as much radio time as possible for Bluetooth Mesh RX, as this is the backbone for Bluetooth Mesh.

Best regards,

Edvin

RE: 54L15 MESH-packet loss

Nathan — Thu, 29 Oct 2026 10:05:43 GMT

Dear Edvin，

Thank you for your reply. The packet loss rate has indeed decreased, but with more nodes, there is still a probability of not receiving. Can you tell me what parameters the software can add or modify to reduce the packet loss rate?

Many Thanks，

Nathan

RE: 54L15 MESH-packet loss

Edvin — Wed, 28 Oct 2026 13:53:46 GMT

Hello,

[quote user=""]Relay retransmission is 0, and there are no other devices in the network. Each device only has one receiving node. It may be caused by time-division multiplexing.[/quote]

Can you clarify one thing for me. When you are not receiving these packets. You say there is only one receiving node, and no other nodes in the network. Does that mean that you have only one mesh node in your network, in addition to the EnOcean switch?

In that case, this will significantly increase the chances for packet loss in your "network". The mesh node will mostly be in RX mode, but that depends on your application. If it is doing something else (e.g. BLE for application purposes, or using BLE as a proxy node), then it will not be in RX 100% of the time.

If you had one additional node in your network, where the relay count > 0, the chances of the EnOcean packet being missed by the network are significantly smaller.

So a Mesh network of only two nodes, especially if the TX burst count is <2 is not a reliable network. This is probably what you are seeing. Even if the mesh node (not the EnOcean node, but the other one) is not doing any other BLE activities, packets may be lost on air (disturbance/noise). In BLE we have retransmissions to encounter this. In mesh we have the advantage that you have multiple devices close by, so the chances are very low that all devices loose the same packet.

Best regards,

Edvin

RE: 54L15 MESH-packet loss

Nathan — Wed, 28 Oct 2026 04:21:14 GMT

The enocean sample routine for testing SDK with DK board also has similar packet loss issues.