You have a type. It is prepareJobFinished without d.
I tested it my self and got all 3 events in one response:
{callback_id: -1, data: [{data: {}, event: "prepareJob", printer: "Anycubic_I3"},…], eventList: true}
callback_id: -1
data: [{data: {}, event: "prepareJob", printer: "Anycubic_I3"},…]
0: {data: {}, event: "prepareJob", printer: "Anycubic_I3"}
1: {data: {modelId: 2,…}, event: "gcodeInfoUpdated", printer: "Anycubic_I3"}
2: {data: {slug: "Anycubic_I3"}, event: "jobsChanged", printer: "Anycubic_I3"}
3: {,…}
4: {data: {activeExtruder: 0, debugLevel: 6, doorOpen: false,…}, event: "state", printer: "Anycubic_I3"}
5: {data: {start: 1603017806}, event: "jobStarted", printer: "Anycubic_I3"}
6: {data: {slug: "Anycubic_I3"}, event: "printqueueChanged", printer: "Anycubic_I3"}
7: {data: {}, event: "prepareJobFinished", printer: "Anycubic_I3"}
eventList: trueDid you maybe forget to parse all entries of the event list? As you see they are all there.
Regarding undocumented events - yes may exist. If you see one I forgot let me know and I add the description. There are also some undescribed actions especially the configuration calls are not documented since no one does this on it's own and they are quite critical and may change.
