Anova Nano - DataUpdateCoordinator questions

[peak hazel]

I've been trying (unsuccessfully) to create an integration for the Anova Nano device. Now that Anova has deprecated App support for it, I want to give it another try. I've written an API for it, but I'm struggling a lot with the home assistant integration. There's a few things that seem a bit special when it comes to the Anova Nano.

• No pairing required
• Communications via protobuf
• It does not send updates via advertisements. Instead you have to request the data each time.

Looking at the docs, I should be using a standard DataUpdateCoordinator.

If your device only communicates with an active Bluetooth connection and does not use Bluetooth advertisements:
I'm wondering if anyone knows an example of a bluetooth integration using the DataUpdateCoordinator?

Any help or pointers would be appreciated!

[jade hill]

I suggest asking in https://discord.com/channels/330944238910963714/1257019582112334014

[cyan star]

Did you have any luck? I just bought an Anova Mini

[silver fog]

I also bought a Mini (yay $20 sous vide), but no luck getting it into HASS either. I'm using an ESP-WROOM-32 as a Bluetooth proxy, and did try the Anova climate esp32 integration but no luck there (the mini seems to use a similar protocol to the nano and isn't the same plain-text that the esp32 does). I'm also trying mcolyer's Anova Nano BLE HACS repo but no joy there either; it's showing no_device_found (presumably because it's looking for a nano on a bluetooth stick as a client, and not a mini on a bluetooth proxy).

I tried to update the SERVICE_UUID in the custom_components/anova_nano/const.py file to the one discovered by my bluetooth proxy but also, no joy.

Infuriatingly, the mini HAS a wifi board onboard, but won't connect to the wifi without a subscription in the app.