svanhoutte/wyze_garmin_sync

Not Updating Unless Container Restarted

esmoyer opened this issue ยท 6 comments

I have noticed in the last couple of weeks, that while the sync is running every 10 mins it is not finding/sending an update from Wyze to Garmin. The logs look fine and just say no new measurement. But if I restart the container, then it will find the new weight and upload it. Did something change? I completely re-did the setup and integration but am not sure if I am missing something.

I m looking into it

To give a little more detail, not sure if it will help but the logs reflect the new weight found but nothing done:

Yesterday's weight (224.67)

10/22/2023
4:40:05 PM
[<wyze_sdk.ScaleRecord: {'age': 36, 'bmi': 26.642067, 'bmr': 2172.8289, 'body_fat': 18.1, 'body_type': 6, 'body_vfr': 12, 'body_water': 60.0, 'bone_mineral': 5.2, 'device_id': 'JA.SC.2CAA8E4046F0', 'family_member_id': 'ca36e9c3bcd5f8c47b94a08a925e1e18', 'height': 195.0, 'id': '5783462743922789947', 'impedance': [436, 391, 373, 353], 'mac': '2CAA8E4046F0', 'measure_ts': 1697906180000, 'metabolic_age': 35, 'muscle': 78.3, 'occupation': 1, 'protein': 16.9, 'timezone': 'America/Chicago', 'user_id': 'ca36e9c3bcd5f8c47b94a08a925e1e18', 'weight': 224.67}>, <wyze_sdk.ScaleRecord: {'age': 36, 'bmi': 26.683893, 'bmr': 2173.4543, 'body_fat': 18.2, 'body_type': 6, 'body_vfr': 12, 'body_water': 59.9, 'bone_mineral': 5.2, 'device_id': 'JA.SC.2CAA8E4046F0', 'family_member_id': 'ca36e9c3bcd5f8c47b94a08a925e1e18', 'height': 195.0, 'id': '8261288414249504004', 'impedance': [427, 388, 369, 348], 'mac': '2CAA8E4046F0', 'measure_ts': 1697838042000, 'metabolic_age': 35, 'muscle': 78.3, 'occupation': 1, 'protein': 16.9, 'timezone': 'America/Chicago', 'user_id': 'ca36e9c3bcd5f8c47b94a08a925e1e18', 'weight': 225.03}>]

Today's weight (227.85)

10/22/2023
5:40:06 PM
[<wyze_sdk.ScaleRecord: {'age': 36, 'bmi': 27.01852, 'bmr': 2182.6763, 'body_fat': 18.8, 'body_type': 6, 'body_vfr': 12, 'body_water': 59.5, 'bone_mineral': 5.2, 'device_id': 'JA.SC.2CAA8E4046F0', 'family_member_id': 'ca36e9c3bcd5f8c47b94a08a925e1e18', 'height': 195.0, 'id': '7171545496594695930', 'impedance': [448, 398, 378, 358], 'mac': '2CAA8E4046F0', 'measure_ts': 1698010269000, 'metabolic_age': 35, 'muscle': 78.8, 'occupation': 1, 'protein': 16.7, 'timezone': 'America/Chicago', 'user_id': 'ca36e9c3bcd5f8c47b94a08a925e1e18', 'weight': 227.85}>, <wyze_sdk.ScaleRecord: {'age': 36, 'bmi': 26.642067, 'bmr': 2172.8289, 'body_fat': 18.1, 'body_type': 6, 'body_vfr': 12, 'body_water': 60.0, 'bone_mineral': 5.2, 'device_id': 'JA.SC.2CAA8E4046F0', 'family_member_id': 'ca36e9c3bcd5f8c47b94a08a925e1e18', 'height': 195.0, 'id': '5783462743922789947', 'impedance': [436, 391, 373, 353], 'mac': '2CAA8E4046F0', 'measure_ts': 1697906180000, 'metabolic_age': 35, 'muscle': 78.3, 'occupation': 1, 'protein': 16.9, 'timezone': 'America/Chicago', 'user_id': 'ca36e9c3bcd5f8c47b94a08a925e1e18', 'weight': 224.67}>]

thanks i think there is an issue with the way cron is lauching the python script. This is why it is working when you restart the container as the 1st execution is not managed by cron. Maybe it is related to the directory of the execution of the script. I ll fix that today or tomorrow. Thanks for pointing it out

No rush...Appreciate it

The docker is being recreated and pushed to docker hub. The issue was the path in the script.
Wait 15 min and update the container and give it a shot. It should work then.

That did it. Thanks again!!