Scame WallBox NetMaster

[Korkki87]

Hi!

I have a Scame Wall Box NetMaster 22kw charger that is supported by OCPP 1.6. The integration connects to the HA, but I get four warnings after boot:

  WARNING (MainThread) [custom_components.ocpp] Rejected while setting MeterValuesSampledData to Energy.Active.Import.Register,Energy.Reactive.Import.Register,Energy.Active.Import.Interval,Energy.Reactive.Import.Interval,Power.Active.Import,Power.Reactive.Import,Power.Offered,Power.Factor,Current.Import,Current.Offered,Voltage,Frequency,RPM,SoC,Temperature,Current.Export,Energy.Active.Export.Register,Energy.Reactive.Export.Register,Energy.Active.Export.Interval,Energy.Reactive.Export.Interval,Power.Active.Export,Power.Reactive.Export
  
  WARNING (MainThread) [custom_components.ocpp] ClockAlignedDataInterval is a read only setting
  
  WARNING (MainThread) [custom_components.ocpp] Rejected while setting ClockAlignedDataInterval to 900
  
  WARNING (MainThread) [custom_components.ocpp] WebSocketPingInterval is unknown (not supported)

I have not been able to test the cahrger with a car yet, but I can use the available and reeboot buttons from HA, but the max power (Amp) selector does not seem to work.

Any ideas for solution to fix those warnings? (that shoud be the first step to get this thing going)

Manual fot the device:
(https://www.emobility-scame.com/documents/20125/1254251/User-manual-charging-stations-AC_ZP91114-GB-7.pdf/abe3a44c-a985-289c-e2cf-1421a2d2308a?t=1680882013903)

HA Log:
home-assistant_2023-06-20T16-24-26.158Z.log

Scame 1.6 JSON settings:

charger Entities I get from HA:

[Korkki87]

Also there are setup for 1.6 JSON like this:

[Korkki87]

And I can't get any Sensor data from charger (I think i should)

[Korkki87]

Just selecting the right sensor data from the integration startup menu, I got rid of the MeterValueSampledData error. Altought I still got some problems. I can not change the maximum current for the charger. I get these warnings:

  Logger: homeassistant.components.websocket_api.http.connection
  Source: custom_components/ocpp/api.py:582
  Integration: Home Assistant WebSocket API (documentation, issues)
  First occurred: 00.08.10 (2 occurrences)
  Last logged: 00.08.11
  
  [140265424877776] argument of type 'NoneType' is not iterable
  Traceback (most recent call last):
    File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 205, in handle_call_service
      await hass.services.async_call(
    File "/usr/src/homeassistant/homeassistant/core.py", line 1910, in async_call
      task.result()
    File "/usr/src/homeassistant/homeassistant/core.py", line 1950, in _execute_service
      await cast(Callable[[ServiceCall], Awaitable[None]], handler.job.target)(
    File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 226, in handle_service
      await service.entity_service_call(
    File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 811, in entity_service_call
      future.result()  # pop exception if have
      ^^^^^^^^^^^^^^^
    File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1034, in async_request_call
      await coro
    File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 851, in _handle_entity_call
      await result
    File "/usr/src/homeassistant/homeassistant/components/number/__init__.py", line 106, in async_set_value
      await entity.async_set_native_value(native_value)
    File "/config/custom_components/ocpp/number.py", line 127, in async_set_native_value
      resp = await self.central_system.set_max_charge_rate_amps(
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File "/config/custom_components/ocpp/api.py", line 281, in set_max_charge_rate_amps
      return await self.charge_points[cp_id].set_charge_rate(limit_amps=value)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File "/config/custom_components/ocpp/api.py", line 582, in set_charge_rate
      if resp is None:
         ^^^^^^^^^^^^^^
  TypeError: argument of type 'NoneType' is not iterable

And:

Logger: custom_components.ocpp
Source: custom_components/ocpp/api.py:281
Integration: Open Charge Point Protocol (OCPP) (documentation, issues)
First occurred: 00.08.10 (2 occurrences)
Last logged: 00.08.11

Get Configuration returned unknown key for: ChargingScheduleAllowedChargingRateUnit

Also I have this ClockAlignedDataInterval Warning. If I understand right, OCPP integration shuld be able to change the value to the Chargers setup and when it's trying to do that we gety that error. Th setup point is grey in the charger menu, so I can't change it there to that 900 it's asking. Is it so that the value has been set to read only and it can not change it, or because it could not change it, it's read only? So is the problem with the integration or with the charger setup?

Logger: custom_components.ocpp
Source: custom_components/ocpp/api.py:433
Integration: Open Charge Point Protocol (OCPP) (documentation, issues)
First occurred: 00.06.45 (2 occurrences)
Last logged: 00.06.45

ClockAlignedDataInterval is a read only setting
Rejected while setting ClockAlignedDataInterval to 900

[Korkki87]

Got rid of the ChargingSchedule problem, when made a new integration setup with no selection to that "Force Smart Charging feature profile". Now I'm in a situation, that after startup warnings I won't get them more.. But it seems that the max amp change is not working. I'll have to get some car to plug in to test.. My new one is over 7 months late already..

[Korkki87]

Had a possibility to try the setup with my friends car (still waiting for my own). It was possible to start and stop the charging from the HA, but the max current set didn't work, but it did not gave any fault log for that, or I did not recognize it. The max current limit worked great when I made it straigth from the charger setup.

What i got was :

Logger: homeassistant.components.sensor
Source: components/sensor/__init__.py:650
Integration: Sensori (documentation, issues)
First occurred: 1. heinäkuuta 2023 klo 22.25.04 (1 occurrences)
Last logged: 1. heinäkuuta 2023 klo 22.25.04

Entity sensor.charger_energy_reactive_import_register (<class 'custom_components.ocpp.sensor.ChargePointMetric'>) is using native unit of measurement 'UnitOfMeasure.kvarh' which is not a valid unit for the device class ('energy') it is using; expected one of ['MJ', 'MWh', 'GJ', 'kWh', 'Wh']; Please update your configuration if your entity is manually configured, otherwise report it to the custom integration author.

[Korkki87]

Still speaking here with myself, but..

For some reason, the Integration started to send ClockAlignedInterval to 0 sec, (as I wanted it) an the Warning hase gone away, Still having issues with the WebSocketPingInterval. Tried different values, but does not make any difference. Sent a message to the Scame, if they would send me a OCPP keys that are recommended to this charger.. Will see, will the answer anything.

Also the maximum_current slider, does not give any log lines, that the integrations even tries to send a message to the charger to set the maximum_current? Do I have to Open a Case?

2023-07-04 17:47:53.020 INFO (MainThread) [ocpp] 100231998: send [2,"024a39f9-f52e-4a8f-84cb-fa9bc97529a7","Reset",{"type":"Hard"}]
2023-07-04 17:47:53.054 INFO (MainThread) [ocpp] 100231998: receive message [3,"024a39f9-f52e-4a8f-84cb-fa9bc97529a7",{"status":"Accepted"}]
2023-07-04 17:47:56.370 DEBUG (MainThread) [custom_components.ocpp] Connection latency from 'central' to '100231998': ping=1.0 ms, pong=4.0 ms
2023-07-04 17:47:59.018 DEBUG (MainThread) [custom_components.ocpp] Connection closed to '100231998': no close frame received or sent
2023-07-04 17:47:59.018 INFO (MainThread) [custom_components.ocpp] Charger 100231998 disconnected from 0.0.0.0:9000.
2023-07-04 17:48:49.940 INFO (MainThread) [custom_components.ocpp] Websocket Subprotocol matched: ocpp1.6
2023-07-04 17:48:49.940 INFO (MainThread) [custom_components.ocpp] Charger websocket path=/ws:/192.168.3.3:9000/100231998
2023-07-04 17:48:49.940 INFO (MainThread) [custom_components.ocpp] Charger 100231998 reconnected to 0.0.0.0:9000.
2023-07-04 17:48:49.940 DEBUG (MainThread) [custom_components.ocpp] Reconnect websocket to 100231998
2023-07-04 17:48:50.063 INFO (MainThread) [ocpp] 100231998: receive message [2,"5e8623c0-a1e9-11e6-8d65-4b5064ba5c67","BootNotification",{"chargePointVendor":"Scame Parre S.p.A.","chargePointModel":"SBC-0","chargePointSerialNumber":"2041SBB17687","firmwareVersion":"1.3.11"}]
2023-07-04 17:48:50.064 DEBUG (MainThread) [custom_components.ocpp] Received boot notification for 100231998: {'charge_point_vendor': 'Scame Parre S.p.A.', 'charge_point_model': 'SBC-0', 'charge_point_serial_number': '2041SBB17687', 'firmware_version': '1.3.11'}
2023-07-04 17:48:50.064 INFO (MainThread) [ocpp] 100231998: send [3,"5e8623c0-a1e9-11e6-8d65-4b5064ba5c67",{"currentTime":"2023-07-04T14:48:50Z","interval":3600,"status":"Accepted"}]
2023-07-04 17:48:50.065 DEBUG (MainThread) [custom_components.ocpp] Updating device info charger: {'charge_point_vendor': 'Scame Parre S.p.A.', 'charge_point_model': 'SBC-0', 'charge_point_serial_number': '2041SBB17687', 'firmware_version': '1.3.11'}
2023-07-04 17:48:51.436 INFO (MainThread) [ocpp] 100231998: receive message [2,"e3f19750-1a79-11ee-8d65-4b5064ba5c67","StatusNotification",{"connectorId":1,"status":"Available","errorCode":"NoError","info":"0","timestamp":"2023-07-04T14:48:51.264Z","vendorId":"","vendorErrorCode":""}]
2023-07-04 17:48:51.438 INFO (MainThread) [ocpp] 100231998: send [3,"e3f19750-1a79-11ee-8d65-4b5064ba5c67",{}]
2023-07-04 17:48:52.068 INFO (MainThread) [ocpp] 100231998: send [2,"86814a74-9213-4dc4-8eb0-e1fbb56bbe4a","GetConfiguration",{"key":["SupportedFeatureProfiles"]}]
2023-07-04 17:48:52.141 INFO (MainThread) [ocpp] 100231998: receive message [3,"86814a74-9213-4dc4-8eb0-e1fbb56bbe4a",{"configurationKey":[{"key":"SupportedFeatureProfiles","readonly":true,"value":"Core,FirmwareManagement,LocalAuthListManagement,Reservation"}]}]
2023-07-04 17:48:52.142 DEBUG (MainThread) [custom_components.ocpp] Feature profiles returned: 43
2023-07-04 17:48:52.143 INFO (MainThread) [ocpp] 100231998: send [2,"4d6a5f25-73d7-45be-918f-9c1f3eeb5b3c","GetConfiguration",{"key":["NumberOfConnectors"]}]
2023-07-04 17:48:52.200 INFO (MainThread) [ocpp] 100231998: receive message [3,"4d6a5f25-73d7-45be-918f-9c1f3eeb5b3c",{"configurationKey":[{"key":"NumberOfConnectors","readonly":true,"value":"1"}]}]
2023-07-04 17:48:52.200 DEBUG (MainThread) [custom_components.ocpp] Get Configuration for NumberOfConnectors: 1
2023-07-04 17:48:52.201 INFO (MainThread) [ocpp] 100231998: send [2,"3f5b086d-5037-42e5-970c-f68341c958f9","GetConfiguration",{"key":["HeartbeatInterval"]}]
2023-07-04 17:48:52.248 INFO (MainThread) [ocpp] 100231998: receive message [3,"3f5b086d-5037-42e5-970c-f68341c958f9",{"configurationKey":[{"key":"HeartbeatInterval","readonly":false,"value":"3600"}]}]
2023-07-04 17:48:52.248 DEBUG (MainThread) [custom_components.ocpp] Get Configuration for HeartbeatInterval: 3600
2023-07-04 17:48:52.248 INFO (MainThread) [ocpp] 100231998: send [2,"d1ae3f99-3434-444a-bf0f-9e6ed126bc9e","GetConfiguration",{"key":["MeterValuesSampledData"]}]
2023-07-04 17:48:52.297 INFO (MainThread) [ocpp] 100231998: receive message [3,"d1ae3f99-3434-444a-bf0f-9e6ed126bc9e",{"configurationKey":[{"key":"MeterValuesSampledData","readonly":false,"value":"Energy.Active.Import.Register,Energy.Reactive.Import.Register,Energy.Active.Import.Interval,Current.Import"}]}]
2023-07-04 17:48:52.299 INFO (MainThread) [ocpp] 100231998: send [2,"d533b7c8-c658-4740-bd7b-9d094e06615e","GetConfiguration",{"key":["MeterValueSampleInterval"]}]
2023-07-04 17:48:52.351 INFO (MainThread) [ocpp] 100231998: receive message [3,"d533b7c8-c658-4740-bd7b-9d094e06615e",{"configurationKey":[{"key":"MeterValueSampleInterval","readonly":false,"value":"60"}]}]
2023-07-04 17:48:52.352 INFO (MainThread) [ocpp] 100231998: send [2,"218b1489-8868-48ca-880a-aecd31cbe367","GetConfiguration",{"key":["ClockAlignedDataInterval"]}]
2023-07-04 17:48:52.408 INFO (MainThread) [ocpp] 100231998: receive message [3,"218b1489-8868-48ca-880a-aecd31cbe367",{"configurationKey":[{"key":"ClockAlignedDataInterval","readonly":true,"value":"0"}]}]
2023-07-04 17:48:52.409 DEBUG (MainThread) [custom_components.ocpp] '100231998' post connection setup completed successfully
2023-07-04 17:48:52.409 INFO (MainThread) [ocpp] 100231998: send [2,"261a7db7-344b-4b62-bdd8-2afb050c2357","GetConfiguration",{"key":["WebSocketPingInterval"]}]
2023-07-04 17:48:52.457 INFO (MainThread) [ocpp] 100231998: receive message [3,"261a7db7-344b-4b62-bdd8-2afb050c2357",{"unknownKey":["WebSocketPingInterval"]}]
2023-07-04 17:48:52.457 WARNING (MainThread) [custom_components.ocpp] WebSocketPingInterval is unknown (not supported)
2023-07-04 17:48:52.460 INFO (MainThread) [ocpp] 100231998: send [2,"b58d9c0c-9930-44c3-a54b-f7b2be35ac51","ChangeAvailability",{"connectorId":0,"type":"Operative"}]
2023-07-04 17:48:52.555 INFO (MainThread) [ocpp] 100231998: receive message [3,"b58d9c0c-9930-44c3-a54b-f7b2be35ac51",{"status":"Accepted"}]
2023-07-04 17:48:52.596 INFO (MainThread) [ocpp] 100231998: receive message [2,"e498d3d0-1a79-11ee-8d65-4b5064ba5c67","StatusNotification",{"connectorId":1,"status":"Available","errorCode":"NoError","info":"0","timestamp":"2023-07-04T14:48:52.364Z","vendorId":"","vendorErrorCode":""}]
2023-07-04 17:48:52.597 INFO (MainThread) [ocpp] 100231998: send [3,"e498d3d0-1a79-11ee-8d65-4b5064ba5c67",{}]
2023-07-04 17:49:09.952 DEBUG (MainThread) [custom_components.ocpp] Connection latency from 'central' to '100231998': ping=1.0 ms, pong=10.0 ms

[drc38]

Your charger does not support the smart charging profile according to its response:
14a74-9213-4dc4-8eb0-e1fbb56bbe4a",{"configurationKey":[{"key":"SupportedFeatureProfiles","readonly":true,"value":"Core,FirmwareManagement,LocalAuthListManagement,Reservation
You can try ticking the the Force smart charging option when you setup the integration, but it may not work either.

[Korkki87]

Oh.. So it seems.. Got contacted by Scame yesterday, so I Have to ask them about it.. I hope I get the OCPP keys to implementation. It would make things lot more easier. Here's the log after ticking the "Force smart charging":

  2023-07-05 06:49:21.788 INFO (MainThread) [custom_components.ocpp] Charger 100231998 disconnected from 0.0.0.0:9000.
  2023-07-05 06:51:39.273 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.ocpp
  2023-07-05 06:51:39.274 INFO (MainThread) [homeassistant.components.switch] Setting up switch.ocpp
  2023-07-05 06:51:39.274 INFO (MainThread) [homeassistant.components.number] Setting up number.ocpp
  2023-07-05 06:51:39.275 INFO (MainThread) [homeassistant.components.button] Setting up button.ocpp
  2023-07-05 06:51:39.309 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.ocpp entity: sensor.charger_energy_active_import_register
  2023-07-05 06:51:39.311 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.ocpp entity: sensor.charger_energy_meter_start
  2023-07-05 06:51:39.312 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.ocpp entity: sensor.charger_energy_active_import_interval
  2023-07-05 06:51:39.313 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.ocpp entity: sensor.charger_energy_session
  2023-07-05 06:51:39.318 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.ocpp entity: sensor.charger_transaction_id
  2023-07-05 06:51:39.320 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.ocpp entity: sensor.charger_energy_reactive_import_register
  2023-07-05 06:51:39.322 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.ocpp entity: sensor.charger_time_session
  2023-07-05 06:51:39.326 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.ocpp entity: sensor.charger_current_import
  2023-07-05 06:51:39.328 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.ocpp entity: sensor.charger_status
  2023-07-05 06:51:39.329 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.ocpp entity: sensor.charger_status_connector
  2023-07-05 06:51:39.332 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.ocpp entity: sensor.charger_heartbeat
  2023-07-05 06:51:39.334 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.ocpp entity: sensor.charger_latency_ping
  2023-07-05 06:51:39.335 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.ocpp entity: sensor.charger_latency_pong
  2023-07-05 06:51:39.343 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.ocpp entity: sensor.charger_error_code
  2023-07-05 06:51:39.344 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.ocpp entity: sensor.charger_error_code_connector
  2023-07-05 06:51:39.346 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.ocpp entity: sensor.charger_stop_reason
  2023-07-05 06:51:39.347 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.ocpp entity: sensor.charger_status_firmware
  2023-07-05 06:51:39.352 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.ocpp entity: sensor.charger_reconnects
  2023-07-05 06:51:39.354 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.ocpp entity: sensor.charger_id_tag
  2023-07-05 06:51:39.357 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.ocpp entity: sensor.charger_id
  2023-07-05 06:51:39.363 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.ocpp entity: sensor.charger_model
  2023-07-05 06:51:39.364 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.ocpp entity: sensor.charger_vendor
  2023-07-05 06:51:39.366 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.ocpp entity: sensor.charger_serial
  2023-07-05 06:51:39.374 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.ocpp entity: sensor.charger_version_firmware
  2023-07-05 06:51:39.375 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.ocpp entity: sensor.charger_features
  2023-07-05 06:51:39.380 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.ocpp entity: sensor.charger_connectors
  2023-07-05 06:51:39.382 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.ocpp entity: sensor.charger_timestamp_data_response
  2023-07-05 06:51:39.384 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.ocpp entity: sensor.charger_timestamp_data_transfer
  2023-07-05 06:51:39.388 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.ocpp entity: sensor.charger_timestamp_config_response
  2023-07-05 06:51:39.390 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new switch.ocpp entity: switch.charger_charge_control
  2023-07-05 06:51:39.392 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new switch.ocpp entity: switch.charger_availability
  2023-07-05 06:51:39.393 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new number.ocpp entity: number.charger_maximum_current
  2023-07-05 06:51:39.396 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new button.ocpp entity: button.charger_reset
  2023-07-05 06:51:39.397 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new button.ocpp entity: button.charger_unlock
  2023-07-05 06:52:02.632 INFO (MainThread) [custom_components.ocpp] Websocket Subprotocol matched: ocpp1.6
  2023-07-05 06:52:02.632 INFO (MainThread) [custom_components.ocpp] Charger websocket path=/ws:/192.168.3.3:9000/100231998
  2023-07-05 06:52:02.633 INFO (MainThread) [custom_components.ocpp] Charger 100231998 connected to 0.0.0.0:9000.
  2023-07-05 06:52:02.665 INFO (MainThread) [ocpp] 100231998: receive message [2,"4cd79b30-1ae7-11ee-b860-775da878047c","BootNotification",{"chargePointVendor":"Scame Parre S.p.A.","chargePointModel":"SBC-0","chargePointSerialNumber":"2041SBB17687","firmwareVersion":"1.3.11"}]
  2023-07-05 06:52:02.666 DEBUG (MainThread) [custom_components.ocpp] Received boot notification for 100231998: {'charge_point_vendor': 'Scame Parre S.p.A.', 'charge_point_model': 'SBC-0', 'charge_point_serial_number': '2041SBB17687', 'firmware_version': '1.3.11'}
  2023-07-05 06:52:02.667 INFO (MainThread) [ocpp] 100231998: send [3,"4cd79b30-1ae7-11ee-b860-775da878047c",{"currentTime":"2023-07-05T03:52:02Z","interval":3600,"status":"Accepted"}]
  2023-07-05 06:52:02.668 DEBUG (MainThread) [custom_components.ocpp] Updating device info charger: {'charge_point_vendor': 'Scame Parre S.p.A.', 'charge_point_model': 'SBC-0', 'charge_point_serial_number': '2041SBB17687', 'firmware_version': '1.3.11'}
  2023-07-05 06:52:04.634 INFO (MainThread) [ocpp] 100231998: send [2,"5ec3147e-6f8a-47ad-8bc1-1b0cba8702e1","GetConfiguration",{"key":["SupportedFeatureProfiles"]}]
  2023-07-05 06:52:04.680 INFO (MainThread) [ocpp] 100231998: receive message [3,"5ec3147e-6f8a-47ad-8bc1-1b0cba8702e1",{"configurationKey":[{"key":"SupportedFeatureProfiles","readonly":true,"value":"Core,FirmwareManagement,LocalAuthListManagement,Reservation"}]}]
  2023-07-05 06:52:04.681 WARNING (MainThread) [custom_components.ocpp] Force Smart Charging feature profile
  2023-07-05 06:52:04.682 DEBUG (MainThread) [custom_components.ocpp] Feature profiles returned: 47
  2023-07-05 06:52:04.682 INFO (MainThread) [ocpp] 100231998: send [2,"729b5e01-0f5b-4c12-ab0a-9456fcdf1811","GetConfiguration",{"key":["SupportedFeatureProfiles"]}]
  2023-07-05 06:52:04.733 INFO (MainThread) [ocpp] 100231998: receive message [3,"729b5e01-0f5b-4c12-ab0a-9456fcdf1811",{"configurationKey":[{"key":"SupportedFeatureProfiles","readonly":true,"value":"Core,FirmwareManagement,LocalAuthListManagement,Reservation"}]}]
  2023-07-05 06:52:04.733 WARNING (MainThread) [custom_components.ocpp] Force Smart Charging feature profile
  2023-07-05 06:52:04.734 DEBUG (MainThread) [custom_components.ocpp] Feature profiles returned: 47
  2023-07-05 06:52:04.734 INFO (MainThread) [ocpp] 100231998: send [2,"a7b6e116-5464-4d6f-963d-c5d89987a1a6","GetConfiguration",{"key":["NumberOfConnectors"]}]
  2023-07-05 06:52:04.784 INFO (MainThread) [ocpp] 100231998: receive message [3,"a7b6e116-5464-4d6f-963d-c5d89987a1a6",{"configurationKey":[{"key":"NumberOfConnectors","readonly":true,"value":"1"}]}]
  2023-07-05 06:52:04.784 DEBUG (MainThread) [custom_components.ocpp] Get Configuration for NumberOfConnectors: 1
  2023-07-05 06:52:04.784 INFO (MainThread) [ocpp] 100231998: send [2,"4b25c32b-bcea-4055-b0cb-df04e07968dc","GetConfiguration",{"key":["NumberOfConnectors"]}]
  2023-07-05 06:52:04.833 INFO (MainThread) [ocpp] 100231998: receive message [3,"4b25c32b-bcea-4055-b0cb-df04e07968dc",{"configurationKey":[{"key":"NumberOfConnectors","readonly":true,"value":"1"}]}]
  2023-07-05 06:52:04.834 DEBUG (MainThread) [custom_components.ocpp] Get Configuration for NumberOfConnectors: 1
  2023-07-05 06:52:04.834 INFO (MainThread) [ocpp] 100231998: send [2,"ed846aa6-5199-4788-aa6d-f44b4095d431","GetConfiguration",{"key":["HeartbeatInterval"]}]
  2023-07-05 06:52:04.879 INFO (MainThread) [ocpp] 100231998: receive message [3,"ed846aa6-5199-4788-aa6d-f44b4095d431",{"configurationKey":[{"key":"HeartbeatInterval","readonly":false,"value":"3600"}]}]
  2023-07-05 06:52:04.880 DEBUG (MainThread) [custom_components.ocpp] Get Configuration for HeartbeatInterval: 3600
  2023-07-05 06:52:04.880 INFO (MainThread) [ocpp] 100231998: send [2,"9f3641f2-fbc6-47bc-84bc-9c08d02e63b9","GetConfiguration",{"key":["HeartbeatInterval"]}]
  2023-07-05 06:52:04.924 INFO (MainThread) [ocpp] 100231998: receive message [3,"9f3641f2-fbc6-47bc-84bc-9c08d02e63b9",{"configurationKey":[{"key":"HeartbeatInterval","readonly":false,"value":"3600"}]}]
  2023-07-05 06:52:04.924 DEBUG (MainThread) [custom_components.ocpp] Get Configuration for HeartbeatInterval: 3600
  2023-07-05 06:52:04.925 INFO (MainThread) [ocpp] 100231998: send [2,"edeafe9f-010c-4bce-abaa-2fe2d828b8ee","GetConfiguration",{"key":["MeterValuesSampledData"]}]
  2023-07-05 06:52:04.973 INFO (MainThread) [ocpp] 100231998: receive message [3,"edeafe9f-010c-4bce-abaa-2fe2d828b8ee",{"configurationKey":[{"key":"MeterValuesSampledData","readonly":false,"value":"Energy.Active.Import.Register,Energy.Reactive.Import.Register,Energy.Active.Import.Interval,Current.Import"}]}]
  2023-07-05 06:52:04.973 INFO (MainThread) [ocpp] 100231998: send [2,"5078d044-3d9a-41e0-a2b2-ccc437f6592c","GetConfiguration",{"key":["MeterValuesSampledData"]}]
  2023-07-05 06:52:05.024 INFO (MainThread) [ocpp] 100231998: receive message [3,"5078d044-3d9a-41e0-a2b2-ccc437f6592c",{"configurationKey":[{"key":"MeterValuesSampledData","readonly":false,"value":"Energy.Active.Import.Register,Energy.Reactive.Import.Register,Energy.Active.Import.Interval,Current.Import"}]}]
  2023-07-05 06:52:05.025 INFO (MainThread) [ocpp] 100231998: send [2,"435cb6d8-1a04-4630-820c-5d399d4c97ad","GetConfiguration",{"key":["MeterValueSampleInterval"]}]
  2023-07-05 06:52:05.072 INFO (MainThread) [ocpp] 100231998: receive message [3,"435cb6d8-1a04-4630-820c-5d399d4c97ad",{"configurationKey":[{"key":"MeterValueSampleInterval","readonly":false,"value":"60"}]}]
  2023-07-05 06:52:05.073 INFO (MainThread) [ocpp] 100231998: send [2,"518eef89-72ff-4782-b3a7-695ce3c89e59","GetConfiguration",{"key":["MeterValueSampleInterval"]}]
  2023-07-05 06:52:05.119 INFO (MainThread) [ocpp] 100231998: receive message [3,"518eef89-72ff-4782-b3a7-695ce3c89e59",{"configurationKey":[{"key":"MeterValueSampleInterval","readonly":false,"value":"60"}]}]
  2023-07-05 06:52:05.120 INFO (MainThread) [ocpp] 100231998: send [2,"dceeca6f-56ba-4ef3-9f52-515329af215d","GetConfiguration",{"key":["ClockAlignedDataInterval"]}]
  2023-07-05 06:52:05.164 INFO (MainThread) [ocpp] 100231998: receive message [3,"dceeca6f-56ba-4ef3-9f52-515329af215d",{"configurationKey":[{"key":"ClockAlignedDataInterval","readonly":true,"value":"0"}]}]
  2023-07-05 06:52:05.167 DEBUG (MainThread) [custom_components.ocpp] '100231998' post connection setup completed successfully
  2023-07-05 06:52:05.168 INFO (MainThread) [ocpp] 100231998: send [2,"ef79b930-652b-4cf8-be0b-1e20b7657068","GetConfiguration",{"key":["ClockAlignedDataInterval"]}]
  2023-07-05 06:52:05.212 INFO (MainThread) [ocpp] 100231998: receive message [3,"ef79b930-652b-4cf8-be0b-1e20b7657068",{"configurationKey":[{"key":"ClockAlignedDataInterval","readonly":true,"value":"0"}]}]
  2023-07-05 06:52:05.215 DEBUG (MainThread) [custom_components.ocpp] '100231998' post connection setup completed successfully
  2023-07-05 06:52:05.215 INFO (MainThread) [ocpp] 100231998: send [2,"6295bb1b-ff02-4068-917b-73b8cdec2237","GetConfiguration",{"key":["WebSocketPingInterval"]}]
  2023-07-05 06:52:05.260 INFO (MainThread) [ocpp] 100231998: receive message [3,"6295bb1b-ff02-4068-917b-73b8cdec2237",{"unknownKey":["WebSocketPingInterval"]}]
  2023-07-05 06:52:05.261 WARNING (MainThread) [custom_components.ocpp] WebSocketPingInterval is unknown (not supported)
  2023-07-05 06:52:05.264 INFO (MainThread) [ocpp] 100231998: send [2,"eaf34a79-b09f-4611-b633-6453f58dac17","GetConfiguration",{"key":["WebSocketPingInterval"]}]
  2023-07-05 06:52:05.309 INFO (MainThread) [ocpp] 100231998: receive message [3,"eaf34a79-b09f-4611-b633-6453f58dac17",{"unknownKey":["WebSocketPingInterval"]}]
  2023-07-05 06:52:05.310 WARNING (MainThread) [custom_components.ocpp] WebSocketPingInterval is unknown (not supported)
  2023-07-05 06:52:05.313 INFO (MainThread) [ocpp] 100231998: send [2,"f87a604f-a168-46fb-a210-9062d9329f68","ChangeAvailability",{"connectorId":0,"type":"Operative"}]
  2023-07-05 06:52:05.383 INFO (MainThread) [ocpp] 100231998: receive message [3,"f87a604f-a168-46fb-a210-9062d9329f68",{"status":"Accepted"}]
  2023-07-05 06:52:05.384 INFO (MainThread) [ocpp] 100231998: send [2,"ce2112e3-c11a-4ffc-bb93-64543d174f2e","ChangeAvailability",{"connectorId":0,"type":"Operative"}]
  2023-07-05 06:52:05.414 INFO (MainThread) [ocpp] 100231998: receive message [2,"4e2af630-1ae7-11ee-b860-775da878047c","StatusNotification",{"connectorId":1,"status":"Available","errorCode":"NoError","info":"0","timestamp":"2023-07-05T03:52:04.627Z","vendorId":"","vendorErrorCode":""}]
  2023-07-05 06:52:05.415 INFO (MainThread) [ocpp] 100231998: send [3,"4e2af630-1ae7-11ee-b860-775da878047c",{}]
  2023-07-05 06:52:05.510 INFO (MainThread) [ocpp] 100231998: receive message [3,"ce2112e3-c11a-4ffc-bb93-64543d174f2e",{"status":"Accepted"}]
  2023-07-05 06:52:05.998 INFO (MainThread) [ocpp] 100231998: receive message [2,"4e3f4180-1ae7-11ee-b860-775da878047c","StatusNotification",{"connectorId":1,"status":"Available","errorCode":"NoError","info":"0","timestamp":"2023-07-05T03:52:04.760Z","vendorId":"","vendorErrorCode":""}]
  2023-07-05 06:52:06.000 INFO (MainThread) [ocpp] 100231998: send [3,"4e3f4180-1ae7-11ee-b860-775da878047c",{}]
  2023-07-05 06:52:22.643 DEBUG (MainThread) [custom_components.ocpp] Connection latency from 'central' to '100231998': ping=3.0 ms, pong=4.0 ms
  2023-07-05 06:52:42.650 DEBUG (MainThread) [custom_components.ocpp] Connection latency from 'central' to '100231998': ping=1.0 ms, pong=5.0 ms
  2023-07-05 06:53:02.657 DEBUG (MainThread) [custom_components.ocpp] Connection latency from 'central' to '100231998': ping=0.0 ms, pong=6.0 ms
  2023-07-05 06:53:22.664 DEBUG (MainThread) [custom_components.ocpp] Connection latency from 'central' to '100231998': ping=1.0 ms, pong=5.0 ms
  2023-07-05 06:53:42.672 DEBUG (MainThread) [custom_components.ocpp] Connection latency from 'central' to '100231998': ping=1.0 ms, pong=6.0 ms
  2023-07-05 06:53:49.275 INFO (MainThread) [ocpp] 100231998: send [2,"80967b09-07ee-46b2-81ff-9e16a07821eb","GetConfiguration",{"key":["ChargingScheduleAllowedChargingRateUnit"]}]
  2023-07-05 06:53:49.323 INFO (MainThread) [ocpp] 100231998: receive message [3,"80967b09-07ee-46b2-81ff-9e16a07821eb",{"unknownKey":["ChargingScheduleAllowedChargingRateUnit"]}]
  2023-07-05 06:53:49.324 WARNING (MainThread) [custom_components.ocpp] Get Configuration returned unknown key for: ChargingScheduleAllowedChargingRateUnit
  2023-07-05 06:53:49.442 INFO (MainThread) [custom_components.ocpp] Charger supports setting the following units: None
  2023-07-05 06:53:49.443 INFO (MainThread) [custom_components.ocpp] If more than one unit supported default unit is Amps
  File "/config/custom_components/ocpp/number.py", line 127, in async_set_native_value
  File "/config/custom_components/ocpp/api.py", line 281, in set_max_charge_rate_amps
  File "/config/custom_components/ocpp/api.py", line 582, in set_charge_rate
  2023-07-05 06:54:02.677 DEBUG (MainThread) [custom_components.ocpp] Connection latency from 'central' to '100231998': ping=1.0 ms, pong=4.0 ms

[Korkki87]

So at this point Scame AC Net Master 22kW (ethernet version) has limited support:

Firmware: 1.4.025.2
Software: 1.3.11

SupportedFeatureProfiles:
"Core, FirmwareManagement, LocalAuthListManagement, Reservation"

And

MeterValuesSampledData:
"Energy.Active.Import.Register, Energy.Reactive.Import.Register, Energy.Active.Import.Interval, Current.Import"

I got data from Scame that there are newer FW (1.4.035.2) and SW (1.3.14) versions, but still haven't got those and no knowledge, will SupportedFeatureProfiles; Smart Charging and Remote Triggers be supported with those or later on.

[Korkki87]

This week I got info, that the Scame is not providing any support and the wallbox is not supportin "smart charge" profile.

SO... I've been working with some Node Red automation to use the webclient with HA Node Red Addon tot make a detour..

With this thing, I can send commands to Scame webpage and make a change to max current straight from there. So no problem with this thing anymore.