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.