[16:06:42] root@openhabian:/home/openhabian# curl -s https://repos.azul.com/azul-repo.key | sudo gpg --dea rmor -o /usr/share/keyrings/azul.gpg
File ‘/usr/share/keyrings/azul.gpg’ exists. Overwrite? (y/N) y
[16:10:55] root@openhabian:/home/openhabian# apt update
Get:1 http://davesteele.github.io/comitup/repo comitup InRelease [4,659 B]
Hit:2 Index of /raspbian buster InRelease
Hit:3 Index of /debian buster InRelease
Hit:4 Index of /node_14.x/ buster InRelease
Hit:5 https://repos.azul.com/zulu/deb stable InRelease
Hit:6 JFrog testing InRelease
Fetched 4,659 B in 2s (2,385 B/s)
Reading package lists… Done
Building dependency tree
Reading state information… Done
All packages are up to date.
N: Skipping acquire of configured file ‘main/binary-armhf/Packages’ as repository ‘https://repos.azul.com/ zulu/deb stable InRelease’ doesn’t support
architecture ‘armhf’
[16:14:34] root@openhabian:/home/openhabian# sudo apt install zulu17-jdk
Reading package lists… Done
Building dependency tree
Reading state information… Done
E: Unable to locate package zulu17-jdk
[16:15:23] root@openhabian:/home/openhab
Please help!! Updated without reading from Openhab3 to openhab 4 via openhabian-config/ Now openhab doesn’t start, what can I do? How to update Java 11 to Java 17?
Don‘t push this way. You won‘t get quicker answers if repeating your question within short time.
In the meantime you could have googled how to get Java 17 on your Pi…
If you have further questions on this one, please open a new topic as it is not Milestone related.
a) make sure to use the stable repo instead of testing. this would enable you to switch back to OH 3.4.2. In case the configuration files are already touched you may have a problem. Especially in case there is no backup.
Great work everyone!
I just upgraded to 4.0.0.M1 and everything seems to be working fine so far, but I get these errors related to the HarmonyHub/HomeConnect bindings at startup:
2023-03-11 14:01:10.417 [WARN ] [core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'harmonyhub:device:LivingRoom:60292581' are missing in the respective registry for more than 120s. This should be fixed in the binding.
2023-03-11 14:01:10.418 [WARN ] [core.thing.internal.ThingManagerImpl] - Failed to normalize configuration for thing 'harmonyhub:device:LivingRoom:60292581': {thing/channel=Type description for {0} not found although we checked the presence before.}
2023-03-11 14:01:10.418 [WARN ] [core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'harmonyhub:device:LivingRoom:60292583' are missing in the respective registry for more than 120s. This should be fixed in the binding.
2023-03-11 14:01:10.419 [WARN ] [core.thing.internal.ThingManagerImpl] - Failed to normalize configuration for thing 'harmonyhub:device:LivingRoom:60292583': {thing/channel=Type description for {0} not found although we checked the presence before.}
2023-03-11 14:01:10.419 [WARN ] [core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'harmonyhub:device:LivingRoom:77733401' are missing in the respective registry for more than 120s. This should be fixed in the binding.
2023-03-11 14:01:10.419 [WARN ] [core.thing.internal.ThingManagerImpl] - Failed to normalize configuration for thing 'harmonyhub:device:LivingRoom:77733401': {thing/channel=Type description for {0} not found although we checked the presence before.}
2023-03-11 14:01:10.419 [WARN ] [core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'harmonyhub:device:LivingRoom:76995753' are missing in the respective registry for more than 120s. This should be fixed in the binding.
2023-03-11 14:01:10.419 [WARN ] [core.thing.internal.ThingManagerImpl] - Failed to normalize configuration for thing 'harmonyhub:device:LivingRoom:76995753': {thing/channel=Type description for {0} not found although we checked the presence before.}
2023-03-11 14:01:10.419 [WARN ] [core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'harmonyhub:device:LivingRoom:77785115' are missing in the respective registry for more than 120s. This should be fixed in the binding.
2023-03-11 14:01:10.420 [WARN ] [core.thing.internal.ThingManagerImpl] - Failed to normalize configuration for thing 'harmonyhub:device:LivingRoom:77785115': {thing/channel=Type description for {0} not found although we checked the presence before.}
2023-03-11 14:01:10.420 [WARN ] [core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'homeconnect:dishwasher:202210be59:0e61f827a1' are missing in the respective registry for more than 120s. This should be fixed in the binding.
2023-03-11 14:01:10.420 [WARN ] [core.thing.internal.ThingManagerImpl] - Failed to normalize configuration for thing 'homeconnect:dishwasher:202210be59:0e61f827a1': {thing/channel=Type description for {0} not found although we checked the presence before.}
2023-03-11 14:01:10.435 [WARN ] [core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'harmonyhub:device:LivingRoom:60946348' are missing in the respective registry for more than 120s. This should be fixed in the binding.
2023-03-11 14:01:10.436 [WARN ] [core.thing.internal.ThingManagerImpl] - Failed to normalize configuration for thing 'harmonyhub:device:LivingRoom:60946348': {thing/channel=Type description for {0} not found although we checked the presence before.}
2023-03-11 14:01:10.436 [WARN ] [core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'harmonyhub:hub:LivingRoom' are missing in the respective registry for more than 120s. This should be fixed in the binding.
2023-03-11 14:01:10.437 [WARN ] [core.thing.internal.ThingManagerImpl] - Failed to normalize configuration for thing 'harmonyhub:hub:LivingRoom': {thing/channel=Type description for {0} not found although we checked the presence before.}
I have already deleted/added all related things, but the error remains.
This is a warning that the binding developer needs to do something. It’s currently not affecting functionality (besides a delay of 120s before the thing comes up on initial startup). There are also other bindings affected.
The PR @laursen linked is the core part to make it easier to fix in the bindings.
Nothing has changed with Jython. It should work. But I don’t think anyone running the snapshots are using Jython so if something’s wrong please let us know.
I’ve installed M1 to start testing but SmartHome/J HTTP Binding seems to not be available. I use it instead of the HTTP Binding due to some issues I had in the past. Will it be available ? Or shall I use the HTTP Binding instead ?
You can try using https://download.smarthomej.org/addons-snapshot.json. But there is ongoing work to merge the “duplicate” bindings. This is already done for snmp, tr064, influxdb, onewire and dmx. PR already exist for mail and knx (thanks @holgerf).