At the moment, if you activate “remove unit”, the value is being rounded to maximum one decimal. So a “0.08578 °C” would become “0.01”. If “remove unit” is not activated, “0.08578 °C” should be displayed in the widget. Or did I understand you wrong?
Could you please describe what you mean with configure access? The settings screen or the possibility to add Collections, add Items and so on? Or the configuration of a widget on your homescreen (which Collections should be shon in that widget)?
thanks for the info. The setting of “remove unit” didn’t matter
5.13 → 5.1
so values are some how rounded to the first number after the comma. The values are all plain numbers.
If a tap on the widget, the configuration screen opens: collections > add item …
I think configuration and widget usage should be separated.
Perhaps just another small thing: All my power values are in kW. As “Number:Power” is in “W” I have to use “Number” as type for theses values. Is there a way to even display the unit “kW” in the widget?
I checked to code and now I got it. Yes, you are right. If openHAB just returns a number without a unit, the number is rounded to one decimal (sometimes it’s hard to remember decisions, you made three months ago … ).
I’ll think up a better solution!
At the moment, a tap on the widget leads you to the section of the app, where you left it. I think, that I have to provide a section in the app to link to on tapping. But I’m not 100% sure, I’ll check that. If I have to: in what section of the app you’d like to land after a tap on the widget?
You can already achieve something like this with the current version of HABly - not the “no action” but the “another collection”. Just create a stack of HABly widgets (https://support.apple.com/en-us/HT207122). You can now swipe through these single widgets.
Although there’s a lot I don’t like about the way Apple has implemented Widgets in iOS, the Widget Stacks are in my opinion a great way to have access to a lot of Widgets without cluttering your screen.
I implemented Anne’s suggestion not to round an Item
value to one decimal by default, but letting the you
choose if, and to how many decimals the value should be rounded.
To make this happen, HABly needs to migrate the existing data on
the first startup of the new version.
I also fixed a rare issue: In some instances, when HABly couldn’t connect to openHAB, Collections were being misplaced, causing HABly to lose track of them. I’ve made improvements to ensure your Collections stay secure, even when there are temporary internet disruptions.
While I’ve tested the update on multiple devices and everything
looks great, I want to be absolutely certain that it works seamlessly
for everyone. This is where you come in! By testing the update on your
device, you help me catch any potential quirks or issues I might have
How to Dive In:
Install Apple’s TestFlight app (if you haven’t already).
I just discovered this App, thanks a lot for sharing this!
I will play a bit more with the app in the next few days but I discovered a problem on my first try:
I realised that the way the widget shows date values in a list is not really ideal: it shows the complete date and time including milliseconds which does not really make sense. Would be great to have the precision configurable and the display match the locale of the device. Alternatively it would be great to use the display state configured in openHAB.
Tbh I never thought about date or time since I don’t use it. I’ll add handling dates and time to my improvements list.
Thanks for your feedback and suggestion, Thomas! If you spot more things that could use a tweak or have ideas for new features, don’t hesitate to reach out.
Looks like a great app. However, I’m getting a url error on the local server. Copy/paste the configured url from the app to a browser shows me the UI Overview page I configured on OpenHab.
Do they conflict?
One other thing I noticed when using the app: for me it’s kind of hard to find matching symbols for all switches of a bigger switch widget. I think it would be great to have more symbols at hand or/and have a widget that shows text next to the buttons, e.g. a list widget with actual buttons instead of just showing the state.
Actually when thinking about it this is a more general problem: for example if I have three different lamps in the living room it will probably always be hard to find matching symbols for every one of them. Or if I have different hallways in the same building. So even if you add more symbols it probably would not be a suitable solution for every situation. So probably the named buttons would be a better solution for these situations.