Known issues on OH3 upgrade

A post was split to a new topic: Issue with GUI defined DSL rules

2 posts were split to a new topic: Tr064 binding new name

2 posts were split to a new topic: openHABian upgrading hangs

A post was split to a new topic: Dimmer issue?

2 posts were split to a new topic: Non default port

Please guys only post here if the issue is of interest to a wide audience and impact many.

For your own issues, open your own threads please, and mind the posting rules.
I’m not your caretaker to sort your communications for you. Thank you.

How to ask a good question / Help Us Help You - Tutorials & Examples - openHAB Community

A post was split to a new topic: Habpanel issues

Hi,

I noticed you split my post about using a custom port. Does this mean you won’t treat this as a general upgrade issue that impacts a wide audience?

Fine with me, but then I’m going to close the thread as I now installed from scratch anyway. Nevertheless I think that an upgrade function shouldn’t ignore such a configuration change.

Stefan

Well I only have a peek at posts so can easily be mistaken when taking the decision to move a post.
A custom port in the first place IMHO is a custom problem. I don’t think many users change it.

1 Like

A post was split to a new topic: Upgrade issue

HABPanelViewer: OH3 changed REST event topics (not mentioned as breaking change), thus HABPanelViewer Command Item is broken. For now use 0.9.27pre linked in first post of HABPanelViewer thread until an official release is available.

A post was split to a new topic: OH3 persistence freeze

A post was split to a new topic: Upgrade issues with Samba et al

A post was split to a new topic: Cors problem

Hi Markus,
I noticed that in the breaking changes it’s missing the fact that this API will no longer be working. I know it’s not an official API, but many users rely on this API for their setups, so I think everyone should know it:

http://localhost:8080/classicui/CMD?<itemname>=<command>

I have opened my own topic on the subject, as a workaround should be provided:

thanks

This is no breaking change as it never was officially supported.
Further answer in your topic.

Just a small hint for further changes in Rule:
With OH2.5
Integer::parseInt(<A String for example with sql result>)
worked fine, equal the result has a carriage return or a line feed in.

With OH3.0 you need to eliminate CR and LF for example with Split:

Integer::parseInt(<A String for example with sql result>.split('\n|\r|\\n\r').get(0))

Otherwise parseInt get the numeric-value with an CR or LF at the end.

just replace classicui by basicui.
still working fine.

As far as I can work out system started trigger does not trigger if a (DSL?) .rules file is modified. See also:

1 Like

Hey Markus,
i mentioned one issue before in this thread and it was moved. i did a little research and maybe it does effect a bunch of people. please take 2minutes to trie it out. i did a description of the problem in the old post.

Thanks for your awesome work.