Closed hewasajumperboy closed 2 years ago
I've opened an issue in the busylight repo to address this problem. Spoiler alert: re-install with the latest version of busylight
and the problem should be fixed.
TIL: you can transfer issues between repos!
Transferred this issue from the blynclight repo to this repo, just because I've never had to do that before.
Fixed with commit a468d6a84f19261fc4d656d0082d852fc3ab090b and should be available on pypi with version 0.12.10:
$ python3 -m pip install -U busylight-for-humans
Awesome! Looks like this change fixed it, I haven't rebooted yet but it was able to control the light as sudo.
You shouldn't need to reboot to use the light, look at the udev-rules
sub-command of the busylight
CLI. There is more info in the README.md that talks about how to enable USB devices for non-root users when using Linux. I'm going to close this issue since the light is now recognized.
Sounds good. I've gone through the udev-rules post install steps, I had to append the new device id to the *.rules file but no dice after reloading and/or rebooting. Running as a regular user gives the "Light 0 not in range..." message. Running as sudo works to control the light.
I haven't looked into it more, it could be some weirdness with running raspbian and once I have some more time I was going to test it with ubuntu server and see if it had the same behavior.
Hey,
I'm trying to use my (probably older) light with this project. It works in the previous, depreciated blynclight repo and looking at embrava/blynclight.py the vendor id for my light doesn't show up in the list. Output from my pi below: