Hello, I try to connect to my boiler with no success. I asked Duck.ai, here's what we've done (I asked it to make a summary):
I’m trying to set up ViCare on a Fairphone 5 running Ubuntu Touch, using Waydroid installed with Waydroid Helper. The boiler is a Viessmann Vitodens 050-W, type B0KA-25.
Waydroid is running (Session: RUNNING, Container: RUNNING, Vendor type: HALIUM_11). The original image did not have Google Services Framework. I ran sudo waydroid init -s GAPPS; after reporting “Already initialized,” it started downloading a GAPPS image. ViCare now launches in Waydroid.
The ViCare QR scanner closes immediately, so I entered the label details manually. To activate the boiler’s Wi-Fi, I have to hold OK for three seconds. Ubuntu Touch then detects the Viessmann network, and the Fairphone connects to it.
However, ViCare still displays this message:
“Could not establish a connection to your device. First hold the MENU button for 3 seconds until setup is closed. After this proceed to repeat the commissioning process.”
I followed those instructions and restarted commissioning, but the same error returned.
I also checked the network routes. On Ubuntu Touch:
default via 192.168.0.1 dev wlan0
192.168.0.0/24 dev wlan0 src 192.168.0.2
192.168.240.0/24 dev waydroid0 src 192.168.240.1
Waydroid initially only had a route to its local subnet:
192.168.240.0/24 dev eth0 src 192.168.240.112
I added a default route inside Waydroid:
ip route replace default via 192.168.240.1 dev eth0
Waydroid can now ping 192.168.0.1, but ViCare still shows the same error.
Is there a known way to make ViCare complete commissioning over the Viessmann Wi-Fi in Waydroid on Ubuntu Touch/Halium? Could this be a routing issue, or does ViCare require access to a real Android Wi-Fi interface that Waydroid does not provide?
That's it, thanks
gpatel-fr@forums.ubports.com 3 days ago
@UncleMeat
Hello
not sure that all your routing instructions were necessary in fact. I tried to ping a computer on my local network from the waydroid console and succeeded even when I created no special route.
As a wild guess, did you look at the app authorizations ?
Also, I think that it's possible to install tcpdump or tshark on UT using nix (crackle). This could help in pinpointing where the packets for your device are going (or are stopped).
UncleMeat@forums.ubports.com 1 day ago
@gpatel-fr I think I'm in the same situation as in this post:
https://forums.ubports.com/topic/9282/waydroid-simulated-wired-vs-wireless-connection
The app needs to connect via wifi but Waydroid simulates an ethernet connection.
I tried this:
I connected to the Viessmann boiler’s wifi network and I can ping it from a terminal in Waydroid
I set Waydroid’s persist.waydroid.fake_wifi property to ViCare’s Android package name, then restarted the Waydroid session. I verified that the property contains the correct package name, but ViCare still cannot connect.
The fake Wi‑Fi setting can make an app appear to be connected to wifi, but it does not turn Waydroid’s virtual Ethernet connection into a real wifi interface. ViCare may need wifi details or behavior that this setting does not provide.
Well, that's too bad. but thanks anyway.