Add Cozify HAN energy reader

[VolkerK62]

This proposal suggests adding a new custom meter template to EVCC for the Cozify HAN energy reader. The template enables EVCC users to retrieve real-time energy data via HTTP from Cozify HAN devices using JQ filters.

Cozify HAN is a smart energy monitoring device that supports OpenAPI and MQTT. Many users have successfully integrated it with EVCC using a custom configuration. However, the lack of a built-in template in EVCC's UI makes it harder for new users to adopt. This template would simplify integration and improve accessibility.

The template uses HTTP as the data source and applies JQ filters to extract power, energy, currents, and voltages from the HAN reader's JSON output.

meters:
  - name: cozify-han
    type: custom
    power:
      source: http
      uri: http://YOUR_HAN_IP:80/meter/data
      timeout: 1s
      jq: (.pi[0] - .pe[0])
    energy:
      source: http
      uri: http://YOUR_HAN_IP:80/meter/data
      timeout: 1s
      jq: (.ic | tonumber)
    currents:
      - source: http
        uri: http://YOUR_HAN_IP:80/meter/data
        timeout: 1s
        jq: .i[0]
      - source: http
        uri: http://YOUR_HAN_IP:80/meter/data
        timeout: 1s
        jq: .i[1]
      - source: http
        uri: http://YOUR_HAN_IP:80/meter/data
        timeout: 1s
        jq: .i[2]
    voltages:
      - source: http
        uri: http://YOUR_HAN_IP:80/meter/data
        timeout: 1s
        jq: .u[0]
      - source: http
        uri: http://YOUR_HAN_IP:80/meter/data
        timeout: 1s
        jq: .u[1]
      - source: http
        uri: http://YOUR_HAN_IP:80/meter/data
        timeout: 1s
        jq: .u[2]

Please consider including this template in the EVCC default configuration or making it available via the UI for easier selection.

Cozify HAN

Originally posted by @PilcQ in #24357

[VolkerK62]

@andig I can create a template based on the custom meter above, but I noticed that most of the http devices do have a go implementation.

[andig]

Should only be the case if there is any additional glue logic required. Templates are the preferred way.

[VolkerK62]

@PilcQ does your api provide "cache headers"

[PilcQ]

@PilcQ does your api provide "cache headers"

Hi, I would say that no, this is the answer when I try locally ( http://cozify-han-a01-0012/meter ) with my browser:

{
  "type": "HAN_METER_MESSAGE",
  "ts": 1760339530,
  "ic": 683.123,
  "ec": 14.036,
  "ric": 7.662,
  "rec": 692.38,
  "p": [71, 71, 0, 0],
  "pi": [71, 71, 0, 0],
  "pe": [0, 0, 0, 0],
  "r": [83, 83, 0, 0],
  "ri": [0, 0, 0, 0],
  "re": [83, 83, 0, 0],
  "u": [237.8, 237.6, 237.6],
  "i": [0.6, 0, 0]
}

[premultiply]

This is only the response body. You need to dump the complete HTTP response including all headers.

[PilcQ]

HTTP/1.1 200 OK
Cache-Control: no-cache, no-store, must-revalidate
Pragma: no-cache
Expires: -1
Connection: close
Accept-Ranges: none
Content-Length: 230
Content-Type: application/json

{"type":"HAN_METER_MESSAGE","ts":1760341170,"ic":683.155,"ec":14.036,"ric":7.662,"rec":692.418,"p":[71,71,0,0],"pi":[71,71,0,0],"pe":[0,0,0,0],"r":[82,82,0,0],"ri":[0,0,0,0],"re":[82,82,0,0],"u":[235.6,235.39,235.5],"i":[0.6,0,0]}