In that case, you might want to show the firmware code for us to determine how you are constructing the publish information that caused the id to be incorrect.
Hmm, this isn’t really a failure that’s generally possible, or one I’ve ever seen. Are you looking at the event list in the console? Maybe the view on the webpage truncated the number? Are you seeing this truncation via a webhook, or from the CLI?
This is the first time I saw this. I rebooted my device and I didn’t see this again. I’ll comment if I see it again. What did you mean by “Can you try using one of the many supported clients for consuming these events”?
No, that is not how the ID is constructed, hence why I said this type of failure doesn’t really make sense. I suspect this is an artifact related to the use of curl for SSE streams.