Sorry, I misunderstood that from the docs. I read that as a server setting and then that you have to make sure the browser settings are enabled as well.
After turning on on my Android Browser it now works.
Sorry about the misunderstanding.
EDIT: And with the setting enabled in the Android App it works there too
Looking at the files details, I see that barking.mp3 is a mono MP3 @ 64 kbps while doorbell.mp3 is a joint stereo MP3 @ 128 kbps.
So for doorbell, we have the most common bitrate, I can’t believe this can be the problem. Maybe an incompatibility of Firefox with joint stereo ???
I tried restarting several times over the course of the day, so this does not seem to be a temporary glitch. After downgrading to 3.3.0 everything works as ecpected.
I am using an installation via apt on a Debian 11.
I did some more research regarding the error above.
Ist is caused by the PostgreSQL JDBC persistence service. I tried to place the postgresql-42.4.1.jar in the /usr/share/openhab/addons folder and it is loaded, as the output of bundle:list shows:
thanks for your help! I just tested it and the issue is resolved.
I am still not sure, why placing the jar file in the addons folder did not work, but I found an old threads describing the exact same problem. So this is not an issue with the current 3.4 Milestone release.
Just updated to M2 today, and now on every restart I am seeing 40 or 50 “Added new thing ‘…’ to inbox.” messages in my log. And even if I mark the things as ignored, they still reappear in the next restart. The issue relates to all of my bindings so it is not a binding issue but rather a core issue.
Just updated to M2 on Windows 10 and once again (as I recall same happned on M1) my org.ops4j.pax.logging.cfg file was blank, so no logging etc working.
Changed to:
I just tried M2 (using a docker container) and got the following error. It seems that the bindings cannot be installed with the new version. I went back to M1 and it worked fine.
Are you importing the addon files directly or having openhab download them? If you are not trying to load them by file, it probably is related to the jfrog issue. Check the thread for the file location if needed.