HI!
I’m struggling with several problems since 4.1.1 publlished.
First when I upgraded it was way too slow starting up just mentioned in this post. I have a beefy (192GB RAM, 12 threads) server with a hyper-V ubuntu guest which runs docker and several containers beside openhab.
I downgraded back to 4.1.0 all started to work except binding install status in marketplace page similar to this.
I managed to get bindings to display correct status in WebUI and in karaf installing them from console manually but I have all my things NOT_YET_INITIALIZED status constantly. Similar problem is here.
Note: While I investigated I found some file path error in usedata/config/org/apache/felix/fileinstall folder that the deploy.config file is not in its (fileinstall) subdirectory but it has a name of fileinstall%007edeploy.config. This might be a file name concat bug in source code but I have no time to investigate further. This does not produce any error or warning in logs and the same happens in the default install with 4.1.1.
Note2: I had some strange listing formats inside userdata/config/org/openhab/addons.config beginning with a comma. I removed these commas and the initial binding install was successful. I list my original file here:
:org.apache.felix.configadmin.revision:=L"94"
automation=",jsscripting"
binding="evohome,ipcamera,samsungtv,systeminfo,jellyfin,ntp,androiddebugbridge,fronius,network,logreader,miio,chromecast,astro,mqtt,unifi,http,exec"
includeIncompatible=B"false"
misc="openhabcloud"
package="standard"
persistence="rrd4j,jdbc-sqlite,influxdb"
remote=B"true"
service.pid="org.openhab.addons"
transformation="jsonpath,regex,scale,map"
ui=",basic"
voice=",googletts"
I’ve tried to add my not working astro sun thing again manually (just for testing) and it suddenly started to work but the original one had still NET_YET_INITIALIZED state. After pause/start cycle it changed to HANDLER_MISSING_ERROR state . Then I tested the same with my fronius binding which caused the same. I checked my thing config in json database and I found that my original thing channels has only numbers without unit definition and my new one has UoM defined.
Original:
"fronius:powerinverter:9b8547c620:abb47a934e": {
"class": "org.openhab.core.thing.internal.ThingStorageEntity",
"value": {
"isBridge": false,
"channels": [
{
"uid": "fronius:powerinverter:9b8547c620:abb47a934e:inverterdatachannelpac",
"id": "inverterdatachannelpac",
"channelTypeUID": "fronius:pac",
"itemType": "Number",
"kind": "STATE",
"label": "AC Power",
"description": "AC power",
"defaultTags": [],
"properties": {},
"configuration": {}
},
...
New:
"fronius:powerinverter:d1aaff817e:25f8ce3580": {
"class": "org.openhab.core.thing.internal.ThingStorageEntity",
"value": {
"isBridge": false,
"channels": [
{
"uid": "fronius:powerinverter:d1aaff817e:25f8ce3580:inverterdatachannelpac",
"id": "inverterdatachannelpac",
"channelTypeUID": "fronius:pac",
"itemType": "Number:Power",
"kind": "STATE",
"label": "AC Power",
"description": "AC power generated by the inverter",
"defaultTags": [],
"properties": {},
"configuration": {}
},
...
So I’m just guessing but may the introduction of UoM changes lead to this? Is there any simple method to repair any undefined UoM states in my json database for my things, items, etc?
I saw that my update.log contains these lines:
Starting JSON database update...
[main] INFO org.openhab.core.tools.internal.Upgrader - Already executed 'itemCopyUnitToMetadata' on 2023-07-25T08:31:38.170672096+02:00[Europe/Budapest]. Use '--force' to execute it again.
[main] INFO org.openhab.core.tools.internal.Upgrader - Already executed 'linkUpgradeJsProfile' on 2023-07-25T08:31:38.179227054+02:00[Europe/Budapest]. Use '--force' to execute it again.
JSON database updated successfully.
Can I repeat this manually? From console or karaf shell? How can I check it the UoM update has really worked? Is there any log settings that displays UoM errors in general?
Any further help would be appreciated as I has 137 things and 677 items that I don’t feel the urge to redefine all via webUI.
P.S.: Right now as I’m writing this some of my things 40-50% of them changed to ONLINE. This happened in 20-30 mins range from openhab startup. Another strange thing is that half of my MQTT things are ONLINE, half of them are still NOT YET READY.