Where is ModBus binding in OH 5.1x?

AndrewFG · February 11, 2026, 5:34pm

I am trying to migrate from an OH v4.3.x to v5.1.x system. The old system has the plain ModBus binding installed. But on the new v5.1.x system the Modbus binding is no longer in the Add-On Store. ???

miwok · February 11, 2026, 5:42pm

The binding is still there, but the title is wrong…

sihui · February 11, 2026, 5:45pm

github.com/openhab/openhab-core

Add-on store not showing subbindings

opened 08:40AM - 27 Dec 25 UTC

lsiepel

bug

This might be a severe issue in 5.1.0. All subbindings are not shown in the stor…e. Screenshots from 5.1.0 stable on windows. They can be installed from a configuration file, so it seems pure UI related. A added screenshots and would expect many more hits for these search terms. They are also not shown in the list itself without search. I assume it might be related to the . in the binding id or something similar, as only 1 is shown For bluetooth <img width="940" height="547" alt="Image" src="https://github.com/user-attachments/assets/8f9e03b5-5367-45a2-a764-73d7b40cb285" /> For MQTT <img width="925" height="379" alt="Image" src="https://github.com/user-attachments/assets/cdd713ea-cefd-42d9-909e-3de693d09728" /> For Modbus: <img width="935" height="503" alt="Image" src="https://github.com/user-attachments/assets/2dc23224-b10e-45c5-9962-c287d18acf03" /> After some more checks i doubt it is UI related. The endpoint http://localhost:8080/rest/addons?serviceId=karaf shows a large json, and checking the content it only shows 1 occurence of sunspec and that is here: So the endpoint does not seem to provide the proper json for the subbindings?! ```json { "uid": "binding-modbus", "id": "modbus", "label": "Lambda Heat Pump Binding", "version": "5.1.0", "compatible": true, "contentType": "application/vnd.openhab.feature;type\u003dkaraf", "link": "https://www.openhab.org/addons/bindings/modbus/", "author": "openHAB", "verifiedAuthor": true, "installed": false, "type": "binding", "description": "Lambda heat pump binding via Modbus TCP/IP.", "configDescriptionURI": "", "keywords": "", "countries": [], "connection": "local", "properties": {}, "loggerPackages": [ "org.openhab.binding.modbus", "org.openhab.binding.modbus.e3dc", "org.openhab.binding.modbus.foxinverter", "org.openhab.binding.modbus.helioseasycontrols", "org.openhab.binding.modbus.kermi", "org.openhab.binding.modbus.lambda", "org.openhab.binding.modbus.sbc", "org.openhab.binding.modbus.stiebeleltron", "org.openhab.binding.modbus.studer", "org.openhab.binding.modbus.sungrow", "org.openhab.binding.modbus.sunspec" ] } ```

AndrewFG · February 11, 2026, 7:09pm

Issue opened

mdillman · February 12, 2026, 3:08pm

The “Lambda” binding is “just” named wrong. If you install it, it will result in the base modbus addon and all sub-bindings (E3DC, Studer …) being installed.

But: as the modbus binding grows, it might be a good idea to split the subbindings and make them able to be installed (and found) individually.

AndrewFG · February 12, 2026, 4:51pm

I may be wrong but I had an idea that ut had already been done.