The problem is likely nothing that you’re doing wrong. There’s some massive issues with the Voice PE that Nabu Casa and developers refuse to fix. I spent a crazy amount of time debugging this and the likely culprit is probably the fact that you’re using local Let’s Encrypt certs - which breaks the product and it’s usefulness.
I’ve told dozens of people: DO NOT BUY A VOICE PE. Nabu Casa has stated, over and over, that you should just run an insecure network if you want to use it. The easiest way to tell that that is BS is to send the device back.
And even though there are ways to workaround this, nobody at the company is working on a fix. They’ve basically just continued the trope of: stop using Let’s Encrypt / valid certs / proper security on your internal network. That’s not going to happen for a lot of us - so the right response is send the Voice PE back to them and tell them it’s not supported by their own software correctly - also tell them to update the VPE FAQ as it does not say anything about TLS being unsupported.
Also… They refuse to fix a bug wherein the PE will send everything through Nabu Casa Cloud by default, even when it should not be. And this is why you can’t get the device registered correctly.
If you want a workaround - here’s my fix (still works today for me):
And if you want to see the issue of the Voice PE not preferring the “internal” URL please see this:
Please comment and tag people that you, as well, are having issues that Nabu Casa refuses to support.