-
Notifications
You must be signed in to change notification settings - Fork 28
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
feat: add logic for parsing sleep data and viz panels #12
Conversation
I'm interested in this as well! 🤩 |
I'll try to finalise this first iteration this weekend ! But if you have a newer watch that does have those metrics, would you be willing to help out ? I'll see how we could export the fields names while ditching the actual metric for the sake of privacy. that would be very cool to expose all those new metrics as well ! |
I have an Apple Watch SE, and I would be willing to share and validate a sample of my sleep data with you! |
yay! awesome! |
@MarshalX yeah finally 😅. I'll test it out this week on other exports, and the next stable version with this feature should land next sunday. If you want to try it beforehand you can use the |
@k0rventen i tried for the first time. rolling tag. i cant find anything about debug mode of debug logging so that's all what i can provide throws after "Inserted 1760000 records" apple-health-grafana-ingester-1 | Traceback (most recent call last):
apple-health-grafana-ingester-1 | File "//app.py", line 189, in <module>
apple-health-grafana-ingester-1 | process_health_data(client)
apple-health-grafana-ingester-1 | File "//app.py", line 162, in process_health_data
apple-health-grafana-ingester-1 | client.write_points(records, time_precision="s")
apple-health-grafana-ingester-1 | File "/usr/local/lib/python3.12/site-packages/influxdb/client.py", line 603, in write_points
apple-health-grafana-ingester-1 | return self._write_points(points=points,
apple-health-grafana-ingester-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
apple-health-grafana-ingester-1 | File "/usr/local/lib/python3.12/site-packages/influxdb/client.py", line 681, in _write_points
apple-health-grafana-ingester-1 | self.write(
apple-health-grafana-ingester-1 | File "/usr/local/lib/python3.12/site-packages/influxdb/client.py", line 413, in write
apple-health-grafana-ingester-1 | self.request(
apple-health-grafana-ingester-1 | File "/usr/local/lib/python3.12/site-packages/influxdb/client.py", line 378, in request
apple-health-grafana-ingester-1 | raise InfluxDBClientError(err_msg, response.status_code)
apple-health-grafana-ingester-1 | influxdb.exceptions.InfluxDBClientError: 413: {"error":"Request Entity Too Large"} |
@k0rventen should i try decrease the batch from 10k to like 5k? is it safe to run the ingester a second time without dropping db? upd. see "drop_database" upd5. |
@k0rventen more info about the bug
well... i think batching is broken now. because at least and i hope that upd. yeah, that was the problem. sent a fix #23 |
that's funny, because that's the exact bug I encountered once (and why I wanted to test more before releasing a new version 🐛 ) If there are other problems related to this feature I'll open a dedicated issue, rather than bumping a closed PR 😉 |
No description provided.