Andyw2100
Well-Known Member
I wrote to my contact, with some questions, and directed him to the last few pages of this thread. Below is his response.
--
Hi Andy – thank you for sharing the forum thread, and it helps us understand the Tesla community better. As I saw a couple of great questions, I will try to response in simple point forms to address as much as I can;
1. Foboshare is patently designed to allow vehicle borrowers to monitor tire pressures as if they are owners. When a borrower uses a borrowed Fobotired vehicle, it will serve no good purpose for the owner to track the pressure real time, while a borrower is driving 50 miles away. Secondly, most Foboshared accounts are related family members, or lived-in friends, and there is little likelihood to remove them once they are shared. And it can go up to a max of 100 per vehicle. An example in my family, we have 8 cars, and 6 family members with 10 smartphones. Hence each car is foboshared to 9 other phones, creating a total of 72 Fobosharing! Multiply that to all Fobotire/Plus/Bike users, and a 3 minutes real-time update, the Fobo server will be jammed pretty soon. All live updates will only happen when an owner-user/Foboshared user is within Bluetooth zone of the said vehicle. This is not to say that Foboshare cannot be real time, it can be done but we are not ready for the above mentioned consequences. It will disrupt traffic tremendously, especially for new installation, new Foboshare set-up, data gathering from users, etc. There is however a plan to send live update only when there is an ALERT! This sounds more meaningful without disrupting the server traffic. Stay tuned for this in the near future.
2. One of the forum commenter got it right when he says the Foboshare is like a master/slave set –up..This should easily explain why you cannot have two masters. A user cannot login into multiple phones simultaneously using the same account. This is for security reason, to prevent multiple login with stolen units or stolen phones. In the event of a lost/stolen phone, a valid user can relogin/activate his new phone, and the Fobo account will be automatically logged from his lost/stolen phone. From thence, everything will work as usual.
3. From the above features; you can see that there is no need to use 2 phones as a master. If a user have multiple phones, he/she can set up 1 master, and multiple slaves thru Foboshare, using different valid emails (they are free, by the way!). Corollary speaking, a user can change a master phone to a slave phone, and a slave phone to a master phone if desired. Logout from both phones, sign in the previous slave phone using the master account, and the previous master phone with the slave account. (note – both need email reactivation again for security reasons). Woola! The slave is now the master, and do a Foboshare to the ‘new’ slave.
4. Regarding a user having a deflated tire, the incar will alert in 3 minutes plus/minus depending on the timing of the incar scan, which is once every 3 minutes. The phone will not alert if the app is in the background, UNLESS it hit below 23 psi. In his case, the pressure was down to 13 psi, so both incar and phone will alert even if the app was in the background. The phone will always alert for any out-of-range pressure whenever the app is in the foreground. We do not expect users to keep app in the foreground all the time during driving, hence the incar should not be silenced for whatever reason. This is also another good reason to know that the incar wakes up everytime the vehicle starts moving, as it’s a simple and gentle reminder that the Fobotire system is now armed, and a running light across all the 4 leds means no pressure is out-of-range, leading to a peaceful and safer drive. Having said this, Fobotire does not allow an option to switch off the wake-up ‘music’ as the driver’s safety is heavily dependent on this functional reminder. This could be detrimental to users who have a hectic start of a day, and have the app in the background, and driving at 75mph with 24 psi, with an unknown nail in one of the tire, gooosh, we don’t want that to happen. An incar unit which refuses to wake up will point to several issues- a flat battery that was previously ignored, or a malfunction unit, etc. This will hilite a system issue that should be fixed, and that the user is aware of this until a solution is found.
Andy – I hope this clarifies all the issues in the thread.
--
