What is being queued by the interface?

[Horst Brinker]

Still playing with mysensors,  there are still many more failure modes than I can sort, and then some FM happens and things sort of start working. Then, they stop working again.  I guess the fairy dust evaporates.

In any case,  maybe I can get a bit of help with this part of the puzzle.  The interface in xtension starts logging ‘queued’ items.  The number of items seems to increase when the sensor has successfully passed a packet to the gateway ( according to the serial monitor ), but xtension hasn’t reacted to the message in the log.

The window I’m seeing this on is:



I can have xtension send a message to the sensor, which makes the round trip and the queued item count does not increase, but a message initiated by the sensor ends up queued.

The way I have found to clear the queue is to disable, then re-enable the interface.  However, those queued messages are then lost.

So, my questions are:
1) what would cause a message to be queued?
2) is there a way to have xtension either list out the queued items or retry receiving or processing them?

Thanks,
Horst
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.machomeautomation.com/pipermail/xtensionlist/attachments/20160917/8f03f918/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PastedGraphic-1.tiff
Type: image/tiff
Size: 21206 bytes
Desc: not available
URL: <http://mail.machomeautomation.com/pipermail/xtensionlist/attachments/20160917/8f03f918/attachment.tiff>