All notable changes to this project will be documented in this file. This project uses semantic versioning.
- Improvement: across the board optimizations to adapt to the myQ server side shifting to a more pedantic approach to API access. Huge thanks to @jarz for the continued collaboration.
- Fix: myQ has begun adapting their OAuth flow and tightening up some tidbits. We adapt. Hat tip to @drysart and @justinlindh for the legwork on this one.
- Housekeeping.
- Improvement: API resiliency has been substantively improved through incorporating automatic retries across myQ regions. This should improve robustness across the occasional cloud infrastructure challenges that the myQ API encounters.
- New feature: added a
login()
function. This is now a required first step prior to using the API for any other calls. The constructor no longer requires login credentials. See the README for details. - Housekeeping.
- Housekeeping.
- Housekeeping.
- Improvement: further refine error handling for offline devices.
- Housekeeping.
- Improvement: update the model/device lookup database, improve error handling for myQ cloud errors, and other optimizations.
- Housekeeping.
- Housekeeping.
- Allow for user-selectable cloud geographic regions for the myQ API.
- Housekeeping.
- Housekeeping.
- This is now an ESM-only package. If you'd like to use this library in Common Javascript (CJS), use v6.
- Improve performance with a shift to HTTP2.
- Revert URI encoding of passwords - turns out it is unneeded.
- Properly URI encode password inputs for myQ logins.
- Housekeeping and dependency updates.
- Housekeeping and dependency updates.
- Lock the version of
node-fetch-cjs
while the project works out a regression.
- Updated to use
node-fetch-cjs
so this package can be easily used in non-ESM environments.
- Housekeeping.
- Further housekeeping and cleanup.
- Housekeeping.
- Housekeeping and documentation updates.
- Initial release: separated from homebridge-myq for wider availability.