You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just see now this topic and probably it is late for the answer but I had the same issue at the time when it appeared. Did wrote to teslamotors/vehicle-command#269 the reason why BLE 4.x is not working. Changing from 2 to 0 allos using BLE versions under 5.0.
I appreciate the update and link to the Tesla update thanks. Looks like 5.0 is the minimum
5.0 zero is minimum since August '24 just because Tesla changed in vehicle-command/pkg/connector/ble/device_linux.go
ScanningFilterPolicy: 2 instead of ScanningFilterPolicy: 0. I don't see a reason for doing that change.
For those who still want to to use older version (e.g. 4.x version) just change back to ScanningFilterPolicy: 0 and recompile tesla-control. It will work for newer versions like 5.x as well.
I am using this change with my 4.2 adapter since August and works the same as an 5.x adapter including for the latest commands added in tesla-control.
I believe @guyank has got it working.
I will keep the thread open for now as I think @HiFuGa still has issues.
Originally posted by @iainbullock in tesla-local-control/tesla-local-control-addon#116 (comment)
The text was updated successfully, but these errors were encountered: