Plugin: Smart Meter DSMR P1 port Reader

TwannieM · July 7, 2015, 2:34pm

Hi Rene

This is in my control panel so i still don’t know what you mean

Meter Type: KFM5KAIFA-METER Active Tariff: 2(1=low 2=High) House:227KWHImport T1:123 KWHImport T2:104 KWHExport T1:0 KWHExport T2:0 KWHImport Gas:10M3

regards

TwannieM · July 7, 2015, 2:38pm

Hi Rene

something total different… do you have dimmable led spots at home?
I always have flickering lights especially when the street lights are switched. Used to have that with KAKU dimmers but now also with Qubuino dimmer

reneboer · July 7, 2015, 2:54pm

[quote=“TwannieM, post:21, topic:187190”]Hi Rene

This is in my control panel so i still don’t know what you mean

Meter Type: KFM5KAIFA-METER Active Tariff: 2(1=low 2=High) House:227KWHImport T1:123 KWHImport T2:104 KWHExport T1:0 KWHExport T2:0 KWHImport Gas:10M3

regards[/quote]
That shows the 1.1 version panel. Did you upgrade and refresh your browser?

TwannieM · July 7, 2015, 3:21pm

I think I might have used the app update

TwannieM · July 7, 2015, 3:27pm

Okay, I also have 4.0 while my meter itself mentiond made in 2015… ???

reneboer · July 7, 2015, 3:39pm

I think the v5 meters will not be available until 2016 at best. See [url=http://www.energytracker.nl/nl/http-www-energeia-nl-news-php-id-54441]Home - Engerytracker

The other changes look nice as well, but not sure a Vera can keep up with all that :o

Cheers Rene

reneboer · August 23, 2015, 3:31pm

Hi,

Just released version 1.4

Version 1.4 changes:

Added support for ALTUI.
Now reads the meter numbers and shows them on the control panel.

Cheers Rene

TwannieM · August 24, 2015, 1:49pm

Hi Rene

I noticed when manually apdating i get a lua error
Luup : Downloading file: J_SmartMeter.js
Smart Meter DSMR P1 port reader : lua error

reneboer · August 24, 2015, 2:03pm

Hi Twannie,

Do you get that after a reload? Do you have ALTUI installed?

Cheers Rene

TwannieM · August 26, 2015, 4:17pm

I only got the message once the first time luup rebooted after updating the app.
I do not have altui

reneboer · August 27, 2015, 11:09am

[quote=“TwannieM, post:30, topic:187190”]I only got the message once the first time luup rebooted after updating the app.
I do not have altui[/quote]
Ok good. That can indeed happen when a new version loads. I see it with some other plugins that I have installed via the Market and then manually update too.

Cheers Rene

orangina · August 29, 2015, 8:23am

Mine is working almost… after a rebooting Vera I get results. But the port reader isn’t filling, as you can see in the attachments. Any idea what’s happening?

mvzut · August 31, 2015, 7:20am

[quote=“reneboer”]I think the v5 meters will not be available until 2016 at best. See [url=http://www.energytracker.nl/nl/http-www-energeia-nl-news-php-id-54441]Home - Engerytracker

The other changes look nice as well, but not sure a Vera can keep up with all that :o

Cheers Rene[/quote]
Talking about “keeping up”… My Vera Edge was close to 100% cpu all the time. Don’t know when this started, I never checked until my spontaneous restarts/reboots got a little too frequent. I started to suspect the Smart Meter plug in (I’m using the previous version since a couple of months), since my log was flooded with all the data the plugin is processing. That’s when I found out about the new version, and installed it. The cpu use is now significantly less, and I haven’t had a single restart since then (although I keep my fingers crossed, it’s only one day ago).

Did you change anything that makes the plugin more cpu-friendly? What typical cpu load do other users have? Mine is still rather high, usually 30-50% (cpu use of the “luaupnp” process in the “top” overview when called from a terminal session). But maybe that’s because I also use several other polling-intensive plugins (Opentherm Gateway, rfxtrx, Netatmo, plus some more).

reneboer · August 31, 2015, 10:57am

Hi Mvzut,

No the logic has not changed, but maybe you had debug log level as it does write about all lines each 10 seconds. With just error level it does not write much to the log. You would then only see the variables getting updated.

I have Openterm on mine too and that is very chatty as well. So mine runs around 40-50% CPU as well.

Orangina, Can you make sure to refresh your browser and see if the data them populates correctly? Looking at the Meter Type it is a new one I have not seen before, so maybe it does some minor things differently. Only way to find out is the set log level to debug and see what gets reported in the log file.

Cheers Rene

mvzut · August 31, 2015, 11:57am

[quote=“reneboer”]I have Openterm on mine too and that is very chatty as well. So mine runs around 40-50% CPU as well.

Cheers Rene[/quote]

Thanks Rene! Anyway, my Vera seems more stable since the update, don’t know if it was because of your new code or because of some other (side) effect of the reconfiguration I did, but my Vera finally seems reliable again. Great plugin by the way!

One last question about cpu use (maybe off topic, sorry): does anybody know why “top” returns cpu values in the range of 30-50%, whereas plugins such as System Monitor or Event Watcher mention values like 1.2 or 120% (roughly at the same time)? There always seems to be some factor between them.

Martijn

orangina · August 31, 2015, 6:25pm

Hi Ren?,

Looks like this:

06 08/31/15 20:15:43.581 Device_Variable::m_szValue_set device: 139 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: KWH_frac was: 309.819 now: 309.82 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2e98e680>
06 08/31/15 20:15:43.582 Device_Variable::m_szValue_set device: 140 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: KWH_frac was: 309.819 now: 309.82 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2e98e680>
06 08/31/15 20:15:43.631 Device_Variable::m_szValue_set device: 140 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: Watts was: 389 now: 387 #hooks: 0 upnp: 0 skip: 0 v:0xb6d4b0/NONE duplicate:0 <0x2e98e680>
06 08/31/15 20:15:43.632 Device_Variable::m_szValue_set device: 140 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: Log was: 389,528,4368,1441044933,2734 now: 387,527,4368,1441044943,2744 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2e98e680>
06 08/31/15 20:15:43.831 Device_Variable::m_szValue_set device: 139 service: urn:rboer-com:serviceId:SmartMeter1 variable: L1ImpWatts was: 389 now: 387 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2e98e680>
01 08/31/15 20:15:44.187

Cheers,

Florens

orangina · August 31, 2015, 6:32pm

And forgot…

06 08/31/15 20:28:25.301 Device_Variable::m_szValue_set device: 140 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: Watts was: 296 now: 298 #hooks: 0 upnp: 0 skip: 0 v:0x97acf8/NONE duplicate:0 <0x2f2e0680>
06 08/31/15 20:28:25.302 Device_Variable::m_szValue_set device: 140 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: Log was: 296,463,4368,1441045695,3496 now: 298,462,4368,1441045705,3506 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2f2e0680>
50 08/31/15 20:28:25.303 luup_log:139: Smart Meter: Found key : 1-0:1.7.0 for Watts to set to value 298 <0x2f2e0680>

50 08/31/15 20:28:25.321 luup_log:139: Smart Meter: Found key : 1-0:2.7.0 for Watts to set to value 0 <0x2f2e0680>
50 08/31/15 20:28:25.322 luup_log:139: Smart Meter: Not processing : 0-0:96.7.21(00001) <0x2f2e0680>
50 08/31/15 20:28:25.331 luup_log:139: Smart Meter: Not processing : 0-0:96.7.9(00000) <0x2f2e0680>

50 08/31/15 20:28:25.591 luup_log:139: Smart Meter: Found key : 0-1:96.1.0 for GasMeterNumber to set to value 4730303332353631323331393630343135 <0x2f2e0680>
50 08/31/15 20:28:25.611 luup_log:139: Smart Meter: Found key : 0-1:24.2.1 for GasMeter to set to value 15.439 <0x2f2e0680>
50 08/31/15 20:28:25.740 luup_log:139: Smart Meter: Not processing : !A13C <0x2f2e0680>

(…)

50 08/31/15 20:28:35.211 luup_log:139: Smart Meter: Found key : / for MeterType to set to value XMX5LGBBFG1009024058 <0x2f2e0680>
50 08/31/15 20:28:35.231 luup_log:139: Smart Meter: Found key : 1-3:0.2.8 for DSMRVersion to set to value 42 <0x2f2e0680>
50 08/31/15 20:28:35.241 luup_log:139: Smart Meter: Not processing : 0-0:1.0.0(150831202828S) <0x2f2e0680>
50 08/31/15 20:28:35.261 luup_log:139: Smart Meter: Found key : 0-0:96.1.1 for MeterNumber to set to value 4530303331303033303131313036393135 <0x2f2e0680>
50 08/31/15 20:28:35.271 luup_log:139: Smart Meter: Found key : 1-0:1.8.1 for KWH to set to value 199.483 <0x2f2e0680>
06 08/31/15 20:28:35.281 Device_Variable::m_szValue_set device: 139 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: KWH_frac was: 309.901 now: 309.902 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2f2e0680>
06 08/31/15 20:28:35.282 Device_Variable::m_szValue_set device: 140 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: KWH_frac was: 309.901 now: 309.902 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2f2e0680>
50 08/31/15 20:28:35.283 luup_log:139: Smart Meter: Found key : 1-0:1.8.2 for KWH to set to value 110.419 <0x2f2e0680>
50 08/31/15 20:28:35.311 luup_log:139: Smart Meter: Found key : 1-0:2.8.1 for KWH to set to value 0 <0x2f2e0680>
50 08/31/15 20:28:35.312 luup_log:139: Smart Meter: Found key : 1-0:2.8.2 for KWH to set to value 0 <0x2f2e0680>
50 08/31/15 20:28:35.321 luup_log:139: Smart Meter: Found key : 0-0:96.14.0 for ActiveTariff to set to value 2 <0x2f2e0680>
06 08/31/15 20:28:35.331 Device_Variable::m_szValue_set device: 140 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: Watts was: 298 now: 297 #hooks: 0 upnp: 0 skip: 0 v:0x97acf8/NONE duplicate:0 <0x2f2e0680>
06 08/31/15 20:28:35.332 Device_Variable::m_szValue_set device: 140 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: Log was: 298,462,4368,1441045705,3506 now: 297,461,4368,1441045715,3516 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2f2e0680>
50 08/31/15 20:28:35.333 luup_log:139: Smart Meter: Found key : 1-0:1.7.0 for Watts to set to value 297 <0x2f2e0680>
50 08/31/15 20:28:35.341 luup_log:139: Smart Meter: Found key : 1-0:2.7.0 for Watts to set to value 0 <0x2f2e0680>
50 08/31/15 20:28:35.351 luup_log:139: Smart Meter: Not processing : 0-0:96.7.21(00001) <0x2f2e0680>
50 08/31/15 20:28:35.361 luup_log:139: Smart Meter: Not processing : 0-0:96.7.9(00000) <0x2f2e0680>

reneboer · September 1, 2015, 9:19am

Hi Florens,

The log actually looks as I would expect. After refreshing your browser is the information still missing?

Cheers Rene

orangina · September 1, 2015, 9:32am

Hi Rene,

Missing isn’t the case. But I expect Imp. Pwr. to display a cumulative figure, just like Import Gas. Or is that not the case?

Cheers,

Florens

reneboer · September 1, 2015, 2:09pm

[quote=“orangina, post:39, topic:187190”]Hi Rene,

Missing isn’t the case. But I expect Imp. Pwr. to display a cumulative figure, just like Import Gas. Or is that not the case?

Cheers,

Florens[/quote]
Hi Florens,

Those Line 1-3 values show the actual values from the Smart Meter directly and should match what either ImportT1 or ImportT2 are showing for power (Watts), depending on the active tariff. The others on that screen are total usage readings from your meter in KWH and M3.

Cheers Rene