You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This morning i received an e-mail where last weighing would be identical to the one before:
Logging shows that these duplicate values were actually retrieved from the scale:
Thu, 31 Mar 2016 07:23:56 INFO processIndication {'gender': 'male', 'age': XX, 'person': 2, 'valid': True, 'activity': 'normal', 'size': YYY}
Thu, 31 Mar 2016 07:23:56 INFO char_write_handle Sent cmd=char-write-req 0x23 026cb4fc56
Thu, 31 Mar 2016 07:23:56 INFO <module> Waiting for notifications for another 30 seconds
Thu, 31 Mar 2016 07:23:56 INFO receive_notification Received notification on handle=0x1b, value=0x1d321e00fe5eb4fc56881200ff020900000000
Thu, 31 Mar 2016 07:23:56 INFO processIndication {'timestamp': 1459401822, 'valid': True, 'weight': 77.3, 'person': 2}
Thu, 31 Mar 2016 07:23:56 INFO receive_notification Received notification on handle=0x1e, value=0x6f5eb4fc5602300ab5f082f26df11df0000000
Thu, 31 Mar 2016 07:23:56 INFO processIndication {'timestamp': 1459401822, 'tbw': 64.2, 'person': 2, 'valid': True, 'fat': 18.1, 'muscle': 36.5, 'kcal': 2608, 'bone': 2.9}
Thu, 31 Mar 2016 07:23:56 INFO receive_notification Received notification on handle=0x1b, value=0x1d321e00fe5eb4fc56881200ff020900000000
Thu, 31 Mar 2016 07:23:56 INFO processIndication {'timestamp': 1459401822, 'valid': True, 'weight': 77.3, 'person': 2}
Thu, 31 Mar 2016 07:23:56 INFO receive_notification Received notification on handle=0x1e, value=0x6f5eb4fc5602300ab5f082f26df11df0000000
Thu, 31 Mar 2016 07:23:56 INFO processIndication {'timestamp': 1459401822, 'tbw': 64.2, 'person': 2, 'valid': True, 'fat': 18.1, 'muscle': 36.5, 'kcal': 2608, 'bone': 2.9}
Thu, 31 Mar 2016 07:23:57 INFO receive_notification Received notification on handle=0x1b, value=0x1d141e00fe4c5ffb561d1300ff020900000000
Thu, 31 Mar 2016 07:23:57 INFO processIndication {'timestamp': 1459314508, 'valid': True, 'weight': 77.0, 'person': 2}
Thu, 31 Mar 2016 07:23:57 INFO receive_notification Received notification on handle=0x1e, value=0x6f4c5ffb56022a0ab4f083f26ef11df0000000
Thu, 31 Mar 2016 07:23:57 INFO processIndication {'timestamp': 1459314508, 'tbw': 64.3, 'person': 2, 'valid': True, 'fat': 18.0, 'muscle': 36.6, 'kcal': 2602, 'bone': 2.9}
Thu, 31 Mar 2016 07:23:57 INFO receive_notification Received notification on handle=0x1b, value=0x1de21d00fe8211fa56581300ff020900000000
Thu, 31 Mar 2016 07:23:57 INFO processIndication {'timestamp': 1459229058, 'valid': True, 'weight': 76.5, 'person': 2}
Thu, 31 Mar 2016 07:23:57 INFO receive_notification Received notification on handle=0x1e, value=0x6f8211fa56021f0ab2f084f26ff11df0000000
Need to run received data through a filter to delete values with duplicate timestamp. Would be interesting to see if this "double" data is stored in memory and will ultimately shift out of it.
As well move the sorting to BS440.py instead of repeating it in mail and domoticz.
The text was updated successfully, but these errors were encountered:
This morning i received an e-mail where last weighing would be identical to the one before:
Logging shows that these duplicate values were actually retrieved from the scale:
Need to run received data through a filter to delete values with duplicate timestamp. Would be interesting to see if this "double" data is stored in memory and will ultimately shift out of it.
As well move the sorting to BS440.py instead of repeating it in mail and domoticz.
The text was updated successfully, but these errors were encountered: