After Scan the wall plug doesn’t show up in the list:
OK, so that’s the problem. It should show up, as the binding discovers all available devices. If it is not shown, not all information about the device can be retreived and therefore it’s state is unknown.
You have to check, why it doesn not show up in inbox.
It sometimes take some time for the devices to show up in inbox, even you do a manual scan.
I’m now trying a new approach:
I’m cloning my installation to a new disk. Here some system parameters:
openhabian@homesrv5:~ $ java --version
openjdk 11.0.9 2020-10-20 LTS
OpenJDK Runtime Environment Zulu11.43+88-CA (build 11.0.9+11-LTS)
OpenJDK Client VM Zulu11.43+88-CA (build 11.0.9+11-LTS, mixed mode)
openhabian@homesrv5:~ $ uname -a
Linux homesrv5 5.10.103-v7l+ #1529 SMP Tue Mar 8 12:24:00 GMT 2022 armv7l GNU/Linux
cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
On the clone I want to do a update from OH 3.4.4 to OH 4.0.0M3
Could you please tell me how to proceed the update?
Is there somewhere a short description how to update from java 11 / OH 3.4.4 to java 17 / OH4.0.0?
I also have to update from java version 11 to 17. I tried it before with openhabian-config but java 17 wasn’t installed…
Once the update succeeded on “old” system I newly would set up openhabian v1.8 and restore the OH Backup from updated system
Than I should have a new openhabian v18 installation with OH 4.0.0M3 running…
I hope that will work
I have no experience with the upgrade process to openHAB 4.0, as I am rebuilding mine from scratch.
This gives me the chance to eliminate some mostakes maken in the past, especially on naming scheme.
So do you create all items, things, rules and so on new or do you restore a backup?
No backup, as this would create same item names.
Most of my things are auto discovered and therefore easy to recreate.
For items, I used a converter script which can be found in the community to export all items from JSONDB to textfiles. Then I edited all items meeting my needs and use “import from textual definition” to create them again.
1 Like
I builded up a clone as described above, installed java 17 and running oh 3.4.4 on it.
All things are online, also the FritzDECT Wallplugs.
After upgrading to OH 4.0.0 the same Wallplugs which were unknown in the previous installation where unknown here too.
I guess it’s really a problem with the OH4.0.0M3 Version of the AVM Binding…
In that case, you should file a bug on github/openhab-addons repo for avmfritz Binding.
Bug created:
Let’s see how it develops 
No News on the created bug…