extensions: Logitech Litra not running

Extension

https://www.raycast.com/timrogers/logitech-litra

Description

Cannot use the Manage Devices option on the Litra extension:

The output of dirname $(which litra-on) is: /opt/homebrew/bin

/Error: Command failed: /opt/homebrew/bin/litra-devices --json
env: node: No such file or directory


env: node: No such file or directory
ChildProcess.exithandler:node:child_process:412:12
ChildProcess.emit:node:events:513:28

One note: if I run the command is trying to run manually I get a correct response:

/opt/homebrew/bin/litra-devices --json
[{"name":"Logitech Litra Glow","serial_number":"XXXXXXXXXXXXX"}]

Steps To Reproduce

  1. Download the Litra extension.
  2. Install Node.
  3. Install the Litra package.
  4. Run extension.

Current Behaviour

CleanShot 2023-03-20 at 15 04 09

Expected Behaviour

Manage the connected Litra devices.

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Comments: 20 (9 by maintainers)

Commits related to this issue

Most upvoted comments

That’s super helpful! Thanks ❤️

My thinking is that I could add an (optional) setting where you specify the path to the Node executable rather than relying on /usr/bin/env node. I think that’ll do the trick! I’ll try to do it in the next couple of days and will share a link so you can test it.

I’ve confirmed with some users that the change in https://github.com/timrogers/raycast-logitech-litra/pull/54 works. I’m going to get it pushed for review, and we should be able to get the fix into the Raycast Store very soon.

I was facing the same nvm issues as others posted. I always use the same brightness and temperature so I really just needed the ability to toggle the light on and off. My workaround was to create a simple Script Command that just runs {full-path-to-litra-nvm-install}/litra-toggle

Funny, I ended up going to same route with the simple script. Only difference was I created it using ‘Shortcuts’. This allowed me to use the built in Raycast Shortcuts functionality, allowing for quicker on/off either via Raycast or a hot key combo. I’d prefer to use this extension though, since it provides more functionality. Regardless it’s a quick work around.

FWIW, it seems to the reason it works using your own script is because my I’m able to source/load the shell variables that NVM relies on. Or to just call the path to the NVM node bin node path.