Thank you… I could not find any reference to this library in the PR!
In looking at this some more, I do not think changing the binding to make different API calls based on the ZM version will be enough. At ZM 1.31.1, some configuration settings were moved from the database to files. These settings are no longer available through the API. The ZM team has made a few of them available, but only through /zm/api/configs/viewByName. Of the configuration settings moved to the file, the only one that the binding uses is ZM_PATH_ZMS. In addition to this, ZM_OPT_FRAME_SERVER appears to have been completely removed.
To make the binding compatible with the updated version of ZM, my suggestion is to update the binding anywhere it uses the config details from the view call for ZM_PATH_ZM (name, type, category, readonly), and change the call for the value to use viewAsName. Or, we could request that the ZM team add it to view and not just viewByName. Also, any reference to ZM_OPT_FRAME_SERVER would need to be removed. Fortunately, I believe these binding changes would be compatible with previous versions of ZM too.
My wife (always my hero!) came up with a workaround for using the binding (2.3.0.201805211219) with the current ZM master snapshot build (ZM 1.31.45). Basically, put the ZM_PATH_ZMS and ZM_OPT_FRAME_SERVER records back into the Config table, and then modify the config.php to ignore them.