[Feature]: Add more bluetooth type devices

[Skied]

Expected behavior

Add more bluetooth type devices like "Input" (Keyboard, mouse, gamepads, etc)

Example of extra devices:

other

No response

[SARDONYX-sard]

Yes. This is why I added 'HeadSet' to the category.

The way I currently know it, I can get battery information for the headset, but not for the wireless controller.

I don't know how to get it or where it is stored.

Therefore, I cannot support it at this time.

If we can find it someday, we may be able to update it.

How does this application get battery information?

It is read using Rust code in a manner similar to the PowerShell code presented below.

https://stackoverflow.com/questions/71736070/how-to-get-bluetooth-device-battery-percentage-using-powershell-on-windows

And that information can be easily tested with my modified script below.

• main.ps1

# https://learn.microsoft.com/windows/client-management/mdm/policy-csp-bluetooth
#           Bluetooth Base UUID: "00000000-0000-1000-8000-00805F9B34FB" # BTBook.pdf P.8
$local:BatteryLevel = '{104EA319-6EE2-4701-BD47-8DDBF425BBE5} 2'
$local:BatteryServiceUuid = "0000111E-0000-1000-8000-00805F9B34FB" # Hands Free Profile (HFP)*: 0x111E + BASE UUID
$local:BluetoothAddressId = "DEVPKEY_Bluetooth_DeviceAddress"
$local:BluetoothClass = "DEVPKEY_Bluetooth_ClassOfDevice"
$local:LastArraivvalDate = "DEVPKEY_Device_LastArrivalDate" # Probably RFC3339 format

# Get-PnpDevice -Class Bluetooth | Get-PnpDeviceProperty -KeyName "DEVPKEY_Bluetooth_LastConnectedTime"
# Get-PnpDevice -Class AudioEndpoint | Select-Object FriendlyName, Status, InstanceId # is connected

$local:Result = @();
# Get-PnpDevice -InstanceId "BTHENUM\{$local:BatteryServiceUuid}_*" | ForEach-Object {
Get-PnpDevice -InstanceId "BTHENUM*" | ForEach-Object {
  $local:Properties = @{
    "instance_id"   = $_.InstanceId
    "friendly_name" = $_.friendlyName
  };

  Get-PnpDeviceProperty -InstanceId $_.InstanceId -KeyName $local:BatteryLevel, $local:BluetoothAddressId, $local:BluetoothClass, $local:LastArraivvalDate |
  ForEach-Object {
    $local:data = $_.Data #! Note: Need local variable! otherwise it will be null.
    $local:keyname = $_.KeyName
    switch ($_.KeyName) {
      $local:BatteryLevel { $local:keyname = "battery_level" }
      $local:BluetoothAddressId { $local:keyname = "bluetooth_address" }
      $local:BluetoothClass { $local:keyname = "bluetooth_class" }
      $local:LastArraivvalDate { $local:keyname = "last_arrival_date" }
    }

    if ($_.KeyName -eq $local:LastArraivvalDate) {
      # NOTE: It must be a string or it will become a Date() object.
      # 2001-07-08T00:34:60.026490+09:30	ISO 8601 / RFC 3339 date & time format.
      # o: %Y-%m-%dT%H:%M:%S%.f%:z
      $local:Properties += @{ $local:keyname = $local:data.toString("o") }
    }
    else {
      $local:Properties += @{ $local:keyname = $local:data }
    }

  }
  $Result += $Properties
}

ConvertTo-Json $local:Result
Read-Host "Press any key."

When I do this, I get the controller information, but the battery information is null.

(instance_id and address are omitted as they are private information)

[Skied]

Thanks for your quick response!

I search what you are using and tested it and you are right. With Get-PnpDeviceProperty battery shows allways empty, but windows uses bluettoth gatt, maybe you can try with bluetooth gatt library for rust like on this project (https://github.com/deviceplug/btleplug).
It doesn't work for everything but shows more options than basic powershell.

[SARDONYX-sard]

That is a great crate. Thanks for the info.

Unfortunately, as I mentioned in the readme, I currently do not have a Bluetooth LE device so even if I did implement it, I would not be able to test it. This makes it impossible to know if the implementation is correct and nothing can be fixed when a bug occurs.

I may implement it if I get one someday. Sorry.