For a device that returns the following information with the lux devices complex:

DEVICE 0
  MAC Address:    E1:18:D4:AD:FC:32:23:92
  Model:          H6008
  Name:           East bulb
  Controllable:   [✓ Yes]
  Retrievable:    [✓ Yes]
  Commands:       turn, brightness, color, colorTem

This error is given following the shown command:

lux color 0 #ff0000
Not enough arguments required. E.g. lux color 0 #0067f4

The command used is taken right from the examples shown after lux help.

I can't determine any error on my part, and other commands such as lux turn 0 on/off and lux brightness 0/00 works as expected.

lux help
Welcome to Lux!
Lux v1.1.0

Is there something I'm missing?

Bumps github.com/AlecAivazis/survey/v2 from 2.3.4 to 2.3.5.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

• [x] Brightness command
• [x] Color command
• [x] Devices command
• [x] Help command
• [x] Query command
• [x] Setup command
• [x] Turn command

Also

• [x] Add version command

I noticed when trying to get some additional information about each of my devices that the lux devices... commands all output the same information. See below for the output of all three commands on my installation.

PS C:\Users\Beau> lux devices
DEVICE 0
  Name:           East bulb
  Model:          H6008
  Controllable:   [✓ Yes]
DEVICE 1
  Name:           Bedroom B
  Model:          H6008
  Controllable:   [✓ Yes]
DEVICE 2
  Name:           Bedroom A
  Model:          H6008
  Controllable:   [✓ Yes]
DEVICE 3
  Name:           North bulb
  Model:          H6008
  Controllable:   [✓ Yes]
DEVICE 4
  Name:           South-east bulb
  Model:          H6008
  Controllable:   [✓ Yes]
DEVICE 5
  Name:           South-west bulb
  Model:          H6008
  Controllable:   [✓ Yes]
PS C:\Users\Beau> # lux devices complex output

PS C:\Users\Beau> lux devices complex
DEVICE 0
  Name:           East bulb
  Model:          H6008
  Controllable:   [✓ Yes]
DEVICE 1
  Name:           Bedroom B
  Model:          H6008
  Controllable:   [✓ Yes]
DEVICE 2
  Name:           Bedroom A
  Model:          H6008
  Controllable:   [✓ Yes]
DEVICE 3
  Name:           North bulb
  Model:          H6008
  Controllable:   [✓ Yes]
DEVICE 4
  Name:           South-east bulb
  Model:          H6008
  Controllable:   [✓ Yes]
DEVICE 5
  Name:           South-west bulb
  Model:          H6008
  Controllable:   [✓ Yes]
PS C:\Users\Beau> # lux devices simple output

PS C:\Users\Beau> lux devices simple
DEVICE 0
  Name:           East bulb
  Model:          H6008
  Controllable:   [✓ Yes]
DEVICE 1
  Name:           Bedroom B
  Model:          H6008
  Controllable:   [✓ Yes]
DEVICE 2
  Name:           Bedroom A
  Model:          H6008
  Controllable:   [✓ Yes]
DEVICE 3
  Name:           North bulb
  Model:          H6008
  Controllable:   [✓ Yes]
DEVICE 4
  Name:           South-east bulb
  Model:          H6008
  Controllable:   [✓ Yes]
DEVICE 5
  Name:           South-west bulb
  Model:          H6008
  Controllable:   [✓ Yes]

I don't believe this is the intended output for these commands, except for perhaps the "simple" version. If this is a work-in-progress feature that hasn't been fully implemented and I missed where that was noted, please accept my apologies.

Lux instance info:

  logged in       [✓ Yes]
  description     Lux is a cli for controlling and monitoring Govee lighting strips
  build           v1.1.1 (x64)
  license         GPL-3.0
  repository      https://github.com/bandev/lux
  up to date      [✓ Yes]

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

Detected Package Files

• .github/workflows/go.yml (github-actions)
• go.mod (gomod)

Configuration

🔡 Renovate has detected a custom config for this PR. Feel free to ask for help if you have any doubts and would like it reviewed.

Important: Now that this branch is edited, Renovate can't rebase it from the base branch any more. If you make changes to the base branch that could impact this onboarding PR, please merge them manually.

What to Expect

It looks like your repository dependencies are already up-to-date and no Pull Requests will be necessary right away.

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section. If you need any further assistance then you can also request help here.

This PR has been generated by WhiteSource Renovate. View repository job log here.

• Updates actions/checkout to v3 from v2.
• Updates actions/setup-go to v3 from v2.
• Removes the hardcoded Go version so the workflow can now always build on the latest stable version of Go.
• Add 'Lux' to command name to clarify what the last section of the workflow is doing.

Bumps github.com/AlecAivazis/survey/v2 from 2.3.2 to 2.3.4.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Bumps github.com/AlecAivazis/survey/v2 from 2.3.2 to 2.3.3.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Should our first chocolatey release be v1.1.0, do you think?

Originally posted by @russellbanks in https://github.com/BanDev/Lux/issues/16#issuecomment-975892632

Add setup command

Provides the user with a better way to access their Govee account through lux.

Merge Checklist

• [x] Follows lux design guidelines (Github Primer)
• [x] API Key is stored
• [x] API Key is checked before storage
• [x] Shows a warning when a user is already authenticated
• [ ] Key setup tutorial page live
• [x] Command has been added to bandev.uk api

Design

Implements major design queues from Github Cli Guidelines & AlecAivazis/survey

The user is asked if they have an API Key

If they have one, they are prompted to enter it

Otherwise, they are prompted to follow a tutorial detailing how to create one

This pull request adds a workflow that automatically publishes Lux to WinGet every release. Please do not merge this pull request without reading the below and making the required changes (The token part is the important bit) :)

• runs-on: windows-latest

The WinGet Releaser action can only run on Windows.

• identifier: JackDevey.Lux

This is the identifier for Lux on Winget. It will use this to find Lux's current package on WinGet.

• installers-regex: '\.exe$'

This will make all .exe files in the assets of the latest Lux release to be included in the pull request (The x64 and x86 variation of Lux).

• delete-previous-version: 'true'

This is optional, and you are welcome to change this to false (or omit it; the default is false). This will essentially overwrite the previous version on WinGet packages, so that only this new version is stored on WinGet.

• token: ${{ secrets.WINGET_TOKEN }}

This is the bit that will require action from yourself. This is a GitHub token with which the action will authenticate with GitHub and create a pull request on the winget-pkgs repository.

To do this, you will need to:

1. Create a Personal Access Token (PAT) with public_repo scope on your GitHub account.

2. Create a repository secret containing the token. Super important: call this token: WINGET_TOKEN. See using encrypted secrets in a workflow for more details.

Finally, make sure you have a fork of winget-pkgs on your GitHub account. Please do not delete the fork after a pull request has been merged as the action will use that fork for making a branch and merging it with the upstream winget-pkgs repository on every Lux release.

The above is made on the assumption that the account that the token is from (and the fork is present) is @jackdevey. If you would like this to be done by another account, the token would have to be from the different user and an extra line would have to be added: fork-user: # Username of other user (this defaults to the repository owner, which is why it doesn't have to be added)

If you would like to read about this action further, the documentation is here and the source code is here.

If you are interested in what a pull request made by this action looks like, here is one from my account: #61982 on winget-pkgs.

Bumps github.com/AlecAivazis/survey/v2 from 2.3.4 to 2.3.6.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Describe the bug A clear and concise description of what the bug is.

To Reproduce Steps to reproduce the behavior:

1. Send any command aside from query to an H6163 light strip
2. It will display "success" but not actually change

Expected behavior The requested change is carried out.

Desktop (please complete the following information):

• OS: Windows 10

Additional context Example of command being carried out attached. I don't know what logs or other information is required to fix this, but I'm happy to provide whatever info I can. Thanks!

C:\Users\Leet>lux query 0
QUERY 0
  Device:         [removed MAC address]
  Model:          H6163
  Online:         [✗ No]
  Power:          [✓ Yes]
  Brightness:     10%
  Colour:         #000000

C:\Users\Leet>lux turn 0 off
TURN 0 OFF
  power           [✗ No]
  transaction     Success

C:\Users\Leet>lux query 0
QUERY 0
  Device:         [removed MAC address]
  Model:          H6163
  Online:         [✗ No]
  Power:          [✓ Yes]
  Brightness:     10%
  Colour:         #000000