What happened to Milestone 3?
I know of changes merged after M2 that are not showing up in M4.
@Kai explained it in his announcenentā¦
Thank you, @hmerk. I had missed it.
1 Like
Sorry I was a bit busy and didnāt find enough time to continue my investigation. 
Same problem, none of my rules which execute groovy scripts are working.
I Upgraded to 4.3m4 and there is one problem with the homewizard binding. It stays in status unkown. Do i open an issue for that?
2024-11-16 20:38:37.735 [WARN ] [mmon.WrappedScheduledExecutorService] - Scheduled runnable ended with an exception:
com.google.gson.JsonSyntaxException: java.lang.NumberFormatException: Expected an int but was 226.800 at line 1 column 515 path $.active_voltage_l1_v
at com.google.gson.internal.bind.TypeAdapters$7.read(TypeAdapters.java:251) ~[?:?]
at com.google.gson.internal.bind.TypeAdapters$7.read(TypeAdapters.java:241) ~[?:?]
at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$1.readIntoField(ReflectiveTypeAdapterFactory.java:212) ~[?:?]
at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$FieldReflectionAdapter.readField(ReflectiveTypeAdapterFactory.java:433) ~[?:?]
at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:393) ~[?:?]
at com.google.gson.Gson.fromJson(Gson.java:1227) ~[?:?]
at com.google.gson.Gson.fromJson(Gson.java:1137) ~[?:?]
at com.google.gson.Gson.fromJson(Gson.java:1047) ~[?:?]
at com.google.gson.Gson.fromJson(Gson.java:982) ~[?:?]
at org.openhab.binding.homewizard.internal.handler.HomeWizardDeviceHandler.pollData(HomeWizardDeviceHandler.java:140) ~[?:?]
at org.openhab.binding.homewizard.internal.handler.HomeWizardDeviceHandler.pollingCode(HomeWizardDeviceHandler.java:160) ~[?:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) ~[?:?]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) ~[?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?]
at java.lang.Thread.run(Thread.java:840) [?:?]
Caused by: java.lang.NumberFormatException: Expected an int but was 226.800 at line 1 column 515 path $.active_voltage_l1_v
at com.google.gson.stream.JsonReader.nextInt(JsonReader.java:1218) ~[?:?]
at com.google.gson.internal.bind.TypeAdapters$7.read(TypeAdapters.java:249) ~[?:?]
ā¦ 16 more
the rest works great!
That is a bug and it should be posted on GitHub. The log file is of great value here
Hello
I have at the moment a very big delay (10-20s) in sending notifications and there are also some lost ones.
A long time hide notifications feature also didnāt work, but seems to work again (I donāt know why).
I use openhab 4.3.0.M2 and iOS app V3.0.8.
Does anyone else have similar issues?
Iām not yet on 4.3 but had similar issues with regards to notifications since 4.2. But it seems to work fine now though sometimes hiding notifications stills seems a bit slow.
1 Like
Have you had a chance to look at this? 4.3 just doesnāt work for me since well over 50% of my rules remain uninitialised due to using Groovy scripts
1 Like
@wborn - will the groovy fix make it into the GA release?
Beginning from M4 (maybe it was even M3) I recognize that my browser freezes a lot (loading forever) escpecially when working in multiple tabs. When the freeze occurs all the other openhab tabs stop working too. After completely closing and restarting the browser everything is back to normal.
Does anybody else discover this issue too?
2 Likes
Yes, but Iāve been having that problem for a long time (and always on the latest release). Although, I wouldnāt classify the occurrence as āa lotā in my case.
I have noticed this as well from time to time on my dev system only, but @stefan.hoehn reported this as well to me.
I have recently found the time and motivation to investigate this issue, and I have been able to verify that this is no server-side or client-side issue of openHAB itself (which is good news) but instead a browser issue (bad news): We are running into a browser limitation about maximum parallel HTTP connections.
The good news is, this is fixable.
One solution is to use HTTP/2, which unfortuntaly requires HTTPS, but this is the reason I never experienced that issue on my production system: I have enabled HTTP/2 in my nginx.
The other solution is to set the Keep-Alive header to keep alive the connections.
Both should be implement-able by changing our Jetty config.
See What are Max Parallel HTTP Connections in a Browser? - GeeksforGeeks for more information.
I have created an issue to take care of this: Enable http/2 for https & Set Keep-Alive header for http Ā· Issue #4466 Ā· openhab/openhab-core Ā· GitHub
6 Likes
OMG had this issue for a while, updated the nginx config (http2), it is super snappy now. Thanks a million!
2 Likes
I also updated my nginx config with http2 and keepalive. So far everything runs smoothly. Thank you for investigating. It was really getting on my nerves but since I never read anything about it here I thought it must be specific to my own setup 
2 Likes
Are you able to create a PR?
What exactly does this mean? For the laymenā¦ 
I run my openhab behind a reverse proxy and I use nginx as webserver for this reverse proxy.
By doing this I can serve openHAB with a proper certificate via https. So in case you donāt have a similar setup already you unfortunately cannot just take these config changes and use them yourself.
But this issue (once resolved) should fix this for everyone even when not running OH behind a reverse proxy (If I understand it correctly):
This is my new upstream configuration (actually I donāt know what a good value for keepalive would be, I just started with the value from the nginx manual).
upstream openhab {
server 127.0.0.1:8080;
keepalive 32;
}
I suppose I donāt have that setup, as I donāt really know what a reverse proxy is
Iāll wait and see. Itās not the biggest problem, luckily.