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