Which JRE do you have installed? I’ve got openjdk-21-jre:amd64 installed on the Debian 13 VM.
Homie doesn’t use Python so I’m not sure that would help.
As for the logs, I’m pretty certain that is what the root problem is. And I’ve no idea how to fix it.
I run in Docker. What ever comes with the default debian openHAB Docker image (also based on trixie). What ever comes with that. --version says
OpenJDK Runtime Environment (build 21.0.9+10-Debian-1deb13u1)
OpenJDK 64-Bit Server VM (build 21.0.9+10-Debian-1deb13u1, mixed mode, sharing)
I don’t think GraalVM Python requires Python to be installed on the host. It doesn’t seem to be installed in the Docker image.
I’m out of ideas and thing the next thing to do is file an issue on the add-on. I don’t have the knowledge to solve this. I was hoping there would be something relevant in the truncated logs but there wasn’t.
Yes, it looks like there’s something funky going on.
I think I was seeing the same thing. I don’t use the HomeAssistant binding, but I installed it and nothing was discovered (and of course no scan button, but that may be by design unlike the old binding that was part of the MQTT binding). However, I upgraded to 5.1.1 and my devices were auto discovered.
Publish attributes is a home assistant setting. It cannot be done in openhab. You to manually add those lines in the configuration of the ha. Then you can restart ha. Later the the topics can be discovered by openhab using the topic.filter.
That’s interesting because the patch didn’t include any relevant changes. I wonder what made it get past the error? Maybe there’s a timing issue. We’ve already tried to clear the cache (which is what happens when you upgrade). But maybe it’s worth trying again.
I went back to 5.1.0 as my zwave network (zwave-js-ui) came to complete stop after I upgraded, even though all looked like it was fine. Downgrading brought it back. So that is a separate issue, but my HA auto discovered items remained in the inbox (ignored status). Not sure of the cause, but will try again when I have time to troubleshoot.
Once discovered, the Things remain in the inbox until ignored or deleted, even if the add-on that discovered them was removed or the discovered device doesn’t exist anymore. So if you did an in-place downgrade instead of a restore from backup, those Things would remain.
Got that. Poor wording, I wasn’t sure of the cause of my meltdown when I upgraded to 5.1.1.
Hey,
i’ve just recognized the same issue: The homeassistant binding is not starting because of missing Graal.Python.
I’m not sure when this happend, because it’s (at the moment) just one thing, thats not used every day. but i think it might be since update to 5.1.3.
This are the log messages:
2026-03-31 22:47:26.473 \[WARN \] \[t.internal.HomeAssistantPythonBridge\] - could not determine Graal.Python’s core path - you may need to pass --python.CoreHome.
2026-03-31 22:47:28.127 \[WARN \] \[t.internal.HomeAssistantPythonBridge\] - could not determine Graal.Python’s sys prefix path - you may need to pass --python.SysPrefix.
2026-03-31 22:47:28.128 \[WARN \] \[t.internal.HomeAssistantPythonBridge\] - could not determine Graal.Python’s standard library path. You need to pass --python.StdLibHome if you want to use the standard library.
2026-03-31 22:47:28.129 \[WARN \] \[t.internal.HomeAssistantPythonBridge\] - could not determine Graal.Python’s C API library path. You need to pass --python.CAPI if you want to use the C extension modules.
2026-03-31 22:47:28.580 \[WARN \] \[t.internal.HomeAssistantPythonBridge\] - could not determine Graal.Python’s C API library path. You need to pass --python.CAPI if you want to use the C extension modules.
2026-03-31 22:47:30.808 \[WARN \] \[t.internal.HomeAssistantPythonBridge\] - could not determine Graal.Python’s C API library path. You need to pass --python.CAPI if you want to use the C extension modules.
2026-03-31 22:47:31.106 \[WARN \] \[t.internal.HomeAssistantPythonBridge\] - could not determine Graal.Python’s C API library path. You need to pass --python.CAPI if you want to use the C extension modules.
2026-03-31 22:47:33.561 \[ERROR\] \[t.internal.HomeAssistantPythonBridge\] - bundle org.openhab.binding.homeassistant:5.1.3 (407)\[org.openhab.binding.homeassistant.internal.HomeAssistantPythonBridge(408)\] : Error during instantiation of the implementation object
java.lang.reflect.InvocationTargetException: null
at jdk.internal.reflect.DirectConstructorHandleAccessor.newInstance(DirectConstructorHandleAccessor.java:74) \~\[?:?\]
at java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:502) \~\[?:?\]
at java.lang.reflect.Constructor.newInstance(Constructor.java:486) \~\[?:?\]
at org.apache.felix.scr.impl.inject.internal.ComponentConstructorImpl.newInstance(ComponentConstructorImpl.java:326) \[bundleFile:?\]
at org.apache.felix.scr.impl.manager.SingleComponentManager.createImplementationObject(SingleComponentManager.java:286) \[bundleFile:?\]
at org.apache.felix.scr.impl.manager.SingleComponentManager.createComponent(SingleComponentManager.java:115) \[bundleFile:?\]
at org.apache.felix.scr.impl.manager.SingleComponentManager.getService(SingleComponentManager.java:1002) \[bundleFile:?\]
at org.apache.felix.scr.impl.manager.SingleComponentManager.getServiceInternal(SingleComponentManager.java:975) \[bundleFile:?\]
at org.apache.felix.scr.impl.manager.SingleComponentManager.getService(SingleComponentManager.java:920) \[bundleFile:?\]
at org.eclipse.osgi.internal.serviceregistry.ServiceFactoryUse$1.run(ServiceFactoryUse.java:220) \[org.eclipse.osgi-3.18.0.jar:?\]
at java.security.AccessController.doPrivileged(AccessController.java:319) \[?:?\]
at org.eclipse.osgi.internal.serviceregistry.ServiceFactoryUse.factoryGetService(ServiceFactoryUse.java:217) \~\[org.eclipse.osgi-3.18.0.jar:?\]
at org.eclipse.osgi.internal.serviceregistry.ServiceFactoryUse.getService(ServiceFactoryUse.java:118) \~\[org.eclipse.osgi-3.18.0.jar:?\]
at org.eclipse.osgi.internal.serviceregistry.ServiceConsumer$2.getService(ServiceConsumer.java:48) \~\[org.eclipse.osgi-3.18.0.jar:?\]
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.getService(ServiceRegistrationImpl.java:547) \~\[org.eclipse.osgi-3.18.0.jar:?\]
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.getService(ServiceRegistry.java:534) \~\[org.eclipse.osgi-3.18.0.jar:?\]
at org.eclipse.osgi.internal.framework.BundleContextImpl.getService(BundleContextImpl.java:660) \~\[org.eclipse.osgi-3.18.0.jar:?\]
at org.apache.felix.scr.impl.manager.SingleRefPair.getServiceObject(SingleRefPair.java:88) \~\[?:?\]
at org.apache.felix.scr.impl.inject.internal.ComponentConstructorImpl.newInstance(ComponentConstructorImpl.java:287) \~\[?:?\]
at org.apache.felix.scr.impl.manager.SingleComponentManager.createImplementationObject(SingleComponentManager.java:286) \~\[?:?\]
at org.apache.felix.scr.impl.manager.SingleComponentManager.createComponent(SingleComponentManager.java:115) \~\[?:?\]
at org.apache.felix.scr.impl.manager.SingleComponentManager.getService(SingleComponentManager.java:1002) \~\[?:?\]
at org.apache.felix.scr.impl.manager.SingleComponentManager.getServiceInternal(SingleComponentManager.java:975) \~\[?:?\]
at org.apache.felix.scr.impl.manager.SingleComponentManager.getService(SingleComponentManager.java:920) \~\[?:?\]
at org.eclipse.osgi.internal.serviceregistry.ServiceFactoryUse$1.run(ServiceFactoryUse.java:220) \~\[org.eclipse.osgi-3.18.0.jar:?\]
at java.security.AccessController.doPrivileged(AccessController.java:319) \[?:?\]
at org.eclipse.osgi.internal.serviceregistry.ServiceFactoryUse.factoryGetService(ServiceFactoryUse.java:217) \[org.eclipse.osgi-3.18.0.jar:?\]
at org.eclipse.osgi.internal.serviceregistry.ServiceFactoryUse.getService(ServiceFactoryUse.java:118) \[org.eclipse.osgi-3.18.0.jar:?\]
at org.eclipse.osgi.internal.serviceregistry.ServiceConsumer$2.getService(ServiceConsumer.java:48) \[org.eclipse.osgi-3.18.0.jar:?\]
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.getService(ServiceRegistrationImpl.java:547) \[org.eclipse.osgi-3.18.0.jar:?\]
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.getService(ServiceRegistry.java:534) \[org.eclipse.osgi-3.18.0.jar:?\]
at org.eclipse.osgi.internal.framework.BundleContextImpl.getService(BundleContextImpl.java:660) \[org.eclipse.osgi-3.18.0.jar:?\]
at org.apache.felix.scr.impl.manager.SingleRefPair.getServiceObject(SingleRefPair.java:88) \[bundleFile:?\]
at org.apache.felix.scr.impl.inject.methods.BindMethod.getServiceObject(BindMethod.java:675) \[bundleFile:?\]
at org.apache.felix.scr.impl.manager.DependencyManager.getServiceObject(DependencyManager.java:2612) \[bundleFile:?\]
at org.apache.felix.scr.impl.manager.DependencyManager.doInvokeBindMethod(DependencyManager.java:2078) \[bundleFile:?\]
at org.apache.felix.scr.impl.manager.DependencyManager.invokeBindMethod(DependencyManager.java:2061) \[bundleFile:?\]
at org.apache.felix.scr.impl.manager.SingleComponentManager.invokeBindMethod(SingleComponentManager.java:443) \[bundleFile:?\]
at org.apache.felix.scr.impl.manager.DependencyManager$MultipleDynamicCustomizer.addedService(DependencyManager.java:336) \[bundleFile:?\]
at org.apache.felix.scr.impl.manager.DependencyManager$MultipleDynamicCustomizer.addedService(DependencyManager.java:304) \[bundleFile:?\]
at org.apache.felix.scr.impl.manager.ServiceTracker$Tracked.customizerAdded(ServiceTracker.java:1232) \[bundleFile:?\]
at org.apache.felix.scr.impl.manager.ServiceTracker$Tracked.customizerAdded(ServiceTracker.java:1152) \[bundleFile:?\]
at org.apache.felix.scr.impl.manager.ServiceTracker$AbstractTracked.trackAdding(ServiceTracker.java:959) \[bundleFile:?\]
at org.apache.felix.scr.impl.manager.ServiceTracker$AbstractTracked.track(ServiceTracker.java:895) \[bundleFile:?\]
at org.apache.felix.scr.impl.manager.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:1184) \[bundleFile:?\]
at org.apache.felix.scr.impl.BundleComponentActivator$ListenerInfo.serviceChanged(BundleComponentActivator.java:116) \[bundleFile:?\]
at org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:123) \[org.eclipse.osgi-3.18.0.jar:?\]
at org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:961) \[org.eclipse.osgi-3.18.0.jar:?\]
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:234) \[org.eclipse.osgi-3.18.0.jar:?\]
at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:151) \[org.eclipse.osgi-3.18.0.jar:?\]
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:937) \[org.eclipse.osgi-3.18.0.jar:?\]
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:874) \[org.eclipse.osgi-3.18.0.jar:?\]
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:141) \[org.eclipse.osgi-3.18.0.jar:?\]
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:262) \[org.eclipse.osgi-3.18.0.jar:?\]
at org.eclipse.osgi.internal.framework.BundleContextImpl.registerService(BundleContextImpl.java:500) \[org.eclipse.osgi-3.18.0.jar:?\]
at org.apache.felix.scr.impl.manager.AbstractComponentManager$3.register(AbstractComponentManager.java:929) \[bundleFile:?\]
at org.apache.felix.scr.impl.manager.AbstractComponentManager$3.register(AbstractComponentManager.java:915) \[bundleFile:?\]
at org.apache.felix.scr.impl.manager.RegistrationManager.changeRegistration(RegistrationManager.java:133) \[bundleFile:?\]
at org.apache.felix.scr.impl.manager.AbstractComponentManager.registerService(AbstractComponentManager.java:984) \[bundleFile:?\]
at org.apache.felix.scr.impl.manager.AbstractComponentManager.activateInternal(AbstractComponentManager.java:752) \[bundleFile:?\]
at org.apache.felix.scr.impl.manager.AbstractComponentManager.enableInternal(AbstractComponentManager.java:674) \[bundleFile:?\]
at org.apache.felix.scr.impl.manager.AbstractComponentManager.enable(AbstractComponentManager.java:437) \[bundleFile:?\]
at org.apache.felix.scr.impl.manager.ConfigurableComponentHolder.enableComponents(ConfigurableComponentHolder.java:671) \[bundleFile:?\]
at org.apache.felix.scr.impl.BundleComponentActivator.initialEnable(BundleComponentActivator.java:310) \[bundleFile:?\]
at org.apache.felix.scr.impl.Activator.loadComponents(Activator.java:593) \[bundleFile:?\]
at org.apache.felix.scr.impl.Activator.access$200(Activator.java:74) \[bundleFile:?\]
at org.apache.felix.scr.impl.Activator$ScrExtension.start(Activator.java:460) \[bundleFile:?\]
at org.apache.felix.scr.impl.AbstractExtender.createExtension(AbstractExtender.java:196) \[bundleFile:?\]
at org.apache.felix.scr.impl.AbstractExtender.modifiedBundle(AbstractExtender.java:169) \[bundleFile:?\]
at org.apache.felix.scr.impl.AbstractExtender.modifiedBundle(AbstractExtender.java:49) \[bundleFile:?\]
at org.osgi.util.tracker.BundleTracker$Tracked.customizerModified(BundleTracker.java:488) \[osgi.core-8.0.0.jar:?\]
at org.osgi.util.tracker.BundleTracker$Tracked.customizerModified(BundleTracker.java:420) \[osgi.core-8.0.0.jar:?\]
at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:232) \[osgi.core-8.0.0.jar:?\]
at org.osgi.util.tracker.BundleTracker$Tracked.bundleChanged(BundleTracker.java:450) \[osgi.core-8.0.0.jar:?\]
at org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:949) \[org.eclipse.osgi-3.18.0.jar:?\]
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:234) \[org.eclipse.osgi-3.18.0.jar:?\]
at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:151) \[org.eclipse.osgi-3.18.0.jar:?\]
at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEventPrivileged(EquinoxEventPublisher.java:229) \[org.eclipse.osgi-3.18.0.jar:?\]
at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEvent(EquinoxEventPublisher.java:138) \[org.eclipse.osgi-3.18.0.jar:?\]
at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEvent(EquinoxEventPublisher.java:130) \[org.eclipse.osgi-3.18.0.jar:?\]
at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor.publishModuleEvent(EquinoxContainerAdaptor.java:217) \[org.eclipse.osgi-3.18.0.jar:?\]
at org.eclipse.osgi.container.Module.publishEvent(Module.java:499) \[org.eclipse.osgi-3.18.0.jar:?\]
at org.eclipse.osgi.container.Module.start(Module.java:486) \[org.eclipse.osgi-3.18.0.jar:?\]
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel$2.run(ModuleContainer.java:1847) \[org.eclipse.osgi-3.18.0.jar:?\]
at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor$1$1.execute(EquinoxContainerAdaptor.java:136) \[org.eclipse.osgi-3.18.0.jar:?\]
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1840) \[org.eclipse.osgi-3.18.0.jar:?\]
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1783) \[org.eclipse.osgi-3.18.0.jar:?\]
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1745) \[org.eclipse.osgi-3.18.0.jar:?\]
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1667) \[org.eclipse.osgi-3.18.0.jar:?\]
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1) \[org.eclipse.osgi-3.18.0.jar:?\]
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:234) \[org.eclipse.osgi-3.18.0.jar:?\]
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:345) \[org.eclipse.osgi-3.18.0.jar:?\]
Caused by: org.graalvm.polyglot.PolyglotException: ModuleNotFoundError: No module named ‘**future**’
at .(Unknown) \~\[?:?\]
at org.graalvm.polyglot.Context.eval(Context.java:449) \~\[?:?\]
at org.openhab.binding.homeassistant.internal.HomeAssistantPythonBridge.(HomeAssistantPythonBridge.java:66) \~\[?:?\]
at jdk.internal.reflect.DirectConstructorHandleAccessor.newInstance(DirectConstructorHandleAccessor.java:62) \~\[?:?\]
… 91 more
2026-03-31 22:47:33.568 \[WARN \] \[nal.discovery.HomeAssistantDiscovery\] - bundle org.openhab.binding.homeassistant:5.1.3 (407)\[org.openhab.binding.homeassistant.internal.discovery.HomeAssistantDiscovery(411)\] : Could not get service from ref {org.openhab.binding.homeassistant.internal.HomeAssistantPythonBridge}={service.id=604, service.bundleid=407, service.scope=bundle, osgi.ds.satisfying.condition.target=(osgi.condition.id=true), component.name=org.openhab.binding.homeassistant.internal.HomeAssistantPythonBridge, component.id=408}
2026-03-31 22:47:33.569 \[ERROR\] \[nal.discovery.HomeAssistantDiscovery\] - bundle org.openhab.binding.homeassistant:5.1.3 (407)\[org.openhab.binding.homeassistant.internal.discovery.HomeAssistantDiscovery(411)\] : Error during instantiation of the implementation object: Unable to get service for reference $001
I’m running openHAB in docker, this are the system information:
runtimeInfo:
version: 5.1.3
buildString: Release Build
locale: de-DE
systemInfo:
configFolder: /openhab/conf
userdataFolder: /openhab/userdata
logFolder: /openhab/userdata/logs
javaVersion: 21.0.10
javaVendor: Debian
osName: Linux
osVersion: 6.8.0-106-generic
osArchitecture: amd64
availableProcessors: 4
freeMemory: 228092568
totalMemory: 645922816
uptime: 28271
startLevel: 70
addons:
automation-jsscripting
automation-jsscriptingnashorn
binding-homeassistant
binding-mqtt
persistence-influxdb
persistence-rrd4j
transformation-jsonpath
transformation-map
transformation-regex
transformation-scale
clientInfo:
device:
ios: false
android: false
androidChrome: false
desktop: true
iphone: false
ipod: false
ipad: false
edge: false
ie: false
firefox: false
macos: false
windows: true
cordova: false
electron: false
capacitor: false
nwjs: false
webView: false
webview: false
standalone: false
os: windows
pixelRatio: 1
prefersColorScheme: light
isSecureContext: true
locationbarVisible: true
menubarVisible: true
navigator:
cookieEnabled: true
deviceMemory: 8
hardwareConcurrency: 12
language: de-DE
languages:
de-DE
de
en-US
en
onLine: true
platform: Win32
screen:
width: 1920
height: 1080
colorDepth: 32
support:
touch: false
pointerEvents: true
passiveListener: true
intersectionObserver: true
themeOptions:
dark: light
autoDarkMode: true
bars: light
homeNavBar: default
homeBackground: default
disableExpandableCardAnimation: false
blocklyRenderer: null
disablePageTransitionAnimation: false
hideChatInput: false
webAudio: false
visibleBreakpointDisabled: false
userAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML,
like Gecko) Chrome/146.0.0.0 Safari/537.36
timestamp: 2026-04-01T04:38:25.242Z
Obviously there was an update of the alpin docker image:
I’ve tried to start with version 5.1.2 instead - the binding starts, but a lot of other bindings do not,
may be there was an incompatible migration. I’ve not checked yet.
EDIT: Version 5.1.2 is working fine with homeassitant binding.
The missing bindings were my fault: I’ve tried the suggested solution from
and added binding = homeassistant to addons.cfg, which seems caused to all other addons to be uninstalled. After reinstalling them, the plugin works.
So seems to be an issue with 5.1.3.