Closed muzena closed 4 years ago
That looks like a couple of bugs.
The first one has to do with firmware for the receiver, I think. Can you provide the output of solaar probe
? (I'm assuming you only have one receiver.)
The second has to do with the device with PID 8522. What do old versions of solaar produce for it?
If possible, can you comment out the two lines in lib/solaar/cli/show.py that print the firmware
for f in receiver.firmware:
print (' %-11s: %s' % (f.kind, f.version))
and try solaar show
again?
Thanks.
Right - of course probe has the same problem. Silly me. Can you comment out the two lines in lib/solaar/cli/show.py
Also, select the receiver in the main window and click on the button with the letter i.
Old Solaar dosen't support this keyboard.
When I uncomment this two line in show.py result is:
linux@mint:~$ solaar show
Nano Receiver
Device path : /dev/hidraw3
USB id : 046d:c517
Serial : None
Has 2 paired device(s) out of a maximum of 1.
Notifications: wireless (0x000100)
linux@mint:~$ solaar probe
Nano Receiver
Device path : /dev/hidraw3
USB id : 046d:c517
Serial : None
Has 2 paired device(s) out of a maximum of 1.
Notifications: wireless (0x000100)
Register Dump
Notification Register 0x00: 0x000100
Connection State 0x02: 0x000200
Device Activity 0xb3: None
Pairing Register 0xb5 0x00: None
Pairing Register 0xb5 0x10: None
Pairing Register 0xb5 0x20: None
Pairing Register 0xb5 0x30: None
Pairing Name 0xb5 0x40: None
Pairing Register 0xb5 0x01: None
Pairing Register 0xb5 0x11: None
Pairing Register 0xb5 0x21: None
Pairing Register 0xb5 0x31: None
Pairing Name 0xb5 0x41: None
Pairing Register 0xb5 0x02: None
Pairing Register 0xb5 0x12: None
Pairing Register 0xb5 0x22: None
Pairing Register 0xb5 0x32: None
Pairing Name 0xb5 0x42: None
Pairing Register 0xb5 0x03: None
Pairing Register 0xb5 0x13: None
Pairing Register 0xb5 0x23: None
Pairing Register 0xb5 0x33: None
Pairing Name 0xb5 0x43: None
Pairing Register 0xb5 0x04: None
Pairing Register 0xb5 0x14: None
Pairing Register 0xb5 0x24: None
Pairing Register 0xb5 0x34: None
Pairing Name 0xb5 0x44: None
Pairing Register 0xb5 0x05: None
Pairing Register 0xb5 0x15: None
Pairing Register 0xb5 0x25: None
Pairing Register 0xb5 0x35: None
Pairing Name 0xb5 0x45: None
Firmware 0xf1 0x00: None
Firmware 0xf1 0x01: None
Firmware 0xf1 0x02: None
Firmware 0xf1 0x03: None
Firmware 0xf1 0x04: None
On further thought, I think that Solaar is behaving as it should for your keyboard. As far as I can tell, Solaar never had any information about this keyboard - at least I can't find it in release 0.9.2 or 1.0.1 or any commit that mentions the keyboard. To do better for your keyboard there needs to be a description of it in lib/logitech_receiver/descriptors.py. But getting the right description requires knowing what the keyboard can do. My guess is that
_D('Wireless Keyboard K510', protocol=1.0, wpid='8522',
registers=(_R.battery_status, ),
settings=[
_RS.fn_swap(),
],
)
Would be close to correct, but I'm assuming that this keyboard has the function-swap register. The way to check would be to add this entry to descriptors.py and see whether changing Fn Swap does indeed change the behaviour of the function keys.
Old Solaar dosen't support this keyboard. I think that the reason that is showing now is a recent new rework of logitech driver in kernel.
Yes, this receiver has no firmware information, which is tickling a very old bug. I'll get that fixed momentarily.
Given that the receiver has no information in the pairing registers, I'm wondering how anything is showing up in the main window. I also see that the receiver doesn't look at all like the current receivers, and the mouse has a connect button, which is not how other mice pair with the receiver. So I don't expect that solaar can do much with your setup. I'll fix the bugs, but even adding the keyboard information might not be a good idea.
I will need to connect this mouse, i use it last time before 7 years This is USB/PS2 cable reciver As i remember in older issue report contain more info about this reciver.
There is more keyboard that use this reciver
The problem is that this receiver doesn't use the same information for paired devices that other receivers do, so Solaar might not be able to do anything with it. You can try, for example solaar pair
to pair a mouse, but be prepared for lots of things to not work.
Do you remember which issue involves the C517?
I searching through closed issues. I found this same or similar reciver: https://github.com/pwr-Solaar/Solaar/issues/234
I tried this command:
linux@mint:~$ solaar -dd show
16:21:06,863 DEBUG [MainThread] logitech_receiver.base: (3) <= w[10 FF 83B5 030000]
16:21:06,872 DEBUG [MainThread] logitech_receiver.base: (3) => r[10 FF 8F83 B50100]
16:21:06,872 DEBUG [MainThread] logitech_receiver.base: (3) device 0xFF error on request {83B5}: 1 = invalid SubID/command
16:21:06,872 DEBUG [MainThread] solaar.cli: [/dev/hidraw3] => <NanoReceiver(/dev/hidraw3,3)>
16:21:06,916 DEBUG [MainThread] logitech_receiver.base: (3) <= w[10 FF 8102 000000]
16:21:06,920 DEBUG [MainThread] logitech_receiver.base: (3) => r[10 FF 8102 000200]
Nano Receiver
Device path : /dev/hidraw3
USB id : 046d:c517
Serial : None
Has 2 paired device(s) out of a maximum of 1.
16:21:06,920 DEBUG [MainThread] logitech_receiver.base: (3) <= w[10 FF 8102 000000]
16:21:06,928 DEBUG [MainThread] logitech_receiver.base: (3) => r[10 FF 8102 000200]
16:21:06,928 DEBUG [MainThread] logitech_receiver.base: (3) <= w[10 FF 8100 000000]
16:21:06,936 DEBUG [MainThread] logitech_receiver.base: (3) => r[10 FF 8100 000100]
Notifications: wireless (0x000100)
16:21:06,936 DEBUG [MainThread] logitech_receiver.base: (3) <= w[10 FF 83B3 000000]
16:21:06,944 DEBUG [MainThread] logitech_receiver.base: (3) => r[10 FF 8F83 B30100]
16:21:06,944 DEBUG [MainThread] logitech_receiver.base: (3) device 0xFF error on request {83B3}: 1 = invalid SubID/command
16:21:06,944 DEBUG [MainThread] logitech_receiver.base: (3) <= w[10 FF 8102 000000]
16:21:06,952 DEBUG [MainThread] logitech_receiver.base: (3) => r[10 FF 8102 000200]
16:21:06,952 DEBUG [MainThread] logitech_receiver.base: (3) <= w[10 FF 83B5 200000]
16:21:06,960 DEBUG [MainThread] logitech_receiver.base: (3) => r[10 FF 8F83 B50100]
16:21:06,960 DEBUG [MainThread] logitech_receiver.base: (3) device 0xFF error on request {83B5}: 1 = invalid SubID/command
16:21:06,960 DEBUG [MainThread] logitech_receiver.base: (3) <= w[10 FF 83B5 040000]
16:21:06,968 DEBUG [MainThread] logitech_receiver.base: (3) => r[10 FF 8F83 B50100]
16:21:06,968 DEBUG [MainThread] logitech_receiver.base: (3) device 0xFF error on request {83B5}: 1 = invalid SubID/command
16:21:06,968 ERROR [MainThread] logitech_receiver.receiver: failed to read Nano wpid for device 1 of <NanoReceiver(/dev/hidraw3,3)>
16:21:06,968 ERROR [MainThread] logitech_receiver.receiver: register_new_device
Traceback (most recent call last):
File "/usr/share/solaar/lib/logitech_receiver/receiver.py", line 422, in register_new_device
dev = PairedDevice(self, number, notification)
File "/usr/share/solaar/lib/logitech_receiver/receiver.py", line 104, in __init__
raise _base.NoSuchDevice(number=number, receiver=receiver, error="read Nano wpid")
logitech_receiver.base.NoSuchDevice: {'number': 1, 'receiver': <NanoReceiver(/dev/hidraw3,3)>, 'error': 'read Nano wpid'}
16:21:06,969 WARNING [MainThread] logitech_receiver.receiver: <NanoReceiver(/dev/hidraw3,3)>: looked for device 1, not found
Issue #109 is probably closer.
The exception and warning are as expected. This receiver does not support the registers that Solaar (at least solaar show) accesses to look for paired devices.
You might want to try solaar -dd
. This might show why the main window gives some information about your keyboard.
Now i connected old Logitech LX5 Cordless Optical Mouse, and only mouse is showed in device list without keyboard. And also missing device name: Mouse Wireless PID: 3622
I expect that something is going wrong, but that the GUI works a bit differently from solaar show
so it can provide some information. Submitting the output of solaar -dd
might make it possible to do a bit better.
solaar -dd: logitech-debug.txt
I see a couple of things in that log: 1/ A device is signalling, but its device number is too high. This should be fixed in my recent patch, so some more information may become available. 2/ There is another place where there is an assumption that firmware is always available. I'm putting in a PR to fix this problem. Once this PR is merged in things might improve. But it is still the case that this receiver is quite different from the receivers that Solaar is built to handle so there may be further problems that are not fixable.
solaar -dd: logitech-debugg-2.txt
Hmm. I didn't see the difference that I was expecting.
Could you try to change the maximum number of pairings for your receiver by changing line 58 to
'max_devices': 6,
in lib/logitech_receiver/base_usb.py. It should currently have a 2 in the line. Also make sure that the C517 receiver line reads
NANO_RECEIVER_C517 = _nano_receiver_max2(0xc517)
Then provide output of solaar -dd
and a screen shot of the main window if it is different from the screen shot you already provided.
Now is showing keyboard and mouse in GUI.
solaar -dd: logitech-debugg-3.txt
OK. I have a couple of changes that will help with the receiver. It would be nice to have names for the keyboard and mouse. The S510 is the name for the entire set. Do you know what the keyboard and mouse are called? This information is probably on the bottom of the keyboard and the mouse.
Logitech S 510 cordless keyboard, Logitech LX5 cordless mouse,
I have another combo keyboard+mouse MK 300 It works, only need to add keyboard and mouse descriptors. Keyboard name is MK300, mouse is no name, I try to search name on google, it says only description: optical mouse 1200 dpi solaar -dd: logitech-debugg-4.txt
It's easier to get the required information out of solaar show
so please provide the output from that command with both the keyboard and mouse active.
solaar show
Nano Receiver
Device path : /dev/hidraw1
USB id : 046d:c517
Serial : None Has 2 paired device(s) out of a maximum of 6.
Notifications: wireless (0x000100)
Aah, right. There is that problem with the c517 and firmware. You have to get the current version of Solaar from this repository or patch the firmware problem again. Note that the current version of Solaar has a bug that prevents unpairing from the GUI so you might want to clone to a different directory.
I add this patch https://github.com/pwr-Solaar/Solaar/issues/716#issuecomment-600217488 and this commit https://github.com/pwr-Solaar/Solaar/pull/722 solaar show
Nano Receiver
Device path : /dev/hidraw1
USB id : 046d:c517
Serial : None Has 2 paired device(s) out of a maximum of 6.
Notifications: wireless (0x000100)
solaar -dd logitech-debugg-5.txt
Ah, yes, no useful output from solaar show -dd
because the receiver doesn't implement the HID++ 1.0 registers.
What I can see from the other output is that you have had five different devices connected
'3622:?': {'_name': '? (3622)'},
'5612:?': {'_name': '? (5612)'},
'6822:?': {'_name': 'Wireless Mouse MK30'}, # mouse
'8521:?': {'_name': '? (8521)'}, # keyboard
'8522:?': {'_name': 'Wireless Keyboard S510'},
To have these devices added to Solaar I'll need their model name, device type (mouse or keyboard), and HID++ version. The first you will probably have to obtain from the device itself; the second and third come from the main window of Solaar with the information section made visible, as you provided for 5612 in the screenshot above. Note that Logitech often changes the internals of devices without changing their model names so there can be different WPIDs for what appear to be the same model of device. Solaar fudges this my adding a differentiator to the model name.
'3622:?': {'_name': '? (3622)'}, # Wireless Keyboard S510 (Logitech S 510 cordless keyboard)
'5612:?': {'_name': '? (5612)'}, # Logitech LX5 cordless mouse
'6822:?': {'_name': 'Wireless Mouse MK30'}, # Wireless mouse MK 300
'8521:?': {'_name': '? (8521)'}, # Wireless Keyboard MK 300
Wireless Mouse MK30' -> This I try to add mouse name, and keyboard > Wireless Keyboard S510
I also need the protocol value.
Which protocol value, I don't understand?
I also need the protocol value.
In the detailed information part of the main Solaar window there is a line that starts "Protocol:". This is the protocol that the device uses. Please provide that.
HID++ 1.0
For all of them?
yes
@pfps I have this problem again.
```EX100 Receiver 27 Mhz Device path : /dev/hidraw1 USB id : 046d:c517 Serial : None Has 2 paired device(s) out of a maximum of 4. Notifications: wireless (0x000100) 1: Wireless Mouse EX100 Codename : EX100m Kind : mouse Wireless PID : 3F00 Protocol : HID++ 1.0 Serial number: ? The power switch is located on the (unknown). Notifications: roller V, mouse extra buttons, battery status, roller H (0x3C0000). Features: special buttons, scroll accel (0x420000) Battery: good, discharging. 3: Wireless Keyboard EX100 Codename : EX100 Kind : keyboard Wireless PID : 6500 Protocol : HID++ 1.0 Serial number: ? The power switch is located on the (unknown). Notifications: battery status (0x100000). Features: special buttons, scroll accel (0x420000) Battery: good, discharging. EX100 Receiver 27 Mhz Device path : /dev/hidraw7 USB id : 046d:c517 Serial : None Has 2 paired device(s) out of a maximum of 4. Notifications: wireless (0x000100) 1: Wireless Mouse EX100 Codename : EX100m Kind : mouse Wireless PID : 3F00 Protocol : HID++ 1.0 Serial number: ? The power switch is located on the (unknown). Notifications: roller V, mouse extra buttons, battery status, roller H (0x3C0000). Features: special buttons, scroll accel (0x420000) Battery: good, discharging. 3: Wireless Keyboard EX100 Codename : EX100 Kind : keyboard Wireless PID : 6500 Protocol : HID++ 1.0 Serial number: ? The power switch is located on the (unknown). Notifications: battery status (0x100000). Features: special buttons, scroll accel (0x420000) Battery: full, discharging. ```
This looks like a different problem - Solaar is getting the wrong value for the WPID sometimes. (Note that Solaar show has the right values.)
This should be fixed in version 1.0.3. Which version are you running?
@pfps git master
Hmm. Then I'm not sure what it causing your problem. Please run with -dd
and provide the output when you see the problem. That should show what message is causing Solaar to get the wrong WPIDs.
@pfps
solaar -dd
```
11:59:34,254 INFO [MainThread] root: language hr_HR (UTF-8), translations path None
11:59:34,315 DEBUG [MainThread] solaar.ui.tray: using AppIndicator3
11:59:34,324 INFO [MainThread] solaar.upower: connected to system dbus, watching for suspend/resume events
```
@muzena That's only three lines of output. There should be more available.
@pfps
I don't now why, I tried 3 times, it showed 3 lines only, now I tried again and output print is work.
solaar -dd
```
12:44:43,893 INFO [MainThread] root: language hr_HR (UTF-8), translations path None
12:44:43,955 DEBUG [MainThread] solaar.ui.tray: using AppIndicator3
12:44:43,963 INFO [MainThread] solaar.upower: connected to system dbus, watching for suspend/resume events
12:44:44,002 DEBUG [MainThread] solaar.ui: startup registered=True, remote=False
12:44:44,003 DEBUG [AsyncUI] solaar.tasks: started
12:44:44,003 INFO [MainThread] solaar.ui.notify: starting desktop notifications
12:44:44,008 DEBUG [MainThread] solaar.ui.icons: sys.path[0] = /usr/share/solaar/lib
12:44:44,008 DEBUG [MainThread] solaar.ui.icons: looking for icons in /usr/share/solaar/icons
12:44:44,008 DEBUG [MainThread] solaar.ui.icons: looking for icons in /usr/share/solaar/share/solaar/icons
12:44:44,008 DEBUG [MainThread] solaar.ui.icons: looking for icons in /home/goran/.local/share/solaar/icons
12:44:44,008 DEBUG [MainThread] solaar.ui.icons: looking for icons in /usr/share/solaar/lib/share/solaar/icons
12:44:44,008 DEBUG [MainThread] solaar.ui.icons: looking for icons in /usr/share/solaar/share/solaar/icons
12:44:44,008 DEBUG [MainThread] solaar.ui.icons: looking for icons in /home/goran/.local/share/flatpak/exports/share/solaar/icons
12:44:44,008 DEBUG [MainThread] solaar.ui.icons: looking for icons in /var/lib/flatpak/exports/share/solaar/icons
12:44:44,008 DEBUG [MainThread] solaar.ui.icons: looking for icons in /usr/share/cinnamon/solaar/icons
12:44:44,008 DEBUG [MainThread] solaar.ui.icons: looking for icons in /usr/share/gnome/solaar/icons
12:44:44,008 DEBUG [MainThread] solaar.ui.icons: looking for icons in /home/goran/.local/share/flatpak/exports/share/solaar/icons
12:44:44,008 DEBUG [MainThread] solaar.ui.icons: looking for icons in /var/lib/flatpak/exports/share/solaar/icons
12:44:44,009 DEBUG [MainThread] solaar.ui.icons: looking for icons in /usr/local/share/solaar/icons
12:44:44,009 DEBUG [MainThread] solaar.ui.icons: looking for icons in /usr/share/solaar/icons
12:44:44,009 DEBUG [MainThread] solaar.ui.icons: looking for icons in /var/lib/snapd/desktop/solaar/icons
12:44:44,009 DEBUG [MainThread] solaar.ui.icons: icon theme paths: ['/usr/share/solaar/icons', '/usr/share/solaar/icons', '/home/goran/.local/share/icons', '/home/goran/.icons', '/home/goran/.local/share/flatpak/exports/share/icons', '/var/lib/flatpak/exports/share/icons', '/usr/share/cinnamon/icons', '/usr/share/gnome/icons', '/home/goran/.local/share/flatpak/exports/share/icons', '/var/lib/flatpak/exports/share/icons', '/usr/local/share/icons', '/usr/share/icons', '/var/lib/snapd/desktop/icons', '/home/goran/.local/share/flatpak/exports/share/pixmaps', '/var/lib/flatpak/exports/share/pixmaps', '/usr/share/cinnamon/pixmaps', '/usr/share/gnome/pixmaps', '/home/goran/.local/share/flatpak/exports/share/pixmaps', '/var/lib/flatpak/exports/share/pixmaps', '/usr/local/share/pixmaps', '/usr/share/pixmaps', '/var/lib/snapd/desktop/pixmaps']
12:44:44,061 INFO [MainThread] solaar.listener: starting receiver listening threads
12:44:44,087 INFO [MainThread] solaar.listener: receiver event add DeviceInfo(path='/dev/hidraw1', vendor_id='046d', product_id='c517', serial='', release=b'3810', manufacturer=b'Logitech', product=b'USB Receiver', interface=1, driver='logitech-djreceiver')
12:44:44,087 DEBUG [MainThread] logitech_receiver.base: (14) <= w[10 FF 83B5 030000]
12:44:44,096 DEBUG [MainThread] logitech_receiver.base: (14) => r[10 FF 8F83 B50100]
12:44:44,096 DEBUG [MainThread] logitech_receiver.base: (14) device 0xFF error on request {83B5}: 1 = invalid SubID/command
12:44:44,097 INFO [ReceiverListener:hidraw1] logitech_receiver.listener: started with
It looks as if some code to handle your EX100 receiver is incorrect. That code was put in to handle someone else's EX100. Pull request #932 should partially fix your problem. Please run it and report back whether you still have problems. PR #932 does not change the Solaar CLI and there may be problems there. Please run solaar -dd show
and provide the output.
To run PR #932, first clone Solaar if you have not already done so and cd to the clone directory. The first time you download the pull request, fetch it into a new branch and checkout that branch, as in:
git fetch origin pull/932/head:pull_932
git checkout pull_932
To download a new version of the pull request, fetch it and then set your pull branch to the new fetch, as in:
git checkout pull_932
git fetch origin pull/932/head
git reset --hard FETCH_HEAD
@pfps Thanks, now it's working.
That's great. How about solaar -dd show
?
@muzena Another output that would be useful is solaar probe
. That will show all the registers of a receiver.
@pfps Now it won't work again.
solaar -dd show
```
20:18:21,099 DEBUG [MainThread] logitech_receiver.base: (3) <= w[10 FF 83B5 030000]
20:18:21,101 DEBUG [MainThread] logitech_receiver.base: (3) => r[10 FF 8F83 B50100]
20:18:21,101 DEBUG [MainThread] logitech_receiver.base: (3) device 0xFF error on request {83B5}: 1 = invalid SubID/command
20:18:21,101 DEBUG [MainThread] solaar.cli: [/dev/hidraw3] =>
solaar -dd
```
20:21:12,279 INFO [MainThread] root: language hr_HR (UTF-8), translations path None
20:21:12,364 DEBUG [MainThread] solaar.ui.tray: using AppIndicator3
20:21:12,375 INFO [MainThread] solaar.upower: connected to system dbus, watching for suspend/resume events
20:21:12,419 DEBUG [MainThread] solaar.ui: startup registered=True, remote=False
20:21:12,420 DEBUG [AsyncUI] solaar.tasks: started
20:21:12,420 INFO [MainThread] solaar.ui.notify: starting desktop notifications
20:21:12,426 DEBUG [MainThread] solaar.ui.icons: sys.path[0] = /usr/share/solaar/lib
20:21:12,426 DEBUG [MainThread] solaar.ui.icons: looking for icons in /usr/share/solaar/icons
20:21:12,426 DEBUG [MainThread] solaar.ui.icons: looking for icons in /usr/share/solaar/share/solaar/icons
20:21:12,426 DEBUG [MainThread] solaar.ui.icons: looking for icons in /home/goran/.local/share/solaar/icons
20:21:12,426 DEBUG [MainThread] solaar.ui.icons: looking for icons in /usr/share/solaar/lib/share/solaar/icons
20:21:12,426 DEBUG [MainThread] solaar.ui.icons: looking for icons in /usr/share/solaar/share/solaar/icons
20:21:12,426 DEBUG [MainThread] solaar.ui.icons: looking for icons in /home/goran/.local/share/flatpak/exports/share/solaar/icons
20:21:12,426 DEBUG [MainThread] solaar.ui.icons: looking for icons in /var/lib/flatpak/exports/share/solaar/icons
20:21:12,426 DEBUG [MainThread] solaar.ui.icons: looking for icons in /usr/share/cinnamon/solaar/icons
20:21:12,426 DEBUG [MainThread] solaar.ui.icons: looking for icons in /usr/share/gnome/solaar/icons
20:21:12,426 DEBUG [MainThread] solaar.ui.icons: looking for icons in /home/goran/.local/share/flatpak/exports/share/solaar/icons
20:21:12,427 DEBUG [MainThread] solaar.ui.icons: looking for icons in /var/lib/flatpak/exports/share/solaar/icons
20:21:12,427 DEBUG [MainThread] solaar.ui.icons: looking for icons in /usr/local/share/solaar/icons
20:21:12,427 DEBUG [MainThread] solaar.ui.icons: looking for icons in /usr/share/solaar/icons
20:21:12,427 DEBUG [MainThread] solaar.ui.icons: looking for icons in /var/lib/snapd/desktop/solaar/icons
20:21:12,427 DEBUG [MainThread] solaar.ui.icons: icon theme paths: ['/usr/share/solaar/icons', '/usr/share/solaar/icons', '/home/goran/.local/share/icons', '/home/goran/.icons', '/home/goran/.local/share/flatpak/exports/share/icons', '/var/lib/flatpak/exports/share/icons', '/usr/share/cinnamon/icons', '/usr/share/gnome/icons', '/home/goran/.local/share/flatpak/exports/share/icons', '/var/lib/flatpak/exports/share/icons', '/usr/local/share/icons', '/usr/share/icons', '/var/lib/snapd/desktop/icons', '/home/goran/.local/share/flatpak/exports/share/pixmaps', '/var/lib/flatpak/exports/share/pixmaps', '/usr/share/cinnamon/pixmaps', '/usr/share/gnome/pixmaps', '/home/goran/.local/share/flatpak/exports/share/pixmaps', '/var/lib/flatpak/exports/share/pixmaps', '/usr/local/share/pixmaps', '/usr/share/pixmaps', '/var/lib/snapd/desktop/pixmaps']
20:21:12,497 INFO [MainThread] solaar.listener: starting receiver listening threads
20:21:12,525 INFO [MainThread] solaar.listener: receiver event add DeviceInfo(path='/dev/hidraw3', vendor_id='046d', product_id='c517', serial='', release=b'3810', manufacturer=b'Logitech', product=b'USB Receiver', interface=1, driver='logitech-djreceiver')
20:21:12,526 DEBUG [MainThread] logitech_receiver.base: (14) <= w[10 FF 83B5 030000]
20:21:12,535 DEBUG [MainThread] logitech_receiver.base: (14) => r[10 FF 8F83 B50100]
20:21:12,535 DEBUG [MainThread] logitech_receiver.base: (14) device 0xFF error on request {83B5}: 1 = invalid SubID/command
20:21:12,535 INFO [ReceiverListener:hidraw3] logitech_receiver.listener: started with
solaar probe
```
EX100 Receiver 27 Mhz
Device path : /dev/hidraw3
USB id : 046d:c517
Serial : None
Has 2 paired device(s) out of a maximum of 4.
Notifications: wireless (0x000100)
Register Dump
Notification Register 0x00: 0x000100
Connection State 0x02: 0x000200
Device Activity 0xb3: None
Pairing Register 0xb5 0x00: None
Pairing Register 0xb5 0x10: None
Pairing Register 0xb5 0x20: None
Pairing Register 0xb5 0x30: None
Pairing Name 0xb5 0x40: None
Pairing Register 0xb5 0x01: None
Pairing Register 0xb5 0x11: None
Pairing Register 0xb5 0x21: None
Pairing Register 0xb5 0x31: None
Pairing Name 0xb5 0x41: None
Pairing Register 0xb5 0x02: None
Pairing Register 0xb5 0x12: None
Pairing Register 0xb5 0x22: None
Pairing Register 0xb5 0x32: None
Pairing Name 0xb5 0x42: None
Pairing Register 0xb5 0x03: None
Pairing Register 0xb5 0x13: None
Pairing Register 0xb5 0x23: None
Pairing Register 0xb5 0x33: None
Pairing Name 0xb5 0x43: None
Pairing Register 0xb5 0x04: None
Pairing Register 0xb5 0x14: None
Pairing Register 0xb5 0x24: None
Pairing Register 0xb5 0x34: None
Pairing Name 0xb5 0x44: None
Pairing Register 0xb5 0x05: None
Pairing Register 0xb5 0x15: None
Pairing Register 0xb5 0x25: None
Pairing Register 0xb5 0x35: None
Pairing Name 0xb5 0x45: None
Firmware 0xf1 0x00: None
Firmware 0xf1 0x01: None
Firmware 0xf1 0x02: None
Firmware 0xf1 0x03: None
Firmware 0xf1 0x04: None
```
Information
uname -srmo
):Linux 5.5.9-050509-lowlatency x86_64 GNU/Linux
solaar show
: