-
Notifications
You must be signed in to change notification settings - Fork 3
RFE: add a udev rule to docs #21
Comments
Thanks, I've stopped working on blynclight for the most part, focusing on busylight which supports more devices than just the Embrava BlyncLight family. Coincidentally, the |
The `blync` tool now has a subcommand "udev-rules" that will print Linux udev rules for known BlyncLight vendor identifiers to stdout or a file specified by the user. The rules are very permissive, allowing read/write access to the devices by any user on the machine.
Version 0.12.0 has the |
tyvm for the ultra quick implementation of this RFE. |
Out of curiosity, do you recall the search terms you used? It would help me improve my "SEO" for busylight. |
digging in my firefox history, it seems to have been:
Yupp, although I guess most users will Google instead of DDG. I also searched as follows May I suggest also changing "Checkout my latest project, Busylight for Humans™!" in the readme to something more clearly noting that busylight a way more advanced tool that supercedes blynclight. Maybe it's just me, but I read "Checkout my" and though, yeah advertisement is OK but I'm here to talk to my Blynclight, then my brain skipped over "latest project, Busylight " and at "for Humans™!" I thought "marketing BS, I really just need that thing to light up in 3 colours before I start this work day in earnest." and scrolled down until I found the heading "Installation" But again, this might just be me. Suggested text
|
Thank you very much for the follow up. I have to write stuffy verbiage like that for the day job and sometimes I just gotta be me (even to my detriment it seems). I'll take your recommendations under advisement and see if I can't find a happy medium that helps potential users find this software easier while still allowing me to laugh. "for Humans™" is from the 2019 April Fools PEP which advised people to write more tools "for Humans™", taking a poke at the Requests project's funny name :) Thanks again for the feedback, I appreciate it very much! |
Request for enhancement
Can you please add a few lines on udev rules to the readme?
At least on Fedora 32 a user will not be allowed to access the blynclight by default.
For my BlyncLight Plus, I created the following rule (
/etc/udev/rules.d/99-blynclight.rules
) to allow all users on this workstation read/write access to the deviceIf you have a list of all the USB IDs embrave uses, then I can make a PR if wished.
The text was updated successfully, but these errors were encountered: