Support for AVATTO H100 Spotlight 2.4GHz Wireless Digital Laser Pointer

[alezzandro]

Hi!

A friend of mine just bought this little digital pointer on the net.
https://www.aliexpress.com/item/32931337912.html

Any chances to get it work with this application?

I can take additional HW info if needed:

I: Bus=0003 Vendor=046a Product=0011 Version=0111
N: Name="HID 046a:0011"
P: Phys=usb-0000:00:14.0-4.3/input0
S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.3/1-4.3:1.0/0003:046A:0011.000D/input/input31
U: Uniq=
H: Handlers=sysrq kbd leds event20 
B: PROP=0
B: EV=120013
B: KEY=1000000000007 ff980000000007ff febeffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=7

I: Bus=0003 Vendor=0c45 Product=8101 Version=0101
N: Name="USB USB Device Consumer Control"
P: Phys=usb-0000:00:14.0-2.4/input0
S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.4/1-2.4:1.0/0003:0C45:8101.000E/input/input32
U: Uniq=
H: Handlers=kbd event21 
B: PROP=0
B: EV=1f
B: KEY=3f000300ff 0 0 483ffff17aff32d bfd4444600000000 1 130ff38b17c000 677bfad9415fed 19ed68000004400 10000002
B: REL=1040
B: ABS=100000000
B: MSC=10

I: Bus=0003 Vendor=0c45 Product=8101 Version=0101
N: Name="USB USB Device System Control"
P: Phys=usb-0000:00:14.0-2.4/input0
S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.4/1-2.4:1.0/0003:0C45:8101.000E/input/input33
U: Uniq=
H: Handlers=kbd event22 
B: PROP=0
B: EV=13
B: KEY=40000000000000 0 0 0 40000010cc00 10000000000000 0
B: MSC=10

I: Bus=0003 Vendor=0c45 Product=8101 Version=0101
N: Name="USB USB Device Keyboard"
P: Phys=usb-0000:00:14.0-2.4/input0
S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.4/1-2.4:1.0/0003:0C45:8101.000E/input/input34
U: Uniq=
H: Handlers=sysrq kbd leds event23 
B: PROP=0
B: EV=120013
B: KEY=1000000000007 ff9f207ac14057ff febeffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=1f

I: Bus=0003 Vendor=0c45 Product=8101 Version=0101
N: Name="USB USB Device"
P: Phys=usb-0000:00:14.0-2.4/input1
S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.4/1-2.4:1.1/0003:0C45:8101.000F/input/input35
U: Uniq=
H: Handlers=mouse3 event24 
B: PROP=0
B: EV=17
B: KEY=1f0000 0 0 0 0
B: REL=903
B: MSC=10

I: Bus=0003 Vendor=0c45 Product=8101 Version=0101
N: Name="USB USB Device"
P: Phys=usb-0000:00:14.0-2.4/input3
S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.4/1-2.4:1.3/0003:0C45:8101.0011/input/input36
U: Uniq=
H: Handlers=event25 js0 
B: PROP=0
B: EV=1b
B: KEY=7fff000000000000 0 0 0 0
B: ABS=1000003063f
B: MSC=10

[rj-jesus]

If I'm not mistaken you could get it to work by adjusting the udev rule to

# Rule for USB Receiver
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0c45", ATTRS{idProduct}=="8101", MODE="660", GROUP="plugdev", ENV{USB_HUB_TYPE}="0c45:8101"

and modifying the vendor and product IDs in spotlight.cc:

-  constexpr quint16 vendorId = 0x46d;
-  constexpr quint16 usbProductId = 0xc53e;
+  constexpr quint16 vendorId = 0x0c45;
+  constexpr quint16 usbProductId = 0x8101;

I would also be interested in this!

[jahnf]

Hi, I am not familiar with that device, but if it works similar to the Logitech one it should be possible the way @rj-jesus already described. I am also interested in the outcome. In September/October I will allocate some time to work on this project and documentation. Would be cool to include another device.

[alezzandro]

Yes! :)

@rj-jesus I've already tried editing the udev rules and the code without success, it could be really useful to have some documentation and some debug output to see where the Device has been rejected as "Not Spotlight".
I've also tried commenting out some other checks that the code makes for ensuring that the device is a Spotlight one, for example:

  /* unsigned long bitmask = 0;
  const int len = ioctl(evfd, EVIOCGBIT(0, sizeof(bitmask)), &bitmask);
  if ( len < 0 )
  {
    ::close(evfd);
    return ConnectionResult::NotASpotlightDevice;
  }

  const bool hasRelEv = !!(bitmask & (1 << EV_REL));
  if (!hasRelEv) { return ConnectionResult::NotASpotlightDevice; } */

@jahnf if you can share some docs or include some Debug / Verbose output on the command line it could be really useful.

I don't own a Logitech device but in the meantime I can confirm you that this device seems to work fine with Linux, if I keep pressed the single button on top then the mouse-like input is activated and then moving the device around let the mouse pointer move aroung too on the screen.

[rj-jesus]

@alezzandro

I actually have one of these devices (arrived like two days ago, what a coincidence!) and I could get it recognized with the modifications I wrote above.

Maybe you're not a member of the plugdev group? I pasted the rule in a hurry and failed to mention I had edited the group assigned to the device so as to avoid having to create a new one just for this.

Check the groups you're a member of and confirm you're in plugdev. Otherwise just change the group in the rule to one you're member of.

--
Ricardo Jesus

[jahnf]

Well basically at startup in connectDevices() we loop over all devices in /dev/input starting with event*

You should not just disable the checks, just add some Debug output yourself. ( I know debug output is missing currently, but will be added in the next version..)
For example you can do sth like: (include the <QDebug> header at top of spotlight.cc)

  const int evfd = ::open(devicePath.toLocal8Bit().constData(), O_RDONLY, 0);
  if (evfd < 0) {
    qDebug() << "*** Could not open" << devicePath;
    return ConnectionResult::CouldNotOpen;
  }

  struct input_id id{};
  ioctl(evfd, EVIOCGID, &id);

  constexpr quint16 vendorId = 0x46d;
  constexpr quint16 usbProductId = 0xc53e;
  constexpr quint16 btProductId = 0xb503;

  if (id.vendor != vendorId || (id.product != usbProductId && id.product != btProductId))
  {
    qDebug() << "*** VENDOR or PRODUCT id mismatch for: " << devicePath;
    ::close(evfd);
    return ConnectionResult::NotASpotlightDevice;
  }

  unsigned long bitmask = 0;
  const int len = ioctl(evfd, EVIOCGBIT(0, sizeof(bitmask)), &bitmask);
  if ( len < 0 )
  {
    qDebug() << "*** Could not get Info via iotcl for:  " << devicePath;
    ::close(evfd);
    return ConnectionResult::NotASpotlightDevice;
  }

  const bool hasRelEv = !!(bitmask & (1 << EV_REL));
  if (!hasRelEv) { 
    qDebug() << "*** Device has no support for relative Mouse Events:  " << devicePath;
    return ConnectionResult::NotASpotlightDevice; 
  }

[alezzandro]

Thanks @rj-jesus !!!

It worked perfectly with your suggested changes.

@jahnf Can we move externally the device ID configuration?

Thanks,
BR

If I'm not mistaken you could get it to work by adjusting the udev rule to

# Rule for USB Receiver
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0c45", ATTRS{idProduct}=="8101", MODE="660", GROUP="plugdev", ENV{USB_HUB_TYPE}="0c45:8101"

and modifying the vendor and product IDs in spotlight.cc:

-  constexpr quint16 vendorId = 0x46d;
-  constexpr quint16 usbProductId = 0xc53e;
+  constexpr quint16 vendorId = 0x0c45;
+  constexpr quint16 usbProductId = 0x8101;

I would also be interested in this!

[jahnf]

Can we move externally the device ID configuration?

I'll note that for the next minor release, probably allowing adding additional vendor/product ids in a config file or something similar.

[jahnf]

Relates to #31

[alinelena]

got one of these
https://www.aliexpress.com/item/32825980124.html?spm=a2g0s.9042311.0.0.32254c4dCk669u
i10 pro version... and confirm works after some changes on current git.

SUBSYSTEMS=="usb", ATTRS{idVendor}=="2571", ATTRS{idProduct}=="4109", MODE="0660", TAG+="uaccess"

and in the src/spotlight.cc add line 30

  26   // List of supported devices                                                                                                      
  27   const std::vector<Device> supportedDevices {                                                                                      
  28     {0x46d, 0xc53e, false},  // Logitech Spotlight (USB)                                                                            
  29     {0x46d, 0xb503, true},   // Logitech Spotlight (Bluetooth)                                                                      
  30     {0x2571, 0x4109, false},   // AVATTO i10 pro (USB)                                                                          
  31   };

spotlight works as expected.

few comments. this seems to have some cycling functions, spotlight/zoom/digital laser. I need to see what events are sent for cycling throw them. volume up and down with long press already works.

a nice feature will be to use the device list to generate the udev file.

Alin

[jahnf]

Support is planned. ✅ I didn't have much time lately for the project but expect new features soon.

[jahnf]

@alinelena You can give the feature branch https://github.com/jahnf/Projecteur/tree/feature/pointer-mode-uinput-dev a try - there is now a devices.conf file that will be read by the CMake build during configuration time.

This will do two things:

1. Devices listed in the file will be be detected as supported by the compiled application
2. The generated udev rule file will also include these devices.