I am running the IOS app 3.1.42 (99) on my iPhone and iPad.
openHAB is 5.2 running on Windows.
I notice when I push the first time on an item af a mapping, the event gets transmitted and seen by openhab (DSL rule: Item CamReadBuiten received update).
The second and continued pressings do nor give an event. Pressing on another button from the same mapping, gets transmitted, the next presses not.
I continuesd testing now with the mappings-option. But the IOS app buttons do not follow the state of the item either. When I let the item expire to null or another value then the current pressed button, the button stays pressed and continued pressing do not generate an event sadly.
Any ideas to solve or workaround this in IOS app. Suggestions are very much appreciated.
Are you testing with the latest release version or TestFlight version? While it currently does not have that many additional commit, I’d suggest to do any further testing with the latest TestFlight version.
Any ideas to solve or workaround this in IOS app. Suggestions are very much appreciated.
Have to tried with adding on dummy mapping, which doesn’t actually do anything, but allows for selecting it to then be able yo re-select the intended segment without any intermediate other state? Likely not the nicest solution, and also depends on the space you have for your mappings in one row, but could be an option until the button grid has been implemented or re-selecting a single selection of the same segmented control might be addressed.
No I am not using the Testflight versions at this moment. I am happy my Apple Watch app works fine after a lot of issues an testing in the Tesflight versions.
I’’l switch back to Testflight when I have found the the courage to do so or when I see the Gridbuttons are implemented.
Hans, Thanks for the workaround suggestion with the dummy item. It’s an option.
This is expected behavior with Switch items, and it’s more visible with the newer iOS app. A Switch only sends a command when its state actually changes. When you press a mapped button the first time, the item changes state, so openHAB receives the event. Pressing the same mapping again sends the same command value, so there is no state change and no new event is generated.
Selection works because it always sends the selected value, even if it’s the same as before. That’s why repeated presses show up correctly. The same logic applies to Setpoint items. If you want every press to be handled, Selection is the right choice, or you need website to reset the item state after handling it in a rule.
I don’t think this answer is correct. The browser UI gives an event for every press on the same switch.
If someone don’t wants multiple events to trigger, they just change the trigger in the rule (received ON versus received update).
The best thing would be in my opinion to generate an event in the IOS UI at every press of a button, even multiple presses on the same button. Just like the browser UI.
I can confirm that this has been implemented in the current OpenHABSitemapViewController to SwiftUI migration and should therefor be included in one of the upcoming TestFlight versions in the nearish future
I tried the Testflight version 3.2.3 and indeed, every push on a mapping button generates an event as requested. It behavious now the same as the Webbrowser UI.
Thanks for this.
Sadly I notice my image item does not update dynamically anymore and had to return to the not Testflight version. I will raise a new issue for this.
but this is definitely in the works from what I’m seeing at