removed additional addons from addons folder
the log now shows
2024-01-01 15:10:10.326 [ERROR] [ternal.service.BootFeaturesInstaller] - Error installing boot features
java.lang.IllegalStateException: Resource has no uri
at org.apache.karaf.features.internal.service.Deployer.getBundleInputStream(Deployer.java:1631) ~[?:?]
at org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:904) ~[?:?]
at org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1069) ~[?:?]
at org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:1004) ~[?:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?]
at java.lang.Thread.run(Thread.java:840) [?:?]
nothing else
reboot, same problem
EDIT: Resetting file permissions and reinstalling Java 17 with openhabian-config doesnāt fix the problem
EDIT2: doing openhab-cli clean-cache 2 more times solved it
As I read on OSHI gitHub, there was a problem with path on windows platform and members of OSHI wrote that the problem should be now resolved. That why Iām asking about upgrade OSHI component in the next OH version.
Unfortunately the same CPU temp - UNDEF In the log:
[til.platform.windows.WmiQueryHandler] - COM exception querying MSAcpi_ThermalZoneTemperature, which might not be on your system. Will not attempt to query it again. Error was -2147217396: Failed to enumerate results.
Iām very sorry, it was some time ago and I can not find it in the browser history, but that does not change the fact that this binding does not work for the entire section āsensorsā, everything else in this binding works. Strangely enough hardwareinfo or other open source soft shows and temperature and fan speed on windows.
oh my gosh, what is doing on. I got some notyfication in bindings. I see 9 notyfications on MQTT and after click I see some elements to add from systeminfo, but fromā¦HomeAssistantā¦
I guess you enabled the homeassistant discovery protocol on your NAS. Thatās all. Items that follow the homeassistant convention can be auto-discovered and configured.
Thank you all for the OH 4.1 release. The upgrade was easy. I moved to new hardware and therefor had problems with the blink binding. I used the blink add-on org.openhab.binding.blink-4.1.0-SNAPSHOT.jar on the old system. On the new system I tried to add the blink binding but it installed āBlink 3.3ā which does not work. I removed āBlink 3.3ā and installed org.openhab.binding.blink-4.1.0-SNAPSHOT.jar on the new system. This version works even with some āservlet nameā errors. Is it possible to integrate org.openhab.binding.blink-4.1.0-SNAPSHOT.jar into OH 4.1 instead āBlink 3.3ā?