Description
Currently to use the MQTT status topics/payloads for home automation integration it is required to subscribe to and parse messages that happen every few seconds just to decide which messages represent a major status change (power on, print start, print end). This is because the same topic is used for all and the nature of the event is encoded in the message body.
Describe the solution you'd like
A far more automation friendly MQTT topic structure would allow the type of event to be specified in the topic path. For someone trying to catch print start and print end messages this would reduce the subscription parsing workload from every few seconds to just two.
Additional context
Moonraker just made exactly the kind of commit I am requesting: Arksine/moonraker@e3bcfb5