I’m in the market for a new scale. I’ve heard some wyze scales have issues with Pixel Phones. I don’t want to buy one just to not have it work.
Some things I would like:
Pet mode
Sync to Google Fit
Multiple Users
Works wirh Pixel 3 and Pixel 3a
Anyone have any insights or recommendations? I’d prefer to stay with Wyze so I don’t have yet another app. Lol
Thanks in advance!
I’ve been using a Scale S for a couple of years now and like it a lot. It’s my first Wyze scale, and I use it regularly with the Bluetooth connection to my Pixel 4a.
I’m not aware of problems with Wyze Scales and Google Pixel phones and haven’t experienced any connectivity problems with mine. I have read about battery life issues but also haven’t experienced those. I haven’t kept track of how long I go between battery replacements, but it’s in the range of several months.
One minor issue I have is that I use Pet Mode regularly (once a week for my guy and his adopted brother because of something I read years ago about how neutering affects the metabolism of male cats in particular), and almost every time I weigh two different cats the scale reports their weights as exactly the same. The two cats are similar in size, but I wouldn’t expect them to have exactly the same weights to the tenth of a pound consistently. I suspect that there’s some programming logic that’s fudging the numbers in attempts to appease the consumer—in other words, I think these things are designed to report the same weight with repeated weighing so that the numbers match and the consumer doesn’t think it’s a faulty scale because of the slightly different weights when measured back-to-back—rather than reporting actual weights with great precision. I haven’t attempted to test this against a different scale, however.
I don’t have any experience with Google Fit but see that it’s being discontinued (and also see that you’ve voted for this Wishlist item).
If I was shopping for a new scale now, I think I’d give the Scale Ultra a look, but that’s mostly because I’m intrigued by its Wi-Fi (in contrast with Bluetooth only) connectivity.
Dang I didn’t know Google fit was going away. Maybe I’ll wait to see if wyze will support the replacement.
Also, interesting about the pet function. Mine are a couple pounds different… But I definitely want to be able to track them separately.
I have a Pixel 5 and had a Pixel 8 Pro and now have a Pixel 9 Pro XL and I have had all the Wyze scales except for the Scale-S. They have worked pretty good for me. (I also have a Pixel 7 Pro, but it’s more of a test phone and was never my daily driver)
Though, keep in mind that Pixel has always had some Bluetooth issues from time to time, not Wyze specific. I think there is a bug with the Pixel Bluetooth programming. There have been times where I have had to either turn off my Bluetooth for a few seconds, then turn it back on and that will then let it pair with whatever it was refusing to connect to, or at worst, restart my phone and then it would connect to anything. A few times I have had to click on the Bluetooth settings, click “Pair new Device” and then find the device and click on it again to get it to connect as normal again. That’s not too painful considering how rare the issue is.
Again, the above isn’t just from Wyze scales though. I have that problem with lots of other various intermittently used Bluetooth non-Wyze smart devices from time to time with my Pixel, but at worst, restarting my phone has ALWAYS worked 100% of the time to make Bluetooth work normally with everything again. It is probably my biggest complaint about Pixel model phones and I’ve had that issues on all 3 pixel models, but it happens rarely and overall it’s not a dealbreaker compared to all the other awesome things that come with Pixel, so I keep buying them even though they have a weird Bluetooth bug that creeps up once in a blue moon. It’s definitely Pixel’s fault, but at least it always works after a restart and then manually clicking on the device at the worst.
I think since I got my first pixel model in 2020, I’ve only had to reboot my phone and click on the Wyze scale in the Bluetooth settings a handful of times, like 4-8 in the last 4-5 years? But restarting and clicking on it again always worked. I think it’s only happened to me once in the last year and a half and I use the scale every single day.
Actually, I have the Scale Ultra now, so I no longer connect the scale to my phone every day anyway. 95% of the time I just have the Scale Ultra connect through the WiFi instead, so now that’s not an issue anyway since it’s no longer connecting to Bluetooth, so the Pixel Bluetooth Flaw is not very relevant for me anymore.
Hope that helps. You’re right that having a pixel means some Bluetooth issues sometimes, but Pixel phones are still pretty awesome.
Yeah, like I said, I merely suspect that the Scale S and app are fudging the numbers a bit because these cats really are close in size, but I wouldn’t expect them to be exactly the same week after week. When a previous (smaller by a few pounds) cat lived here, the weights were always different, as expected. I haven’t tried pulling in a different scale for comparison, so I’m reporting only a guess based on my own limited observations and @carverofchoice’s commentary.
A cool thing about Pet Mode is that the app allows you to designate which pet you just weighed, so you can actually keep historical data for several pets and give each its own profile within the app, and that data is included if you do an export (where Wyze servers will generate an e-mail message to you with a workbook attachment).
Glad to see someone appreciate that post/explanation I did on scale anchoring. 
It really is great information.
That’s an example of a post I would add to a potential “Wiki” like @ssummerlin and I were talking about to explain to people why their scales may act in a certain way. It may not be a good thing to add to a “Manual” for devices, but it is the kind of stuff I like to share with people that can answer edge case questions that commonly come up and add some interesting valuable info to some people (even though others won’t care).
Seems there should be a way to add a Wiki in this discourse forum. Maybe you need extra permissions. I may google it later.
There is. Discourse forum software has a feature for it. I brought it up with Loki some time ago and he had some hesitancy about it for some reason. I don’t remember all of his rationales but I think it had something to do with Trust Level limitations and how they use some of those trust level limitations for Volunteers, and few people reach up to next highest trust level, so it wouldn’t be enabled for very many people anyway. Also, would it be a pain for Mods to keep up with every wiki change? What would a wiki do that wouldn’t work as either a forum post or a Wyze support article? Like, a Person could potentially write out an article or walkthrough about a feature that doesn’t exist yet and see if Brenda or someone else will add it to the support site.
IDK, I don’t even remember what the real considerations were, I’m just thinking off the top of my head why it may be seen as not worth it and why it was never enabled. I think it would be a kind of cool experiment, even if they limit it to “Power User TL3” (Trust Level 3 users). There aren’t a lot of us TL3 users, but many of the regulars qualify, including you, Antonius, TowelKingdon, ronl4625, StevenA, grapefruityoda, and all the volunteers and employees. I would say that is a fairly decent group that is unlikely to do something that would seriously violate the guidelines with access to build some community-sponsored Wiki pages for reference. There’s nobody in that list that I am concerned about…besides me 
(j/k).
If you do google it and learn any decent details, feel free to ask Loki about it in the forum feedback thread. He and Jason would have to decide whether to enable it. I think I casually asked about it a long time ago, but I didn’t press much. If someone else decides they would be interested in it, I would of course throw my support behind the idea if others think it might be of some value and think of good uses for it that aren’t better served simply by making a post or thread or support article instead. I do think it has potential and could be kind of fun to experiment with, but there may be valid reasons to avoid it. I just think limiting it to people who earn up to Trust Level 3 seems like a reasonable safety measure to start with. It’s hard to get up to TL3 without a long history of following the guidelines and having good behavior.
This is the default way to earn TL3 and the default privileges that come with it in Discourse Forum software:
Actually, that could be an issue, it looks like it says TL3 can START a wiki, but it can then be edited by TL1 user (anyone who has spent 10+ reading in the forum)…that could be a problem if Loki isn’t able to change that to only allow other TL3+ users to be able to edit the Wiki…unless we get to choose what level can edit it. Maybe we can select the Trust level limits for each post? IDK. that could be a deal breaker if TL1 can edit any wiki. Sometimes there are spammers or trolls or angry users who would sabotage ro change the entire narrative or a wiki because they’re emotional at the moment and want vengeance to their narrative. That would be a dealbreaker if you can’t limit TL1 from editing wikis. --I just asked some AI’s and they claim admins could change the default permission to a higher Trust level instead of the TL1 editing permission that is the default. So, I would certainly say limiting it to other TL3+ would be a good experiment with very little risk.
IMO, anyone who organically earns up to TL3 all on their own merits is basically an unofficial, honorary volunteer already. --There are several TL2’s that I think could make good volunteers too, I’m just saying TL3 is so rare to EARN that it’s impressive for the few of you who actually get it organically. It seems to basically mean you’ve been acting like a volunteer already and don’t get a bunch of people flagging your posts. 
Honestly, I’m kind of shocked @Antonius made the cut since the requirements say:
The stingey likes guy must have just barely made the cut on that requirement. 
I might need to make up for it and just flag him more often. 
Of course that solution would only last for 100 days 
Good information.
It’s too bad Mavens don’t have the power. I am sure moderators are quite busy with their job. I am a Level 3, but I would rather let Mavens control the creation and editing. I could see it becoming a hornet’s nest if everyone had editing rights.
Glad you brought it up. Maybe it would be too much to govern.
I have Lobbyist 
, 
and MFP. 
Wait… I’m a TL3?? When did that happen?
That’s what I said when I saw mine.
@Antonius & @towelkingdom I just recently noticed that about both of y’all, as well as some others in recent months. Congrats!
What I like about wikis is that they can be edited/amended when new information develops (for instance, when Wyze decides to add a new feature to a product line via an app or firmware update) instead of being historical or static, like a lot of other documents, so it seems like something like that might mollify some users who want documentation that’s more like a manual than what Wyze provides but still has the flexibility for growth when the content becomes outdated or inaccurate. On the other hand, the Forum already has the Tips & Tricks category that seems like a good place for user-created articles, and I personally think that Wyze should to a better job of maintaining its own accurate documentation in the Help Center.
If someone really wanted to, I guess that person could start an independent OWW—preferably with an apt logo to indicate user pain—and that should relatively easy to do (in a previous job, someone at our institution decided to use PBworks’s wiki product, and I got a lot of work done inside that; there are certainly other “free” options available), but I wouldn’t want to be responsible for maintaining it. Seems like the maintenance and policing could potentially be a weighty (trying to be at least tangentially relevant to the topic) task.
Again relevant to the topic, apparently this posted earlier today:
