-
-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
10 is an unsupported value for <enum 'MeasurementAttribution'> #86
Comments
Thanks for creating this issue. Can you maybe explain a bit more on what kind of measurements this is? Withings marks every measurement with an attribution to say how measurements are attributed to the user. For example, someone stood on the scale and withings can't really recognize if you are the one on the scale or someone else. There's also a different value for measurements that are not 100% sure but got confirmed in the app. So if you can maybe tell a bit more about how this can be reproduced, I can also try. Last time I checked the API docs, this value wasn't there. I will double check later. |
I found this in my logs: Protokolldetails (WARNUNG) Logger: aiowithings I will try to restart to see if I can find out more. |
Yes, I receive this message at every restart: Logger: aiowithings 10 is an unsupported value for <enum 'MeasurementAttribution'>, please report this at https://github.com/joostlek/python-withings/issues This below is the diagnostic information of the integration. I switched on the debugging logging and will report tomorrow. { |
Yes yes, I know this is happening, but can you maybe tell about how this measurement got added to withings? What device do you use? Did you have to do anything special? |
The measuregrp attrib 10 comes with the meastype 91 = "Pulse Wave Velocity". |
I have a Body Cardio C2 scale and a sleep mat and get same error message in log. |
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. |
Oh whoops, let me mark it with no-stale |
Also have the same issue, Sleep Analyzer and Body Cardio scale. |
Well you found it, thats what matters ;-) Thanks for looking into it.. |
no I did not find it haha, I need to know what 10 means, but they don't update their docs on time |
I'll join the party... Getting these on reboot: I have multiple scales, including the newest one with the ECG, both blood pressure cuffs, the pulse Ox sensor and thermometer. Scale is the only one I use with any frequency. I turned on debug logging and reloaded and see this: |
Oh but those are different, can you open a new issue? Also include what measurements you see in the app. |
@joostlek , I have the same issue with "10 is an unsupported value". Withings has updated their API docu and "10" is now listed as "Systolic Blodd Pressure": https://developer.withings.com/api-reference/#tag/measure/operation/measure-getmeas |
I just installed the withings integration to HA. I can see the following in the log: Logger: aiowithings 10 is an unsupported value for <enum 'MeasurementAttribution'>, please report this at https://github.com/joostlek/python-withings/issues I have Body Cardio (sw version 2231) and Body Smart (1071) scales. I understand the problem was raised by BodyCardio scale as I have not taken measurements with Body Smart when having the integration active. |
Finally found some time to send an email to Withings. Will follow up. |
Did you get an answer? |
Haven't seen any :/ |
As of this morning I am also seeing "226 is an unsupported value for <enum 'MeasurementType'>", using a Body Smart device. These errors started showing up at approximately 0830 BST, having been using the device for months. |
That's a different issue, is already fixed |
Getting 4 copies of this error every 10 minutes in the logs. Enabled debug logging to capture whatever additional details I could:
|
Problem/Motivation
Expected behavior
Actual behavior
Steps to reproduce
The text was updated successfully, but these errors were encountered: