8.2 -> Still migration error

[ssieppi]

OCPP v0.8.2
HA Core 2025.2.5
Supervisor 2025.03.0
Operating System 14.2

Configuration
One Ha installation conncted to ABB terra w22

Describe the bug
After the last update from v0.64 to v.0.8.2 (also tested from v0.70 to v.0.82) got a migration error and Entities are no longer available. Deleting device "central" before update dont fix this issue (this also tested)
Also tested remove central+charger devices after 0.8.2 installation but then charger status remain unknown.
All other updates before 0.80 are fine.

Debug log
Describe the bug
A clear and concise description of what the bug is.

[ssieppi]

This is weird.. After upgrade to 0.8.2 -> migration error -> then delete "central" and "charger" then I connect from ABB mobile app to my charger -> now everything works..

[erepeo]

I don't know which version is safe anymore. I'm not touching anything until something certain is released because after one update it set the charging to 32A and overloaded the inverter... I am grateful for the Author's work but this error was already big because it affects devices at home. Of course I could update when the car was not connected but it didn't even occur to me that something like this could happen. It has never happened.

[emm-mag]

Solved this way :

Still migration error with 8.0.2
I made a whole backup of HA then removed "central" and rebooted HA
I added back ocpp and discovered charger with default settings (except the charger name) and everything seems fine !
History values are still available for ocpp entities

Thank you to author for his work 👍

[Arnoudd]

Managed to get things running again on version 8.2. I had to remove all and after reboot re-add things.

Only thing thats weird is that the current slider seems to have a max of 32A allthough I set a max of 16A while setting things up.
I used to have a max of 16A on the slider so this seems a bit risky. Am I the only one where the slider seems a bit off?

[emm-mag]

32A is fine for my use and seems to work on graphic.
I hope it'll work on next VE charge because I'm using it for dynamic charge !

[erepeo]

It worked. I'm not sure about the procedure but I think deleting 'central' and 'charger' and restarting HA and adding it again helped.

Thanks again for the work to the Author. This integration is very helpful.

[BikeMikeAU]

I'm using it for dynamic charge !

Do not use the max charge current for dynamic charge. It's value is written to storage in the charger and you will potentially wear it out with frequent updates. Use a charge profile instead. https://github.com/lbbrhzn/ocpp/wiki/Charge_automation#dynamically-adjusting-ev-charge-current-a-smart-approach

Using the example code in the link above, I extended this with an input_number slider helper, and an automation triggered on it's state. This gives me a new slider that can be adjusted manually or by other automations, without risking damage to the charger.

alias: SC1 Charge Rate
description: >-
  Shortly after the charger is switched on, or any time the charge rate slider
  is moved, set the maximum charge rate through OCPP using a charging profile.
  By using this method, it is not written to the charger flash memory and will
  not wear it out.
triggers:
  - trigger: state
    entity_id:
      - switch.sc1_charge_control
    to: "on"
    id: Switch On
  - trigger: state
    entity_id:
      - input_number.sc1_charge_rate
    id: Change Rate
conditions:
  - condition: state
    entity_id: binary_sensor.sc1_charge_cable
    state: "on"
actions:
  - if:
      - condition: trigger
        id:
          - Switch On
    then:
      - delay:
          hours: 0
          minutes: 0
          seconds: 20
          milliseconds: 0
    alias: If triggered by Switch On, delay for startup
  - if:
      - condition: state
        entity_id: switch.sc1_charge_control
        state: "on"
    then:
      - action: ocpp.set_charge_rate
        data:
          custom_profile: |
            {
              "transactionId": {{ states('sensor.sc1_transaction_id') | int }},
              "chargingProfileId": 1,
              "stackLevel": 0,
              "chargingProfilePurpose": "TxProfile",
              "chargingProfileKind": "Relative",
              "chargingSchedule": {
                "chargingRateUnit": "A",
                "chargingSchedulePeriod": [
                  {"startPeriod": 0, "limit": {{ states('input_number.sc1_charge_rate') | int }}}  
                ]
              }
            }
          conn_id: 1
    alias: If charger is on, set the charge rate
mode: queued
max: 5
trace:
  stored_traces: 25

[emm-mag]

@BikeMikeAU
Thanks a lot for this advice !
I've already setup automation based on charge status and current house load to change max current charge.
I'll use your sample and reuse my calculation.

Side note : My ABB Terra AC should handle dynamic charge by requesting current load to a modbus meter,
It works but charging stops and restart many times without explanation. I don't know if this may damage the car charger.

ABB support doesn't reply to my emails anymore - some (usefull) settings can't be changed in terra config application

[Arnoudd]

@BikeMikeAU Thanks for the info!
Just updated my load balancing script too.

[filip-heens]

Strange after deleting the OCPP integration and reinstalling it (with the reboots in between) only the central comes back. no charger.
waited more than an hours, still no charger. Then I removed the integration and reinstalled version 7.0 and directly I had my charger back.
What could be the issue in version 8.2 that it keeps failing to find the the charger? I'm using a Smappee charger...

[erepeo]

Używam go do ładowania dynamicznego!

Nie używaj maksymalnego prądu ładowania do ładowania dynamicznego. Jego wartość jest zapisywana w pamięci w ładowarce i potencjalnie zużyjesz ją dzięki częstym aktualizacjom. Zamiast tego użyj profilu ładowania. https://github.com/lbbrhzn/ocpp/wiki/Charge_automation#dynamically-adjusting-ev-charge-current-a-smart-approach

Używając przykładowego kodu w powyższym łączu, rozszerzyłem go o pomocnika suwaka numer_wejściowy i automatyzację uruchomioną w jego stanie. Daje mi to nowy suwak, który można regulować ręcznie lub za pomocą innych automatyzacji, nie ryzykując uszkodzenia ładowarki.

alias: SC1 Charge Rate
description: >-
  Shortly after the charger is switched on, or any time the charge rate slider
  is moved, set the maximum charge rate through OCPP using a charging profile.
  By using this method, it is not written to the charger flash memory and will
  not wear it out.
triggers:
  - trigger: state
    entity_id:
      - switch.sc1_charge_control
    to: "on"
    id: Switch On
  - trigger: state
    entity_id:
      - input_number.sc1_charge_rate
    id: Change Rate
conditions:
  - condition: state
    entity_id: binary_sensor.sc1_charge_cable
    state: "on"
actions:
  - if:
      - condition: trigger
        id:
          - Switch On
    then:
      - delay:
          hours: 0
          minutes: 0
          seconds: 20
          milliseconds: 0
    alias: If triggered by Switch On, delay for startup
  - if:
      - condition: state
        entity_id: switch.sc1_charge_control
        state: "on"
    then:
      - action: ocpp.set_charge_rate
        data:
          custom_profile: |
            {
              "transactionId": {{ states('sensor.sc1_transaction_id') | int }},
              "chargingProfileId": 1,
              "stackLevel": 0,
              "chargingProfilePurpose": "TxProfile",
              "chargingProfileKind": "Relative",
              "chargingSchedule": {
                "chargingRateUnit": "A",
                "chargingSchedulePeriod": [
                  {"startPeriod": 0, "limit": {{ states('input_number.sc1_charge_rate') | int }}}  
                ]
              }
            }
          conn_id: 1
    alias: If charger is on, set the charge rate
mode: queued
max: 5
trace:
  stored_traces: 25

Hello, I have a question: when using TxProfile, does the memory not wear out at all and can I modify the power even every second without worrying about EVSE, or is it not that great and is it better not to overdo it?

[BikeMikeAU]

No, charge profile will not be written to flash storage, it is temporary in RAM. However it is dependent on your charger and vehicle how quickly it responds to changes. In my experience, that's about once per minute maximum.

[erepeo]

OK, I understand. I gave the time "second" as an example of very frequent changes so that we would understand each other. I wanted to be sure that Tx is COMPLETELY safe and I can send any number of messages without worrying about the durability of the device. Thank you for the information.

[BikeMikeAU]

I made some improvements in my automation and created a separate discussion, since not related to this issue discussion
#1566