Hi,
sorry for my late response! I was quite busy the last weeks again. I looked a bit into your issue and the problem is due to the fact, that both plugins are using device-tree overlays.
For some reason (need to investigate) the IR plugin kills overlays that are installed by my plugin, which causes the error message.
I will try to look into it and catch the error to re-install the overlays. But this may take some time, since I am still quite packed with tasks at the moment.
Greetings, T.
no problem as long as you donāt turn it off it works fine.
Hi all,
driven by the effort of the Volumio Community to release the Bookworm version of Volumio I have taken some time to work on a Bookworm compatible version of the Plugin.
I did some significant improvements to how the plugin is working and fixed some weaknesses. The new version 2.0.0 which is now completely identical for both bookworm and buster is available on the beta channel.
Feel free to test it and let me know, if it does not work on your setups.
I did not address the issue with the IR plugin reported by michel8166 yet, but with the new structure, it should become easier to work on this soon.
Regards!
Hi Michel8166,
I did not yet work on your issue, but with version2.0.0 it might work already, if you activate the IR plugin first and then the rotary plugin, since it now does not remove all overlays anymore but add and removes only its own overlays.
However, if you deactivate the other plugin or activate it after the rotary plugin, things may still breakā¦
Let me know, if I am right.
Thank you for taking the time to update the Rotary Encoder. A few people have reported that the Rotary Encoder fails when using pin 17 (PinA) and pin 27 (PinB). Has this issue been addressed?
Hi @Wheaten,
seems that I missed that. But I would not see, why pin 17 and 27 would be a particular issue, since specification wise they are all the same. On my Bookworm Test-System I use those pins for the first rotary encoder of two without any issues (RPi5).
If you refer to this post that is solved, since onoff is no longer used.
I am not aware of any reliable method to determine, if a GPIO is in use by any other user, so if users are picking GPIOs, which are occupied by other system functions or hardware, it might be that there are issues. Also, as you know, many people do strange things with hardware.
However, on my own systems I found some timing issues, because the child-process installing the device tree overlays can return, before they are actually available (took me some time to figure out, since it did not reliably occur). I fixed that by monitoring the devices and only continue now, after they appear - that improved stability on my system significantly - may also fix other peoples issues.
1 Like
Iām sorry but I donāt use the rotary encoder anymore.
@T0MR0
Sorry for not replying sooner.
Rotary encoder works without problems including 17/27
Thanks