Android app: Alignment in semantic model not always as it should be

[ErikDB87]

See also https://community.openhab.org/t/alignment-in-semantic-model-not-always-as-it-should-be/156724?u=erikdb

As you can see, Lampje Spiegel badkamer (1ste verdieping) is more to the left than it should be…

Some details about my phone:
Android 11
'Smallbandversion': MPSS.AT.4.0.2-00602-SDM710_GEN_PACK-1.353333.3.468668.1
'Kernel version': 4.9.227-perf+
openhab/openhab-addons#1 Mon Jan 17 16:05:56 CST 2022
Build number: 00WW_6_210_SP06

[openhab-bot]

This issue has been mentioned on openHAB Community. There might be relevant details there:

https://community.openhab.org/t/alignment-in-semantic-model-not-always-as-it-should-be/156724/3

[jlaur]

@ErikDB87 - I'm not sure in which component this issue is to be found, but I'm sure it's not in addons. I would recommend filing this issue in openhab-android.

[ErikDB87]

@ErikDB87 - I'm not sure in which component this issue is to be found, but I'm sure it's not in addons. I would recommend filing this issue in openhab-android.

Aha, I didn't see that component. Then again, I thought I had posted the issue in 'WebUI', so I messed up anyway. 🙄

I assume someone can move the issue?

[ErikDB87]

@ErikDB87 - I'm not sure in which component this issue is to be found, but I'm sure it's not in addons. I would recommend filing this issue in openhab-android.

Aha, I didn't see that component. Then again, I thought I had posted the issue in 'WebUI', so I messed up anyway. 🙄

I assume someone can move the issue?

@addon-maintainers, I've been told tagging you would help speed up the process...

[jlaur]

I believe it can only be done by someone with write access to both repositories:

• https://github.com/orgs/openhab/teams/android-maintainers
• https://github.com/orgs/openhab/teams/add-ons-maintainers

Or perhaps someone with super powers, @kaikreuzer are you able to do this? 😉

[florian-h05]

Does the issue also occur when opening Main UI in the browser?

I don‘t think this is an Android issue, because you are using Main UI inside the Android App.
Should be a UI issue, but I have just checked and I am not sure if we can fix it — the model treeview is using a component from the UI framework being used, so this is likely a upstream bug.
(Which is probably fixed in the latest version, but the upgrade is some major work and hasn‘t been done yet.)

[ErikDB87]

Does the issue also occur when opening Main UI in the browser?

It does. So apparently it's "a MainUI issue and should be moved to the webui repo"...

[ErikDB87]

@florian-h05 suggested I ping @kaikreuzer to get this issue in the correct component... Sorry for the trouble.