Releases: MTrab/pyworxcloud
v6.3.6
v6.3.5
Contributors
Assets 4
v6.3.4
Contributors
Assets 4
v6.3.3
v6.3.2
v6.3.1
Contributors
Assets 4
v6.3.0
Changes
Firmware update support is now available through the API layer via new helpers for toggling firmware auto-upgrades, checking firmware availability, and triggering OTA deployments. The implementation exposes set_firmware_auto_upgrade, get_firmware_upgrade_info, and start_firmware_upgrade on WorxCloud and adds the domain exceptions needed to surface firmware-state errors to callers.
Cached mower and device firmware state is kept aligned, a 404 from GET /api/v2/product-items/{serial}/firmware-upgrade is treated as “no firmware available,” and changelog data now ships in both the raw payload and a Markdown-friendly changelog_markdown variant so downstream integrations can render release notes cleanly. Debug logging around OTA trigger attempts also makes queueing decisions and no-update rejections visible during troubleshooting.
🚀 Features / Enhancements
Say thanks
Contributors
Assets 4
v6.2.0
Changes
v6.2.0 adds full support for automatic scheduling by normalizing the observed auto_schedule payloads into a stable structure and exposing matching write helpers for the supported schedule settings. This makes automatic scheduling data easier to inspect and update across the mower payload shapes currently seen in the field.
This release also fixes schedule progress reporting for days without any scheduled slots. daily_progress now remains None when there is no schedule today instead of incorrectly reporting a fully completed day.
It also restores party_mode as the primary API name after the accidental rename to pause_mode. Existing pause_mode aliases remain available as deprecated compatibility paths, so callers can move over without an immediate break.
🚀 Features / Enhancements
🐛 Bug Fixes
- #361 Set daily progress to none without schedule today @MTrab
- #362 Revert direct master merge of #361 @MTrab
- #363 Set daily progress to none without schedule today @MTrab
- #365 Restore party_mode as primary, deprecate pause_mode aliases @MTrab
Say thanks
Contributors
Assets 4
v6.1.1
Changes
v6.1.1 fixes schedule progress and next-slot calculations so they consistently follow the mower's own timezone. This avoids schedule state drifting when the host runtime is running in a different timezone.
This release also hardens MQTT command handling after an unexpected hangup. If a session appears resumed before any inbound traffic has been seen again, the client now reconnects cleanly before sending the first command to reduce the risk of commands disappearing into a half-recovered session.
🐛 Bug Fixes
- #355 Use mower timezone for schedule progress @MTrab
- #360 Reconnect cleanly before the first command after a hangup @MTrab
Say thanks
Contributors
Assets 4
v6.1.0
Changes
v6.1.0 adds normalized schedule CRUD support, making it easier to work with schedule entries through a more stable and consistent model. It also completes the Party mode rename to Pause mode so the public surface and terminology stay aligned.
This release also improves shutdown behavior by speeding up MQTT cleanup, which should make disconnect and teardown paths feel more reliable in day-to-day use.