py-smart-gardena/hass-gardena-smart-system 3.2.0

Release 3.2.0

on GitHub

Added

• Valve error sensor. Each valve exposes its Gardena last_error_code (frost, broken valve, current limit, and the other ValveError values) so a missed watering can be told apart from a healthy schedule (#382)
• Optional duration on valve_pause (multiple of 60 seconds, up to 4 hours). Leaving it out keeps the device's own pause length (#374, #388)
• Integration option for the lawn mower Start button: keep resuming the schedule, or mow immediately for a chosen duration. The start_automatic service still resumes the schedule (#399)
• Lawn mower button "Park Until Further Notice". It sends PARK_UNTIL_FURTHER_NOTICE, so the mower returns to the dock and stays there until it is started again, instead of resuming the schedule at the next task (#387)

Changed

• valve_pause, valve_unpause and valve_close sent with a controller device_id now apply to every valve on that device. valve_open on a multi-valve controller still needs a service_id, and a valve command that cannot find its target fails the service call instead of reporting success (#396, #388)
• Battery sensors no longer force a full-battery icon. Home Assistant now picks the icon from the actual charge level (#386)
• Manual mower duration can now be up to 24 hours (86400 seconds), matching power sockets. The previous 4-hour cap was only in the service schema — the API already accepted longer runs (#385)

Fixed

• Device command failures now raise HomeAssistantError, so automations and scripts can use continue_on_error: true after a transient Gardena cloud 5xx. Custom services no longer swallow the error and pretend the command succeeded (#390)

• Security: Stop disabling TLS certificate verification on every install. dev_mode=True was hardcoded in setup (a leftover for local macOS SSL issues), so HACS users exchanged OAuth credentials and tokens with the Gardena API and WebSocket without checking the server certificate. SSL verification is now on by default. Local development can still opt out with GARDENA_DEV_MODE=true (make ha-start already sets this)

  After upgrading, a host with an incomplete CA store or a TLS-inspecting proxy will now fail to connect instead of silently accepting any certificate. The symptom is a certificate error in the Home Assistant log (ClientConnectorCertificateError / CERTIFICATE_VERIFY_FAILED) — the fix is to update the host's CA certificates, not to disable verification