Open damclarkd opened 2 years ago
Yes, because Tesla has locked down the Powerwall API even for local networks, the middleware is now setup to act as the authentication layer to access the Powerwall API.
If you need further assistance for getting your middleware up and running, I am happy to assist. Just ask your questions here and I will do what I can to assist.
Hello Jason, Thank you for your assistance in this matter. I have really missed the data since using your original configuration before the Tesla lockdown.
Following your instructions, here is where I am stalling:
After npm start, I get...
@.*** start NODE_TLS_REJECT_UNAUTHORIZED='0' node app.js
Server running at http://10.1.20.45:3301 /home/pi/teslaPowerDash/middleware/api/controllers/appController.js:85 if (error) throw new Error(error); ^
Error: Error: Invalid URI "/api/login/Basic" at Request._callback (/home/pi/teslaPowerDash/middleware/api/controllers/appController.js:85:26) at self.callback (/home/pi/teslaPowerDash/middleware/node_modules/request/request.js:185:22) at Request.emit (node:events:376:20) at Request.init (/home/pi/teslaPowerDash/middleware/node_modules/request/request.js:273:17) at new Request (/home/pi/teslaPowerDash/middleware/node_modules/request/request.js:127:8) at request (/home/pi/teslaPowerDash/middleware/node_modules/request/index.js:53:10) at /home/pi/teslaPowerDash/middleware/api/controllers/appController.js:84:7 at FSReqCallback.readFileAfterClose [as oncomplete] (node:internal/fs/read_file_context:75:3)
Cannot connect to http://10.1.20.45:3301 http://10.1.20.45:3301/ in a browser.
Any thoughts?
Cheers,
On Jul 23, 2021, at 06:59, Jason Rhodes @.***> wrote:
Yes, because Tesla has locked down the Powerwall API even for local networks, the middleware is now setup to act as the authentication layer to access the Powerwall API.
If you need further assistance for getting your middleware up and running, I am happy to assist. Just ask your questions here and I will do what I can to assist.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/rhodesman/teslaPowerDash/issues/29#issuecomment-885658784, or unsubscribe https://github.com/notifications/unsubscribe-auth/AM5WU5KLQUAPFYUBC24T3UDTZFYTPANCNFSM5A23EUAQ.
Hello Erik, What is the proper way to implement the patch files?
Cheers,
https://google.com/search?q=git+patch
JK... kinda. Something like:
cd
to middleware sub-directory in checked out git codegit apply /path/to/unzipped_patch_file.patchfile
git apply
you can review what changed (should look just like patch file) with git status
and git diff
.Point taken. Thanks for the tip. Newer to git so the nudge will help.
Cheers
Sent from my iPad
On Jul 23, 2021, at 10:12 AM, Erik Persson @.***> wrote:
https://google.com/search?q=git+patch
JK... kinda. Something like:
Checkout this git repo Download and unzip patch file cd to middleware sub-directory in checked out git code git apply /path/to/unzipped_patch_file.patchfile If no errors from git apply you can review what changed (should look just like patch file) with git status and git diff. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.
@damclarkd, I actually deleted my comment from here and created a new issue as I feel like I hijacked your issue. So we should probably move the discussion of the patch to: https://github.com/rhodesman/teslaPowerDash/issues/30
Your error may be totally unrelated to my patch.
Regardless, I am interested in finding out if my patch works for others so I can decide if working up a formal PR is worth it.
While I had this all working before being updated to 20.49.0, I previously had no need for the middleware setup. After being updated to 20.49.0 a few months ago, I am now looking at getting this back up and running again. However I can't seem to get any of the middleware stuff working. Is that part of the setup now required if on 20.49.0 and above?
Cheers,
damclarkd