Unfortunately I do not… But I’ve been planning to, so am interested in helping to figure this out.
@imlac - you can definitely do this, and it’s a lot easier than setting up the zwave network - I’ve been using DuckDNS from the start of working with HA, and it’s very robust. Here is the HA doc for that. It’s pretty straightforward to set up: Duck DNS - Home Assistant (home-assistant.io). This one is a little more clear on the explanation of how it’s secured: Effortless encryption with Let’s Encrypt and DuckDNS - Home Assistant (home-assistant.io). Fortunately DuckDNS comes let’s encrypt features already, so you don’t need to install Let’s Encrypt. The DuckDNS add-on does it all now.
For the lock, here’s a good discussion of how to set everything up, along with some sensor template code others have written: Yale Zwave locks - Configuration - Home Assistant Community (home-assistant.io)
One of the main things I gleaned was that it has to be securely added to see the full functionality of the lock - otherwise it is in some kind of limited mode.
I’m not sure this helps you a lot, as you may be past all this - where are we in the process of getting it to work?