Currently Rubble will panic when the master sets a non-zero slave latency. It shouldn't do that.
I'm not entirely sure, but I think we can just ignore the field, log a warning, and pretend it's always zero. This will waste energy listening for events that never happen, but should function correctly.
Testing this requires support for requesting a non-zero slave latency from the master.
Currently Rubble will panic when the master sets a non-zero slave latency. It shouldn't do that.
I'm not entirely sure, but I think we can just ignore the field, log a warning, and pretend it's always zero. This will waste energy listening for events that never happen, but should function correctly.
Testing this requires support for requesting a non-zero slave latency from the master.