Latest posts

View all latest posts

Blog categories

View all categories

Search in blog

Archived posts

Kamstrup Omnipower HAN port not working

6 Comments
(5)
Posted on: 29-Feb-2024

The Kamstrup Omnipower meter is a very popular smart meters, installed in millions of sites in a number of countries.

However, its HAN port seems to have a flaw that some of us have been unfortunate to experience: After having delivered data to the HAN port every 10 seconds for months or years, the port suddenly stops sending data. It continues delivering voltage and power to attached equipment, there is just no data.

If this happens to you and your installation has the main breaker on the "street side" of the Omnipower meter you can consider yourself lucky: Just cut power from the meter by opening the main breaker, wait a few seconds, then close the breaker again. Problem solved!

In some countries (for instance Denmark) the main breaker is typically situated on the other side of the meter, so there is no way to cut its power. This is a more tricky situation.

This is what we have found after having investigated the issue:

If you are in Denmark and Radius is your grid company (Copenhagen and surrounding region), it is relatively easy to fix this:

Note: There might be other grid companies that have outsourced the Omnipower meter management to Kamstrup. If you have this issue, contact your grid company and ask if they are able to request Kamstrup to do a remote restart of your meter.

So, what is the solution if the grid company says they cannot reset the HAN port?
In that case, we recommend you to insist that they find a solution. The grid company owns the power meter, it stopped working - and it is not your fault. The grid company should send you (with no cost for you) an electrician/technician that can either disconnect/reconnect your power meter - or reboot it via the optical port of the meter. If they claim that it is the connected equipment that caused the disruption, you can tell them that the HAN port is still delivering power (which is confirmed if your Pow-K is still working, just not receiving data), so it is not an overload shutdown.

Posted in: FAQ, Information, How to

Leave a comment

Comments

  • buffer 512 or 256
    By: Preben Madsen On 08-Apr-2026
    Rating:
    5.0

    Hi mine failed after i was in and edited the MQTT settings, here it was req. to change the buffer from 512 to 256 since then it has not receiving anything. I have contacted my friend there bought one as well. and here it is running fine 512.

    Replied by: Egil Opsahl On 09-Apr-2026 Please contact us by email (post - at - amsleser.no) to sort this out. Your situation is probably not what this article is about.

  • Issue remains after meter disconnect
    By: Christian On 25-Mar-2026
    Rating:
    5.0

    My issue remains after I today got my installation upgraded (same meter but everything else in the installation box replaced, so the meter was physically disconnected for an hour). Does it still make sense to contact Radius (DK) or should the physical disconnection have fixed it?

    I get a valid HAN message once in a while (up o maybe 10 min apart), but most are unknown.
    This might not be the best place for debugging it (where should I ask this?)
    My debug output via telnet shows this kind of thing:
    (W) Used 1198ms to read HAN port (true)
    (E) Ended up in default case while unwrapping...(tag 96)
    (W) Unknown data received
    (W) Used 1054ms to read HAN port (true)
    (W) No HAN data received last 30s, single blink
    (I) (PriceService) Price point reset
    (W) No HAN data received last 30s, single blink
    (W) No HAN data received last 30s, single blink
    (W) Boundary flag missing
    (W) Used 1166ms to read HAN port (true)
    (E) Ended up in default case while unwrapping...(tag 4A)
    (W) Unknown data received

    Replied by: Egil Opsahl On 30-Mar-2026 Contact us by email: post(at)amsleser.no
    We'll assist you in debugging your situation.

    Kind regards
    Egil Opsahl
    amsleser.no

  • Got the problem in SE
    By: Thomas F On 07-Jan-2026
    Rating:
    5.0

    FYI I also had this issue. Suddenly the Kamstrup meter just stopped reporting data.
    I tried by unplugging the board over the night, but nothing happened.
    So I had to cut the power on the main switch and after that it worked again as expected.

    Is there an event from the AMS Reader when the HAN-port is dead?
    I didn't check daily so I didn't noticed this for a while, but I guess that I just could have an automation in Home Assistant that notifies me when data is not received any more, but an error event from the board (MQTT) indicating what kind of problem would be nice (e.g. "No HAN data received").

    Thanks for a nice product!

    Cheers,
    Thomas

  • Alternative HAN reset for DK
    By: Høgni Z On 24-Jul-2025
    Rating:
    5.0

    I had the problem with AMS Reader not recieving data from Kamstrup HAN port.
    Then there was a power outtage, and the entire area went dark.
    When power came back the HAN port was reset... Problem solved.

    Replied by: Egil Opsahl On 28-Jul-2025 So the alternative HAN reset is to cause a power blackout? :-)
    It will certainly work, but we cannot recommend it!

  • No access in my LAN
    By: Lars K On 21-Oct-2024
    Rating:
    5.0

    I can do the initial setup just fine, and my device (K+) connects, gets an IP address. But then there is no response - it seems like its blocked somehow. It has been working flawlessly for a long time until now.

    I have tried resetting and factory defaults. It boots up fine, but wont let me see http pages over my LAN. Any advice?

    Replied by: Egil Opsahl On 24-Oct-2024 That is an unusual error, seems to be related to your Wi-Fi.
    Please contact us on post@amsleser.no to help you on this.

View all comments

Related posts