Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UoM handling in iOS App differs from BasicUI #721

Open
2 of 3 tasks
pelerner opened this issue Jun 2, 2023 · 0 comments
Open
2 of 3 tasks

UoM handling in iOS App differs from BasicUI #721

pelerner opened this issue Jun 2, 2023 · 0 comments

Comments

@pelerner
Copy link

pelerner commented Jun 2, 2023

Referring to #555

The behavior of openhab iOS App differs from the openhab BasicUI regarding UoM items, esp. max/min/step-values.

  1. My UoM-item is defined in seconds — because the knx-device delivers seconds only.
    Number:Time iZEIT "item in seconds [%.1f s]" {channel="knx:…"}

  2. The item on the Sitemap as a Setpoint in seconds works just fine in BasicUI and in openhab iOS App
    Setpoint item=iZEIT label="item in seconds [%.1f s]" minValue=300 maxValue=3600 step=60

  3. The item on the Sitemap as a Setpoint in minutes works just fine in BasicUI and fails to recognize minutes in the iOS App
    Setpoint item=iZEIT label="item in minutes [%.1f min]" minValue=5 maxValue=60 step=5

The BasicUI handles the step value of “5” as minutes, OK.
The iOS App handles the step value of “5” as seconds, NOT EXPECTED BEHAVIOUR.

  1. and 3) are expected to be functional equivalent.
    This is only true in BasicUI.

IMG_0528

Peter

New bug checklist

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant