Provide automation friendly MQTT topics

[sprior]

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: https://github.com/Arksine/moonraker/commit/e3bcfb5ea0a3256bdbe19855d20c4431b57cd398

[andreifinski]

need this as well!

[LayerCakeMakes]

+1 this just makes sense to me

[Kaloszer]

+1

[frakki1986]

+1

[KyleTeal]

+1

[NairoDorian]

+1

[FlyingHippo]

+1 But https://github.com/bambulab/BambuStudio/issues/1536 has higher priority for me

[Metallica22]

+1

[mike391]

+1

[kylek29]

+1 Sensible request.

[trati629]

+1

[LordBoos]

+1

[Nicoautoxp]

+1 for me too

[pandel]

+1

[FriedCheese2006]

+1

[NPetersenDK]

+1 - love more MQTT Integration <3

[kriordan37]

+1

[chansearrington]

+1

[Pitax]

+1

[ZanzyTHEbar]

+1

[hubertron]

Would love to see this as well

[jimtng]

+1

[apadua]

+1

[cbenhagen]

Please upvote the issue by giving it a thumbs up instead of leaving +1 comments. Issues can be sorted by reactions. And even more importantly you don't send a notification to everyone subscribed to this issue.