Project Fi Phone Service For Real Estate

Jim Shepherd (360) 229-2235 thanks for the heads up!  I just did some research on this and it appears that the key gets confused when the phone switches between phone carriers (Sprint, T-Mobile, US Cellular and WIFI). When I get my new Pixel XL tomorrow, I will set it up on Project FI and see if I can figure out how to force it to update on WIFI only and that should solve the bug for now.  For some reason, SUPRA has never acknowledged updates via WIFI only even though I used it for about a year with the original iPAD and a few PDA's that they never supported because they couldn't out how to update it without being a phone.  I even posted a video on Supra's site of my using my iPAD a few years ago and they still never even acknowledged it would work!

I got my new phone and will update this regarding Supra after I test a few work arounds.  I admit I smiled when I read their response today about my previous work around (that might still work on Project Fi).  "Mr Paulson's fix for the iPAD (and other devices) is ingenious and I applaud him, but we really can't support it." 

If you want to try Project FI, I just learned of an invite code that you can enter that will go you (and me) each a $20 credit on your bill after you have been on the service for a month.  The code is:  https://g.co/fi/r/RNE2V4 

Supra won't support Google Fi, however mine has updated twice without problems so far (probably because it is updating via my wifi connection and therefore not getting confused by which cell phone carrier).  If I start to experience problems, I will update this.

The main thing I want it to do is just update automatically so I can use the lockbox.  I hope we can get other Google FI based Realtors that use SUPRA to share their feedback so we can trouble shoot any issues that might come up so we can work together to become our own tech support until Supra decides to support it. 

After working well for a few days, it glitched again updating with Supra.  It is easy to cure by logging in and getting an update code for the day, but is a step I would rather not have to take.  I just "unchecked" the "location tracking" to see if that helps.  Worse case scenerio, I can keep my old phone and have it update via WIFI and use it as my key. (until Supra programs a WIFI only update option or some other work around).

Jim Shepherd (360) 229-2235 , good news - SUCCESS (better bandaid anyway).

When your eKey fails to update:

1. On your phone, go to the Supra Web button (you might have to scroll to pay 2 of the Supra Display) and click it.
2. It will launch Supra Web and ask for your Key Serial Number:  (found on the about key tab on first screen but might be saved from previous time) & then PIN (your four digit code). It should default to your Association/MLS.
3. Click "Login"
4. Click "Authorization Code" (not "update code").  This resets the device on SUPRA's end.  You don't need to actually re-enter the code.
5. Go back to the SUPRA home screen and click "update Key".
6. Click Wireless update.
7. Lucky Number 7 here says that should have worked!
8. If not, you probably did these steps yesterday so you can't do them on your phone two days in a row.  Just log into Supra Web on your computer and click the quick link for "Authorization Code" which will reset your phone code at Supra.
9. Go back to your phone and repeat steps 5 and 6 above.
10. This completes my 10 step program for the work around.

Hope this helps!

SUPRA is still amazingly quite on this issue.  I just went to their Facebook page and they have not even posted to their page in 3 months.  I found a copy of their 2017 midyear report and they say they are "investigating" Google Project Fi's Nexus 6P and 5X phones; however, those are now obsolete.  Even the next generation of Pixel's is about to be replaced with a new line.  

One thing that appears to help in the meantime is to turn off other nearby Bluetooth devices (smart watches, car Bluetooth, etc.) so it doesn't get confused.  I am not sure if the Bluetooth issue is a factor on other services / devices.  

Please share your experiences and work arounds.

Two weeks after my post, SUPRA sent me an email follow up.  Still no fix.  Wouldn't a setting that allowed a WIFI only update keep the system from crashing due to it getting confused by different cell service providers?  If you take away the cellular componant, and used it like an Active Key, I would think that would be a near term band aid solution.  Thoughts?

FYI, Still having issues with Sprint/Tmobile confusing the authorization and bluetooth connecting to my vehicles instead of the lockbox sometimes, but at least I have figured out how to resolve them short term.