Can't connect, 'No events found', unresponsive screen etc

[strodgers]

I suspect any kind of connection issues are going to be related, so combining issues #48 (diedo42) and #51 (mdvries) here.

Basically I haven't been able to work out how to confirm whether or not a command has been received and processed by the keyboard, which is a problem.

There are also these annoying URB_INTERRUPT messages regularly (unrelated to key strokes) which might be messing with something. It might be fixable if I used a lower level driver to interact with the keyboard so it can properly be put into idle mode, but I think that would get in the way of the regular keyboard function like typing etc

One thing I noticed is that when I ran the controller when the keyboard was connected through a hub, I would get strange connection issues sometimes and it would stop responding. These problems stopped when I plugged it directly into my machine (no hub inbetween). @diedo42 and @mdvries can you confirm that the USB C cable is going directly to your machine? Is the same behaviour observed on different USB ports? I am probably doing something wrong with the HID reports and maybe a bad connection exacerbates the problem

[strodgers]

I have also done a new release with some small changes, you can ensure its the latest by running
pip install EpomakerController==0.0.7

[mdvries]

I did encounter also issues when connected to a hub with the screen: The screen gave distorted/flashing picture and when plugging it direct to the PC that issue is gone but I still get that read error. I did however manage to get it working with wireless but direct USB still that read error. Will try the pip install when I am back downstairs behind my ubuntu instead of the Mac in the living.

[diedo42]

Same problem with multiple port directy connect to the notebook

┌──(epomaker)─(diedo㉿diedo-bk)-[~]
└─$ pip install EpomakerController==0.0.7
Requirement already satisfied: EpomakerController==0.0.7 in ./epomaker/lib/python3.12/site-packages (0.0.7)
Requirement already satisfied: appdirs==1.4.4 in ./epomaker/lib/python3.12/site-packages (from EpomakerController==0.0.7) (1.4.4)
Requirement already satisfied: click>=8.0.1 in ./epomaker/lib/python3.12/site-packages (from EpomakerController==0.0.7) (8.1.7)
Requirement already satisfied: hidapi==0.14.0 in ./epomaker/lib/python3.12/site-packages (from EpomakerController==0.0.7) (0.14.0)
Requirement already satisfied: numpy<2.0 in ./epomaker/lib/python3.12/site-packages (from EpomakerController==0.0.7) (1.26.4)
Requirement already satisfied: opencv-python-headless==4.10.0.82 in ./epomaker/lib/python3.12/site-packages (from EpomakerController==0.0.7) (4.10.0.82)
Requirement already satisfied: psutil>=6.0.0 in ./epomaker/lib/python3.12/site-packages (from EpomakerController==0.0.7) (6.0.0)
Requirement already satisfied: python-dateutil==2.8.2 in ./epomaker/lib/python3.12/site-packages (from EpomakerController==0.0.7) (2.8.2)
Requirement already satisfied: setuptools>=19.0 in ./epomaker/lib/python3.12/site-packages (from hidapi==0.14.0->EpomakerController==0.0.7) (75.1.0)
Requirement already satisfied: six>=1.5 in ./epomaker/lib/python3.12/site-packages (from python-dateutil==2.8.2->EpomakerController==0.0.7) (1.16.0)

┌──(epomaker)─(diedo㉿diedo-bk)-[~]
└─$ epomakercontroller start-daemon
WARNING: If this program errors out or you cancel early, the keyboard
may become unresponsive. It should work fine again if you unplug and plug
it back in!
Device opened, initializing..
Error in start-daemon: read error

┌──(epomaker)─(diedo㉿diedo-bk)-[~]
└─$ epomakercontroller start-daemon
WARNING: If this program errors out or you cancel early, the keyboard
may become unresponsive. It should work fine again if you unplug and plug
it back in!
No events found with description: 'ROYUAN .* System Control'
Error in start-daemon: No device found

┌──(epomaker)─(diedo㉿diedo-bk)-[~]
└─$ epomakercontroller start-daemon
WARNING: If this program errors out or you cancel early, the keyboard
may become unresponsive. It should work fine again if you unplug and plug
it back in!
Device opened, initializing..
Error in start-daemon: read error

┌──(epomaker)─(diedo㉿diedo-bk)-[~]
└─$ epomakercontroller start-daemon
WARNING: If this program errors out or you cancel early, the keyboard
may become unresponsive. It should work fine again if you unplug and plug
it back in!
No events found with description: 'ROYUAN .* System Control'
Error in start-daemon: No device found

┌──(epomaker)─(diedo㉿diedo-bk)-[~]
└─$ cat /sys/class/input/event*/device/name
Lid Switch
Power Button
Power Button
AT Translated Set 2 keyboard
Telink Wireless Gaming Mouse
Telink Wireless Gaming Mouse Keyboard
Telink Wireless Gaming Mouse
Telink Wireless Gaming Mouse
Ideapad extra buttons
Elan Touchpad
Video Bus
HDA Intel PCH Mic
HDA Intel PCH Headphone
HDA Intel PCH HDMI/DP,pcm=3
HDA Intel PCH HDMI/DP,pcm=7
HDA Intel PCH HDMI/DP,pcm=8
Generic USB Audio Consumer Control
Generic USB Audio
HP HP USB-C Dock G5 System Control
ROYUAN RT100 Wired

┌──(epomaker)─(diedo㉿diedo-bk)-[~]
└─$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 04f3:0c4b Elan Microelectronics Corp. ELAN:Fingerprint
Bus 001 Device 003: ID 04ca:7070 Lite-On Technology Corp. Integrated Camera
Bus 001 Device 004: ID 320f:221d Telink Wireless Gaming Mouse
Bus 001 Device 005: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP)
Bus 001 Device 007: ID 03f0:036b HP, Inc HP USB-C Dock G5
Bus 001 Device 008: ID 03f0:056b HP, Inc USB Audio
Bus 001 Device 009: ID 03f0:086b HP, Inc USB2734
Bus 001 Device 010: ID 03f0:046b HP, Inc HP USB-C Dock G5
Bus 001 Device 021: ID 214b:7250 Huasheng Electronics USB2.0 HUB
Bus 001 Device 022: ID 214b:7250 Huasheng Electronics USB2.0 HUB
Bus 001 Device 023: ID 3151:4010 ROYUAN RT100 Wired
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 03f0:066b HP, Inc HP USB-C Dock G5
Bus 002 Device 003: ID 03f0:076b HP, Inc USB5734
Bus 002 Device 004: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter

┌──(epomaker)─(diedo㉿diedo-bk)-[~]
└─$ cat /etc/udev/rules.d/99-epomaker-rt100.rules

Epomaker RT100 keyboard

SUBSYSTEM=="usb", ATTRS{idVendor}=="3151", ATTRS{idProduct}=="4010", MODE="0666", GROUP="plugdev"

┌──(epomaker)─(diedo㉿diedo-bk)-[~]
└─$ epomakercontroller dev --udev
Generating udev rule for the connected keyboard.
WARNING: If this program errors out or you cancel early, the keyboard
may become unresponsive. It should work fine again if you unplug and plug
it back in!
[
{
"path": "1-3.3.3:1.0",
"vendor_id": "0x3151",
"product_id": "0x4010",
"serial_number": "",
"release_number": 1287,
"manufacturer_string": "ROYUAN",
"product_string": "RT100 Wired",
"usage_page": 0,
"usage": 0,
"interface_number": 0,
"bus_type": 1
},
{
"path": "1-3.3.3:1.1",
"vendor_id": "0x3151",
"product_id": "0x4010",
"serial_number": "",
"release_number": 1287,
"manufacturer_string": "ROYUAN",
"product_string": "RT100 Wired",
"usage_page": 0,
"usage": 0,
"interface_number": 1,
"bus_type": 1
},
{
"path": "1-3.3.3:1.2",
"vendor_id": "0x3151",
"product_id": "0x4010",
"serial_number": "",
"release_number": 1287,
"manufacturer_string": "ROYUAN",
"product_string": "RT100 Wired",
"usage_page": 0,
"usage": 0,
"interface_number": 2,
"bus_type": 1
}
]
Generating udev rule for Epomaker RT100 keyboard
Rule content:

Epomaker RT100 keyboard

SUBSYSTEM=="usb", ATTRS{idVendor}=="3151", ATTRS{idProduct}=="4010", MODE="0666", GROUP="plugdev"

Rule file path: /etc/udev/rules.d/99-epomaker-rt100.rules
Please enter your password if prompted
[sudo] password for diedo:
Rule generated successfully

┌──(epomaker)─(diedo㉿diedo-bk)-[~]
└─$ epomakercontroller start-daemon
WARNING: If this program errors out or you cancel early, the keyboard
may become unresponsive. It should work fine again if you unplug and plug
it back in!
No events found with description: 'ROYUAN .* System Control'
Error in start-daemon: No device found

[mdvries]

I have also done a new release with some small changes, you can ensure its the latest by running pip install EpomakerController==0.0.7

Tried this version but still I get: Error in start-daemon: read error. Interesting thing is that after I run the daemon I get this and when I try to run it again it says:
"
Could not find Wired interface
Error in start-daemon: No device found
"
I need to unplug/plug the USB cable to have epomakercontroller recognize the keyboard again but then the same read error appears.

I double checked that the cable was plugged in one of the USB ports that are directly connected to the motherboard.

Additional info: I did check syslog whilst running the daemon. This is the output it generates when I get the read error:

2024-12-11T00:19:10.568721+01:00 mars acpid: input device has been disconnected, fd 30
2024-12-11T00:19:10.583612+01:00 mars acpid: input device has been disconnected, fd 31
2024-12-11T00:19:10.605540+01:00 mars acpid: input device has been disconnected, fd 32
2024-12-11T00:19:10.667409+01:00 mars kernel: hid-generic 0003:3151:4010.0054: unknown main item tag 0x0
2024-12-11T00:19:10.667420+01:00 mars kernel: message repeated 5 times: [ hid-generic 0003:3151:4010.0054: unknown main item tag 0x0]
2024-12-11T00:19:10.667421+01:00 mars kernel: hid-generic 0003:3151:4010.0054: collection stack underflow
2024-12-11T00:19:10.667424+01:00 mars kernel: hid-generic 0003:3151:4010.0054: item 0 0 0 12 parsing failed
2024-12-11T00:19:10.667425+01:00 mars kernel: hid-generic: probe of 0003:3151:4010.0054 failed with error -22

[mdvries]

Some additional findings:

So wired I get that read error as described above. If I configure the wireless option in the config file it does start sending the temps. However, the display doesn't show them. I am sure it sends it to the device as when I run the epomakercontroller with wireless it does send AND the volume control of the keyboard doesn't work anymore. When I quit the epomakercontroller the volume control works again. So when sending (wirelessly at least) to the device it blocks the volume control.