cfeenstra1024/kamstrup-multical-hardware

PCB and housing for ESPHome integration with Kamstrup Multical 403 meter

Hardware for use with ESPHome and Kamstrup Multical 403

This repository contains a PCB and housing that can be used as the hardware to read the measurements from a Kamstrup Multical 403. The PCB uses a 'D1 Mini' ESP8266 board. A software component for use in ESPHome has been created.

Using this setup you can read measurements from the Kamstrup Multical (e.g. city heating) and publish the measurements to Home Assistant.

Electronics

The Kamstrup Multical 403 uses an optical interface for communication. A PCB was designed that uses a mini-D1 ESP8266 board. The PCB Gerbers folder contains the required files to fabricate the PCB. The PCB Components folder contains the BOM (bill of materials) and the component placement files. A special version for use with JLCBCB has been created for these.

The PCB has the following features:

• Optical interface for use with the Kamstrup meter
• Pulse counter (can be used with a proximity sensor to measure water consumption)
• 2 free open collector outputs
• 2 free inputs

What you need

• Order (or build) the PCB with the transistors and resistors
• IR LED 940 nm
• IR Photo Diode 940 nm
• D1 Mini ESP8266 board
• Optional: Header pins

Images

Housing

The housing can be 3D printed with a regular 3D printer. The Fusion 360 design and STL files are provided.

The Kamstrup Multical 40x meter needs to be waken up by pressing a button. It then stays awake for a few minutes. To keep the meter awake, magnets must be placed in the 4 holes. Every hole fits 2 magnets (using a total of 8).

What you need

• PCB printer to print the 2 STL files (housing and lid)
• 8x 6x3 mm neodymium magnets

Images

Software

Use the kamstrup_kmp component in ESPHome. Refer to the Documentation for all details regarding this component.

Example config file:

uart:
  baud_rate: 1200
  stop_bits: 2
  tx_pin: GPIO15
  rx_pin: GPIO13

sensor:
  - platform: kamstrup_mc40x
    heat_energy:
      name: 'Heat Energy'
    power:
      name: 'Heat Power'
    temp_diff:
      name: 'Heat Temperature Difference'
    flow:
      name: 'Heat Flow'
    custom:
      - name: Custom Heat Energy
        command: 0x003C
      - name: Custom Heat Power
        command: 0x0050
    update_interval: 60s

kamstrup-multical-hardware's Issues

Improve component with extra registers for multiple device types

Hi' @cfeenstra1024

Still waiting for the ESPHome PR to be merged before testing 🙂
I'm currently using ESPHome with my own 'tweaked' version of @cenobitedk Kamstrup custom component. Both for my district heating meter (Multical 602) as well as my water meter (flowIQ 2200).

I would suggest that you add the High Resolution register(s) to your component as well. For the x03 meter series it's a straight forward process. For the x02 series it's a bit more complicated as the HiRes register is a delta value. I've also added a calculated yearly cooling average sensor. Very useful in countries where the utility companies enforce 'penalty' tariffs for customers not cooling the water sufficiently. Reading the Unit Of Measurement from the actual device would also be a nice feature (not sure if you've already done that ?)

You could take a peek at my fork if you're interested 🙂

jlcpcb BOM not working anymore + CPL file missing

Hi,

this is a really great project and I would like to implement this in my home as well - ordered via jlcpcb. I don't know if the changed something in the input files format, but now they request a CPL file (Pick&Place File) which I cannot find in the github files. Futhermore in the BOM file there are several components that cannot be matched (even when I use the special jlcpcb file. Can someone with better electronic knowledge than I have please update the BOM file and add the CPL file so that I - and everyone else who will get the stuff from jlcpcb.com can be sure to order the right parts?

Thanks a lot in advance!

best regards,
Stephan

Full documentation link is broken

@cfeenstra1024 The link to the full documentation is broken. Do you have any idea, when the PR will be merged.