You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 17, 2021. It is now read-only.
After a postUpdate() change of a Number item, the PaperUI shows the new number instead of the mapped value. This occurs with item definitions like
Number exhibitionStatus "Exhibition is [MAP(status.map):%s]"
as well as when using the mappings= option for the same item in the sitemap.
The BasicUI and iOS app do the mapping immediatelly without requiring a manual page reload.
Tested with todays OH2 build nr. 99 from cloudbees.
The text was updated successfully, but these errors were encountered:
Yes, sorry, too many module names... I meant the Basic UI as the non-working one and the Classic UI(!) as the working one, reflecting mapings without page reloads.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
After a postUpdate() change of a Number item, the PaperUI shows the new number instead of the mapped value. This occurs with item definitions like
Number exhibitionStatus "Exhibition is [MAP(status.map):%s]"
as well as when using the mappings= option for the same item in the sitemap.
The BasicUI and iOS app do the mapping immediatelly without requiring a manual page reload.
Tested with todays OH2 build nr. 99 from cloudbees.
The text was updated successfully, but these errors were encountered: