You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for your great work! It is useful and helpful. However, when I tried out it on Raspberry Pi 4B+ with the Bluetooth mode, throwing an error. The file I tried is example/leds.py and the error shown in following,
Exception in thread Thread-1:
Traceback (most recent call last):
File "/usr/lib/python3.8/threading.py", line 932, in _bootstrap_inner
self.run()
File "/usr/lib/python3.8/threading.py", line 870, in run
self._target(*self._args, **self._kwargs)
File "/home/xxx/.local/lib/python3.8/site-packages/pydualsense/pydualsense.py", line 231, in sendReport
inReport = self.device.read(self.input_report_length)
AttributeError: 'pydualsense' object has no attribute 'input_report_length'
And this is my system configuration:
System: Ubuntu Mate 20.04
Architecture: Linux 5.4.0-1118-raspi aarch64 GNU/Linux
Python: 3.8 version
Pydualsense: 0.7.1 version
To solve it, I checked the pydualsense.py and found that the class actually doesn't have this object, only the input_report_length variable. Confusedly, in the mode of the USB connection, there was no such error. I am just getting up the speed with it, so could you give me some advice?
Thanks again.
The text was updated successfully, but these errors were encountered:
Hi developers,
Thanks for your great work! It is useful and helpful. However, when I tried out it on Raspberry Pi 4B+ with the Bluetooth mode, throwing an error. The file I tried is example/leds.py and the error shown in following,
And this is my system configuration:
To solve it, I checked the pydualsense.py and found that the class actually doesn't have this object, only the input_report_length variable. Confusedly, in the mode of the USB connection, there was no such error. I am just getting up the speed with it, so could you give me some advice?
Thanks again.
The text was updated successfully, but these errors were encountered: