New iOS release today
Curious, did it hose up the sorting of devices in your Room from whatever you had to alphabetically? Android v2.14 did that and it wonât let you sort anymore. I did let support know, but itâs all crickets over at ST right now.
Iâll update my iPad mini to check as well.
Mine are OK
Edit: I take that back. not allowing to reorder
Mine are sorted alphabetically and I canât sort them. Very inconvenient.
Looking at the IDE the devices are sorted correctly there. Somebody must have done an awesome job of coding on the mobile appsâŚ
Hey, @slagle it looks like itâs not just an Android issueâŚ
I reported this bug almost a week ago for the Android version.
Yup. Favorite for the room works, but rearranging does not.
Is anyone having issues with this latest update? Iâm using an iPhone X and it just crashes every time I start the app.
Tried uninstalling and reinstalling yet still it crashes while itâs trying to load the dashboard?
No crashes but experiencing slowness loading things here and there with a couple of timeouts.
I am on IOS and I just ordered my rooms. I opened a room and moved items around. Am I missing something?
rearranging and saving rooms works but when you open a room, rearrange items inside, click save, does it keep the order you rearranged them. For me, when I click save it goes back to alphabetical
OK you got it right it lets you move, but doesnât save when done.
The crashes seem to be isolated to iOS and custom device handlers.
We are looking into it but please reach out to support so we can track and follow up.
If iOS is crashing on 2.14.0, please check if you have an incorrect type set for a multiAttributeTile in a custom device handler. Here is an example of incorrect code
tiles {
multiAttributeTile(name:"contact", type: "contact", width: 3, height: 2, canChangeIcon: true){
tileAttribute ("device.contact", key: "PRIMARY_CONTROL") {
attributeState "open", label: '${name}', icon: "st.contact.contact.open", backgroundColor: "#ffa81e"
attributeState "closed", label: '${name}', icon: "st.contact.contact.closed", backgroundColor: "#79b821"
}
}
Changing the âtypeâ from âcontactâ to âgenericâ should resolve the issue. We are also looking into fixing the app so it doesnât crash with an incorrect type. On Android, this seems to manifest in a â?â tile.
Count me in as one with crashing iOS app. Iâve opened a support ticket.
Is it just the âcontactâ type that is incorrect and should be replaced? What âtypesâ are acceptable to use? Is there an easy way to determine which custom device handlers are affected?
âlightingâ, âthermostatâ, âmediaPlayerâ, and âgenericâ are the accepted types.
I donât know of a programatically way to check unfortunately. If you have an Android device, the app shouldnât crash but will show a â?â which would help narrow down which device handlers need updating.
Whatâs being done about the sorting issue?
I found the errant device handler. Added the correct code. The app is no longer crashing, but like the other reports, I also am unable to re-arrange my devices.
The issue with sorting has been documented internally but I donât have a timeline on a fix.
Iâm confused. âIt has been documentedâ sounds like past tense to me. Was this regression known before the app was released? If so, wouldnât it have been prudent to let people know it is broken and will return at some later date (assuming this release was important enough for some other reason to get out there now)?
Sorry for the confusion, past tense as in âI filed a bug reportâ. I am able to reproduce and reported the issue to our mobile developers.