Hi,

I want to use a Fluksometer for my German electricity meter (EMH type ehz-IW8E2A5L0EQ2P, see http://shop.co-met.info/artikeldetails/kategorie/zaehler/artikel/amh-dre...) for saving data automatically to Pvoutput. The data I want to gather is the kWh consumed and the kWh returned by a PV system.

In Germany they use the Smart Message Language protocol and D0 interface on electricity meters which can be read by using an Optical Probe (see several 'Schreib-Lesekopf' on http://wiki.volkszaehler.org/hardware/controllers).

Does anybody know if it is possible using the Fluksometer in combination with an Optical Probe?

Cheers,

Vince

Just installed my FLM yesterday and all seamed to go OK, but no data displays in the dash board yet. It shows message: "Error - The call for sensor Mains experienced a timeout. You are probably not in the same local network as the FLM."

I've already RTFM and tried both, ethernet and wifi server connection modes and wifi and ethernet host pc connections. All LEDs are on, heart is beating at 1s (approx).

Syslog contains entries like this at regular intervals: Jun 3 10:57:06 flukso user.info heartbeat[24886]: POST https://api.flukso.net/device/5eaf3d422c5e9671475b3f3d1e44903f: 200

I've configured only one sensor and the FLM was able to synchronize with the server. Currently I'm using wifi for server connection and ethernet for local network connection. My host is Windows 7 at this moment (started installing a VM with Ubuntu).

Several posts in the forum point to server connection issues and sensor configuration issues, tried their recommendations with no success.

Am I missing something? Is there any test I could do to solve it?

Only had my FLM a few weeks and been running well, then this morning on the first day of Winter it stops reporting at 9:21am, checked FLM to find the Globe light is off.

Checked the Status page and everything shows OK, even the ping test to flukso.net and WIFI is connected fine

So not wanting to loose the last three hours data I went into the Sensor setting and saved to force a restart of the DAEMON

Resulting syslog was

Jun 1 02:18:06 flukso-5ddbba daemon.info avahi-daemon[775]: Files changed, reloading.
Jun 1 02:18:06 flukso-5ddbba user.err fsync[17811]: POST https://api.flukso.net/sensor/56cabcf0b107576de2c95774d50aef88: -151
Jun 1 02:18:07 flukso-5ddbba daemon.info fluksod[1194]: processed pulse 72f595e494f15304c533e5233c6c02f1:1401589087:251980
Jun 1 02:18:07 flukso-5ddbba daemon.info fluksod[1194]: processed pulse 5d9d1654db2c1a583d0bf1ffe0baba88:1401589087:81467
Jun 1 02:18:07 flukso-5ddbba user.err fsync[17811]: POST https://api.flukso.net/sensor/72f595e494f15304c533e5233c6c02f1: -151
Jun 1 02:18:08 flukso-5ddbba user.err fsync[17811]: POST https://api.flukso.net/sensor/5d9d1654db2c1a583d0bf1ffe0baba88: -151
Jun 1 02:18:08 flukso-5ddbba user.err fsync[17811]: POST https://api.flukso.net/sensor/9f2b6cab67706c6822bd8ee15b75474e: -151
Jun 1 02:18:09 flukso-5ddbba daemon.info fluksod[1194]: processed pulse 72f595e494f15304c533e5233c6c02f1:1401589089:251981
Jun 1 02:18:09 flukso-5ddbba user.err fsync[17811]: POST https://api.flukso.net/sensor/40ac18d29ab4e35b3a4b485c5b4cf27a: -151
Jun 1 02:18:10 flukso-5ddbba user.err fsync[17811]: POST https://api.flukso.net/sensor/018c94300d4b7bb4cd73576e4768ca13: -151
Jun 1 02:18:10 flukso-5ddbba user.err fsync[17811]: POST https://api.flukso.net/sensor/41a609e38982399fcbdf9307cbead641: -151
Jun 1 02:18:11 flukso-5ddbba daemon.info fluksod[1194]: processed pulse 72f595e494f15304c533e5233c6c02f1:1401589091:251982
Jun 1 02:18:11 flukso-5ddbba user.err fsync[17811]: POST https://api.flukso.net/sensor/a18da6c420d0a134744cdf93b649fca3: -151
Jun 1 02:18:11 flukso-5ddbba user.err fsync[17811]: fsync exit status: 7, synchronisation with Flukso server failed
Jun 1 02:18:12 flukso-5ddbba daemon.info parsed[1199]: Caught a SIGTERM. Exiting...
Jun 1 02:18:12 flukso-5ddbba daemon.info fluksod[1194]: Caught a SIGTERM. Exiting...
Jun 1 02:18:13 flukso-5ddbba daemon.info spid[1191]: Caught a SIGTERM. Exiting...
Jun 1 02:18:14 flukso-5ddbba daemon.info supd[1188]: Caught a SIGTERM. Exiting...
Jun 1 02:18:15 flukso-5ddbba daemon.info supd[17830]: Sucessfully started with DEAMON=supd and DAEMON_PATH=/var/run/supd
Jun 1 02:18:15 flukso-5ddbba daemon.info spid[17833]: Sucessfully started with DEAMON=spid and DAEMON_PATH=/var/run/spid
Jun 1 02:18:16 flukso-5ddbba daemon.info fluksod[17836]: Sucessfully started with DEAMON=fluksod and DAEMON_PATH=/var/run/fluksod
Jun 1 02:18:16 flukso-5ddbba daemon.info parsed[17841]: Sucessfully started with DEAMON=parsed and DAEMON_PATH=/var/run/parsed
Jun 1 02:18:20 flukso-5ddbba daemon.info fluksod[17836]: processed pulse 72f595e494f15304c533e5233c6c02f1:1401589100:251987
Jun 1 02:18:21 flukso-5ddbba user.info heartbeat[17844]: POST https://api.flukso.net/device/5ddbba6ed40dc604b70f12ef55725c06: 200
Jun 1 02:18:22 flukso-5ddbba daemon.info fluksod[17836]: processed pulse 72f595e494f15304c533e5233c6c02f1:1401589102:251988

Which from the second last line appeared to have fixed the issue

However GLOBE went out again and the the following syslog err for both sensors

Jun 1 02:23:21 flukso-5ddbba daemon.info fluksod[17836]: processed pulse 72f595e494f15304c533e5233c6c02f1:1401589401:252169
Jun 1 02:23:22 flukso-5ddbba daemon.err fluksod[17836]: POST https://api.flukso.net/sensor/72f595e494f15304c533e5233c6c02f1: -151
Jun 1 02:23:22 flukso-5ddbba daemon.err fluksod[17836]: POST https://api.flukso.net/sensor/5d9d1654db2c1a583d0bf1ffe0baba88: -151
Jun 1 02:23:22 flukso-5ddbba daemon.info fluksod[17836]: processed pulse 5d9d1654db2c1a583d0bf1ffe0baba88:1401589402:81522

If I completely power down the FLM do I loose the data ?

And is that the next step to try and rectify

Thanks for any assistance

Glenn

Not sure re the reference to the DHCP bits mean. Seems to be looking for something thats not there?

May 29 07:44:14 flukso-4d93ce daemon.info fluksod[4191]: processed pulse b4a04e554f01781b518eeae703abebb8:1401349454:2099559
May 29 07:44:15 flukso-4d93ce daemon.info fluksod[4191]: processed pulse b4a04e554f01781b518eeae703abebb8:1401349455:2099560
May 29 07:44:17 flukso-4d93ce daemon.info fluksod[4191]: processed pulse b4a04e554f01781b518eeae703abebb8:1401349457:2099561
May 29 07:44:17 flukso-4d93ce daemon.info dnsmasq-dhcp[770]: DHCPREQUEST(br-lan) 192.168.0.24 5c:95:ae:ae:c9:5a
May 29 07:44:17 flukso-4d93ce daemon.info dnsmasq-dhcp[770]: DHCPNAK(br-lan) 192.168.0.24 5c:95:ae:ae:c9:5a wrong network
May 29 07:44:18 flukso-4d93ce daemon.info fluksod[4191]: processed pulse b4a04e554f01781b518eeae703abebb8:1401349458:2099562
May 29 07:44:19 flukso-4d93ce daemon.info fluksod[4191]: processed pulse b4a04e554f01781b518eeae703abebb8:1401349459:2099563
May 29 07:44:20 flukso-4d93ce daemon.info fluksod[4191]: processed pulse b4a04e554f01781b518eeae703abebb8:1401349460:2099564
May 29 07:44:21 flukso-4d93ce daemon.info dnsmasq-dhcp[770]: DHCPDISCOVER(br-lan) 5c:95:ae:ae:c9:5a
May 29 07:44:21 flukso-4d93ce daemon.info dnsmasq-dhcp[770]: DHCPOFFER(br-lan) 192.168.255.240 5c:95:ae:ae:c9:5a
May 29 07:44:21 flukso-4d93ce daemon.info dnsmasq-dhcp[770]: DHCPREQUEST(br-lan) 192.168.0.24 5c:95:ae:ae:c9:5a
May 29 07:44:21 flukso-4d93ce daemon.info dnsmasq-dhcp[770]: DHCPNAK(br-lan) 192.168.0.24 5c:95:ae:ae:c9:5a wrong server-ID
May 29 07:44:21 flukso-4d93ce daemon.info dnsmasq-dhcp[770]: DHCPREQUEST(br-lan) 192.168.0.24 5c:95:ae:ae:c9:5a
May 29 07:44:21 flukso-4d93ce daemon.info dnsmasq-dhcp[770]: DHCPNAK(br-lan) 192.168.0.24 5c:95:ae:ae:c9:5a wrong server-ID
May 29 07:44:22 flukso-4d93ce daemon.info fluksod[4191]: processed pulse b4a04e554f01781b518eeae703abebb8:1401349462:2099565
May 29 07:44:23 flukso-4d93ce daemon.info fluksod[4191]: processed pulse b4a04e554f01781b518eeae703abebb8:1401349463:2099566
May 29 07:44:24 flukso-4d93ce daemon.info fluksod[4191]: processed pulse b4a04e554f01781b518eeae703abebb8:1401349464:2099567
May 29 07:44:26 flukso-4d93ce daemon.info fluksod[4191]: processed pulse b4a04e554f01781b518eeae703abebb8:1401349466:2099568
May 29 07:44:27 flukso-4d93ce daemon.info fluksod[4191]: processed pulse b4a04e554f01781b518eeae703abebb8:1401349467:2099569
May 29 07:44:28 flukso-4d93ce daemon.info fluksod[4191]: processed pulse b4a04e554f01781b518eeae703abebb8:1401349468:2099570
May 29 07:44:30 flukso-4d93ce daemon.info fluksod[4191]: processed pulse b4a04e554f01781b518eeae703abebb8:1401349470:2099571
May 29 07:44:31 flukso-4d93ce daemon.info fluksod[4191]: processed pulse b4a04e554f01781b518eeae703abebb8:1401349471:2099572
May 29 07:44:32 flukso-4d93ce daemon.info fluksod[4191]: processed pulse b4a04e554f01781b518eeae703abebb8:1401349472:2099573
May 29 07:44:32 flukso-4d93ce daemon.info dnsmasq-dhcp[770]: DHCPINFORM(br-lan) 192.168.0.14 08:11:96:91:a5:68
May 29 07:44:32 flukso-4d93ce daemon.info dnsmasq-dhcp[770]: DHCPACK(br-lan) 192.168.0.14 08:11:96:91:a5:68 Bazzle-PC
May 29 07:44:34 flukso-4d93ce daemon.info fluksod[4191]: processed pulse b4a04e554f01781b518eeae703abebb8:1401349474:2099574
May 29 07:44:35 flukso-4d93ce daemon.info fluksod[4191]: processed pulse b4a04e554f01781b518eeae703abebb8:1401349475:2099575
May 29 07:44:36 flukso-4d93ce daemon.info fluksod[4191]: processed pulse b4a04e554f01781b518eeae703abebb8:1401349476:2099576
May 29 07:44:38 flukso-4d93ce daemon.info fluksod[4191]: processed pulse b4a04e554f01781b518eeae703abebb8:1401349478:2099577
May 29 07:44:39 flukso-4d93ce daemon.info fluksod[4191]: processed pulse b4a04e554f01781b518eeae703abebb8:1401349479:2099578
May 29 07:44:40 flukso-4d93ce daemon.info fluksod[4191]: processed pulse b4a04e554f01781b518eeae703abebb8:1401349480:2099579
May 29 07:44:41 flukso-4d93ce daemon.info fluksod[4191]: processed pulse b4a04e554f01781b518eeae703abebb8:1401349481:2099580

I want to install a Fluksometer but I'm not a professional, so I hope to get some help here before ordering..... I posted some photos:
http://www.postimg.com/image/151000/img_0315-150479.jpg
http://www.postimg.com/image/151000/image-150487.jpg
http://www.postimg.com/image/151000/image-150488.jpg

- I have 3 phases, so I wonder if there's enough space under in the fuse box to install 3 clamps around the wires or can I spread the clamps under and above the differential?
- how many supplementary sensors can be installed: if possible I would like to install a gas- and waterprobe and a kWh solar meter too (or is there a limit of 2 additional?)
- my gasmeter is a krom Schröder BK6 (Elster Handel). Is the gasprobe suitable here?

Thanks for your help!