I do have a system, that is using a mqtt broker as central state hub (it is an EV Charging station).
The software used in there is quite unique and open source, as well as getting frequent updates.
When I try out a beta version, things sometimes get messed up/unexpected.
While the number of topics used is quite large but the debug log in the EV station is quite small, I thought of ...
a solution to continously record every topic change (maybe keeping the log for a 24-36hrs, not more)
..and when things get wrong (often only discoverd later throughout the day), try and find/evaluate the state/topic change by some way of inspecting/replaying the log (in a nice UI).
I thought of storing things in an influx DB and then finding a way to present the information in a nice UI, when rolling over/replaying the timeline.
Any Ideas, hints, pointers are very welcome!
happy easter and stay save!