Hi
@ciapw ,
I do like MQTT a lot and I fond it very useful in a few projects. Now, since you control both sides of your implementation (Raspy and Tablet), Erel's suggestion to use B4XSerializator is to be carefully taken in account (it makes things very easy about data exchange). When MQTT (or FCM) is to be preferred is when you send a message "in the wild"..not knowing if the intented listening device it's listening at that time.
Anyway, in both cases you could code a "spec field", so the receiving device could know where to show the received message (or, more generally what to do with that message).
With B4XSerializator is trivial: you define a type where a field indicates what to do with the message field (I would add a m-type field too).
Using MQTT, you could use a single topic, where each message begins with a "code" (i.e "001" means direct the remaining part of the message to label1 and so on). In my implementations I generally devote a topic as the "control codes" channel and one or more topics to real data; this is not needed, but I prefer it that way.