I think that requires actually connecting a physical dial to the GPIO pins on the Pi (which I could probably figure out) and then a bunch LINUX code magic, which I cannot
I tried the PlugIn with the MS Surface Dial connected via BT but no joy.
Correct… a rotary encoder and the relevent componants connected to the GPIO pins.
No none of that is needed, all you have to do is configure the rotary encoder II plugin with the correct details.
Not 100% sure what you mean by this, but I have a external volume control that sits on the arm of my chair with a 1.2 meter cable running to my Volumio box with zero issues
The 1/2 watt resistors are a little excessive but they will do.
And ideally a 100nf capacitor between ground and each of the gpio’s. Just to make the action acurate and stable.
If you are also using the button on the rotary bear in mind there is no pull up resistor on the CYT1062’s for the switch.
That’s EXACTLY what I wanted to do. I got a Microsoft Surface Dial, got it connected to the device but couldn’t figure out where to go from there. Would what you have above work or does it need to be customized for each device?
Thanks… that level of code awareness is beyond me - I’m hardware guy with great Photo editing skills and zero coding ability. If I could hire someone to write it for me - that’s another skill
I already gave you the complete code all you have to do is get the proper events as instructed.
I get the impression your better in asking questions than in reading?
I literally have no idea what do with the code or how to “get” the events. I’ve read through it but it’s just a wall of text that assumes you understand the coding and instruction set.
Sorry to be a bother and you can go ahead and consider this closed - this has skill requirements above what I have or am willing to invest the time to learn so I’ll just another option for volume control.
type: cat /dev/input/event0
press buttons and see if there is a response, if yes note it down and continue to the next cat /dev/input/event1
press buttons and see if there is a response, if yes note it down and continue to the next cat /dev/input/eventx
so if in your case event1 and event2 triggers a response update the code:
mousea = InputDevice(‘/dev/input/event1’)
mouseb = InputDevice(‘/dev/input/event2’)
and change for device in mousea, mouseb, mousec, moused:
to for device in mousea, mouseb:
Aug 01 01:33:29 volumio systemd[1]: Started BlueTooth Mouse Plugin.
Aug 01 01:33:29 volumio sudo[3346]: pam_unix(sudo:session): session closed for user root
Aug 01 01:33:29 volumio python3[3349]: device /dev/input/event5, name “Surface Dial System Multi Axis”, phys “D8:3A:DD:AD:26:C5”
Aug 01 01:33:29 volumio python3[3349]: === Start ===
Aug 01 01:33:29 volumio python3[3349]: Traceback (most recent call last):
Aug 01 01:33:29 volumio python3[3349]: File “/home/volumio/mouse.py”, line 46, in
Aug 01 01:33:29 volumio python3[3349]: for device in mousea:
Aug 01 01:33:29 volumio python3[3349]: TypeError: ‘InputDevice’ object is not iterable
Aug 01 01:33:29 volumio systemd[1]: btmouse.service: Main process exited, code=exited, status=1/FAILURE
Aug 01 01:33:29 volumio systemd[1]: btmouse.service: Failed with result ‘exit-code’.
Also, are all the pcieport & nvme error messages normal?