Cookie preferences
We assume this is a bug on Aidon smart meters with HAN-NVE interface (Norway, Sweden and possibly Finland).
Latest posts
-
Assumed bug on Aidon meters with HAN-NVE interfaceRead more -
Kamstrup Omnipower in Sweden: 10x kWh errorRead moreGrid companies in Sweden has increased the number of decimals on energy (kWh), here is how to update your device.
-
Updating device over USB cable, simplified methodRead moreSome users experience difficulties using one of the Over-the-air (OTA) methods for firmware upgrade. We propose a...
-
Kamstrup Omnipower HAN port not workingRead moreHow to cure the Kamstrup Omnipower meter hick-up (meter stops pushing data)
-
Kamstrup Omnipower meters in Sweden: Which configuration should you choose?Read moreSwedish grid companies are moving from "HAN-NVE" configuration to "P1" configuration. Some grid companies allow their...
-
L2 current not available!?Read moreSome users have noticed that the device is no longer reporting current on phase L2.
-
Swedish customers and PostNord as "Tullombud"Read moreSwedish customers receiving our shipments via Postnord are mislead to think they have to pay customs fee and VAT....
-
One-click upgrade is not workingRead moreOne-click firmware upgrade works just fine for most users - but what to do if it fails?
-
-
I have a Kaifa/Nuri meter, and my new Pow-U does not work!?Read moreOK... so we made a (minor) bummer on a design update of Pow-U. The fix is maybe not elegant, but it is easy!
Blog categories
Search in blog
Assumed bug on Aidon meters with HAN-NVE interface
We have seen on our own meter and had at least one customer report on the same issue. It concerns meters configured with HAN-NVE interface (RJ45 socket).
These meters send 3 different payloads:
- List 1
A very small payload sent each 2.5 second - List 2
A longer payload with more parameters, sent each 10 second - List 3
A payload with all parameters, sent hourly just after passing of whole hour.
This is the only payload that contains Accumulated energy (kWh), and is used to calculate and display the consumption for the previous hour.
The issue is that the meter sometimes send identical value for Accumulated Import Energy (kWh) in two consecutive List 3.
The consequence is that the user sees something like this on her/his consumption graph:
In this case, the user knew that the consumption was higher than normal in the periods 21/22 - but it was definitively not zero during hour 21.
Our own investigatons, after having seen the same issue, show that this is not a firmware bug, it is actually the meter that sent the same value for Accumulated energy for hour 20 and for hour 21. When the meter then transmitted the correct value for hour 22, the result is as shown in the graph.
Some of you may think that the reason is a missing List 3 (checksum error for instance). But if that happens, the firmware will not register a value for the missing hour. When the next list 3 then arrives, covering a two-hour period, the firmware will average the value and distribute it over the two hour periods.
Posted in:
Information
Related posts
-
Where are our customers located?
This map shows the postal code position for amsleser.no registered customers. We have customers in Finland, devices...Read more -
Emergency factory reset
Your device has become unresponsive for some reason. Is there some way to recover? Yes!Read more -
Can my device connect to 5 GHz Wifi?
Sorry - the answer is No.Read more -
Vattenfall - opening the HAN port
Andreas in Sweden informed us on 26th Sep -22 that Vattenfall currently has a long backlog in handling incoming emails.Read more -
Telnet debug
If you need to take a peek under the hood!Read more
Leave a comment