Setup is done, WLAN SSID is IoT. Homey´s WLAN SSID is homey, and for the sake of accuracy, Apple TV´s WLAN SSID is Fritzchen. They are all sharing the same IP range, though.
Hooking up the Deebot to Apple’s Home via Matter over WiFi is as easy as 1-2-3. However, I am failing to hook the robot up to Homey, both when connected to SSID IoT and SSID homey:
Using the adding via homey option fails entirely, it would find the device after entering the pairing code.
Using the option add via iOS I am presented a screen with all devices that can be added, can choose the Deebot, but this also fails when the connections is to be established…
Distance is around 3m, I already reduced it to 1.5. with no change.
Any helpful suggestions would be greatly appreciated.
So you have 3 different SSIDs for the same VLAN? It shouldn’t be an issue though. Do you have your phone on the IoT WLAN during pairing? This is important because your phone likely needs to reach the device when it’s connected to your IoT network.
I can’t get around my head around the meaning of this description, Philip.
SSID’s are not relevant
That is also my state of knowledge, but I usually provide the information which I believe others may ask for anyhow.
Homey 2016-2019 don’t have a user configurable AP SSID → you can’t change it to homey
homey is the name/SSID, which I was recommended to setup to in an attempt to overcome other network instabilities, e.g. with a Nuki door lock.
Why is Apple TV mentioned? Not relevant.
I very much respect you, and appreciate any help. Let me put it this way: If I try to analyze issues I always try to rule out hardware issues. The fact that Matter pairing with Apple TV works may provide some information in that regard.
Make sure to reset the robovac Matter connection.
What is SSID homey?
You’d use the SSID of your wifi router.
I deleted the pairing in the robovac app innumerable times.
The robovac is connected to IoT (also tried it when connected to SSID homey, see above).
Yes, iPhone was almost on any SSID during the pairing attempts (did multiple tries), except maybe for homey (which I regret now, but I am at work, so I can´t do anything about it now). But it was for sure on Fritzchen and IoT…
The strange thing is (or maybe it isn’t even that strange): The pair using iOS functionality shows the robovac in a list after all devices available…. but then again, this may be BT, right? After I select the robovac there and the actual pairing starts, after approximately 60s the “cannot pair“ error message appears. Again, connection it the Apple TV server as a matter hub works flawlessly.
