KINETOS WB - own build for WS32-eth1 and SDM630 energy meter?

[linuxdep]

Hello,
i have build a version for KINETOS WB, this has a WS32-ETH1 modul inside, this is working. But this WB has also a energy meter inside (SDM630 i think) this is connected to esp32 over rs485 adapter (pins not yet clear, but i can messure it).
I have not found any information how can i add this, AI is not so helpfully, 2 question 2 answers...

Is this correct at point "-D ENABLE_METRICS=1" ?
And need i some libs to add?
The second question, inside is a rfid reader, rdif is enabled on firmeware, but witch kind of rfid chips i need? An mirafe chip was not recognised. Handy App can read the ID.

My platformio.ini with spezial part

[env:wt32-eth01-kinetos-auem]
# For Wireless Tag used in Kinetos-AUEM Wallbox
board = wt32-eth01
lib_deps =
  ${common.lib_deps}
  ${common.neopixel_lib}
  ${common.ws2812fx_lib}
build_flags =
  ${common.build_flags}
  ${common.src_build_flags}
  #${common.debug_flags}
  -D WIFI_PIXEL_NUMBER=1
  -D WIFI_BUTTON=2
  -D WIFI_BUTTON_PRESSED_STATE=LOW
  -D NEO_PIXEL_PIN=4
  -D NEO_PIXEL_LENGTH=7
  -D ENABLE_WS2812FX
  -D DEBUG_PORT=Serial2
  -D RX2=5
  -D TX2=17
  -D RAPI_PORT=Serial
  -D ENABLE_WIRED_ETHERNET
  -D RESET_ETH_PHY_ON_BOOT=1
  -D ETH_PHY_TYPE=ETH_PHY_LAN8720
  -D ETH_PHY_ADDR=1
  -D ETH_PHY_MDC=23
  -D ETH_PHY_MDIO=18
  -D ETH_CLK_MODE=ETH_CLOCK_GPIO0_IN
  -D ETH_PHY_POWER=16
  -D ENABLE_OTA
  ; Aktiviert die Zähler-Unterstützung
  -D ENABLE_METRICS=1
  ; Definiert den Zählertyp (z.B. SDM120, SDM630 oder Finder)
  -D RS485_METER=1 
  -D RS485_METER_SDM630=1
  ; Pins für RS485 (Beispielwerte, bitte mit deiner Verkabelung prüfen!)
  -D PIN_RS485_RX=5
  -D PIN_RS485_TX=17
  
#build_type = debug
board_build.partitions = ${common.build_partitions}

Where do you actually find the possible parameters?

[linuxdep]

Hi, i have some check on Wb, and i see the energy meter should at evse board connected... but i have only update the esp32_wifi firmeware, should the energy meter work as before?

[jeremypoulter]

The OpenEVSE firmware doesn't currently have support for using a local energy meter, only for receiving the voltage over MQTT and current is natively supported by the OpenEVSE board.

[linuxdep]

thanks. the old FW had it implemented, i will see how can i solve this.

When the current values ​​for phases L1, L2, and L3 are received over MQTT, are they then transmitted to the EVSE board via $T0 L1 L2 L3? Or was that also a separate implementation? I've initially built a version adapted to my hardware; problems with that will be in a separate post, so there's no confusion.