Initially, I do not directly associate a peripheral with a Gladys user,
the OAuth2 Withings account is linked to 1 Withings user (some devices are multi-user)
when I made this service, multi-user did not exist yet, I thought in the long term to add this notion in a service evolution (perhaps by adding a user to a device like the room)
I have this: Body+ | Withings France
Bought about 10 years ago now… might help for some tests 
@euguuu I understand, but how do you retrieve/display the data?
Because the Withings scale returns the weight of each user in the house, so you end up with values from many people.
This is not where it will happen, maybe a new type of data in Gladys and open a « Health » API limit, which would take a variety of measurements on the user (weight, number of steps per day, etc.). In my opinion, this is really different from the values of the home sensors.
I think it’s important to ask these questions before developing, if you want to take the lead on writing functional specifications, why not 
In the doc I clearly state that the method to use is 1 client_id = 1 Withings user, so I only retrieve data from a single user for now
I thought that for a V1 it would allow initializing the service and the multi-user aspect could be seen later in a PR, not necessarily on Withings, the way you describe it is probably better but requires a lot of development and specification time as well
Ok @euguuu I’ll take a look at that and give you feedback in the PR
I don’t have a device to test it, but I really like the presentation of your device with the image.
Isn’t it possible to do this in a more global way in Gladys @pierre-gilles?
The image? Yes, everything is possible. However, it requires considerable work to find each model in high-quality photos, especially for services like Zigbee2mqtt, Z-Wave, or Philips Hue, which have hundreds or thousands of references. I’m not sure the time and maintenance investment would be worth it.
Wouldn’t it be possible for the user to have the option to add an image via an input?
Either we automate it when possible, or we let the user choose, right?
After all, it’s just a matter of personal preference (maybe it’s just me who cares ^^).
This is purely cosmetic for the configuration.
On the dashboard, we won’t see them anyway.
Personally, I don’t mind, but I don’t see the point other than adding a bit of color to Gladys
My personal opinion:
I think this will make our Gladys, so light, heavier, whether visually or in terms of disk weight.
We could leave this choice to the user as proposed by @spenceur, which I think would be the best understood.
The one who wants to do it, and looks for his own image himself.
But I’m afraid we’ll quickly get to the demand to put default images, because a SML-w9 device is the same for everyone… or almost, because I have it in white, but the image shows a black device… (Alex in annoying mode!!)
(yes @spenceur today I’m not your friend!!! 
)
It’s sad on my birthday too ;(
Happy birthday @spenceur! 
Happy birthday @spenceur, if you had said before, I would have been nicer
Happy birthday, if I had known, I would have seen 2 yellows!
By the way (I’m surprised Gladys didn’t wish me a happy birthday!), anyway, nothing to do with this service!
Hey hello everyone here!
I just came across this topic and it’s perfect because I recently got a wthings Body Cardio scale if you ever need help testing, let me know
Hello!
For info, there is a PR here:
The PR works great, then I gave feedback on the code that will be fixed by @euguuu
Hello there!
I did my little test locally with my Body Cardio, it works like a charm, great job @euguuu, I can’t wait for this integration to be released now
Hello,
Thank you for your feedback @Legw4nn
the PR has progressed and there have been quite a few changes, could you retest on your side?
Hello !!
I’m going to test this then (but only in a few days, I’m not at home right now).