Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

error: invalid choice ' config.yaml #28

Closed
djryan012 opened this issue Jan 3, 2018 · 2 comments
Closed

error: invalid choice ' config.yaml #28

djryan012 opened this issue Jan 3, 2018 · 2 comments

Comments

@djryan012
Copy link
Contributor

I got thru the entire install process but got an error when running insteon-mqtt start config.yaml. Config is setup correctly, except I think it doesn't know how to talk to my 2014 hub. I can use the insteon terminal just fine but useing the "connectToMyHub()" connection which i couldnt find in insteon-mqtt.

'def connectToMyHub():
#connects to my insteon hub modem at pre-defined address
connectToHub("192.168.0.xxx", 25105, 1000, "hubuser", "hubpassword")

Here is the error i got

'(insteon-mqtt) insteon@ubuntu:/opt/insteon-mqtt$ insteon-mqtt start config.yaml
usage: insteon-mqtt [-h]
config.yaml
{start,refresh-all,linking,refresh,get-flags,set-flags,on,set,off,up,down,scene,pair,db-add,db-delete,set-button-led,print-db}
...
insteon-mqtt: error: invalid choice: 'config.yaml' (choose from 'start', 'refresh-all', 'linking', 'refresh', 'get-flags', 'set-flags', 'on', 'set', 'off', 'up', 'down', 'scene', 'pair', 'db-add', 'db-delete', 'set-button-led', 'print-db')

Not sure why getting error if start is a choice and is in command line.

@TD22057
Copy link
Owner

TD22057 commented Jan 3, 2018

The error is saying that the order is wrong. I moved the config.yaml before the commands because it made things simpler to run from the command line and missed some references in the docs.
Run insteon-mqtt config.yaml start

@bfranske
Copy link

bfranske commented Jan 3, 2018

Just ran across this myself this morning, see my issue #27

There are several places in the docs where this is still backwards. As Ted said, it should be config.yaml then start anywhere you see those two listed.

@TD22057 TD22057 closed this as completed in 907dabd Jan 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants