We have a task loop that stores the incoming mqtt message onto an internal queue, but these messages are the primary triggers for the mtc4bt actions and should not be delayed.
Side effect: the resulting code/library should also be able to run on an eps8266, which could make it possible to experiment with these libaries and an MLC and MTC4PF. Reason, the esp8266 does have one core and no taskloops.
When this branch is done, the antique "Feature remove internal mqtt queue" branch will be removed. For now that branch has some ideas how to remove the queue, but this branch has some suborn merge problems and it not done quite right, there is a better solution.
We have a task loop that stores the incoming mqtt message onto an internal queue, but these messages are the primary triggers for the mtc4bt actions and should not be delayed.
Side effect: the resulting code/library should also be able to run on an eps8266, which could make it possible to experiment with these libaries and an MLC and MTC4PF. Reason, the esp8266 does have one core and no taskloops.
When this branch is done, the antique "Feature remove internal mqtt queue" branch will be removed. For now that branch has some ideas how to remove the queue, but this branch has some suborn merge problems and it not done quite right, there is a better solution.
Without moving files to the MTC4BT tree!