openHAB 4.1 Release discussion

@Wolfgang_S, many thanks. That did the trick.

What settings do you expect for the Signal binding? Changing the logging is only available for distribution add-ons (and JSON 3rd party if the developer provides that information). It is not available for other add-ons.

Thanks for the clarification, bindings with no settings obviously won’t have a Settings icon on their page. This is clearly correct behaviour.

My confusion has arisen because bindings with no settings are listed under “Add-on Settings” on the Settings page and display a blank page when you click on them.

That’s probably an UI bug then.

I tend to disagree, as you at least can change the log level.

It is written in the tutorial:

In conf folder, you should find one folder for items, another for things and you have now one for tags => conf/tags

For marketplace add-ons?

He was not limiting to marketplace addons.

just wanted to give a big shoutout to all developers and maintainers!
Updated just fine from 4.0 to 4.1 - everything works as it should.

Merry Christmas to all, who celebrate and Happy Holidays to all, who don’t!

5 Likes

Are you able to change the log settings? I had a similar issue, although not caused by the upgrade, where my logging stopped. the file org.ops4j.pax.logging.cfg was empty and all the Add-on Settings were blank. I follewed the the guidance at https://community.openhab.org/t/my-logs-broke-today-not-sure-why/141647 from @Udo_Hartmann and then all the addon settings reappeared.

I just upgraded to 4.1, everything looks fine, except this warning which popups every second:

2023-12-27 09:57:27.547 [WARN ] [ab.core.internal.events.EventHandler] - Dispatching/filtering event for subscriber 'org.openhab.core.events.EventSubscriber' failed: null
java.lang.NullPointerException: null
	at java.util.Objects.requireNonNull(Objects.java:209) ~[?:?]
	at java.util.ImmutableCollections$List12.indexOf(ImmutableCollections.java:590) ~[?:?]
	at java.util.ImmutableCollections$AbstractImmutableList.contains(ImmutableCollections.java:329) ~[?:?]
	at org.openhab.core.automation.internal.module.handler.GroupStateTriggerHandler.receive(GroupStateTriggerHandler.java:137) ~[?:?]
	at org.openhab.core.internal.events.EventHandler.lambda$2(EventHandler.java:169) ~[?:?]
	at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1804) [?:?]
	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) [?:?]

Is this an items which is still null and used somewhere? If so, how can I find this item?

The item is not null., the groupName from the configuration of the GroupStateTrigger is null. It is set from the configuration during the creation of the GroupStateTriggerHandler, so I would say that there is an issue with the configuration. Do you use GroupStateTrigger in many rules?

Yes I use this on a lot of groups. I’ll try to check them all. It would be handy if the error tells which group causes the error :slight_smile:

Is this issue with the mqqt broker now fixed??

I have added a fix for that in Fix NPE in GroupStateTriggerHandler and GroupCommandTriggerHandler by J-N-K · Pull Request #3966 · openhab/openhab-core · GitHub

1 Like

great!

I checked all my groups (it were only 15) which have ‘group settings’ configured, but all these groups have a correct value.
Or do you mean there is an error in the configuration of these group settings?

groupType: Switch
function:
  name: OR
  params:
    - ON
    - OFF

No, You have a rule that has a “GroupStateTrigger” configured. And that rule is missing the groupName parameter in its configuration.

Thanks! I found it. There was indeed a rule which was causing the error. In the Code tab everything was ok, but in de Design tab the group was completely missing.
My warning is solved now.

1 Like

Hello…

I have now updated my three (DEV,TEST,PROD) system every two day‘s from 4.0.4-2 to 4.1.0-1.
It looks like, that everything works as aspected. Things, items, graphs, performance, rules (we all know that 1.st time it takes longer since 4.0x) but everything works so far.

So a big, big, applause for developers, and maintainers.

Thanks for a new stabile version!!!

2 Likes

With the 4.1 release my contact items aren’t stored anymore:

2023-12-29 09:49:53.115 [DEBUG] [.influxdb.InfluxDBPersistenceService] - Connection lost, trying re-connection
2023-12-29 09:49:53.122 [DEBUG] [rnal.influx1.InfluxDB1RepositoryImpl] - database status is OK, version is 1.8.10
2023-12-29 09:49:53.916 [DEBUG] [rnal.influx1.InfluxDB1RepositoryImpl] - Writing to database failed
org.influxdb.InfluxDBException$FieldTypeConflictException: partial write: field type conflict: input field "value" on measurement "con_Fuel_Aral_Open" is type integer, already exists as type float dropped=4
	at org.influxdb.InfluxDBException.buildExceptionFromErrorMessage(InfluxDBException.java:144) ~[?:?]
	at org.influxdb.InfluxDBException.buildExceptionForErrorState(InfluxDBException.java:173) ~[?:?]
	at org.influxdb.impl.InfluxDBImpl.execute(InfluxDBImpl.java:837) ~[?:?]
	at org.influxdb.impl.InfluxDBImpl.write(InfluxDBImpl.java:470) ~[?:?]
	at org.openhab.persistence.influxdb.internal.influx1.InfluxDB1RepositoryImpl.write(InfluxDB1RepositoryImpl.java:131) ~[?:?]
	at org.openhab.persistence.influxdb.InfluxDBPersistenceService.commit(InfluxDBPersistenceService.java:286) ~[?:?]
	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) [?:?]
2023-12-29 09:49:53.919 [WARN ] [.influxdb.InfluxDBPersistenceService] - Re-queuing 46617 elements, failed to write batch.