When i try and open smart start it kills the app

🛎️ Get Help
1

My mobile app shuts when I try and go to the smart start QR reader
C8 Pro

2

Perhaps provide app version and platform, as well as the firmware version on your C8 Pro.

3

Platform version 2.4.3.156
Mobile app 2.4.3.156

4

That is probably not the mobile app version. It should be something like 2.1.45 (446).

To find it, open the mobile app on your phone, click the More (three horizontal lines) at the bottom right, then App Settings, and look at the App Version line.

1 Like
5

Yes you are right, 2.1.45 (446)

1 Like
6

Maybe try uninstalling the Mobile App on your phone and then reinstalling it? :man_shrugging:t2:

1 Like
7

I have uninstalled and no luck. Even tried on a second iPad and same thing.

8

Here is what it does. On both an iPad and iphone

9

Can I revert back to an older version of app?

10

Tagging @bobbyD and @bcopeland from the Hubitat Team. I am not all that familiar with Smart Start, so it probably makes more sense for those who are to hopefully step in and take a look.

11

I tried another newer ipad and downloaded the app and it does it as well.
Anyone else seeing this?

12

I am too -- I just tried and it happens to me (iPhone). It's something in the past couple weeks, because I added a SmartStart device fairly recently...

@moncho1138 -- is is possible that something in the 11/8 iOS app update is causing this SmartStart crash? I'm not sure about android - I don't have any to test with.

13

Does rolling back hub firmware version make a difference?

I'm on an internal build for iOS, and it works. But, the latest hub firmware update has some extra data points, so perhaps that's the culprit. I'll try to reproduce with someone else's phone.

Please tag me on the mobile app issues.

1 Like
14

How do you roll back firmware

15

Use Restore previous version in the diagnostics tool:

16

This worked
I had to roll back to
2.4.3.149

Thank You!

1 Like
17

Thanks for confirming that... I'm unfortunately not in a spot to try a rollback right now, so I'm glad you tested it out.

When you say "I had to roll back to 2.4.3.149", does that mean .149 was just the next most recent option you had, or did you try versions in between it and .156?

18

I was able to reproduce the issue. Don't know what the fix is going to be yet, but it's coming in the next build.

3 Likes
19

2.4.3.158 is out with the fix. Please let me know if it works (or keeps breaking).

3 Likes
20

.158 fixes it for me - hopefully same is true for OP.

Thanks Victor!

2 Likes