In the current implementation of the mqtt message content, its hard to determine (as a mqtt subscriber) if we already seen a message.
In our (more specific case): What message should I put into InfluxDB and what message not?
Current behaviour:
From time to time, my mqtt subscriber recieves a message like matomat;item-consumed;1;1;Club Mate;100;
Wanted behaviour A)
From time to time, my mqtt subscriber recieves a message like matomat;item-consumed;1;1;Club Mate;100;42, where 42 is the total number of Club Mate items consumed
Wanted behaviour B)
From time to time, my mqtt subscriber recieves a message like matomat;item-consumed;1;1;Club Mate;100;1549967539 where 1549967539 is the timestamp the item was consumed
Hi,
In the current implementation of the mqtt message content, its hard to determine (as a mqtt subscriber) if we already seen a message. In our (more specific case): What message should I put into InfluxDB and what message not?
Current behaviour:
From time to time, my mqtt subscriber recieves a message like
matomat;item-consumed;1;1;Club Mate;100;Wanted behaviour A)
From time to time, my mqtt subscriber recieves a message like
matomat;item-consumed;1;1;Club Mate;100;42, where42is the total number of Club Mate items consumedWanted behaviour B)
From time to time, my mqtt subscriber recieves a message like
matomat;item-consumed;1;1;Club Mate;100;1549967539where1549967539is the timestamp the item was consumedPlease pick one (preferably A)