Consider some version-compatibility check between this library and the server it connects to

[marc-portier]

Since the /api endpoint is so kind to inform about the server side software version we could easily have this library embed some knowledge of the version boundaries [min, max] for safe operation of the library.

Depending on the outcome of the check and some 'operational -mode' the net effect could be

• log all is ok, or else log the mismatch and suggested course of action (i.e. upgrade server or lib ?)
• warn about the mismatch, yet still try on in best effort or bluntly fail and break

(Thought came up while pondering on #7 and how this might of have come to be.)

I know we are still in 0.*.* releases and thus little contract on upwards compatibility are to be expected. (assuming semver to be used on both api and lib)

Paradoxically though exactly that moving-target-environment only increases the need/usefulness of such guarding mechanism? (and suggests narrowing the min-max to maybe even exact match)

[linknum23]

It seems reasonable to add a check that the amplipi server is >= some version and == to the same major version, adding a warning that things may break otherwise.