Support Modbus/TCP in the Wi-Fi energy meter of IAMMETER

Modbus TCP is common protocol that used in industrial system such as ICS, DCS, SCADA. After the latest firmware upgrading, the energy meter of IAMMETER had supported the modbus tcp protocol now.

https://www.iammeter.com/newsshow/news-modbus-tcp-energy-meter

If you met any problem after this firmware upgrading ,please post your problem here directly (please hide the SN)

Debug version download file

https://iammeterglobal.oss-ap-southeast-1.aliyuncs.com/download/x.75.82.bin

SHA256: C29F611F4FB8EA8B4B447FB4FFF48852ABCEB0CCA1A65664A8CD311B3DF3C003

How to upgrade the firmware, please refer to https://www.iammeter.com/docs/firmware-upgrade

For the register of the Modbus TCP,  please refer to https://www.iammeter.com/newsshow/news-modbus-tcp-energy-meter

please note:
Please use the browser of chrome in upgrading.
Please wait patiently in the upgrading process.
In the firmware before 2.75.70, if you do a new upgrading before the previous upgrading is complete(For example, you close the previous browser that the firmware is in upgrading and start a new upgrading from a new browser), the energy meter will be brick and not be able to recover.
This is a free upgrade, we would not be responsible for any problem if you bricked the energy meter in the upgrade.

Hi.

I did the upgrade in my 3phase meter. The upgrade itself went ok. The modbus tcp looks working as it should (I made just a few test with modbus mechanic). BUT, I using home assistant, and the buit-in iammeter "integration", Now, one of the export meters have wrong data!

And than the energie dashboard freezing completely.

In the entitles I can see the details, now it looks like:

Before the upgrade the numbers was good:

What can I do now? Can I downgrade to the old version of fw (until this problem is fixed)?

Thanks

Other interesting thing is, if I ask the meter data from modbus tcp, the numbers are:

A forward: 634669 (009A F2D8) = 793,33625 kWh
A reverse: 494157 (0078 A4D0) = 617,69625 kWh

B forward: 480613 (0075 5658) = 600,76625 kWh
B reverse: 501964 (007A 8CC8) = 627,455 kWh

C forward: 457991 (006F D078) = 572,48875 kWh
C reverse: 552506 (0086 E3A8) = 690,6325 kWh

sum forward: 552506 (0086 E3A8) = 690,6325 kWh
sum reverse: 1548655 (017A 16F0) = 1935,81875 kWh

The monitorjson looks:

And from your cloud:

Why have the modbus different data? Otherwise, here the numbers looks good, from your cloud there is no as huge step like in HA. So, I don't know why it happened...

I added the meter via modbus tcp to HA, but the result are same :O , there are still some jumps out:

Just for example the export_b and export_c working good, it looks like (that's how the export_a should look like too!):

The import_a and the pf_a have this problem also:

I hope I gave enough info to give me a solution.

Until that let me know how can I downgrade.

Thanks

Hi.

can you please answer me! Now the data is unusable, so I cannot use my long therm statistics :( . Just tell me if I can downgrade, and are there any special instructions or not.

Thanks

Hello

Just download the non Modbus firmware here:

https://iammeterglobal.oss-ap-southeast-1.aliyuncs.com/download/2.75.76.ota.bin

Go to the IP address of the meter and login admin / admin

Choose system and then choose file , browse to file downloaded above then choose upload.

Takes about 15 seconds, do not power off the device while it come back online

Done!

Regards

Dale

Hi :daleph

Thanks for help us to answer this question.

Hi :nzperx

Sorry, because this post is on top, we miss your question before.

I have forwarded your question to my colleague.

Before we confirm what had happen to your problem, please download the latest released version here.

https://imeter.club/topic/11

1 whether the abnormal only exists in phase A or all three-phase?

2 The mistake  Modbus TCP return (as below) always exist or just exist when the phase A kwh return the wrong value?

"A forward: 634669 (009A F2D8) = 793,33625 kWh

A reverse: 494157 (0078 A4D0) = 617,69625 kWh
B forward: 480613 (0075 5658) = 600,76625 kWh
B reverse: 501964 (007A 8CC8) = 627,455 kWh

C forward: 457991 (006F D078) = 572,48875 kWh

C reverse: 552506 (0086 E3A8) = 690,6325 kWh"

In addition,I do not understand the relationship between these digits, take A forward as an example

"A forward: 634669 (009A F2D8) = 793,33625 kWh

0x9AF2D8=10,154,712    10154712/800=12693   this is the same with the monitorjson

634669 = 0x9AF2D(seem lost the last character "8" in “0x 009A F2D8” ) , so what is this "634669" mean?

793,33625, what is this number mean?

3 How do you poll the data from Modbus TCP? how fast? whether the Modbus tcp polling kept on all the time?

4 How fast do you request the data in HA, just use the default setting or request the data more faster ?

5 How long have you integrated the IAMMETER into your HA system? Whether there is such a problem before you upgrade the firmware?

Thanks 

one more question,please help us to confirm whether these data graph below are read from modbus tcp or the integration directly 

1 modbus tcp or integration?

2  modbus tcp or integration?

Hi.

Thanks. It was successfully, so now the data is correct again!

Hi.

Thanks.

Let me answer like you:

1. Yes, just with Phase A

2. My calculation was wrong, so forget it ;)

3, Everything is on the default. So I use your yaml example for HA!

4. Everything is on the default.

5. I'm using this about 1 year. There was no problem before upgrade to the modbus tcp firmware!

laoliu

1 whether the abnormal only exists in phase A or all three-phase?2 The mistake  Modbus TCP return (as below) always exist or just exist when the phase A kwh return the wrong value?"A forward: 634669 (009A F2D8) = 793,33625 kWhA reverse: 494157 (0078 A4D0) = 617,69625 kWhB forward: 480613 (0075 5658) = 600,76625 kWhB reverse: 501964 (007A 8CC8) = 627,455 kWhC forward: 457991 (006F D078) = 572,48875 kWhC reverse: 552506 (0086 E3A8) = 690,6325 kWh"In addition,I do not understand the relationsh

Yes as you can see, it happens also when I use the modbus tcp protocol! So the problem is not related what protocol I use, it happening with built is integration and with modbus tcp as well!

laoliu

one more question,please help us to confirm whether these data graph below are read from modbus tcp or the integration directly 1 modbus tcp or integration?2  modbus tcp or integration?

And one more info. I have domoticz as well. It reading data using monitorjson. And domoticz have the same jumps out! So I'm 100% sure that the wrong data comes from the meter!

And I found thin in your web as well!

The interesting thing is in graph mode there is no jumps out (on your official cloud page), maybe your algorithm knows that than cannot happen so not dealing with it...

And because it happened, now my long therm data is corrupted, the numbers are wrong :( . Can anybody tell me how can I remove the wrong numbers from HA?

Hi:

Let me confirm the situation that causes this problem.

1 the API of the energy meter (monitorjson) is called by HA  and domesticz.

I know that the HA would call the API every 30 secs, do you know what is the call interval of the domesticz?

2  You also use the modbus tcp to read the data of WEM3080T from the Home assistant, in the default setting(every 15 seconds).

3 you used the IAMMETER-cloud at the same time.

Please let me know, Is there any other client that call the local api (monitorjson) or request the modbus tcp data?

Thanks

1. Yes. The domoticz calling it in every 20 seconds.

2. I just used it to try if the problem exist with modbus also or not...

3. Yes, of course, the cloud is enabled by default.

There is no more client. But, before the fw upgrade I had the same setup and there was no problem!

laoliu

Hi:Let me confirm the situation that causes this problem.1 the API of the energy meter (monitorjson) is called by HA  and domesticz.I know that the HA would call the API every 30 secs, do you know what is the call interval of the domesticz?2  You also use the modbus tcp to read the data of WEM3080T from the Home assistant, in the default setting(every 15 seconds).3 you used the IAMMETER-cloud at the same time.Please let me know, Is there any other client that call the local api (monito

Hi, could you please let me know ,whether the problem occurred immediately(within one day) when your requested the data from Modbus tcp or after several days?

It happened before I requested any data from modbus tcp, just I tried maybe once to read modbus tcp with modbus mechanic, but nothing else! So, just to make it clear, I upgraded to the modbus fw on 24th of may, tried to read, and than I left it, so there was no modbus test etc. After a day I faced with the problem. And just one day later on 25th of may I setup the modbus tcp on HA, just to make it clear where is the problem. So when the problem occurred then there was mo modbus connection!

laoliu

Hi, could you please let me know ,whether the problem occurred immediately(within one day) when your requested the data from Modbus tcp or after several days?

Yes, I think so.
Now I doubt this problem has nothing to do with the modbus tcp ,I found you have also submit a feedback about this question in customer`s system.
Because I should confirm some other information about this energy meter,I will reply to you there.
Thanks for your feedback again.