No meter readings from Landis + Gyr ZMF110 smart meter over P1

by bellyf on

Since this is about a different meter I created a new entry but it looks like I have a similar/same problem as posted about the Kaifa smart meter. All connections seem to be OK but no meter readings.

My installation:

  • brand new Landys+Gyr ZMF110 smart meter with P1 connector
  • brand new flmv2b
  • flm connected via LAN
  • P1 connected on sensor 6 with cable provided (I didn't see any options to configure P1 under "Sensor" so nothing enabled)
  • I see gas and electricity sensors on flukso.net
  • I see my device ID (version 244) on flukso.net
  • status page 3x OK (System, network, sensor config sync -- latest yesterday evening 22:56)
  • All my device are in the 192.168.178.* local network segment as is the fluksometer

Despite all the good signs I don't see any electricity or gas readings in my dash. After a few seconds I see Error - The call for sensor smart-main experienced a timeout. You are probably not in the same local network as the FLM.

What to do next?

‹ Water Probe wire length Empty smart meter P1 telegrams ›
bellyf's picture
bellyf |

Who can help? Anyone else with same/similar Landis + Gyr smart meter?

My Fluksometer is not of much use to me in this operating mode I'm afraid.

bellyf's picture
bellyf |

I have been measuring the voltage on the connector at the fluksometer and get the following results:

  • red (gnd) and black (rts) appr 0.2V only
  • red (gnd) and yellow (data) appr 0.08V

I checked for broken connections between the RJ11 and Fluksometer connectors but the connection seem to be OK.

Still no readings on my flukso dash. Also querying they api.flukso.net via JSON only delivers nan values.

What can be wrong? Is the voltage too low?

icarus75's picture
icarus75 |

Your FLM has been offline for the last 7.5 days. Could you bring it back online so that we can remotely have a peek?

bellyf's picture
bellyf |

Since noon today there is no lan-connection any longer.
Q: Can I do a firmware reset to make it accessible again? Cycling the power doesn't solve the problem. The on/off, heartbeat and pan indicators are on but the globe is off.

On my flukso.net page the last heartbeat shows as 01 Dec 2014 12:01:03 (shortly after I made the call with Bart). I also see now the version has changed to 998** (it used to be 244).
I also still see a device and a smart-main/electrical and smart-main/gas sensor on my flukso page with sensor and tokens.

Strange there is no trace of my fluksometer being online as I had it connected for most of the weekend. I have been testing quite a bit on Sunday with a number of resets and each time it came back online (visible on the status page and reporting heartbeats on my flukso.net page).

icarus75's picture
icarus75 |

You can restore the networking defaults of your FLM by keeping the recessed 'toggle' pushbutton pressed between 10 and 30 secs, see the Fluksometer Manual par 1.2. Once the FLM is able to successfully connect with the Flukso server, the globle LED will light up.

bellyf's picture
bellyf |

Fluksometer up and running again. Web status pages are not really different from before.

Status:

  • Model: FLM02B
  • Firmware: 244
  • Time: 1 December 2014 19:02:05 GMT+1
  • reporting mode: ethernet
  • flukso.net ping test: Successful
  • Last server config synchronisation: 30 November 2014 13:14:46 GMT+1
  • Status: successful

Services:

  • Send reading to the Flukso platform: checked
  • Enable local real-time read ins: checked
  • Allow remote firmware upgrades: checked

On Flukso.net

  • version: 244
  • resets: 25
  • Last heartbeat: 01 Dec 2014 19:01:03
  • Sensors: smart-main/electricity and smart-main/gas both with sensor-id and token

I can also do a CURL request but just like before I just get 'nan' values returned:

  1.  curl -k -v -X GET -H "Accept: application/json" -H "X-Version: 1.0" -H "X-Token: xxxx” "https://api.flukso.net/sensor/yyy?interval=hour&unit=watt"
  2. * Adding handle: conn: 0xzzz
  3. * Adding handle: send: 0
  4. * Adding handle: recv: 0
  5. * Curl_addHandleToPipeline: length: 1
  6. * - Conn 0 (0xzzz) send_pipe: 1, recv_pipe: 0
  7. * About to connect() to api.flukso.net port 443 (#0)
  8. *   Trying 178.79.177.6...
  9. * Connected to api.flukso.net (178.79.177.6) port 443 (#0)
  10. * TLS 1.0 connection using TLS_RSA_WITH_AES_256_CBC_SHA
  11. * Server certificate: api.flukso.net
  12. > GET /sensor/yyy?interval=hour&unit=watt HTTP/1.1
  13. > User-Agent: curl/7.30.0
  14. > Host: api.flukso.net
  15. > Accept: application/json
  16. > X-Version: 1.0
  17. > X-Token: xxx
  18. >
  19. < HTTP/1.1 200 OK
  20. * Server nginx/1.4.7 is not blacklisted
  21. < Server: nginx/1.4.7
  22. < Date: Mon, 01 Dec 2014 18:12:24 GMT
  23. < Content-Type: application/json
  24. < Content-Length: 1141
  25. < Connection: keep-alive
  26. < Vary: Accept
  27. < Access-Control-Allow-Origin: *
  28. <
  29. * Connection #0 to host api.flukso.net left intact
  30. [[1417454040,"nan"],[1417454100,"nan"],[1417454160,"nan”],…
  31. .
  32. .
  33. .

icarus75's picture
icarus75 |

I had to do some sensor provisioning in your FLM. All seems to be set up fine now. Could you double-check the voltage between 5- and 6a with and without the RJ11 jack inserted? Should read 5V on your multimeter.

bellyf's picture
bellyf |

With the RJ11 jack insert the voltage is 0.16-0.17V and without the RJ11 jack insert it's fractionally lower at 0.15V. Not a really big change with the values reported yesterday (could be within the error margin of the multimeter?). In any case a far distance from the required 5V.

icarus75's picture
icarus75 |

If you're shipped a replacement daughter board, could you open the FLM and substitute it for the current one? The screws are hidden below the pads.

bellyf's picture
bellyf |

I just had a look at the FLM's inside. I assume I have to replace the small red board with 'flukso' printed on it. This is what I have done occasionally only. Do I need tools (screwdriver?) or do I just carefully try to lift it with my fingers?

bellyf's picture
bellyf |

Icarus ... is there any other info you require from me? Will you send the replacement daughterboard on the basis of my previous answer or do you have another solution in mind?

icarus75's picture
icarus75 |

The replacement daughter board is ready for shipment. It should work out-of-the-box once installed. I've checked the 5V voltage between terminals 5- and 6a as well.

bellyf's picture
bellyf |

After I replaced the daughter board it still don't get any readings. I have now also replaced the cable to the smart meter: I do get 5V between terminals 5- and 6a as well as 5- and 6b.

What is the next step to fix this?

Two observations:

  1. In the log file I now read that the decoder returns empty telegrams:
    Dec 22 16:49:24 flukso-336da5 daemon.err parsed[690]: /usr/sbin/parsed.lua:131: decoder returned an empty telegram
  2. when I try to read real time sensor data (following the instructions in section 3.6 of the manual) I get a HTTP 404 not found error while I got an "< HTTP/1.1 200 OK" message earlier before I reset the Flukso:
    1. curl -v "http://192.168.178.52:8080/sensor/<<smart-main electricity sensor-id>>?version=1.0&interval=minute&unit=watt&callback=realtime"
    2. * About to connect() to 192.168.178.52 port 8080 (#0)
    3. *   Trying 192.168.178.52...
    4. * Adding handle: conn: 0x7ff86a003000
    5. * Adding handle: send: 0
    6. * Adding handle: recv: 0
    7. * Curl_addHandleToPipeline: length: 1
    8. * - Conn 0 (0x7ff86a003000) send_pipe: 1, recv_pipe: 0
    9. * Connected to 192.168.178.52 (192.168.178.52) port 8080 (#0)
    10. > GET /sensor/<<smart-main electricity sensor-id>>?version=1.0&interval=minute&unit=watt&callback=realtime HTTP/1.1
    11. > User-Agent: curl/7.30.0
    12. > Host: 192.168.178.52:8080
    13. > Accept: */*
    14. >
    15. < HTTP/1.1 404 Not Found
    16. < Connection: close
    17. < Content-Type: text/plain
    18. < Transfer-Encoding: chunked
    19. <
    20. * Closing connection 0