I have the local roborock server working pretty well with an S8 Pro Ultra with a few issues.
I am unable to get the Roborock app to work. I have set up the mitm proxy per your instructions, and I can validate that it is working as I can see decrypted traffic in it's interface when I use some other apps such as Home Assistant app and the apps from some other IOT thing vendors. However submitting the request to get a verification code with the Roborock app just gives a message saying "Network unavailable". The only roborock related traffic I see in mitmproxy for roborock are a few DNS queries. It appears that the app on Android might employ certificate pinning. Have you tested the app functionality on an Android device?
The other issue that I had, which likely needs some better documentation, or will perhaps be resolved in future versions of the integration, was difficulty in getting the URL change in core.config_entries to stick. Edit the file, restart Home Assistant, back to defaults. Disable the integration, edit the file, enable the integration, back to default domains.
I ended up using the HA CLI to stop HA core, then I edited the file, then I started HA core back up (just `ha core stop/start from an SSH connection) and that finally got the updated domains to work.
So everything seems to be working, with the exception of the Roborock App, likely due to certificate pinning. I now have the vacuum fully firewalled off from the internet, great work!
I have the local roborock server working pretty well with an S8 Pro Ultra with a few issues.
I am unable to get the Roborock app to work. I have set up the mitm proxy per your instructions, and I can validate that it is working as I can see decrypted traffic in it's interface when I use some other apps such as Home Assistant app and the apps from some other IOT thing vendors. However submitting the request to get a verification code with the Roborock app just gives a message saying "Network unavailable". The only roborock related traffic I see in mitmproxy for roborock are a few DNS queries. It appears that the app on Android might employ certificate pinning. Have you tested the app functionality on an Android device?
The other issue that I had, which likely needs some better documentation, or will perhaps be resolved in future versions of the integration, was difficulty in getting the URL change in core.config_entries to stick. Edit the file, restart Home Assistant, back to defaults. Disable the integration, edit the file, enable the integration, back to default domains.
I ended up using the HA CLI to stop HA core, then I edited the file, then I started HA core back up (just `ha core stop/start from an SSH connection) and that finally got the updated domains to work.
So everything seems to be working, with the exception of the Roborock App, likely due to certificate pinning. I now have the vacuum fully firewalled off from the internet, great work!