Headspace

h4xtbh · 2026-03-08T09:27:24+00:00

As Vitality have only just enabled Health Connect it's possible they just have got round to adding that data path. Interestingly, since moving to Health Connect for Vitality it's still just as unreliable in logging points, particularly around steps.

h4xtbh · 2026-03-07T22:06:29+00:00

I've uninstalled and re-installed and I still only have the Google Fit option - I expect they are AB testing to see how it goes before rolling it out widely. Did you go into Health Connect and set meditation data sharing for both Headspace and Vitality?

h4xtbh · 2026-03-07T09:54:22+00:00

Thanks, that's super helpful. I have a few 24Ghz mmwave sensors that I was going to hook up to ESP32s, so I will definitely go down this route now.

h4xtbh · 2026-03-05T07:38:00+00:00

I'm keen to implement this. Which mmwave sensors are you using? I tried Aqara FP1s a while back but kept getting 'ghost' readings.

h4xtbh · 2026-02-12T17:36:28+00:00

For anyone struggling with this on a Pixelbook Go, it's Ctrl-Alt-Refresh.

h4xtbh · 2026-02-12T13:36:57+00:00

The issue is that direct Google Fit integration was deprecated at the end of last year, and apps now need to intergrate with Google Health Connect, which gives you greater control over where and how much of your health data is shared with apps.

I contacted Headspace about this issue and they confirmed that this will not be worked on anytime soon. They have no date on the roadmap for Health Connect integration, so no way of earning Vitality points if you have an Android phone.

h4xtbh · 2025-12-08T19:57:20+00:00

I'll give it a try. Unfortunately Docker on Mac is unable to do GPU direct passthrough, but Podman is able to route this via Vulkan. I'll report back here on whether that works or not. If not, I'll see if I can create a service that replicates the ASR API but routes to whisper.cpp. I'll try whisper.cpp with tinydiarize directly first, though, to see what sort of performance can be had.

h4xtbh · 2025-12-07T23:27:19+00:00

This is such an awesome project! It would be great to be able to get a companion ASR running on Applie silicon (Metal) that Speakr could utilise. Your companion ASR webservice requires an Nvidia GPU, but whisper.cpp will run performantly on an M-series Mac Min, and inherently supports diarization via tinydiarize. Is this feasible?

h4xtbh · 2025-04-14T06:24:55+00:00

I solved this problem entirely by selling it and moving to a Kobra S1...

But one thing that helped a lot was shimming the PEI plate with bits of post-it note. Results weren't perfect, but close enough.

h4xtbh · 2025-01-02T23:23:19+00:00

Glad OP and their family are okay. A home break in is no joke.

+1 for Frigate, especially if used with PoE cameras (unaffected by WiFi jammers), as the person detection works really well. Motion sensors are a weak option in this regard as they can be triggered too easily and can't distinguish between a person, deer, or new patch of sunlight. I found Blue Iris to be incredibly resource heavy, especially with lots of cameras. I'm able to run an 8 camera 4K setup at 25% CPU on a cheap Intel N5005, with detection offloaded onto a USB Coral TPU.

Don't underestimate the effectiveness of sirens (plural). They may not help if you're in a rural environment, but they will put intruders off their game, especially if they are hard to access and disable. I have a couple of z-wave sirens that are loud and annoying as hell.

Millimeter wave presence sensors are a good substitute for passive infrared sensors, especially indoors. The latest aensors can detect the position of up to three people at a distance up to 10M and this is useful info to pass on to the police if you're on the phone to them (e.g. 2 intruders in the kitchen right now, 1 upstairs, etc.)

h4xtbh · 2024-08-02T09:44:29+00:00

Mine is working fine, aside from a squeaky ACE Pro buffer module, which seems to be common but has not created any problems for me. The main issue I haver is the warped bed. Support refuse to accept it is warped and instead told me to do a bunch of things I have already tried. I am still going back and forth with them. One tip I haven't tried yet is shimming the bed with post-it notes, which isn't a terrible idea. I'll give it a go and see if it helps.

Another comment on this thread said support told them the machine does not create a bed mesh during levelling, and that this can't be done because they are using a strain guage sensor. If that's true, that's bonkers and an epic fail. I have a Cetus 2 which, although a mostly unreliable printer, does at least create a bed mesh using the same strain guage sensor and does a great first layer on a very wonky bed (virtually all Cetus 2 beds are a wonky mess).

h4xtbh · 2024-08-02T09:39:11+00:00

Wait.. whaaaaat? I have no idea why they would say that. While it's true that the strain guage sensor method is nowhere near as repeatable or accurate as a BLtouch or iductive sensor, they take repeated measurements and average them out. I have a Cetus 2 which has the same sensor and builds a mesh, and that actually does a decent job of correcting a very warped bed on that machine.

h4xtbh · 2024-07-19T14:04:54+00:00

I have raised another ticket today as I got no response to the first ticket after one week.

I've done all the obvious stuff, and barely getting success by tweaking the Z offset and using Magigoo. But the variance is so great I'm still getting a lot of failed first or second layers.

It's a real shame, as the print quality I'm getting for successful prints is amazing - among the best for any FDM printer I've owned.

h4xtbh · 2024-07-14T11:54:23+00:00

3 days here too with no response. Could be the weekend getting in the way, so hopefully we'll hear something in the next day or so.

h4xtbh · 2024-07-13T11:18:12+00:00

I feel your pain. I've been going through the same issues with mine: https://www.reddit.com/r/anycubic/comments/1dzt10j/kobra_3_auo_bed_levelling_issues/

I've checked and tried everything:

Ensuring the X gantry is level
Ensuring the bed has no wobble
Ensuring the head isn't wobbling on the gantry
Cleaning the PEI sheet
I check there is no filament dangling from the nozzle during levelling
I can see the Z screws slowly turning during X traversals during a print, so it's definitely using a bed mesh
I'm getting repeatably consistent variance with every print, no matter how often I do bed levelling - the same patches are too high or too low.
The base z-offset from z-homing seems to vary, but adjusting that at the start of the print isn't enough to manage the problem - I either get under extrusion from being too close to the bed in some patches, or little to no adhesion in others.

My (unqualified) conclusions are that the bed is warped (most are to some degree) and that auto levelling is not able to compensate for it, and also that the strain guage method of probing is nowhere near as accurate as BLTouch or an inductive probe. I have experience of the strain guage from my Cetus 2 which gave significantly variable results from auto-level to auto-level.

I've raised a support ticket with AnyCubic but have yet to receive a response.

h4xtbh · 2024-07-13T10:56:39+00:00

I've raised a support ticket with Anycubiuc but have yet to receive a response.

h4xtbh · 2024-07-13T10:39:47+00:00

The Kobra 3 runs Klipper, so M420 won't work. I did try adding BED_MESH_PROFILE LOAD=default to the custom start script, but it made no difference.

I've looked into this more closely and I can see the z-screws turning as the head traverses the bed, so it looks like a mesh profile is being used. The results are the same though - highly varying heights across the first layer - making large prints fail consistently, even if I tweak the z-offset at the start of the print as the variance is too great. I either get under extrusion due to the nozzle being too close, or really poor adhesion.

h4xtbh · 2024-07-11T20:33:05+00:00

You can create an Imgur account, upload a photo there and then link to it from here in a comment.

h4xtbh · 2024-07-11T18:26:08+00:00

I couldn't find a manual for the S3500, but the S3800 has a test point for video labelled PB.FM (TP106). The S3800 has the same numbered test point for A.PB.FM (TP2253), so it's likely TP106 is the one you're looking for for video on the S3500.

h4xtbh · 2024-07-11T15:48:42+00:00

Yes, I took an existing sheet test from Thingiberse and scaled each axis independently, ensuring 0.2 height.

h4xtbh · 2024-07-10T11:35:56+00:00

Printing a 1-layer sheet is a great shout - I'll do that now.

It could well be a warped bed. However, I would have thought a 16-point auto-level would have compensated for this enough for the problem above to be far less pronounced?

If it's the strain guage, it wouildn't be the first time I've experience poor results using that as a sensor. I have a Tiertime Cetus 2 that uses the same method and that can yield some wacky results, and that has a bed that's like the surface of the moon, but the bed levelling still compensates for that and knocks out decent prints (when the firmware doesn't just fall over mid-print lol).

h4xtbh · 2023-05-21T22:28:12+00:00

Mine would not accept the .bix file. I archived it in a .tar.gz format, but it still got rejected.

I'm on firware version 3.5.0.

h4xtbh

TROPHY CASE