[OBIS V2] - Jetzt auch mit SML-Unterstützung

dbox2user · 17 Mai 2016, 20:06:16

Hallo Stefan!
Danke für die neue Version des Moduls!!!!!!!!

Jetzt funzt es auch bei meinem "tollen" Zähler.
Anbei zwei pics....
Einmal direkt nach dem anlegen und einmal mit den channel-Attribut.

DANKE !!!

Gruß,
Chris

Icinger · 17 Mai 2016, 20:27:51

Hi,

sorry, my mistake.
Uploaded the fixed version now.
For readings and the channel-attribute: All ":" and "-" are now converted to "."
So an OBIS-Number would look like 0.1.24.2.1

For the Gas-Reading: You have to give the OBIS-Number to the attribute, so correct is:

Code Auswählen

"0.1.24.2.1"=>"total_gas"

Have a nice evening,

Stefan

KölnSolar · 17 Mai 2016, 21:09:28

Hi Stefan,

ZitatFrage an alle: Wollt ihr ein Attribut, mit dem man ungenutzte, unbekannte Readings auf "stumm" setzen kann? Oder ist das egal und ihr ignoriert diese Readings dann einfach?

BITTE etwas zum stumm schalten, denn jetzt kommt allermöglicher Schrott als neues reading an

Und dann hatte ich doch noch das Problem, dass ohne Angabe des metertypes nicht immer Standard resultiert. Systematik konnte ich keine feststellen. Mal gehts, mal nicht. Was ich aber feststellen konnte: Selbst wenn man es über ein modify durch ändern des metertypes=Standard korrigiert, bleibt der pollingmode=on außen vor. Warum auch immer. Ich hab jetzt einfach mal metertype=Standard in der cfg definiert und dann läufts auch wie geschmiert.
Grüße, Markus

HarryT · 17 Mai 2016, 22:46:41

Hi Stefan

Zitat von: Icinger am 17 Mai 2016, 20:27:51
Hi,

sorry, my mistake.

No problem, I am happy I can provide a bit help by testing. Thanks for all the work.

Zitat

Uploaded the fixed version now.
For readings and the channel-attribute: All ":" and "-" are now converted to "."
So an OBIS-Number would look like 0.1.24.2.1
For the Gas-Reading: You have to give the OBIS-Number to the attribute, so correct is:
Code Auswählen Erweitern
"0.1.24.2.1"=>"total_gas"

Nice, this works fine.
However the old name Gas is still displayed in the detail page but not updated. The same for other names I don't use anymore. How to get rid of them? Resetting my desktop and my fritzbox (on which fhem is running) is not sufficient. Shutting FHEM down and removing the values from fhem.save and start FHEM again works but it doesn't look as the way how this should be handled.

0.0.1.0.0 is still 01-01-1970 01:00:01 and that doesn't change. (It is the timestamp of the last message) If I remember correct this worked in the past.

Maybe you missed it, in
2016.05.15 18:10:03 5: OBIS (MyObis) - Msg-Parse: 0-1:24.2.1(160515180000S)(00041.661*m3)
160515180000S is the time of the last gas measurement. Is it possible to make a reading for it?

Zitat

Have a nice evening,

Stefan

Although it is a bit late, have a nice evening too.

BTW I don't mind to see the other readings which I don't know yet what they mean. Maybe I can find out if I see the values.

{HT}

KölnSolar · 17 Mai 2016, 22:54:21

ZitatShutting FHEM down and removing the values from fhem.save and start FHEM again works but it doesn't look as the way how this should be handled.

similar, but more easy: delete the device(without saving fhem.cfg) - shutdown - restart - Voila
Regards, Markus

HarryT · 17 Mai 2016, 23:13:33

Hoi

Do you guys know this document?
http://files.domoticaforum.eu/uploads/Smartmetering/DSMR%20v4.0%20final%20P1.pdf

Now I only miss the meaning of code 1.0.22.7.0

{HT}

Just found the link below which gives a newer document:
http://nbn-assets.netbeheernederland.nl/32768/?k=aHyn8n3Kk9ch_GFgG7TdJk-DFCl-ZaBOna0WUSvqYBfhdggUuSR_pbVF6YbO6SYcWv6IjNhu4-uQCkkVTjXFiJaPWY1T_KytQrYJnnVLQdYOeBw6hGWkqpyZOGTKnhpin2aQD8CS6v3rtlya3Jx2X_4JEd2NV9RcbJaN_CQNppERAvqLFctIKjWN6FCgb6bQ56M9wRdgH5N_ssdkN5VHiiiK6_ZuXzgJEzLIG9gDOALQ-Q8-qCt9dum54l-RAToBRuYVOflju8sh970jmgi1Z4wMxr9fAAxTPAw2waJPthSws_mU4WSE2o_zQu5pngCCqxkkXbGnQCBxf7ReaJ9nHvl9fvRU8igWz9hM6pCl4PdozRoAxHMhmvmO4hRsAm62sr2mdqFlfOQGYLAmwO1cNP0zZo0tnLQm6lynS5ttBEyGsUoFNrBtf81Ad74MUCo3dlTQsMKVtbrEIjR3jrrwpsJgMMy1rhG4WwmtnF-aLqLSBB8YlAcx5Hw8xBPc588OK4LMTuKWfP7DxhaAYsxEvmhUbWERFjdLVSt84PqWMhkM9BSLRhVGDFTJmr_ydv5Zn1vFRnjbwKk_01RRiuiNGwjJm6glrcCVLj0jPNxQW6emC-FNU5DPg3W2w6JIHrKgcHl1cnriYkagbwhcKhaYFUTj8dMNiXlglp83Q0eAwH526iUxZy_KZIQ-sj_x4wJmdDjQ1fof_yPuVf5KtH9iZZDOYXdYqRLM5h0QNs4UhHfJcKQXtPtrOxDJne3KQMCx8ugcitkgw1dYDnbTe3HhEKV2GTvGRm0dMmc_T6aNszg=&u=

Icinger · 18 Mai 2016, 05:31:06

Zitatdelete the device(without saving fhem.cfg) - shutdown - restart - Voila

ZitatHowever the old name Gas is still displayed in the detail page but not updated. The same for other names I don't use anymore. How to get rid of them? Resetting my desktop and my fritzbox (on which fhem is running) is not sufficient. Shutting FHEM down and removing the values from fhem.save and start FHEM again works but it doesn't look as the way how this should be handled.

That what's "deletereading" is for

Just a simple

Code Auswählen

deletereading <device> <reading-regexp>
and everything is fine

Cheers,

Stefan

Icinger · 18 Mai 2016, 06:09:53

Zitat0.0.1.0.0 is still 01-01-1970 01:00:01 and that doesn't change. (It is the timestamp of the last message) If I remember correct this worked in the past.

No, this never worked....
I'm unsure, how to deal with that. Standard-OBIS should be a Unix-Timestamp, and also .
Your reading is a <ddmmyyhhmmss>-Format. Now sure how to distinguish that.
Same for

Zitat2016.05.15 18:10:03 5: OBIS (MyObis) - Msg-Parse: 0-1:24.2.1(160515180000S)(00041.661*m3)

That first pair of () would need a very special treatment.....

BTW. Just uploaded a new version with a "ignoreUnknown"-Attribute, so that unknown readings (x.x.x.x) are ignored.
If you use a channel-attribute, which covers this unknown readings, these are correctly handled.

HarryT · 18 Mai 2016, 22:31:35

Zitat von: Icinger am 18 Mai 2016, 06:09:53
No, this never worked....
I'm unsure, how to deal with that. Standard-OBIS should be a Unix-Timestamp, and also .
Your reading is a <ddmmyyhhmmss>-Format. Now sure how to distinguish that.
Same for That first pair of () would need a very special treatment.....

BTW. Just uploaded a new version with a "ignoreUnknown"-Attribute, so that unknown readings (x.x.x.x) are ignored.
If you use a channel-attribute, which covers this unknown readings, these are correctly handled.

Nice. With the channel attribute I also used
"1.0.2.8.1"=>"ElektriciteitsstandTerugleveringLaagtarief",
to overwrite the channel settings in the OBIS module. This works except it adds -Ch1 to the names. Is this intentional? No big deal if it stays this way.
The same for the dates. I like it to see the dates, but if it is to difficult, it is not a show stopper.

BTW, the OBIS module changed the last week from a simple module to a utility-module with much more possibilities. But it needs specific settings to work nice. I will post my settings as I think these will be a good starting point for almost every smartmeter user in the netherlands.

Thansk for all the fantastic work.

{HT}

HarryT · 18 Mai 2016, 22:41:36

Hi

Here are my settings for the 47_OBIS.pm module. I use a Landis E350 smartmeter with a BK-G4 ETB gasmeter in the Netherlands. Most likely it is compatible with other smartmeters in the Netherlands.

In my fhem.cfg:

Code Auswählen


define SmartMeter OBIS /dev/ttyUSB1@115200,8,N,1
attr SmartMeter channels {"0.0.1.0.0"=>"date-time_laatste_P1_bericht",  "0.1.24.1.0"=>"_andere_apparaten_op_de_M-Bus", "0.1.24.2.1"=>"VerbruikteHoeveelheidGas", "0.1.96.1.0"=>"_identificatie_van_de_gasmeter", "0.0.96.1.1"=>"_equipment identifier", "0.0.96.7.9"=>"_number_of_long power_failures_in_any_phase", "0.0.96.7.21"=>"_number_of_power_failures_in_any_phase", "0.0.96.13.1"=>"BerichtNumeriek", "0.0.96.13.0"=>"BerichtTekst", "0.0.96.14.0"=>"ActueleTarief", "1.0.1.7.0"=>"HuidigVerbruik", "1.0.2.7.0"=>"HuidigTeruglevering", "1.0.1.8.1"=>"ElektriciteitsstandLaagtarief", "1.0.1.8.2"=>"ElektriciteitsstandNormaaltarief", "1.0.2.8.1"=>"ElektriciteitsstandTerugleveringLaagtarief", "1.0.2.8.2"=>"ElektriciteitsstandTerugleveringNormaaltarief", "1.0.21.7.0"=>"_Instantaneous_active_power_L1_+P_in_W_resolution", "1.0.22.7.0"=>"_Instantaneous_active_power_L1_-P_in_W_resolution", "1.0.32.32.0"=>"_number_of_voltage_sags_in_phase_L1", "1.0.32.36.0"=>"_number_of_voltage_swells_in_phase_L1", "1.0.99.97.0"=>"_power_Failure_Event_Log_long_power_failures", "1.0.31.7.0"=>"_instantaneous_current_L1_-P", "1.3.0.2.8"=>"_DSMR_version_ 4.0"}
attr SmartMeter event-on-change-reading VerbruikteHoeveelheidGas,BerichtNumeriek,BerichtTekst,ActueleTarief,HuidigVerbruik,HuidigTeruglevering,ElektriciteitsstandLaagtarief_Ch1,ElektriciteitsstandNormaaltarief_Ch2,ElektriciteitsstandTerugleveringLaagtarief_Ch1, ElektriciteitsstandTerugleveringNormaaltarief_Ch2
attr SmartMeter room Sturing
#attr SmartMeter verbose 5
define FileLog_SmartMeter FileLog ../USB-LOGGING/logs/fhem/%Y-%m-SmartMeter.log SmartMeter
attr FileLog_SmartMeter logtype text
attr FileLog_SmartMeter room Sturing
define weblink_SmartMeter SVG FileLog_SmartMeter:mySmartMeter:CURRENT
attr weblink_SmartMeter label "SmartMeter Max $data{max1}, Last $data{currval1}"
attr weblink_SmartMeter room Plots

And I have a plot file fhem/www/gplot/mySmartMeter.gplot

Code Auswählen


# Created by FHEM/98_SVG.pm, 2016-05-18 22:16:37
set terminal png transparent size <SIZE> crop
set output '<OUT>.png'
set xdata time
set timefmt "%Y-%m-%d_%H:%M:%S"
set xlabel " "
set title '<L1>'
set ytics nomirror
set y2tics 
set grid ytics y2tics
set ylabel "kW"
set y2label "m3"

#FileLog_SmartMeter 4:SmartMeter.HuidigTeruglevering\x3a:1:
#FileLog_SmartMeter 4:SmartMeter.HuidigVerbruik\x3a:1:
#FileLog_SmartMeter 4:SmartMeter.VerbruikteHoeveelheidGas\x3a:1:

plot "<IN>" using 1:2 axes x1y1 title 'kW geleverd' ls l1fill lw 1 with steps,\
     "<IN>" using 1:2 axes x1y1 title 'kW gebruikt' ls l0fill lw 1 with steps,\
     "<IN>" using 1:2 axes x1y2 title 'm3 gebruikt' ls l3 lw 1 with lines

Hope this helps people to start with the 47_OBIS module

{HT}

HarryT · 19 Mai 2016, 22:31:09

Hi Stefan

After the latest update I get these error messages:
2016.05.19 22:14:22 1: PERL WARNING: Use of uninitialized value $channel in substitution (s///) at ./FHEM/47_OBIS.pm line 335.
2016.05.19 22:14:22 1: PERL WARNING: Use of uninitialized value $channel in substitution (s///) at ./FHEM/47_OBIS.pm line 336.
2016.05.19 22:14:22 1: PERL WARNING: Use of uninitialized value $channel in hash element at ./FHEM/47_OBIS.pm line 408.
2016.05.19 22:14:22 1: PERL WARNING: Use of uninitialized value $1 in hash element at ./FHEM/47_OBIS.pm line 408.

{HT}

Icinger · 20 Mai 2016, 05:56:29

Hi Harry,

a little bit mor Info would be great

Just a Verbose 5 of the Data please.

Cheers, Stefan

HarryT · 20 Mai 2016, 14:47:28

Zitat von: Icinger am 20 Mai 2016, 05:56:29
Hi Harry,

a little bit mor Info would be great

Just a Verbose 5 of the Data please.

Cheers, Stefan

Hi Stefan

It looks as if verbose 5 doesn't give more info, but there is another line in the log which might be usefull:

Constant subroutine main::URL redefined at /var/InternerSpeicher/fhem/lib/perl5/5.12.2/constant.pm line 130, <$fh> line 444.
main::OBIS_decodeTL() called too early to check prototype at ./FHEM/47_OBIS.pm line 623, <$fh> line 507.
Use of uninitialized value in concatenation (.) or string at ./FHEM/47_OBIS.pm line 129, <$fh> line 507.
Use of uninitialized value in concatenation (.) or string at ./FHEM/47_OBIS.pm line 129, <$fh> line 507.
2016.05.20 14:36:52 3: Opening SmartMeter device /dev/ttyUSB1
2016.05.20 14:36:52 3: Setting SmartMeter serial parameters to 115200,8,N,1
2016.05.20 14:36:52 3: SmartMeter device opened
2016.05.20 14:36:55 3: ZWave: cannot load Crypt::Rijndael, SECURITY class disabled
2016.05.20 14:36:57 1: Including ./fhem.save
2016.05.20 14:36:58 1: usb create starting
2016.05.20 14:37:01 1: usb create end
2016.05.20 14:37:01 0: Featurelevel: 5.7
2016.05.20 14:37:01 0: Server started with 162 defined entities (fhem.pl:11256/2016-04-16 perl:5.012002 os:linux user:root pid:24400)
2016.05.20 14:37:01 2: ZWDongle_ProcessSendStack: no ACK, resending message 0107000301020100f9
2016.05.20 14:37:01 1: PERL WARNING: Use of uninitialized value $channel in substitution (s///) at ./FHEM/47_OBIS.pm line 335.
2016.05.20 14:37:01 1: PERL WARNING: Use of uninitialized value $channel in substitution (s///) at ./FHEM/47_OBIS.pm line 336.
2016.05.20 14:37:01 1: PERL WARNING: Use of uninitialized value $channel in hash element at ./FHEM/47_OBIS.pm line 408.
2016.05.20 14:37:01 1: PERL WARNING: Use of uninitialized value $1 in hash element at ./FHEM/47_OBIS.pm line 408.

And with verbose 5:

2016.05.20 14:42:45 0: Server shutdown
Useless use of a constant (myTwilight) in void context at ./FHEM/99_myUtils.pm line 39.
Useless use of a constant (twilight) in void context at ./FHEM/99_myUtils.pm line 39.
Useless use of a constant (myTwilight) in void context at ./FHEM/99_myUtils.pm line 40.
Useless use of a constant (twilight_weather) in void context at ./FHEM/99_myUtils.pm line 40.
main::GetOutsideWeather() called too early to check prototype at ./FHEM/99_myUtils.pm line 24.
2016.05.20 14:42:50 1: Including fhem.cfg
2016.05.20 14:42:51 3: telnetPort: port 7072 opened
2016.05.20 14:42:52 3: WEB: port 8083 opened
2016.05.20 14:42:52 3: WEBphone: port 8084 opened
2016.05.20 14:42:52 3: WEBtablet: port 8085 opened
2016.05.20 14:42:52 3: Opening RFXTRXUSB device /dev/ttyUSB0
2016.05.20 14:42:53 3: RFXTRXUSB device opened
2016.05.20 14:42:56 1: TRX: Initialization Error hexline='0873ff', expected 0d0100......................
2016.05.20 14:42:56 1: Cannot init /dev/ttyUSB0, ignoring it (RFXTRXUSB)
2016.05.20 14:42:56 3: Opening TRX_0 device /dev/ttyUSB0
2016.05.20 14:42:56 3: Setting TRX_0 serial parameters to 38400,8,N,1
2016.05.20 14:42:56 3: TRX_0 device opened
2016.05.20 14:42:58 1: TRX: Init OK
2016.05.20 14:42:58 1: TRX: Init status: '433.92MHz transceiver, firmware=64, protocols enabled: Lighting4 LaCrosse Hideki Visonic OREGON HOMEEASY AC X10 '
2016.05.20 14:42:58 3: Opening ZWDongle_0 device /dev/ttyACM0
2016.05.20 14:42:58 3: Setting ZWDongle_0 serial parameters to 115200,8,N,1
2016.05.20 14:42:58 3: ZWDongle_0 device opened
2016.05.20 14:43:03 3: owo mijnWeer: created
Constant subroutine main::URL redefined at /var/InternerSpeicher/fhem/lib/perl5/5.12.2/constant.pm line 130, <$fh> line 444.
main::OBIS_decodeTL() called too early to check prototype at ./FHEM/47_OBIS.pm line 623, <$fh> line 507.
Use of uninitialized value in concatenation (.) or string at ./FHEM/47_OBIS.pm line 129, <$fh> line 507.
Use of uninitialized value in concatenation (.) or string at ./FHEM/47_OBIS.pm line 129, <$fh> line 507.
2016.05.20 14:43:04 3: Opening SmartMeter device /dev/ttyUSB1
2016.05.20 14:43:04 3: Setting SmartMeter serial parameters to 115200,8,N,1
2016.05.20 14:43:04 3: SmartMeter device opened
2016.05.20 14:43:07 3: ZWave: cannot load Crypt::Rijndael, SECURITY class disabled
2016.05.20 14:43:09 1: Including ./fhem.save
2016.05.20 14:43:10 1: usb create starting
2016.05.20 14:43:13 1: usb create end
2016.05.20 14:43:13 0: Featurelevel: 5.7
2016.05.20 14:43:13 0: Server started with 162 defined entities (fhem.pl:11256/2016-04-16 perl:5.012002 os:linux user:root pid:24618)
2016.05.20 14:43:13 2: ZWDongle_ProcessSendStack: no ACK, resending message 0107000301020100f9
2016.05.20 14:43:13 5: OBIS (SmartMeter) - Msg-Parse:
/XMX5LGBBFG1009198749
2016.05.20 14:43:13 1: PERL WARNING: Use of uninitialized value $channel in substitution (s///) at ./FHEM/47_OBIS.pm line 335.
2016.05.20 14:43:13 1: PERL WARNING: Use of uninitialized value $channel in substitution (s///) at ./FHEM/47_OBIS.pm line 336.
2016.05.20 14:43:13 1: PERL WARNING: Use of uninitialized value $channel in hash element at ./FHEM/47_OBIS.pm line 408.
2016.05.20 14:43:13 5: OBIS (SmartMeter) - Msg-Parse:
2016.05.20 14:43:13 5: OBIS (SmartMeter) - Msg-Parse: 1-3:0.2.8(42)
2016.05.20 14:43:13 5: OBIS (SmartMeter) - Msg-Parse: 0-0:1.0.0(160520144306S)
2016.05.20 14:43:13 5: OBIS (SmartMeter) - Msg-Parse: 0-0:96.1.1(4530303331303033313438313939363135)
2016.05.20 14:43:13 5: OBIS (SmartMeter) - Msg-Parse: 1-0:1.8.1(000090.025*kWh)
2016.05.20 14:43:13 5: OBIS (SmartMeter) - Msg-Parse: 1-0:1.8.2(000031.211*kWh)
2016.05.20 14:43:13 5: OBIS (SmartMeter) - Msg-Parse: 1-0:2.8.1(000098.284*kWh)
2016.05.20 14:43:13 5: OBIS (SmartMeter) - Msg-Parse: 1-0:2.8.2(000192.568*kWh)
2016.05.20 14:43:13 5: OBIS (SmartMeter) - Msg-Parse: 0-0:96.14.0(0002)
2016.05.20 14:43:13 5: OBIS (SmartMeter) - Msg-Parse: 1-0:1.7.0(00.000*kW)
2016.05.20 14:43:13 5: OBIS (SmartMeter) - Msg-Parse: 1-0:2.7.0(00.628*kW)
2016.05.20 14:43:13 5: OBIS (SmartMeter) - Msg-Parse: 0-0:96.7.21(00001)
2016.05.20 14:43:13 5: OBIS (SmartMeter) - Msg-Parse: 0-0:96.7.9(00000)
2016.05.20 14:43:13 5: OBIS (SmartMeter) - Msg-Parse: 1-0:99.97.0(0)(0-0:96.7.19)
2016.05.20 14:43:13 5: OBIS (SmartMeter) - Msg-Parse: 1-0:32.32.0(00000)
2016.05.20 14:43:13 5: OBIS (SmartMeter) - Msg-Parse: 1-0:32.36.0(00000)
2016.05.20 14:43:13 5: OBIS (SmartMeter) - Msg-Parse: 0-0:96.13.1()
2016.05.20 14:43:13 5: OBIS (SmartMeter) - Msg-Parse: 0-0:96.13.0()
2016.05.20 14:43:13 5: OBIS (SmartMeter) - Msg-Parse: 1-0:31.7.0(004*A)
2016.05.20 14:43:13 5: OBIS (SmartMeter) - Msg-Parse: 1-0:21.7.0(00.000*kW)
2016.05.20 14:43:13 5: OBIS (SmartMeter) - Msg-Parse: 1-0:22.7.0(00.798*kW)
2016.05.20 14:43:13 5: OBIS (SmartMeter) - Msg-Parse: 0-1:24.1.0(003)
2016.05.20 14:43:21 5: OBIS (SmartMeter) - Msg-Parse: 0-1:96.1.0(4730303235303033333630333031323136)
2016.05.20 14:43:21 5: OBIS (SmartMeter) - Msg-Parse: 0-1:24.2.1(160520140000S)(00043.563*m3)
2016.05.20 14:43:21 5: OBIS (SmartMeter) - Msg-Parse: !C02C
2016.05.20 14:43:21 1: PERL WARNING: Use of uninitialized value $1 in hash element at ./FHEM/47_OBIS.pm line 408.
2016.05.20 14:43:21 5: OBIS (SmartMeter) - Msg-Parse: /XMX5LGBBFG1009198749

Hope thise helps
{HT}

Icinger · 22 Mai 2016, 11:36:27

Hi guys,

hope everything works now? Uploaded a new version 3 Days ago to fix this Startup-Problem.

Any complains?

Sunny Sunday,

Stefan

HarryT · 22 Mai 2016, 13:36:24

Hi Stefan

Just updated to the latest version.

Right after the start I get:

Constant subroutine main::URL redefined at /var/InternerSpeicher/fhem/lib/perl5/5.12.2/constant.pm line 130, <$fh> line 444.
main::OBIS_decodeTL() called too early to check prototype at ./FHEM/47_OBIS.pm line 629, <$fh> line 507.
Use of uninitialized value in concatenation (.) or string at ./FHEM/47_OBIS.pm line 129, <$fh> line 507.
Use of uninitialized value in concatenation (.) or string at ./FHEM/47_OBIS.pm line 129, <$fh> line 507.
2016.05.22 13:09:21 3: Opening SmartMeter device /dev/ttyUSB1
2016.05.22 13:09:21 3: Setting SmartMeter serial parameters to 115200,8,N,1
2016.05.22 13:09:21 3: SmartMeter device opened

But the module works nice.

There is an isssue, but I don't know if this is in the smartmeter or in your module:
2016-05-22_12:29:00 SmartMeter CurConsume: 2.267
2016-05-22_12:29:10 SmartMeter CurConsume: 2.127
2016-05-22_12:29:20 SmartMeter CurConsume: 0
2016-05-22_12:29:20 SmartMeter CurFeed: 2.244
2016-05-22_12:29:30 SmartMeter CurFeed: 0.391
2016-05-22_12:29:40 SmartMeter CurFeed: 0.627

The measurements on 12:29:20 can't be right. They should be the opposite. I have seen more strange readigns, but not investigated them. These are simply impossible. It seems there is sometimes an issue when there is a switch from consume to feed.

Further I didn't find a way to get the time of the last changed readings. It is show on the webinterface, but when I use ReadingsTimestamp("SmartMeter","HuidigVerbruik","0") I simply get the last time SmartMeter did on update. Not the last change. Is there a way to get the last change of a reading? I use event-on-change.

{HT}