Repository navigation
Releases
5.2.1.6 alpha: pump state fix
Alpha pre-release for testing. 5.2.1.4 stays the current stable release. Everything said in the 5.2.1.5 alpha notes still applies.
Changes since 5.2.1.5
- Pump:
pump-stateis nowUNDEFwhile the motor stands. The pump only updates it while running, so after a stop the channel used to keep the last result, e.g. "water flows". - Pump:
outlet-pressureis documented as the value last reported by the pump. Whether the pump reports the pressure while stopped is still being checked. - The "gateway refused the connection" status now points to the README section on enabling the gateway's WebSocket API.
Test status
- First user tests of 5.2.1.5: irrigation control, pump and power adapter work as expected.
- SILENO mowers are still untested on real hardware - feedback with a TRACE log (
log:set TRACE io.github.larsenlocke.binding.gardena) is very welcome. - This alpha has not been tested on the maintainer's own installation; the change is covered by unit tests.
5.2.1.5 alpha: Power Adapter, Pump and SILENO mowers
Alpha pre-release for testing. Not recommended for production use; 5.2.1.4 stays the current stable release.
New
Supports the same appliances as GARDENA's own Home Assistant integration:
power-adapter: smart Power Adapter. Switch on for a duration or until switched off.pump: smart Automatic Home & Garden Pump. Run for a duration (scheduled mode), operating mode, turn-on pressure, dripping alert, reset commands; outlet pressure, water temperature, flow rate, volumes, pump state and errors.mower: SILENO robotic mowers, first generation (smart SILENO, SILENO+, city, life, also with LONA) and second generation (pro, max, free). Start for a duration, park until next schedule or until further notice, pause (second generation only); activity, battery, error code and lifetime counters.
Channels and configuration are described in the README.
Test status - please read
- None of the new devices has been run against real hardware. They follow GARDENA's reference implementations (gardena-smart-local-api and ha-gardena-smart-local-preview) and are covered by unit tests only.
- Existing devices (irrigation controls, water controls, sensors): their behaviour is unchanged and pinned by characterization tests, but this alpha has not been tested on the maintainer's own installation either.
- The mapping of the first-generation mower status codes to
activityfollows the reference library and needs confirming: please report whenactivitydoes not match what the mower does. - First-generation mowers: it is not confirmed whether
park-until-next-scheduleorstartlifts a pause set bypark-until-further-notice. - In automatic mode the pump ignores manual starts; the binding refuses
statecommands then and logs a warning.
How to help
- Install the jar into
addons, run a scan for the GARDENA Binding (local) in the Inbox and add the new things. - Set the log level to TRACE:
log:set TRACE io.github.larsenlocke.binding.gardena - Try the channels and commands, and report what works and what does not in the forum thread or a GitHub issue, with the TRACE log. The log contains your device IDs but never the gateway password.
Change in behaviour for all devices
A command for a device the gateway does not currently know now puts the switch back to its last state instead of leaving it at the commanded value.
v5.2.1.4 - license and maintainer in the bundle metadata
Same functionality as v5.2.1.3; the bundle now declares its license and maintainer.
Changed
Bundle-License(EPL-2.0),Bundle-Vendor(Larsen-Locke) and the Maven license/developer metadata are declared in the JAR.- Copyright is claimed as Larsen-Locke, not the openHAB project; NOTICE states independence, trademarks and the use of an AI coding assistant.
- A unit test checks that the English translation file matches the XML.
Hardware coverage
Verified on real hardware: a first-generation smart Irrigation Control and a smart Sensor II (openHAB 5.2.1). Water controls and second-generation devices follow GARDENA's reference implementation but are untested on hardware.
Upgrading
Replace the JAR in addons/ and remove the previous io.github.larsenlocke.binding.gardena-*.jar. Things and items stay as they are.
v5.2.1.3 - package io.github.larsenlocke.binding.gardena
The Java package is now named after the device like the other Larsen-Locke bindings (balboa, jablotron100,
modbus.goodwe): io.github.larsenlocke.binding.gardenalocal became io.github.larsenlocke.binding.gardena, and the
add-on is called "GARDENA Binding (local)". The binding ID stays gardenalocal, so it still differs from the official
cloud binding's gardena and both can run side by side. The jar is the exact build that is running on a real
openHAB 5.2.1 installation.
Changed
- Package, Maven artifact and bundle symbolic name
io.github.larsenlocke.binding.gardena. - Add-on, bundle and project name "GARDENA Binding (local)" instead of "GARDENA smart local Binding".
- The jar no longer carries leftover source copies and component descriptions from earlier builds; no behaviour
change.
Upgrading
The bundle has a new symbolic name again, so openHAB does not replace the old jar by itself: remove
io.github.larsenlocke.binding.gardenalocal-*.jar (or an older org.openhab.binding.gardenalocal-*.jar) from the
addons folder, then drop in io.github.larsenlocke.binding.gardena-5.2.1.3-20261002-083657.jar. Things and items
stay as they are.
If you set a log level for io.github.larsenlocke.binding.gardenalocal, change it to
io.github.larsenlocke.binding.gardena.
v5.2.1.2 - package namespace io.github.larsenlocke
First release under the io.github.larsenlocke namespace. The org.openhab namespace is reserved for the openHAB
project (openHAB trademark policy, item 8), so the Java packages, the Maven coordinates and the bundle name moved from
org.openhab.binding.gardenalocal to io.github.larsenlocke.binding.gardenalocal. The binding ID stays gardenalocal. The jar is the exact
build that is running on a real openHAB 5.2.1 installation.
Changed
- Package namespace
io.github.larsenlocke.binding.gardenalocal, bundle vendor "Larsen-Locke". - The build runs openHAB's add-on checks like the official add-ons (Spotless, Checkstyle, PMD, SpotBugs), and CI runs
them on every push. Sources were reformatted accordingly; no behaviour change. - The jar carries the NOTICE file, as the official add-ons do.
- Thing-type labels are at most 25 characters and channel labels at most 20, as openHAB's checks require. Labels
you set on your own things and items are not affected.
Upgrading
The bundle has a new symbolic name, so openHAB does not replace the old jar by itself: remove
org.openhab.binding.gardenalocal-*.jar from the addons folder, then drop in io.github.larsenlocke.binding.gardenalocal-5.2.1.2-20261002-004122.jar. Things and items stay as they are.
If you set a log level for org.openhab.binding.gardenalocal, change it to io.github.larsenlocke.binding.gardenalocal.
v5.2.1.1 - discovery only on scan
Fixed
- Inbox noise every 10 minutes. Since the device list is re-read periodically (v0.2.1), every configured device was proposed again, auto-ignored by the Inbox, dropped on the next refresh and added again - an Inbox added/removed log pair every 10 minutes. Devices that already have a thing are no longer proposed, and a leftover proposal for them is withdrawn.
Changed
- Devices are proposed only during a scan started from the UI. Background discovery is off by default; the periodic device-list refresh keeps
last-seencurrent but no longer touches the Inbox. - Devices unpaired from the gateway are withdrawn from the Inbox by id rather than by result age.
Upgrading
Replace the jar in addons/ and remove the previous org.openhab.binding.gardenalocal-*.jar. Things and items stay as they are.
v5.2.1 - version follows openHAB 5.2.1
From now on the version follows the openHAB release the binding is built for, like the official add-ons. This
release is for openHAB 5.2.1.
No code changes since v0.2.1. Only the version number changed (1.0.0-SNAPSHOT -> 5.2.1), and the repository
got its new name openhab-gardena-local-binding. The jar is the exact build that is running on a real openHAB 5.2.1 installation.
Installation
Remove any older 1.0.0-SNAPSHOT jar of this binding from the openHAB addons folder, drop in org.openhab.binding.gardenalocal-5.2.1-20260926-185749.jar and restart
openHAB. Otherwise the old and the new version are loaded side by side.
v0.2.1 - last-seen stays current
Fixed
last-seenstayed at the last changed value. The gateway pushes an event only when a value changes; a device reporting the same values again only refreshes timestamps on the gateway. On a real gatewaylast-seenshowed 22:53 the previous day while the device had reported at 18:03. The gateway thing now re-reads the device list everyrefreshIntervalminutes (new advanced parameter, default 10,0= off). The request is a few kilobytes.last-seenis no longer an advanced channel, so the UI shows it without "Show advanced".
Upgrading from v0.2.0
Replace the jar in addons/. Existing things keep working; the new parameter appears on the gateway thing with its default.
v0.2.0 - tested on a real gateway, cloud-binding migration
First version verified against a real GARDENA smart Gateway: a first-generation smart Irrigation Control (19032) and a smart Sensor II (19040) on openHAB 5.2.1. Login, device list, live sensor updates and a full valve cycle (open for 1 min, device closes it by itself, state follows) work.
Changes since v0.1.0
durationis now a setting, not a command to open. It holds how long the valve stays open on the nextON; setting it never opens the valve. This matches the cloud binding'scommandDuration+ start pattern, and an item linked with thefollowprofile can no longer start watering by accident.- New
last-seenchannel on every device: when the device last reported to the gateway. battery-levelis nowNumber:Dimensionlessin % (the plainNumbersystem channel showed 98 as 9800 % on a Dimensionless item).- A gateway found via mDNS is named by its host name (
GARDENA-123456) instead of repeating the product name.
Upgrading from v0.1.0
Replace the jar in addons/. Things created with v0.1.0 lack the last-seen channel; delete and re-add them from the Inbox if you want it.
Migrating from the cloud binding
See the README section "Migrating from the Cloud Binding".
v0.1.0 - first version, not yet tested on hardware
First version of the local GARDENA smart binding for openHAB 5.2.
Not yet tested against a real gateway. The protocol handling is covered by unit tests and by a test against a stand-in gateway (login, device list, valve command, reconnect), but not by hardware.
Supported
- GARDENA smart Gateway (bridge), discovered via mDNS
- smart Irrigation Control (Gen1 19032 / Gen2 19035): 6 valves with state, water-for duration, name, connected, error
- smart Water Control (Gen1 19031 / Gen2 19033), Pipeline Water Control (19050), Dual Water Control (19034)
- smart Sensor (19030) and Sensor II (19040): soil moisture, soil/air temperature, light, battery, frost warning
- German translation
Installation
- Enable the WebSocket API on the gateway (web interface, advanced options, or
curl, see README). - Copy the jar into openHAB's
addons/folder. - Add the gateway from the Inbox (or manually: host, password = first block of the gateway ID), then approve the devices from the Inbox.
The binding ID gardenalocal differs from the cloud binding's gardena, so both can run side by side while migrating.