unsigned_cmds_hardlocked

[pflodo]

Log shows this when it tries to set Amps:

[07-Jan-2024 11:37:00.048 DBG TeslaSolarCharger.Server.Services.ChargingService] Adding powerbuffer 0
[07-Jan-2024 11:37:00.048 DBG TeslaSolarCharger.Server.Services.ChargingService] Averaged overage -6394
[07-Jan-2024 11:37:00.048 DBG TeslaSolarCharger.Server.Services.ChargingService] Overage after subtracting power buffer (0): -6394
[07-Jan-2024 11:37:00.048 DBG TeslaSolarCharger.Server.Services.ChargingService] Home battery min soc: null
[07-Jan-2024 11:37:00.048 DBG TeslaSolarCharger.Server.Services.ChargingService] Home battery should charging power: null
[07-Jan-2024 11:37:00.048 DBG TeslaSolarCharger.Server.Services.ChargingService] At least one car is charging.
[07-Jan-2024 11:37:00.049 DBG TeslaSolarCharger.Server.Services.ChargingService] Power to control: -6394
[07-Jan-2024 11:37:00.049 DBG TeslaSolarCharger.Server.Services.ChargingService] Amp to control: -10
[07-Jan-2024 11:37:00.049 DBG TeslaSolarCharger.Server.Services.ChargingService] Update Car amp for car Elmo
[07-Jan-2024 11:37:00.049 DBG TeslaSolarCharger.Server.Services.ChargingService] Amps to set: 6
[07-Jan-2024 11:37:00.049 DBG TeslaSolarCharger.Server.Services.ChargingService] Min amp for car: 5
[07-Jan-2024 11:37:00.049 DBG TeslaSolarCharger.Server.Services.ChargingService] Max amp for car: 16
[07-Jan-2024 11:37:00.049 DBG TeslaSolarCharger.Server.Services.ChargingService] Normal amp set
[07-Jan-2024 11:37:02.653 DBG TeslaSolarCharger.Server.Services.TeslaFleetApiService] Response: {"response":{"result":false,"reason":"unsigned_cmds_hardlocked"}}

Background:

• Long time TeslaMate user, Setting up TeslaSolarCharger:
• using latest docker image, ie FleetAPI - selected "all" when giving permissions for token
• getting GRID, SOLAR via MQTT with no issue
• 2023 Model Y plugged in via 3phase wall connector, in Tesla app I can set this between 5A and 16A (16A = 11kw)

To test I set it to PV only - and plugged in my vehicle.

When cloud comes over and there is not enough solar the UI just says not enough solar and that it will stop charging in 5 minutes. There is no change in kW. The Last Set Amp is always 0.

[pkuehnel]

You never used this car with TSC before? Looks like Tesla just enabled the need of signed commands. Just add UseFleetApiProxy=true to your environment variables of the TSC and rebuild the container with docker compose up -d. After that you get an instruction how to add the key.

[pflodo]

Correct - never setup TSC before.

I am having problems adding the virtual key.

I have removed and added the phone again - and as you can see in the error, behind, it even says "Phone key connected"

[pkuehnel]

Hmm interesting. As you are one of the first three users to enable this I don't have much experience here but I can tell you how I did it: I used a phone which has the mobile key enabled (so do you) and clicked on the link in TSC to add the key on my PC, there a QR Code is displayed which I scanned with my mobile key enabled phone. There is no need to be around the vehicle while doing that. Maybe the car needs to be awake and have internet connection during the setup process? At least your phone has pretty bad signal, does the car have too?

[pflodo]

So 24 hours later I retried and it just worked - first try - Thanks for being so responsive.

-EDIT -
the below issue was because I switched from using the teslamate MQTT server to an external, when I switched back it worked again - I am happy to use it for now, might check later why it would cause an issue, as Teslamate was happily writing to it.

Now I have a different issue, in that my car status in TSC is stuck - the car is not even at home, but it thinks that it is charging at home at 11kW. I restarted everything, but it just logs that a charging session is open (when there should be none).

Teslamate is correctly reporting the car at the same time:

[pkuehnel]

You need to change the MQTT Server in the settings of TSC (spoiler menu at the bottom of the Base Configuration). For now no authentication is supported for that MQTT Server.

[pkuehnel]

From v2.24.1 onwards this issue is auto detected and TSC automatically switches to use the FleetAPI Proxy. @pflodo thanks for adding the log message, helped me to implement the auto switch.

[pkuehnel]

@pflodo My autoswitch to use fleetapi proxy seems not to work. Sorry for that question, but could you add me as a driver for a few days to your car so I can test? It yes, please send me the invitation link to [email protected]. Would help me a lot.

[pkuehnel]

Ok looks like i fixed the issue