search

mgb / tesla-powerwall-local

7 stars 1 forks source link

Any chance of a step by step guide for this. #3

Open wrexed03 opened 3 years ago

wrexed03 commented 3 years ago

Hi i installed go... No issues there. But when running the command you have specified i received the following.

-bash: tesla-powerwall-proxy: command not found Any chance of a step by step guide. Would like to get my monitoring going once again.

mgb commented 3 years ago

Updated the README so you don't need to clone the code and can just use Go's go install directly to get a binary on your machine. Give that a try and see if that helps you along.

wrexed03 commented 3 years ago

I Tried again but no joy. go install /mgb/tesla-powerwall-local/cmd/tesla-powerwall-proxy/ can't load package: package /mgb/tesla-powerwall-local/cmd/tesla-powerwall-proxy: import "/mgb/tesla-powerwall-local/cmd/tesla-powerwall-proxy": cannot import absolute path

mgb commented 3 years ago

Try running go get github.com/mgb/tesla-powerwall-local/cmd/tesla-powerwall-proxy, which should output something like:

go: downloading github.com/mgb/tesla-powerwall-local v0.0.0-20210311041012-85ae76e4fc42
go: downloading github.com/avast/retry-go v3.0.0+incompatible
go: downloading golang.org/x/net v0.0.0-20210119194325-5f4716e94777
go get: added github.com/mgb/tesla-powerwall-local v0.0.0-20210311041012-85ae76e4fc42

Then you can install it via: go install github.com/mgb/tesla-powerwall-local/cmd/tesla-powerwall-proxy

At that point, the binary tesla-powerwall-proxy should be in your $HOME/go/bin folder, which you can confirm by running ls ~/go/bin/tesla-powerwall-proxy

If that is all true, you can then execute it: ~/go/bin/tesla-powerwall-proxy

That should dump out something like this:

2021/03/21 11:43:51 host, username, and password flags are required

If so, your binary is installed. Pass along the username, host, and password via the --host, --username, and --password flags and your proxy should be running.

wrexed03 commented 3 years ago

Awesome managed to get it going in relation to host username etc do you need to run this command every time you start the proxy? Or does it remember the details. Im no linux guru but thought i would ask. Based on the above im thinking of autostarting the proxy on startup so it just runs every time i reboot the raspberrypi if it is at all possible.