Installation FQDN subdomain feedback

[Wylan]

Hey,

First off awesome project! Being able to have my vacuum totally local is just awesome!

Over the weekend I successfully moved our Saros 10R over to the local server using the Home Assistant addon & the web gui. I ran into one little issue that took me a little while to debug and I figured might be useful to document in case anyone else.

In my network I run different VLANs for my home devices, work, IOT, etc. and each one of them has their own subdomain too just to keep things organized so something like:

device.home.example.com 
device.work.example.com
device.iot.example.com
etc.

When it came time to pick my FQDN for the Roborock server I naturally picked api-roborock.iot.example.com. And then waited for the robot to connect to wifi and start sending the onboarding packets... and waited... and waited 🤣. After trying different certificates as other people had, and re-attempting the process a few times via the web GUI and the CLI.

I eventually decided to just do api-roborock.example.com instead and it worked instantly, two attempts and the public key was found 🎉

So I guess the TLDR here is it might be useful to mention in the installation docs that multi level subdomains like api-roborock.iot.example.com won't work you really need to pick something like api-roborock.example.com.

Again, really appreciate all the hard work you've done on this!

[Lash-L]

Very interesting... I'm not sure what the reasoning for the vac rejecting it would be. But that is good to know and I will add to the docs!

[Lash-L]

Figured it out! There is a max length of 32 characters for the full region we inject. It's nothing to do with subdomains but rather the length.

[Wylan]

Ahh interesting! Good to know, glad that this was helpful 😄