openHAB 4.1 Release discussion

Yeah,

Watchtower/Portainer did it as there are about 15 container running everything is automatic.

But I am not the only person struggeling, anyway good job, everything is great.

It was just my 2cents and supposed to be a feedback. with hope for the future

Happy Christmas

Solong
B

Why did you upgrade if this was going to be a problem? When to upgrade to a new version is wholly under your control.

Seems a bit extreme. Maybe delay updates until they are convenient or you have time to handle stuff that breaks.

As far as I’m aware, the only lost functionality is because of events while outside of OH’s control (e.g. MyQ shutting down 3rd part access).

4.1, as a point release, has no deliberate breaking changes and consists primarily of new features and bug fixes.

4 Likes

Riko,

no worries, as expected people are in their own little world and we say in Germany “don"t see the forest because of all the trees anymore”

I have deleted my post with my concerns and wish every one

a Happy Christmas.

It was critisicm which was pointed towards the future and how things could be improvesd. Maybe I took the wrong track with Openhab, maybe not.

Solong
B

I don’t agree with your assessement that about the suggestion finders being the cause. Jmdns has always been running in previous versions as well. Disabling the suggestion finder will stop the suggestion finder from running and create a dependency on it. You will not see mdns based suggestions.
It is different for UPnP as it is not running by default without an add-on that uses it. That should be completely stopped when disabling the suggestion finder.
The real issue seems to be that jmdns tries to scan on all network interfaces. That is independent of the suggestion finder. I don’t know if anything changed there.

I’m trying to upgrade my OH4.0.3 to 4.1.0. I must be really blind because the upgrade process under Win10 stops with an error message. Any ideas?

I upgrade from 4.0.4 to 4.1 and all is good except I have a roller shutter blind widget and the stop command has been stripped out of the thing channel.
I can put it back in easily enough but it is strange how it has been removed.

Here is the code in the thing channel under the advanced settings after the upgrade:

UID: mqtt:topic:mqttbroker:0cb7d742b7
label: Blinds 1 - 7
thingTypeUID: mqtt:topic
configuration: {}
bridgeUID: mqtt:broker:mqttbroker
location: Lounge
channels:
  - id: blind1control
    channelTypeUID: mqtt:rollershutter
    label: Blind 1 control
    description: ""
    configuration:
      commandTopic: zigbee2mqtt/blind1/set
      stateTopic: zigbee2mqtt/blind1
      transformationPattern: JSONPATH:$.position
      off: CLOSE
      on: OPEN

Here is the same part after I put the STOP back in.

UID: mqtt:topic:mqttbroker:0cb7d742b7
label: Blinds 1 - 7
thingTypeUID: mqtt:topic
configuration: {}
bridgeUID: mqtt:broker:mqttbroker
location: Lounge
channels:
  - id: blind1control
    channelTypeUID: mqtt:rollershutter
    label: Blind 1 control
    description: ""
    configuration:
      commandTopic: zigbee2mqtt/blind1/set
      stop: STOP
      stateTopic: zigbee2mqtt/blind1
      transformationPattern: JSONPATH:$.position
      off: CLOSE
      on: OPEN

The other strange part is the word STOP is in the place where the stop command is entered but if I clear it using the x on the right hand side of the field it just comes back again but doen’t update the code.

See the picture below of what I mean:

I just have to go through my 7 binds and highlight the word STOP anf type STOP back in and then it is happy.

I have now tried to run update.bat 4.1.0 but update fails when backup is being created and upgrading fails. I have also tried to delete the backup part in update.ps1 file but still the backup is being made. Any ideas?

Try to remove the tmp folder under \userdata\ ( \userdata\tmp\ ) and then do the update again.

1 Like

For a number of bindings I have newly installed in 4.1.0 from Community Marketplace and Other Add-ons, the Settings icon does not appear on the binding’s page.

The bindings are listed on the Settings page under Add-on Settings, but when I click on them, the settings page for the binding appears and is blank.

I’ve tried this with a selection of bindings and almost all I have tried have inaccessible settings. For example, HABSpeaker works and I can access the settings, but Signal does not.

Where do I need to store the yaml file for the customs semantic tags?

I found this how to https://community.openhab.org/t/oh-4-1-tutorial-to-manage-custom-semantic-tags/148135....but where to store it?

@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.