Type of change

Type A:

• [x] Bug fix (non-breaking change which fixes an issue)
• [x] UI Feature
• [ ] Refactor/Code Cleanup

Description (Type A)

Fixed manufacturer and model TextView not being displayed entirely if too long, made discovered_instance_list_item_layout responsive Original |    New    :-------------------------:|:-------------------------: |

Added webserver opening in Custom Tabs (if supported, see https://developer.chrome.com/docs/android/custom-tabs/)

Since some of my "IoT" stuff is in a separated subnet and passes a router, zeroconf with UDP broadcasts doesn't really work. I'd need to enter the IP manually to use this app. I think it could be integrated as some sort of "advanced" option.

To keep dependencies up-to-date

I started doing this for Catima recently, it works nicely.

If wanted I could also set

    allowed_updates:
      - match:
          update_type: "security"

to only allow security updates, but not sure how well that works with gradle.

What do you think, @Hypfer?

Valetudo Companion will crash here if no browser (or other app) is present to handle http::

https://github.com/Hypfer/valetudo-companion/blob/f745b08ae29c91f549355aab8335568561934286/app/src/main/java/cloud/valetudo/companion/MainActivity.kt#L57-L62

I assume it will require something like this: https://developer.android.com/training/basics/intents/sending#no-app-available

There should probably be a descriptive error and a copyable-URL should be shown for manual use.

I have my robot in an isolated subnet which does not allow bonjour. I know the IP I want to add a robot by simply hardcosong it's IP instead of relying on auto discovery.

Valetudo Companion currently targets SDK level 30 (Android 11).

SDK level 33 (Android 13) introduces new permissions for scanning for Wi-Fi access points: NEARBY_WIFI_DEVICES. ACCESS_FINE_LOCATION is no longer necessary. See https://developer.android.com/about/versions/13/behavior-changes-13#nearby-wifi-devices-permission for more info.

Preferably, updating the targetSdk should be done before November 2022 so that releasing updates onto Google Play isn't blocked. It should definitely be done before November 2023 so the app doesn't disappear from Google Play: https://support.google.com/googleplay/android-developer/answer/11926878

Hi, I'm new to valetudo and robots. I installed valetudo on my L10Pro. I can connect to robots own wifi network and ssh into it. But when I started valetudo on my phone (tried both FDroid and GPlay), I chose 'Use App', selected robots wifi network and connected. The connection is confirmed by voice of robot. But then I only see on my phone: 'scan for valetudo / No Valetudo found on this network'. What I'm doing wrong? I also tried to connect via browser to IP of robot, but there is no webserver online. Via nmap I verified all open ports on robot:

$ nmap -p- -sV --version-all --reason -v 192.168.5.1
Starting Nmap 7.80 ( https://nmap.org ) at 2021-12-26 11:58 CET
NSE: Loaded 45 scripts for scanning.
Initiating Ping Scan at 11:58
Scanning 192.168.5.1 [2 ports]
Completed Ping Scan at 11:58, 0.00s elapsed (1 total hosts)
Initiating Parallel DNS resolution of 1 host. at 11:58
Completed Parallel DNS resolution of 1 host. at 11:58, 0.03s elapsed
Initiating Connect Scan at 11:58
Scanning _gateway (192.168.5.1) [65535 ports]
Discovered open port 53/tcp on 192.168.5.1
Discovered open port 22/tcp on 192.168.5.1
Completed Connect Scan at 11:58, 4.23s elapsed (65535 total ports)
Initiating Service scan at 11:58
Scanning 2 services on _gateway (192.168.5.1)
Completed Service scan at 11:58, 6.01s elapsed (2 services on 1 host)
NSE: Script scanning 192.168.5.1.
Initiating NSE at 11:58
Completed NSE at 11:58, 0.02s elapsed
Initiating NSE at 11:58
Completed NSE at 11:58, 0.01s elapsed
Nmap scan report for _gateway (192.168.5.1)
Host is up, received conn-refused (0.013s latency).
Not shown: 65533 closed ports
Reason: 65533 conn-refused
PORT   STATE SERVICE REASON  VERSION
22/tcp open  ssh     syn-ack Dropbear sshd 2020.81 (protocol 2.0)
53/tcp open  domain  syn-ack dnsmasq 2.80
Service Info: OS: Linux; CPE: cpe:/o:linux:linux_kernel

Read data files from: /usr/bin/../share/nmap
Service detection performed. Please report any incorrect results at https://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 10.67 seconds


$ ssh [email protected]
--------------------------------------------------------------
    _   _   _                        _     _                  
   / \ | |_| |__   ___ _ __   __ _  | |   (_)_ __  _   ___  __
  / _ \| __| '_ \ / _ \ '_ \ / _` | | |   | | '_ \| | | \ \/ /
 / ___ \ |_| | | |  __/ | | | (_| | | |___| | | | | |_| |>  < 
/_/   \_\__|_| |_|\___|_| |_|\__,_| |_____|_|_| |_|\__,_/_/\_\
                                                              
--------------------------------------------------------------
 Athena Linux (p2029_release)
--------------------------------------------------------------

build with dustbuilder (https://builder.dontvacuum.me)
Sat 25 Dec 2021 04:24:04 PM UTC
1105
[root@p2029_release:~]# 

I think there should be a port open for some kind of webservice to connect companion app? Did I miss something during installation? Thanks in advance Tom

As

• connecting to the robots AP
• disabling mobile data
• telling Android that you really want to be connected to that AP even though it has no internet
• figuring out the correct IP for the robot
• typing http://192.168.8.1 into the browser on your phone
• hoping it doesn't redirect you to https://192.168.8.1
• Ignoring the fact that Valetudo polling the robots state doesn't work
• Navigating to Settings > Wifi
• Entering the Credentials

isn't exactly straightforward, the idea here would be to let this app do most of this.

Namely

• Look for the gateway IP of the wifi the phone is connected to
• Check if there's a Valetudo responding on said IP
• Display a found unprovisioned Valetudo instance
• Have some kind of basic form where you type in SSID + Password which then calls the Valetudo REST API for the WifiConfigurationCapability
• Done

Further enhancements could include

• Connecting to the robots AP via the App
• Maybe scanning for 2.4ghz wifi networks to offer some autocomplete

Note that installing a rooted firmware is out of scope for this feature. This assumes that there already is a Robot with Valetudo on it which isn't connected to any wifi network just yet.

Entering this wizard(?) could be done with like a plus sign on the top right of the main screen or something like that.

ActivityCompat.shouldShowRequestPermissionRationale only returns true when Android decides that the user needs extra explanation to understand why they need to grant the permission. It shouldn't be used as a check for "should we ask for the permission".

valetudo-companion finds my fresh flashed Roborock S5 ("Found unprovisioned robot: Roborock S5"). But after I filled in SSID and Password from the wifi the S5 should use, I always get the message "Wifi Provisioning failed with code 500" after tipping on "CONNECT" and nothing happens.

I'm using valetudo-companion 2022.03.0 from f-droid.org.

Is there a possibility to debug this issue?

Feel free to edit the short and full description.

Please note short description can only be up to 80 characters.

When you make a new release, please add a 2.txt to the changelog directory before tagging :)