I am working on the update from OH2 to OH3 for some weeks. The inplace upgrade was not successful so this is the reason that I copy my whole setup to another machine and work on it in parallel.
I am nearly at the end and now I noticed that the installation of the Hue Emulation addon results in a non working OH3 environment. After installation the UI is not usable anymore. I have to uninstall the binding via Karaf to make it working again.
I have updated to the newest v3.4.1 but still the same issue. I tried to install this binding manually while adding the .jar file to the addons folder but also no success.
In my OH2 environment there is no issue with this. But on OH3 after installation I have the following entry in my OH3 log:
I did some more investigation. After clearing the cache nothing changed.
If I run OH on my Windows via the “start.bat” file everything is fine and controllable and also the Hue Emulation is running without issues.
If I went back to my default mode that I use the Windows service to start OH, then I am running in this issue. This is reproducable.
I have already deleted and installed the service again without success. Any ideas whats the different is between this 2 start modes via batch and via windows service?
Hmm it looks that there is a general issue. I have downloaded a complete new OH 3.4.1 for Windows and run it. My old version was copied to another destination.
After the initial setup with the username and the location I just installed the Hue emulation binding via UI with the same result. There is no other configuration inside.
The only thing is that this version was started as service and not via batch.