Rejected currentTime message might be interpreted connector count

Oct 13, 2025 by talynt.org 74 views

Rejected currentTime message might be interpreted connector count

Introduction

When using the OCPP (Open Charge Point Protocol) integration in Home Assistant, a warning notification may appear each time the system starts or after updates to the OCPP integration. This warning is related to a rejected currentTime message and its potential interpretation as the charger having one connection. In this article, we will delve into the details of this issue and explore possible solutions.

Version of the custom_component

The version of the custom component being used is v.0.8.4. It is essential to note that if you are not using the newest version, it is recommended to download and try the latest version before opening an issue.

Configuration

The configuration file is provided below:

# Loads default set of integrations. Do not remove.
default_config:

# Load frontend themes from the themes folder
frontend:
  themes: !include_dir_merge_named themes

automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml

recorder:
  exclude:
    entities:
      # Disable recorder making entries for water usage
      # It causes miscalculations with the retrospective imports
      - sensor.water_usage_mains


http:
    use_x_forwarded_for: true
    trusted_proxies:
      - 172.21.0.10
      - 192.168.1.150

logger:
  default: warning
  logs:
     custom_components.solcast_solar: debug
     custom_components.epa_victoria_air_quality: debug
     ocpp: debug
     #ocpp: warning

Describe the bug

The warning notification is related to a rejected currentTime message and its potential interpretation as the charger having one connection. The issue is not a bug but rather a misunderstanding of the sequence of messages in the log. The entire log is provided below:

17:08:02.954 INFO (MainThread) [custom_components.ocpp] Websocket Subprotocol matched: ocpp1.6
17:08:02.954 INFO (MainThread) [custom_components.ocpp] Charger websocket path=/MySerialNumber
17:08:02.955 INFO (MainThread) [custom_components.ocpp] Charger match found for MySerialNumber:MySerialNumber
17:08:02.955 DEBUG (MainThread) [custom_components.ocpp] Central settings: CentralSystemSettings(csid='central', host='0.0.0.0', port=9000, ssl=True, ssl_certfile_path='/ocppcerts/fullchain.cer', ssl_keyfile_path='/ocppcerts/ocpp.sheppard-family.au.key', websocket_close_timeout=10, websocket_ping_interval=20, websocket_ping_timeout=20, websocket_ping_tries=2, cpids=[{'MySerialNumber': {'cpid': 'MySerialNumber', 'force_smart_charging': False, 'idle_interval': 900, 'max_current': 32, 'meter_interval': 10, 'monitored_variables': 'Current.Export,Current.Import,Current.Offered,Energy.Active.Export.Interval,Energy.Active.Export.Register,Energy.Active.Import.Interval,Energy.Active.Import.Register,Energy.Reactive.Export.Interval,Energy.Reactive.Export.Register,Energy.Reactive.Import.Interval,Energy.Reactive.Import.Register,Frequency,Power.Active.Export,Power.Active.Import,Power.Factor,Power.Offered,Power.Reactive.Export,Power.Reactive.Import,RPM,SoC,Temperature,Voltage', 'monitored_variables_autoconfig': True, 'skip_schema_validation': True}}], subprotocols=['ocpp1.6', 'ocpp2.0.1'])
17:08:02.957 INFO (MainThread) [custom_components.ocpp] Charger MySerialNumber:MySerialNumber connected to 0.0.0.0:9000.
17:08:02.957 INFO (MainThread) [custom_components.ocpp] 1 charger(s): {'MySerialNumber': 'MySerialNumber'} now connected to central system:central.
17:08:03.347 INFO (MainThread) [ocpp] MySerialNumber: receive message [2,"250311060803-40","DataTransfer",{"vendorId":"EN+","messageId":"gatewayInfo","data":"{\"SN\":\"MySerialNumber\",\"fwVer\":\"V43.178.555\",\"projectName\":\"EESP32WIIIHome3_7670_V43\",\"branch\":\"dev_home_v3\",\"gateCode\":109,\"measureType\":1,\"disconnectReason\":0,\"maxCurr\":320,\"phase\":1,\"netType\":1,\"chgMode\":0,\"sdCardStatus\":1,\"sdCardFreeSize\":109352,\"rateCurrent\":32}"}]
17:08:03.348 DEBUG (MainThread) [custom_components.ocpp] Data transfer received from MySerialNumber: {'message_id': 'gatewayInfo', 'data': '{"SN":"MySerialNumber","fwVer":"V43.178.555","projectName":"EESP32WIIIHome3_7670_V43","branch":"dev_home_v3","gateCode":109,"measureType":1,"disconnectReason":0,"maxCurr":320,"phase":1,"netType":1,"chgMode":0,"sdCardStatus":1,"sdCardFreeSize":109352,"rateCurrent":32}'}
17:08:03.348 INFO (MainThread) [ocpp] MySerialNumber: send [3,"250311060803-40",{"status":"Accepted"}]
17:08:03.837 INFO (MainThread) [ocpp] MySerialNumber: receive message [2,"250311060803-41","DataTransfer",{"vendorId":"EN+","messageId":"cpCapabilityInfoRpt","data":"{\"availableOperationMode\":[\"NETWORK\",\"BLUETOOTH\",\"EMS\"],\"supportPlugAndPlayFeatureOnNetwork\":true,\"supportPlugAndPlayFeatureOnBluetooth\":true,\"supportConnectorLock\":false,\"bluetoothAlwaysOpenOrOther\":true,\"supportBluetoothConfigNetwork\":true,\"supportBluetoothMode\":true,\"bluetoothEncrypted\":true,\"supportApMode\":true,\"supportRemoteStartTransactionWithProfile\":true,\"supportSingleLoadBalance\":true,\"supportConnectorLockStatusRpt\":false,\"supportLightQuietSetting\":true,\"supportHttps\":true,\"loadBalanceCapability\":{\"supportMeasureTypes\":[\"CT\",\"METER\",\"CT_AND_METER\"],\"supportCTRadios\":[\"100:5\",\"150:5\",\"1000:1\"],\"supportGreenMode\":true,\"greenModeCapability\":{\"supportEcoMode\":true,\"supportMixMode\":true,\"supportMultiModeMerge\":true}}}"}]
17:08:03.838 DEBUG (MainThread) [custom_components.ocpp] Data transfer received from MySerialNumber: {'message_id': 'cpCapabilityInfoRpt', 'data': '{"availableOperationMode":["NETWORK","BLUETOOTH","EMS"],"supportPlugAndPlayFeatureOnNetwork":true,"supportPlugAndPlayFeatureOnBluetooth":true,"supportConnectorLock":false,"bluetoothAlwaysOpenOrOther":true,"supportBluetoothConfigNetwork":true,"supportBluetoothMode":true,"bluetoothEncrypted":true,"supportApMode":true,"supportRemoteStartTransactionWithProfile":true,"supportSingleLoadBalance":true,"supportConnectorLockStatusRpt":false,"supportLightQuietSetting":true,"supportHttps":true,"loadBalanceCapability":{"supportMeasureTypes":["CT","METER","CT_AND_METER"],"supportCTRadios":["100:5","150:5","1000:1"],"supportGreenMode":true,"greenModeCapability":{"supportEcoMode":true,"supportMixMode":true,"supportMultiModeMerge":true}}}'}
17:08:03.838 INFO (MainThread) [ocpp] MySerialNumber: send [3,"250311060803-41",{"status":"Accepted"}]
17:08:12.961 INFO (MainThread) [ocpp] MySerialNumber: send [2,"fa10a465-58cf-4902-b558-38e10645e4e9","GetConfiguration",{"key":["SupportedFeatureProfiles"]}]
17:08:13.709 INFO (MainThread) [ocpp] MySerialNumber: receive message [3,"fa10a465-58cf-4902-b558-38e10645e4e9",{"configurationKey":[{"key":"SupportedFeatureProfiles","value":"Core,Reservation,FirmwareManagement,LocalAuthListManagement,RemoteTrigger,SmartCharging","readonly":true}],"unknownKey":[]}]
17:08:13.714 DEBUG (MainThread) [custom_components.ocpp] Feature profiles returned: Profiles.CORE|FW|SMART|RES|REM|AUTH
17:08:13.718 INFO (MainThread) [ocpp] MySerialNumber: send [2,"74552db3-f1b8-4989-a58f-135c99075a09","GetConfiguration",{"key":["NumberOfConnectors"]}]
17:08:14.198 INFO (MainThread) [ocpp] MySerialNumber: receive message [3,"74552db3-f1b8-4989-a58f-135c99075a09",{"configurationKey":[{"key":"NumberOfConnectors","value":"1","readonly":true}],"unknownKey":[]}]
17:08:14.202 DEBUG (MainThread) [custom_components.ocpp] Get Configuration for NumberOfConnectors: 1
17:08:14.204 INFO (MainThread) [ocpp] MySerialNumber: send [2,"032ff2fd-ea97-40dd-8b67-cbeb4b083dd6","GetConfiguration",{"key":["HeartbeatInterval"]}]
17:08:14.677 INFO (MainThread<br/>
**Rejected currentTime message might be interpreted connector count**

**Q&A**

**Q: What is the issue with the OCPP integration in Home Assistant?**

A: The issue is related to a rejected `currentTime` message and its potential interpretation as the charger having one connection.

**Q: What is the rejected `currentTime` message?**

A: The rejected `currentTime` message is a message sent by the OCPP central station to the charger, which is rejected by the charger.

**Q: Why is the rejected `currentTime` message being interpreted as the charger having one connection?**

A: The rejected `currentTime` message is being interpreted as the charger having one connection because the OCPP integration in Home Assistant is not correctly handling the sequence of messages in the log.

**Q: What is the sequence of messages in the log?**

A: The sequence of messages in the log is as follows:

1. The OCPP central station sends a `currentTime` message to the charger.
2. The charger rejects the `currentTime` message.
3. The OCPP integration in Home Assistant interprets the rejected `currentTime` message as the charger having one connection.

**Q: Why is this interpretation incorrect?**

A: This interpretation is incorrect because the rejected `currentTime` message is not related to the number of connections on the charger.

**Q: What can be done to fix this issue?**

A: To fix this issue, the OCPP integration in Home Assistant needs to be updated to correctly handle the sequence of messages in the log.

**Q: How can I update the OCPP integration in Home Assistant?**

A: To update the OCPP integration in Home Assistant, you can follow these steps:

1. Check the Home Assistant documentation for the latest version of the OCPP integration.
2. Download the latest version of the OCPP integration.
3. Install the latest version of the OCPP integration.
4. Configure the OCPP integration to use the correct sequence of messages in the log.

**Q: What are the benefits of updating the OCPP integration in Home Assistant?**

A: The benefits of updating the OCPP integration in Home Assistant include:

1. Correct handling of the sequence of messages in the log.
2. Improved accuracy of the number of connections on the charger.
3. Reduced errors and warnings in the log.

**Q: How can I troubleshoot this issue?**

A: To troubleshoot this issue, you can follow these steps:

1. Check the log for any errors or warnings related to the OCPP integration.
2. Verify that the OCPP integration is correctly configured.
3. Check the sequence of messages in the log to ensure that it is correct.
4. Update the OCPP integration to the latest version.

**Q: What are the common causes of this issue?**

A: The common causes of this issue include:

1. Incorrect configuration of the OCPP integration.
2. Incorrect handling of the sequence of messages in the log.
3. Outdated version of the OCPP integration.

**Q: How can I prevent this issue from occurring in the future?**

A: To prevent this issue from occurring in the future, you can follow these steps:

1. Regularly update the OCPP integration to the latest version.
2. Verify that the OCPP integration is correctly configured.
3. Check the sequence of messages in the log to ensure that it is correct.