Fix XML Bots and add FirmwareEvent

[nanomad]

No description provided.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.01%. Comparing base (4cc81d1) to head (cd96050).
Report is 1 commits behind head on dev.

✅ All tests successful. No failed tests found.

Additional details and impacted files

@@            Coverage Diff             @@
##              dev     #935      +/-   ##
==========================================
+ Coverage   92.84%   93.01%   +0.17%     
==========================================
  Files         125      125              
  Lines        4865     4885      +20     
  Branches      315      318       +3     
==========================================
+ Hits         4517     4544      +27     
+ Misses        285      282       -3     
+ Partials       63       59       -4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[codspeed-hq]

CodSpeed Performance Report

Merging #935 will not alter performance

_{Comparing nanomad:bugfix/xml-compat-changes (cd96050) with dev (4cc81d1)}

Summary

✅ 6 untouched benchmarks

[nanomad]

@edenhaus Those are the bugs I found while integration testing everything:

• device.py was assuming any message could be decoded as JSON, erroring out on any XML bot message
• message.py was not decoding string payloads properly. Strange that mypy didn't catch this as we were basically ignoring some valid payload types declared by MQTT

[nanomad]

@edenhaus eventually I think we should switch the "bot firmware version" to be handled differently as for XML bots we have to send a specific command (not yet implemented) so I'd consider this portion of the patch more of a workaround

[edenhaus]

I refactored the code to use a FirmwareEvent, which can be used by the XML bot in the feature too

[edenhaus]

Thanks @nanomad 👍