-
Notifications
You must be signed in to change notification settings - Fork 11
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
problems with openTrunk and setTemps #21
Comments
Ok, I solved the openTrunk problem. But the setTemps problem I can not figure out the problem. Does anybody has the same problem? |
I will look into it. |
How did you solve the openTrunk problem? What exact syntax for the commandArgs did you use? |
I have also the Problem with the open Trunk and Frunk command. Debug give back "invalid_value" what is the right value. 1 or true didn't work |
Hi folks in tesla.js the line around 90 (openTrunk) has to be adapted. I deleted the line and added the following: |
Thanks, I'll try this. |
A last question on the setTemp driver and passanger issue (see first comment): It seems, that it does not work for a Model3. Can anybody confirm that. For wich model does it work? |
@Langer75 |
Hi, I tried it, but for me it didn't worked... Any Ideas |
In the current Version openTrunk and openFrunc lines are already there. But the parameters have to be adapted (front and rear) |
@andijegg Just curious if your issue is with the TeslaJS library instead of this one. |
I don't know how to do this... sry |
@andijegg Gotcha, well just out of curiosity - do other calls from node-red work? Can you open the charge port for instance? |
Yes other work. Open/Close Car Open Charge Port etc. And yes I've restarted the node-red instance after updating the tesla.js file. |
@andijegg Anything appear in a debug message payload from the openFrunk node? |
Yes the same as in the Picture above. „false“ and „invalide_value“ |
It must not be picking up the change you made. What's the file path of your tesla.js that you edited? |
/home/pi/node_modules/node-red-contrib-tesla/tesla.js |
Kind of a long shot here, but from your home directory, what do you see when you run:
Just that one file? Or does it find another? |
It finds two... ./.node-red/node_modules/node-red-contrib-tesla/src/tesla.js |
Ah, alright - the one you want is that first one: |
both files have the "front" "rear" edit, I've just checked it... |
Hm, must be symlinked. Can you reboot the whole machine just to make sure the instance is being restarted? Everything looks fine, not sure what else to suggest here. |
I‘ll try a restart and report the result |
There was 3 files... my fault, in the third file, were still the old paterns. I changed it an now it works fine... Thank you for the help! |
Hah, I almost asked about that one too.. Glad to hear it's working! |
Hi, I am new with Tesla and I got nearly all function running with my Model 3. Two function will not work as expected:
openTrunk. it is stated that no commandArgs are necessary. How can I distingush between trunk and frunk? I read in the tesla.js github project that it was changed to "rear" and "front" But how can I pass these parameters to openTrunk. Currently it does not work at all.
With set Temp I have the effect that it does not matter whether I pass cammandArgs.driver or commandArgs.pass to setTemps. Both values are changed to the same value. Is this a bug or did I something wrong?
Thanks for your help
Langer
The text was updated successfully, but these errors were encountered: