I’m am please to announce we have pushed out version 2.0 of our mobile applications.
Our Android client had the most activity with many people contributing. I would especially like to thank @mueller-ma for stepping up with not only code contributions, but reviewing and managing PR’s, tagging issues and other needed house keeping. I would also like to thank maniac103, lolodomo , FlorianSW and boc-tothefuture (github handles) for their contributions and help getting 2.0 out the door! For a full list of changes see https://github.com/openhab/openhab.android/blob/master/CHANGELOG.md .
The IOS client was updated to work with the latest version of IOS, the iPhone X as well as other small fixes.
Both clients now have our updated logos and graphics.
@digitaldan Thanks for the new release! Is it a known issue that SVG icons are flashing while updates are being processed on Android? Now it is certainly an improvement because previously I didn’t see any SVG icons at all! I’m on a Google Pixel with Android 8.1.0.
Thanks all for the work on the Android app - I’m in the process of getting stuff set up, and graphs consistently stopped working in the previous version, which was making it difficult! Now, however - seems to be working really nicely!
Is there a way to have a setpoint item behave as it used to in previous versions? I have setpoints for a few rooms that control volume of the audio zone for that room. Previously I could tap the plus and minus buttons until the volume was sufficient. My sitemap uses a setpoint with a minimum of 0 and a maximum of 70 (so the children can’t really annoy the neighbours) with a step size of 5. Now, I need to go through the tap-to-bring-up-the-setpoint-choices, swipe-to-choose-the-setpoint-value, then tap to set it. If the volume I choose isn’t quite right I have to do that all over again. The plus and minus buttons were perfect for this use case.
Alternatively, is there another way I can replicate the plus and minus button functionality?
The rest of the changes look awesome, many thanks for all the hard work!
+1 to what @higgers is saying. I’m using setpoint item to control the speed of my air ventilation unit so this new control mechanism suits much more better for this kind of ‘selection’. But when you are controlling volume, old style was much more better for that use case. Worked nicely as a traditional remote controller.
@mueller-ma I totally understand it’s advantages and I’m not suggesting the behaviour be reverted and the advantages be lost to everyone. I’m asking if there’s a way that the old behaviour can be used if needed. As I described in my post yesterday the new system doesn’t work well for my use case and as @gitMiguel described there are situations where the new system is an improvement (ventilation unit speed) and situations where it’s a regression in functionality (volume control).
If users could choose which behaviour suits their situation that would be perfect.
Ah, I didn’t notice that change… and it now works differently to how BasicUI works, which isn’t great if you’ve got people using both…
I’d certainly like the option to select which style to use on an item-by-item basis - do we need a different item type other than just “SetPoint” to differentiate between the two? (I know that this means it’ll need support from as far back up the chain as ESH to do so)
Thank you very much for these great works.
Excellent app (and excellent openHAB).
I found two bugs in 2.0 Android version:
Sending a voice command by widget throws error. Voice command is successfully sent by remote connection (myopenhab) but app closes showing an error. When local connection to openHAB is available (LAN), app closes showing an error, and no voice command is sent to openHAB.
Rollershutter item icon does not change with height state, as it has always done in previous versions (Classic UI web interface icon shows height state properly).
The same problem I also face much time when I use the android app, After that, I take a help of Avast Support to solve out the problem is it possible refer me to a page related to this topic from this site?
I’m on a Google Pixel with Android 8.1.0.
