openHAB 4.3 Release Discussion

Adi.Corrales · December 17, 2024, 2:17pm

Ok, it seems some kind of incompatibility with NORD VPN extension (is that ever a thing?). I don’t know if there is something you can do to solve this, but definitively not related to openHAB.

/* latin-ext */
@font-face {
  font-family: 'Lato';
  font-style: normal;
  font-weight: 400;
  src: url(https://fonts.gstatic.com/s/lato/v24/S6uyw4BMUTPHjxAwXjeu.woff2) format('woff2');
  unicode-range: U+0100-02BA, U+02BD-02C5, U+02C7-02CC, U+02CE-02D7, U+02DD-02FF, U+0304, U+0308, U+0329, U+1D00-1DBF, U+1E00-1E9F, U+1EF2-1EFF, U+2020, U+20A0-20AB, U+20AD-20C0, U+2113, U+2C60-2C7F, U+A720-A7FF;
}
/* latin */
@font-face {
  font-family: 'Lato';
  font-style: normal;
  font-weight: 400;
  src: url(https://fonts.gstatic.com/s/lato/v24/S6uyw4BMUTPHjx4wXg.woff2) format('woff2');
  unicode-range: U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+0304, U+0308, U+0329, U+2000-206F, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD;
}

Matthias_Kaufmann · December 17, 2024, 2:19pm

I also get hundreds of warnings like

2024-12-17 15:16:39.045 [WARN ] [rest.core.item.EnrichedItemDTOMapper] - Failed transforming the state 'NULL' on item 'SonosKinderzimmerNordSleeptimer' with pattern 'JS(visualizeminutes.js):%s': Transformation service of type 'JS' is not available.

When the system is started, the transformation service is shown to be active!? Maybe some issue on loading the service too late?

Matthias_Kaufmann · December 17, 2024, 2:46pm

I removed the file based config and restarted and get several info logs, not sure what this tells me:

2024-12-17 15:28:39.248 [INFO ] [ll.impl.action.osgi.CommandExtension] - Registering commands for bundle org.apache.karaf.kar.core/4.4.6
2024-12-17 15:28:39.271 [INFO ] [ll.impl.action.osgi.CommandExtension] - Command registration delayed for bundle org.apache.karaf.log.core/4.4.6. Missing service: [org.apache.karaf.log.core.LogService]
2024-12-17 15:28:39.273 [INFO ] [ll.impl.action.osgi.CommandExtension] - Registering commands for bundle org.apache.karaf.log.core/4.4.6
2024-12-17 15:28:39.290 [INFO ] [ll.impl.action.osgi.CommandExtension] - Registering commands for bundle org.apache.karaf.package.core/4.4.6
2024-12-17 15:28:39.564 [INFO ] [ll.impl.action.osgi.CommandExtension] - Registering commands for bundle org.apache.karaf.service.core/4.4.6
2024-12-17 15:28:39.622 [INFO ] [ll.impl.action.osgi.CommandExtension] - Command registration delayed for bundle org.apache.karaf.shell.ssh/4.4.6. Missing service: [org.apache.sshd.server.SshServer]
2024-12-17 15:28:39.646 [INFO ] [ll.impl.action.osgi.CommandExtension] - Registering commands for bundle org.apache.karaf.system.core/4.4.6
....
2024-12-17 15:28:41.344 [INFO ] [internal.BundleWhiteboardApplication] - No matching target context(s) for Whiteboard element ServletModel{id=ServletModel-3,name='cxf-servlet',urlPatterns=[/*],contexts=[]}. Filter: (osgi.http.whiteboard.context.name=default). Element may be re-registered later, when matching context/s is/are registered.
2024-12-17 15:28:41.377 [INFO ] [ax.web.service.spi.model.ServerModel] - Created new ServletContextModel{id=ServletContextModel-4,contextPath='/'}
2024-12-17 15:28:41.421 [INFO ] [jetty.internal.JettyServerController] - Receiving Batch{"Registration of OsgiContextModel{WB,id=OCM-1,name='default',path='/',bundle=org.ops4j.pax.web.pax-web-extender-whiteboard,context=(supplier)}", size=2}
2024-12-17 15:28:41.423 [INFO ] [ce.jetty.internal.JettyServerWrapper] - Creating new Jetty context for ServletContextModel{id=ServletContextModel-4,contextPath='/'}
2024-12-17 15:28:41.521 [INFO ] [ce.jetty.internal.JettyServerWrapper] - Adding OsgiContextModel{WB,id=OCM-1,name='default',path='/',bundle=org.ops4j.pax.web.pax-web-extender-whiteboard,context=(supplier)} to o.o.p.w.s.j.i.PaxWebServletContextHandler@dc8cd0{/,null,STOPPED}
...
2024-12-17 15:29:25.773 [INFO ] [af.deployer.kar.KarArtifactInstaller] - Found a .kar file to deploy.
2024-12-17 15:29:25.774 [INFO ] [af.deployer.kar.KarArtifactInstaller] - KAR openhab-addons-4.3.0.kar is already installed. Please uninstall it first.

I then re-installed OH via openhabian-config, keeping several los especially

2024-12-17 15:33:34.841 [INFO ] [af.deployer.kar.KarArtifactInstaller] - Found a .kar file to deploy.
2024-12-17 15:33:34.842 [INFO ] [af.deployer.kar.KarArtifactInstaller] - KAR openhab-addons-4.3.0.kar is already installed. Please uninstall it first.

Michael_Feurle · December 17, 2024, 3:08pm

I found a strange behavior in the UI pages. As I said bevor, when i refresh the page e.g “http://192.168.20.20:8080/page/Dusche” in the browser, nothing is shown, The same, when I type the address into the browser by hand. But when I klick on the “Dusche icon” on the sidebar its working, an I can see the page. Refreshing again, and nothing more is shown.
Sorry for my bad English…

sihui · December 17, 2024, 3:22pm

Did you try

florian-h05 · December 17, 2024, 3:33pm

Good to know you found the reason and things got sorted, I am sorry I can’t help you with this.

Michael_Feurle · December 17, 2024, 3:49pm

Yes I tried this with no success…

sihui · December 17, 2024, 4:02pm

Did you already clean the cache of your browser or tried another browser?

rlkoshak · December 17, 2024, 4:24pm

I don’t know if this is related to the relase or not and its really niche. But after upgrading to the release from M4, OH wouldn’t come up because of the Gelf appender (I use it for Graylog) I had added to the log4j2.xml file.

		<!-- Gelf appender -->
		<!-- https://logging.apache.org/log4j/2.x/manual/layouts.html#GELFLayout -->

		<Socket host="10.10.1.74" immediateFail="true" name="GRAYLOG" port="12201" protocol="tcp">
			<GelfLayout compressionType="OFF" host="localhost" includeNullDelimiter="true" includeStacktrace="true">
				<!-- <KeyValuePair key="additionalField1" value="constant value"/>
				     <KeyValuePair key="additionalField2" value="$${ctx:key}"/> -->
			</GelfLayout>
		</Socket>

I’ve not looked into it closely yet but if anyone is using something similar and OH won’t come up, remove that appender and you can get OH back.

I’m not getting anything out of Graylog so I probably won’t actually look into this myself, unless someone asks on another thread, I just wanted to give a heads up.

flobee · December 17, 2024, 5:24pm

Hi, just for information for debian 12:
apt update && apt upgrade

Result:

–>–

openhab (4.3.0-1) wird eingerichtet ...

[openHAB] Listing important changes for version 4.3.0:
  Warning:  CORE: The sendFrequency parameter for Slider and Colorpicker sitemap elements has been removed.
  Warning:  CORE: The DateTimeType methods toZone(zone), toLocaleZone() and getZonedDateTime() have been deprecated. They will be removed in a future version. In DSL rules, please use getZon
edDateTime(ZoneId) as replacement for getZonedDateTime(), for example getZonedDateTime(ZoneId.systemDefault()) to use system time-zone.
  Warning:  ElectroluxAir Binding: The binding has been removed since the Electrolux Delta API has been discontinued.
  Warning:  JavaScript Automation: The isJsInstanceOfJavaType method of the utils namespace has been removed. Use JavaScript's instanceof operator instead.
  Warning:  MeteoAlerte Binding: The underlying API stopped delivering data in May 2023. Binding has been removed and is now replaced by Météo France Binding based on a new API.
  Warning:  MQTT Binding (Home Assistant): Thing types and channel IDs have been significantly restructured and simplified. Delete and re-create your things to opt in to the new style. In a 
subsequent openHAB release, existing things will also convert to the new style.
  Warning:  MQTT Binding (Home Assistant): Legacy schema vacuums are no longer supported.
  Warning:  Pentair Binding: EasyTouch thing has been renamed to more generic Controller and all channels have been organized into groups. You will need to reconfigure your setup to the new 
thing structure.

[openHAB] Running JSON Database upgrade tool (${OPENHAB_RUNTIME}/bin/upgradetool.jar).
[main] INFO org.openhab.core.tools.internal.Upgrader - Already executed 'itemCopyUnitToMetadata' on 2024-12-01T11:04:56.535679685+01:00[Europe/Berlin]. Use '--force'  to execute it again.
[main] INFO org.openhab.core.tools.internal.Upgrader - Already executed 'linkUpgradeJsProfile' on 2024-12-01T11:04:56.652199208+01:00[Europe/Berlin]. Use '--force'  to execute it again.
[main] INFO org.openhab.core.tools.internal.Upgrader - Already executed 'linkUpgradeScriptProfile' on 2024-12-01T11:04:56.678140404+01:00[Europe/Berlin]. Use '--force'  to execute it again.
[openHAB] JSON Database upgrade completed.

...

–<–

Just the install process.

I can not decide if it is a good or a bad report.
But: for a stable release of the OS: this should not happen.

Pls let me know if i have to do something
Now i’m checking if it working.

Kind Regards
Florian

tardismechanic · December 17, 2024, 5:28pm

Turns out for me it was user error. It seems NGINX Proxy Manager already does that by default, I just had my headers in the wrong area. Needed to put them in a custom location like this instead of under advanced.

These lines get auto added by NPM so if you have them in, the proxy won’t start.

proxy_http_version                    1.1;
proxy_pass                            http://localhost:8080/;
proxy_set_header Host                 $http_host;
proxy_set_header X-Real-IP            $remote_addr;
proxy_set_header X-Forwarded-For      $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto    $scheme;

rlkoshak · December 17, 2024, 5:36pm

Those “warnings” are telling you there are breaking changes between your old version and the new version of OH. These are things you will have manually change. You absolutely want to be told about these changes.

Or are you referring to the logs from the updateTool saying that the steps have already been executed?

flobee · December 17, 2024, 5:43pm

Thx for feedback but i dont understand your question!

I’m just a user using the web frontend to set stuff of things, currently no extra yml file or anything. just avm fritzbox things and using build in functions to track data (jdbc persistance).

So, and the warnings are confusing. Do i have to do anything? Probably not. !?

rlkoshak · December 17, 2024, 5:59pm

What you posted are the outputs from the installation/upgrade scripts of OH. The Warnings are telling you that you may need to manually change something. For example,

Warning:  CORE: The sendFrequency parameter for Slider and Colorpicker sitemap elements has been removed.

If you use sitemaps that use Slider or Colorpicker and you use the sendFrequency parameter your sitemaps will be broken until you remove the sendFrequency parameter.

Warning:  CORE: The DateTimeType methods toZone(zone), toLocaleZone() and getZonedDateTime() have been deprecated. They will be removed in a future version. In DSL rules, please use getZonedDateTime(ZoneId) as replacement for getZonedDateTime(), for example getZonedDateTime(ZoneId.systemDefault()) to use system time-zone.

If you have Rules that call getZonedDateTime() on the state of a DateTime Item, you need to change them to getZonedDateTime(ZoneId.systemDefault()).

The warnings are a very brief summary of the breaking changes documented in the Announcement thread. And they are to let you know that these are things you need to pay attention to after the upgrade because the new OH won’t work correctly unless you fix them.

Not all the warnings will apply to you. But those that do you will need to take an action to correct.

flobee · December 17, 2024, 6:10pm

Thank you!

I will check if something is wrong. Seems to be not. Currently the setup is very limited. None of the mentioned seems to be in use. The logs are very silent. Thank you. I will come back on another post if i can tell more. if so

Kind regards
Florian

Matthias_Kaufmann · December 17, 2024, 6:17pm

I decided to take the nightly backup and take the chance to migrate to docker (planned anyhow) to oh 4.2.2 first and upgrading to 4.3 the next days.

I have the openhabian system still available if someone wants to find out eats going wrong.

supersjel · December 17, 2024, 6:34pm

Hi, I’m having trouble with Zigbee device/binding since the upgrade. They’ve become self-conscious .I can control the devices but OH reports random states at random times. Usually in the order of one “incident” per device every one to four hours. So OH might show the device is turned on (without any command). When checking the device physically it’s still off. Trying to find the cause. Just to start with the basics … is there a way to install the previous 4.2.x binding on the current 4.3 version of OH. I want to avoid to do a complete rollback …

edit: This became a serious W.A.F. incident so I performed a roll-back to 4.2.3-1. Downgrade itself went smooth and OH restarted normal. I hope this solves the Zigbee issue (else it’s just a timing coincidence). I’ll let you know.

Edit 2 Seems to work, so far no spontanious status changes

jon.hazan · December 17, 2024, 7:17pm

Clearing the web cache didn’t work. But signing in on the app to grant admin access did cause the charts to be displayed, and they are still there when I log out. Now everything seems fine!

ErikDB · December 17, 2024, 7:18pm

Is there a way to automatically install openhab-transport-coap after an upgrade?

hmerk · December 17, 2024, 7:23pm

If you install shelly or tradfri binding from the UI, there is no need to.