Network Binding slows down OpenHAB loading very much on boot

  • Platform information:
    • openHAB version: 4.1.0 … 5.0.1
    • Java Runtime Environment OH4x: zulu17.60.17-ca-jdk17.0.16-win_x64
    • Java Runtime Environment OH5x: Temurin OpenJDK21U-jdk_x64_windows_hotspot_21.0.8_9
    • Hardware: ASUSPN41/IntelPentiumSilverN6000@2100/8GB_DDR4-2666/256GB_SSD-WD-GREEN
    • OS: Windows Server 2022 Std Latest

I have a lot of errors:

  1. Rules are loaded several times
  2. Javascript rules cannot be initialized
  3. Rules cannot find bindings on startup

All these problems arise because of Network Binding, which slows down OpenHAB loading very much. If you remove it (Network Binding), everything loads without problems.

I tried several computers (powerful and not so powerful), Windows 10/Server 2022. Always one problem, while initialization of all things managed by Network Bindings is in progress, everything is slow to initialize.

Full log

2025-08-26 11:19:40.923 [INFO ] [org.openhab.core.Activator          ] - Starting openHAB 4.3.7 (Release Build)
2025-08-26 11:19:41.756 [INFO ] [.core.internal.i18n.I18nProviderImpl] - Measurement system set to 'SI'.
2025-08-26 11:19:51.789 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'debug_sensor_climat_voltage.items'
2025-08-26 11:19:53.042 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'jdbc.persist'
2025-08-26 11:19:53.795 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'mapdb.persist'
2025-08-26 11:19:57.808 [WARN ] [rg.openhab.core.io.net.exec.ExecUtil] - Failed to execute commandLine '[arping, --help]'
2025-08-26 11:20:01.558 [INFO ] [.core.model.lsp.internal.ModelServer] - Started Language Server Protocol (LSP) service on port 5007
2025-08-26 11:20:01.934 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'openhab.rules'
2025-08-26 11:20:07.541 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'intercom.rules'
2025-08-26 11:20:08.641 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'rflnk.rules'
2025-08-26 11:20:12.816 [INFO ] [persistence.jdbc.internal.JdbcMapper] - JDBC::openConnection: Driver is available::Yank setupDataSource
2025-08-26 11:20:13.188 [ERROR] [ipt.internal.ScriptEngineManagerImpl] - ScriptEngine for language 'application/vnd.openhab.dsl.rule' could not be found for identifier: 96128d9b-abdb-4074-9281-fe91ad5684af
2025-08-26 11:20:13.202 [ERROR] [ipt.internal.ScriptEngineManagerImpl] - ScriptEngine for language 'application/vnd.openhab.dsl.rule' could not be found for identifier: 6eadb272-b050-496c-94a2-7721de976537
2025-08-26 11:20:13.206 [ERROR] [ipt.internal.ScriptEngineManagerImpl] - ScriptEngine for language 'application/vnd.openhab.dsl.rule' could not be found for identifier: 3316f9a3-bdf9-4b61-ad26-3f9bcf8439ce
2025-08-26 11:20:13.208 [ERROR] [ipt.internal.ScriptEngineManagerImpl] - ScriptEngine for language 'application/vnd.openhab.dsl.rule' could not be found for identifier: 8b239fae-51dc-4afc-86c5-0eb279110282
2025-08-26 11:20:13.210 [ERROR] [ipt.internal.ScriptEngineManagerImpl] - ScriptEngine for language 'application/vnd.openhab.dsl.rule' could not be found for identifier: 0c63aed7-934c-423f-8e68-9d74785cf9e1
2025-08-26 11:20:13.250 [ERROR] [ipt.internal.ScriptEngineManagerImpl] - ScriptEngine for language 'application/vnd.openhab.dsl.rule' could not be found for identifier: 4557d690-9280-4a7f-b330-df3dccbb81c3
2025-08-26 11:20:13.257 [ERROR] [ipt.internal.ScriptEngineManagerImpl] - ScriptEngine for language 'application/vnd.openhab.dsl.rule' could not be found for identifier: 94527923-3068-43d1-8992-3a4e3be4d1e3
2025-08-26 11:20:13.260 [ERROR] [ipt.internal.ScriptEngineManagerImpl] - ScriptEngine for language 'application/vnd.openhab.dsl.rule' could not be found for identifier: 3a74d684-9fb5-4151-b4dd-4bacc18fc44d
2025-08-26 11:20:13.267 [ERROR] [ipt.internal.ScriptEngineManagerImpl] - ScriptEngine for language 'application/vnd.openhab.dsl.rule' could not be found for identifier: 6e178ece-36f2-45d5-8a06-5cddb0b5385f
2025-08-26 11:20:13.271 [ERROR] [ipt.internal.ScriptEngineManagerImpl] - ScriptEngine for language 'application/vnd.openhab.dsl.rule' could not be found for identifier: 83506dbe-0c2b-4376-8373-fac891b80277
2025-08-26 11:20:16.648 [INFO ] [ab.ui.habpanel.internal.HABPanelTile] - Started HABPanel at /habpanel
2025-08-26 11:20:19.308 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'socketplug.rules'
2025-08-26 11:20:26.343 [ERROR] [b.automation.script.javascript.stack] - Failed to execute script: Error: Failed to get any services of type(s): org.openhab.core.thing.link.ItemChannelLinkRegistry
        at <js>.getService(@openhab-globals.js:2)
        at <js>.236(@openhab-globals.js:2)
        at <js>.o(@openhab-globals.js:2)
        at <js>.605(@openhab-globals.js:2)
        at <js>.o(@openhab-globals.js:2)
        ... 28 more
2025-08-26 11:20:26.390 [ERROR] [ipt.internal.ScriptEngineManagerImpl] - ScriptEngine for language 'application/vnd.openhab.dsl.rule' could not be found for identifier: d12ee59a-73ee-4584-8983-384dc561aeb7
2025-08-26 11:20:26.577 [ERROR] [b.automation.script.javascript.stack] - Failed to execute script: Error: Failed to get any services of type(s): org.openhab.core.thing.link.ItemChannelLinkRegistry
        at <js>.getService(@openhab-globals.js:2)
        at <js>.236(@openhab-globals.js:2)
        at <js>.o(@openhab-globals.js:2)
        at <js>.605(@openhab-globals.js:2)
        at <js>.o(@openhab-globals.js:2)
        ... 28 more
2025-08-26 11:20:26.790 [ERROR] [b.automation.script.javascript.stack] - Failed to execute script: Error: Failed to get any services of type(s): org.openhab.core.thing.link.ItemChannelLinkRegistry
        at <js>.getService(@openhab-globals.js:2)
        at <js>.236(@openhab-globals.js:2)
        at <js>.o(@openhab-globals.js:2)
        at <js>.605(@openhab-globals.js:2)
        at <js>.o(@openhab-globals.js:2)
        ... 28 more
2025-08-26 11:20:26.795 [ERROR] [ipt.internal.ScriptEngineManagerImpl] - ScriptEngine for language 'application/vnd.openhab.dsl.rule' could not be found for identifier: 07f2336b-34d5-4301-98f1-1c269e9c861b
2025-08-26 11:20:26.797 [ERROR] [ipt.internal.ScriptEngineManagerImpl] - ScriptEngine for language 'application/vnd.openhab.dsl.rule' could not be found for identifier: 5fd532b2-d4fb-401f-9335-dbbbd56cb9a3
2025-08-26 11:20:26.799 [ERROR] [ipt.internal.ScriptEngineManagerImpl] - ScriptEngine for language 'application/vnd.openhab.dsl.rule' could not be found for identifier: eddf2cf8-be6b-4dd0-bf5f-970fd77e2ac7
2025-08-26 11:20:26.841 [ERROR] [ipt.internal.ScriptEngineManagerImpl] - ScriptEngine for language 'application/vnd.openhab.dsl.rule' could not be found for identifier: 0c17479e-5218-4c0a-82f4-7e734c89f438
2025-08-26 11:20:27.108 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'bluetooth.rules'
2025-08-26 11:20:28.368 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'lightbulb.rules'
2025-08-26 11:20:31.567 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'relay.rules'
2025-08-26 11:20:32.367 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'debug.rules'
2025-08-26 11:20:33.635 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'siren.rules'
2025-08-26 11:20:35.378 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'weather.rules'
2025-08-26 11:20:35.659 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'intrusion.rules'
2025-08-26 11:20:39.397 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'alarms.rules'
2025-08-26 11:20:46.447 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'voice.rules'
2025-08-26 11:20:52.814 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'network.rules'
2025-08-26 11:20:54.633 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'scenes.rules'
2025-08-26 11:21:01.433 [WARN ] [.discovery.sddp.SddpDiscoveryService] - listenActiveScanUnicast() error 'Invalid argument: setsockopt'
2025-08-26 11:21:37.881 [INFO ] [ternal.dhcp.DHCPPacketListenerServer] - DHCP request packet listener online
2025-08-26 11:21:47.958 [ERROR] [e.automation.internal.RuleEngineImpl] - Failed to compile rule ‘tgbot' with status 'UNINITIALIZED'
2025-08-26 11:21:47.963 [ERROR] [e.automation.internal.RuleEngineImpl] - Failed to compile rule ‘smsbot' with status 'UNINITIALIZED'
2025-08-26 11:21:47.969 [ERROR] [e.automation.internal.RuleEngineImpl] - Failed to compile rule ‘javascript' with status 'UNINITIALIZED'
2025-08-26 11:21:47.975 [INFO ] [e.automation.internal.RuleEngineImpl] - Rule engine started.
2025-08-26 11:22:36.047 [INFO ] [.transport.mqtt.MqttBrokerConnection] - Starting MQTT broker connection to '127.0.0.1' with clientid openhab
2025-08-26 11:25:18.066 [INFO ] [nhab.core.model.script.network_rules] - Initialization 'network.rules'
2025-08-26 11:25:18.066 [INFO ] [nhab.core.model.script.openhab_rules] - Initialization 'openhab.rules'
2025-08-26 11:25:18.066 [INFO ] [ab.core.model.script.bluetooth_rules] - Initialization 'bluetooth.rules'
2025-08-26 11:25:18.068 [INFO ] [b.core.model.script.socketplug_rules] - Initialization 'socketplug.rules'
2025-08-26 11:25:18.070 [INFO ] [enhab.core.model.script.scenes_rules] - Initialization 'scenes.rules'
2025-08-26 11:25:18.076 [ERROR] [.handler.AbstractScriptModuleHandler] - Script execution of rule with UID 'openhab-1' failed: 'sendTelegram' is not a member of 'org.openhab.core.thing.binding.ThingActions'; line 51, column 5, length 70 in openhab
2025-08-26 11:25:18.076 [INFO ] [ab.core.model.script.intrusion_rules] - Initialization 'intrusion.rules'
2025-08-26 11:25:18.078 [INFO ] [enhab.core.model.script.rflink_rules] - Initialization 'rflink.rules'
2025-08-26 11:25:18.086 [INFO ] [penhab.core.model.script.siren_rules] - Initialization 'siren.rules'
2025-08-26 11:25:18.086 [INFO ] [penhab.core.model.script.voice_rules] - Initialization 'voice.rules'
2025-08-26 11:25:18.089 [INFO ] [enhab.core.model.script.alarms_rules] - Initialization 'alarms.rules'
2025-08-26 11:25:18.095 [INFO ] [penhab.core.model.script.debug_rules] - Initialization 'debug.rules'
2025-08-26 11:25:18.101 [INFO ] [ab.core.model.script.lightbulb_rules] - Initialization 'lightbulb.rules'
2025-08-26 11:25:18.146 [INFO ] [core.model.script.network_wol_device] - network:pingdevice:OHSERVER
2025-08-26 11:25:18.157 [INFO ] [core.model.script.sonoff_rfbr2_dev01] - state initialized
2025-08-26 11:25:42.450 [INFO ] [nhab.core.model.script.openhab_rules] - Initialization 'openhab.rules'
2025-08-26 11:25:44.586 [INFO ] [enhab.core.model.script.rflink_rules] - Initialization 'rflink.rules'
2025-08-26 11:25:44.619 [INFO ] [core.model.script.sonoff_rfbr2_dev01] - state initialized
2025-08-26 11:25:46.473 [INFO ] [b.core.model.script.socketplug_rules] - Initialization 'socketplug.rules'
2025-08-26 11:25:47.144 [INFO ] [ab.core.model.script.bluetooth_rules] - Initialization 'bluetooth.rules'
2025-08-26 11:25:48.159 [INFO ] [ab.core.model.script.lightbulb_rules] - Initialization 'lightbulb.rules'
2025-08-26 11:25:48.751 [INFO ] [penhab.core.model.script.debug_rules] - Initialization 'debug.rules'
2025-08-26 11:25:49.827 [INFO ] [penhab.core.model.script.siren_rules] - Initialization 'siren.rules'
2025-08-26 11:25:51.555 [INFO ] [ab.core.model.script.intrusion_rules] - Initialization 'intrusion.rules'
2025-08-26 11:25:55.590 [INFO ] [enhab.core.model.script.alarms_rules] - Initialization 'alarms.rules'
2025-08-26 11:25:59.169 [INFO ] [penhab.core.model.script.voice_rules] - Initialization 'voice.rules'
2025-08-26 11:26:00.392 [INFO ] [nhab.core.model.script.network_rules] - Initialization 'network.rules'
2025-08-26 11:26:00.803 [INFO ] [enhab.core.model.script.scenes_rules] - Initialization 'scenes.rules'

What is your openHAB version ? 4.1.0 or 5.0.1 ?

If 5.0.1, you need to install Java 21 !!!

Hi: Temurin OpenJDK21U-jdk_x64_windows_hotspot_21.0.8_9

Unsuccessful implementation of multithreading in Network Binding appeared in OH4.1+. The code has not changed significantly since this version.

Since then, I, like millions of other users across the Galaxy, have constant problems with this binding: slow system startup (lots of problems because of it), slow editing of things in this binding, bad implementation of ping in this binding.

Java code analysis showed that there is a problem, but the author hasn’t fixed it yet. For OH4.1+ I use Java 17, for OH5+ I use Java 21 (you understand that I wouldn’t be able to run just OH5).

What if you ran it in docker?

Hello :slight_smile:

I don’t use Linux/Docker/Embedded.

But people (docker) from the forum complained about problems when 4.1 came out. Apparently they are waiting like me for it to be fixed.

I saw that the whole system works poorly at startup because of this binding.

I don’t understand why no one sees this! It is enough to take any Windows 10+ computer and install clean OH4.1+ and Network Binding.

Maybe there is not a lot of use of this binding?

And I also assume not a lot of users are running openHAB on Windows. Most are probably running on Linux (RPI in particular).

Hi,

so, t least for me I’m still unclear about a few of your statements starting with the subject line of this post

Network Binding slows down OpenHAB loading very much on boot

on boot of what? your windows PC or of the OpenHab JVM?
Are running OH as a windows service?
Please clarify your Problem statement a little more.

For example if your saying this is occurring during the boot up of the OS windows 10 or server 2022 really does not matter which do you have any additional event logging enabled for system or application.

You state

everything what?

The OS or OH or what?

Next you state

Do you have any additional info on that did you raise an issue with backing documentation when this was first released on the version you say it changed on.

Then you go on to what to me at least sounds like a rant.

Perhaps no one has addressed this because no user has raised it as an issue and Backed it up with data.

Pretty sure most of the maintainers would have looked at this and worked on a solution if there was in fact data points and clear examples (reproducible) logged as a issue on GitHub .

But they do not have crystal balls that just tell them oh gee a user running OH on windows has so problem with OH running in some configuration with some other things running and has some slowness when he adds the network binding.

Be realistic here. If you have data and reproducible steps and clear timings then open an issue on GitHub provide a clear problem statement and related info and then it will likely get worked on as dev’s have time.

OR you can load the dev environment figure out what this so call bad implementation is yourself and submit a pull request with your fix!

I am sure maintainers or dev folks would be happy to review and verify your fix and then get it implemented in forth coming release.

Remember everyone here is a volunteer not paid support or developers.

An issue already exists in Git:

https://github.com/openhab/openhab-addons/issues/17956

And for docker:

https://github.com/openhab/openhab-addons/issues/16810

Hi! Don’t be offended by my cry of despair! I’ve been waiting for fixes for two years now and nothing is happening. I recently wrote a node.js service that does the same thing as Network binding, I’ve already lost all hope that there will be a fix.

  1. Boot => running openhab, not windows

  2. Service => It doesn’t matter, it works poorly both when running as a service and from the console

  3. Everything loads without problems:

  • automation-jsscripting
  • binding-exec
  • binding-gpstracker
  • binding-ipcamera
  • binding-logreader
  • binding-mqtt
  • binding-openweathermap
  • binding-serial
  • binding-smsmodem
  • binding-telegram
  • persistence-jdbc-postgresql
  • persistence-mapdb
  • persistence-rrd4j
  • transformation-basicprofiles
  • transformation-jsonpath
  • transformation-map
  • transformation-regex
  • transformation-scale
  • ui-basic
  • ui-habpanel
  • voice-rustpotterks
  • voice-voicerss
  • voice-voskstt

But if binding-network is installed and a couple of its things are configured, then slowdowns begin. For example, mqtt connection will be established a couple of minutes after OpenHAB is launched, and not immediately, when binding-network is not installed and configured. Other bindings behave the same way, they start their initialization later. Other things, rules and scripts are initialized for a very long time. If rules depend on binding-mqtt, binding-sms or binding-telegram (and etc), for example, then they crash with java exceptions (various errors that leave extension authors stumped). The authors of all these extensions do not understand what the problem is. They confirmed that they have nothing to do with it. I checked the code. They have nothing to do with it. I spent a long time looking for who was to blame.

  1. Unsuccessful implementation of multithreading in =>

I don’t know. I took the extension code to the new multithreaded code and the old one, which was before version 4.1. I went through the debugging and saw that the old one works, and the new one works very strangely. I’m not a Java programmer, I’m only a Windows C++ Frontend/Backend programmer. It’s hard for me to analyze what I don’t fully understand. Maybe someone will be able to see the problem in the code/implementation.I just implemented all the functionality on Node.js until someone fixes it. There was an idea to make a backport of the extension version 4.0, but I stopped - somehow it’s not right. Plus the old version heavily loaded the processor once a ping, if there were a lot of things and when doing a ping.

  1. Then you go on to what to me at least sounds like a rant =>

I tried. I did everything as you say. I offered my help. I installed the development environment, I analyzed the code. Nothing happens. I am not alone, this topic has been discussed more than once. I created topics several times, sent logs, tried to help somehow.

  1. Remember everyone here is a volunteer not paid support or developers.

I want to remind you that I am not writing this just because I want to. I understand that if our beloved system is in such a terrible and broken state, then all users will abandon it. Two or three developers will use it, and everyone will go to Home Assistant or others. In OpenHub, something important is always broken and does not work. As a person who has been using the system for 4 years, I can state this with full responsibility. And of course, I worry, try to influence, report the problem, but as a rule, it takes months (for example, a broken mqtt under Windows), a year (collapsing lists in the semantic model), two year (bad functioning of network binding) to fix many problems. This is unrealistic, an ordinary user will not wait. Just like all my friends who switched to other systems did not wait. This upsets me.

I’m trying to get someone to fix the problem.

I don’t know. If it doesn’t work under Windows, then exclude it from the list. If no one uses network binding, then mark it as depricated. Why ask me?! I don’t know the answers to your questions. I chose OpehHAB because it is compatible with Windows, because it has network binding, among other things.

I use these:
binding-exec
binding-gpstracker
binding-ipcamera (badly compatible with cameras even from the compatibility list, few cameras)
binding-mqtt (broken in 5.0.0, fixed in 5.0.2)
binding-network (broken since 4.1.0)
binding-openweathermap
binding-serial
binding-smsmodem
binding-telegram (they don’t want to add new functionality)
persistence-jdbc-postgresql
persistence-mapdb
persistence-rrd4j
transformation-basicprofiles
transformation-jsonpath
transformation-map
transformation-regex
transformation-scale
ui-basic (broken semantic model tree in version 4, fixed in 5)
ui-habpanel
voice-rustpotterks (not works, the author wants to do it like in HomeAssist)
voice-voicerss
voice-voskstt

The funniest thing is that when I ask to fix it. They tell me: it’s Windows - no one uses it, or no one uses this binding. Is this normal? Well, tell me: nothing works under Windows and all our bindings don’t work either. Make a list of what works and don’t say that you have +100500 working extensions.

While the problem is being recognized, this is a somewhat bold statement. Up until now I have not been able to reproduce the issue.
Both on windows and Linux. I think it greatly depends on 1. Host hardware and 2. Network configuration for the problem to be exposed.

I have some thoughts on how to reproduce, but have not been able to find enough time to do so. It is one of the things high on my list, but there might be others who also look into it.

You wrote the ping implementation is bad. Please advise the improvements you see, so we can all benefit.

I am ready to help you when you have time, I will give you access via anydesk to my computer with Visual Studio Code and OH code. If you want.

I apologize for my English. Not my native language. Maybe I expressed myself incorrectly. I didn’t mean to be so critical. Sorry :grinning_face:

Host Hardware, Network configuration => I’ve already looked at it many times on seven Windows machines with different hardware and networks. The problem is clearly elsewhere.

Language is always problematic on multi-nationality platforms, so I assume everyone tries with the best intention, no worries.

I’ll ping you when I have done some work on it that needs testing or otherwise. But i’m not the only one who can, so if someone else fixes this in the mean time, it would be great.

I am always ready to help if needed! Thank you!

With docker desktop on windows, Started the openhab/openhab:latest docker image, set the port and nothing else in the default configuration.

2025-08-28 18:26:52.469 [TRACE] [al.discovery.NetworkDiscoveryService] - Starting Network Device Discovery
2025-08-28 18:27:05.373 [TRACE] [al.discovery.NetworkDiscoveryService] - Scan of 254 IPs successful

13 seconds from start to finish. 1.25GB was used, CPU spiked, but that is obvious. So i can;t reproduce yet.

Could you share your hardware configuration? sorry you did already.

Another run but now a docker container with --cpus 2.5

2025-08-28 19:05:36.952 [TRACE] [al.discovery.NetworkDiscoveryService] - Starting Network Device Discovery
2025-08-28 19:07:46.200 [TRACE] [al.discovery.NetworkDiscoveryService] - Scan of 254 IPs successful

130 seconds. 10 times as slow. that is more like the described problem. So one conclusion is that the hardware is greatly affecting the performance here.

Run3: Same settings as run2. Now with the jar from the current pending PR: 130 seconds
Run4: Same settings. Now with improve thread handling, see PR for details: 37 seconds
Run5: Same settings. Now with improve allocations / memmory handling: 6 seconds.

These results (if true) are stunning and can hardly believe this is valid.

Please test and confirm that the changes improved the experience. In a real-life openHAB instance, it may still not be fully fixed, but really want to know if you experience improvement. It would be appreciated if you start the binding and record the time it completes, or abort after 10 mins. And a second run with this jar, also timed and abort after 10 mins if not finished.

openHAB 5.0.x compatible. Not sure about 4.3.x
org.openhab.binding.network-5.0.0-SNAPSHOT.jar

I have the same issue with Openhab in Docker with network: host. The problem began with 4.1 release and since then I do not dare to use network binding as is it slowing down Openhab startup for ages. One thing: network mask is /25.

I’ll check it a bit later today. In my case, I don’t need a special instance. Any computer configuration with any windows 2022/10 causes problems. I have a copy of my config for version 5, but with a broken mqtt under Windows.

Can you share fixed mqtt binding? (Windows bug with pathes)

https://github.com/user-attachments/files/22013169/org.openhab.binding.mqtt.homeassistant-5.1.0-SNAPSHOT.jar.zip