openHAB 4.2 Release Discussion

[Cplant]

Thanks to everyone involved! So far a very smooth update!

Quick question on the issue of Graphs in the iOS app only loading after pressing on “Steuerelemente”:

• Initial error: openHAB 4.1 Release discussion - #188 by scheuerer
• The fix implemented by @florian-h05: openHAB 4.1 Release discussion - #192 by florian-h05
• The link to the GitHub issue: Analyzer: Fix analyzer not initially visible on iOS 17.4 by florian-h05 · Pull Request #2511 · openhab/openhab-webui (github.com)):

I just updated my OH to 4.2, and in the iOS App I still have to press “Steuerelemente” for the graph to load. Does this have to do with the new iOS app being released soon, or am I looking at a caching problem?

[florian-h05 (Florian H.)]

@Cplant

Does this have to do with the new iOS app being released soon, or am I looking at a caching problem?

This doesn’t relate to the new iOS apps, it seems like a caching problem.
Can you please to to Help & About and „reload app“ or „clean cache and refresh“?

[Cplant]

@florian-h05

Can you please to to Help & About and „reload app“ or „clean cache and refresh“?

Could only find an option for „Reload App“, which I did. So far, so good. Thanks!

[openschwall (Peter Mueller)]

same problem here with http thing producing a warning

2024-07-12 00:54:37.025 [WARN ] [.internal.http.RateLimitedHttpClient] - Could not find authentication result for 'http://192.168.0.158:83/xx.html?part=readerstats&label=x', failing here

Obviously, username and password is not sent to the thing correctly.

[J-N-K (Jan N. Klug)]

Please show the thing configuration.

[Falk (Falk S.)]

Hi, thanks for the new release!!

I upgraded from 4.1.3 to 4.2. When login into cli, I do see the following:

SLF4J(W): No SLF4J providers were found.
SLF4J(W): Defaulting to no-operation (NOP) logger implementation
SLF4J(W): See SLF4J Error Codes for further details.
SLF4J(W): Class path contains SLF4J bindings targeting slf4j-api versions 1.7.x or earlier.
SLF4J(W): Ignoring binding found at [jar:file:/openhab/runtime/system/org/apache/karaf/org.apache.karaf.client/4.4.6/org.apache.karaf.client-4.4.6.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J(W): See SLF4J Error Codes for an explanation.

Is this relevant and if yes, is there a fix to this?
Thanks

[florian-h05 (Florian H.)]

@Falk

Is this relevant and if yes, is there a fix to this?

Thanks for reporting, we are aware of this and it is a known in Apache Karaf 4.4.6, see SLF4J(W) console output when logging into Karaf console · Issue #4283 · openhab/openhab-core · GitHub. Once Karaf 4.4.7 is released, we can upgrade to it and this should be fixed then.
Until then I guess you can ignore it.

[Falk (Falk S.)]

I am still testing my new release installation 4.2 and found the message

The method last(Iterable) from the type IterableExtensions is deprecated

for

val changeditem = gAlarmBreak.members.sortBy[lastUpdate].last

I haven’t found a solution / replacement for “.last” to this. Any hints?

Thanks

UPDATE: Method “lastOrNull” seems to have replaced “last” method.

[scheuerer]

Friends…

I have tested once more. So the issue is NOT away.
On an iPhone and on my iPad still the same issue not matter which browser I use.
The only thing which helps, is to press the reload button from the browser and the reload the whole page.
Also cleaning cache from the browser is not helping to solve the issue.

BR
Jochen

[Cplant]

@scheuerer

So the issue is NOT away.

Maybe you’d like to add a detailed description here: Analyzer: Fix analyzer not initially visible on iOS 17.4 by florian-h05 · Pull Request #2511 · openhab/openhab-webui · GitHub

So far I could not reproduce the error myself.

[openschwall (Peter Mueller)]

this is my thing configuration

UID: http:url:25e1999b91
label: URL_xx
thingTypeUID: http:url
configuration:
  authMode: BASIC
  ignoreSSLErrors: false
  baseURL: http://192.168.0.158:83/xxx.html?part=readerstats&label=aaa
  password: password
  delay: 0
  stateMethod: GET
  refresh: 30
  commandMethod: GET
  timeout: 3000
  bufferSize: 2048
  username: username
channels:
  - id: URL_xx
    channelTypeUID: http:string
    label: URL_xx
    description: ""
    configuration:
      stateTransformation: XPATH://reader/@status
  - id: last-success
    channelTypeUID: http:request-date-time
    label: Last Success
    configuration: {}
  - id: last-failure
    channelTypeUID: http:request-date-time
    label: Last Failure
    configuration: {}

Update: I have changed authentication method from basic to digest for all my http things. Since then, they are online again.

[Cplant]

Quick question: After upgrading to OH 4.2 from OH 4.1.3 (on docker / Raspi 4) the settings page warns me of health issues:

… which then present themselves as orphaned links:

… which then look the following (btw: I have 676 items)

At the very bottom it offers me to purge all managed links, though this sounds rather dangerous:

Not 100% sure whether this comes from the update to OH 4.2, but I did not change anything else in the past months.

Any hints?

[Falk (Falk S.)]

@Cplant

Not 100% sure whether this comes from the update to OH 4.2, but I did not change anything else in the past months.

Any hints?

I just worked through over 300 issues. I started with a manual approach (my definitions are mostly per *.items files) and took the chance to take advantage of the automatic approach wherever possible. However, it’s worth checking the entries since you may want to ‘repair’ the broken links rather than just deleting them.

To what I’ve understood, this new health UI has been introduced with 4.2. I found it very useful to clean up and repair all the lost links that have been caused in the last years by removing things, changed API’s, changed channels/bindings and so on …

This feature is also mentioned here
openhab 4.2 release notes

Good luck

[Cplant]

@Falk

To what I’ve understood, this new health UI has been introduced with 4.2.

Thanks. Good to know that these problems have been there all along, but only visible with 4.2. Will have to do some houseworks then as well.

[Lolodomo]

@Cplant

Good to know that these problems have been there all along, but only visible with 4.2

For your information, a console command existed since a very long time doing the same thing.

[Falk (Falk S.)]

I am facing a persistence problem with 4.2.0:

item.lastChange() and
item.lastUpdate()

both return null. I’ve checked the existence of data in the database.

On the other hand

item.previousState.getTimestamp()

works.
lastChange() and lastUpdate() have worked in my DSL script with 4.1.3.

I have mysql 5.

Anyone else facing this problem?
Thanks

UPDATE: This problem does not apply to all of my items … will check further.

[Piffer (Tim)]

Hi All,

thanks for the update. Update process went smooth as usual, however I experienced an issue with Math calculations in Blockly which worked on 4.1.
It looks like calculations with “new state of item” blocks don’t work anymore. They do, when I put them into a variable before.
Example:

Output:

Power greater than 1000 W:

1452.3

1452.3

1452.3

now working with a Variable instead of new state of item:

1452.3

1.4523

1.5

[Oliver2 (Oliver)]

Adding an item to a trigger-based channel is not possible anymore via MainUI.

When clicking on “Create a new item” it does not provide any input fields.

[Mherwege (Mark Herwege)]

@Falk

I am facing a persistence problem with 4.2.0:

item.lastChange() and
item.lastUpdate()

both return null. I’ve checked the existence of data in the database.

If the last persisted state is different from the current state, it will return null now, as there is no precise timepoint for the last change or update.