HomeBridge does not fully start after configuring this plugin

[RienduPre]

Hi,

After configuring the plugin by adding: { "platform": "P1" }, to the config.json the HomeBridge does not fully start anymore

I see this in the log, so I thought this is okay, but the Homebridge process is not loading

Aug 31 16:58:45 homebridge homebridge[20966]: [2018-8-31 16:58:45] [P1] Initializing P1 platform... Aug 31 16:58:45 homebridge homebridge[20966]: [2018-8-31 16:58:45] [P1] homebridge-p1 v0.1.8, node v8.11.4, homebridge v0.4.44

If I remove the { "platform": "P1" }, from the config.json and leave the plugin installed, everything is working again.

So there must be something with the P1 plugin :-(

Any help is appreciated

Thanks, Rien

[ebaauw]

What other messages are shown in the log? Could you please attach a full debug logfile, see https://github.com/ebaauw/homebridge-hue#debug-log-file.

I suspect the plugin finds the wrong USB serial port and is waiting indefinitely for the first message from the smart meter.

[RienduPre]

Lots of logging, but no errors

Aug 31 17:31:10 homebridge homebridge[24030]: [2018-8-31 17:31:10] --- Aug 31 17:31:12 homebridge homebridge[24030]: [2018-8-31 17:31:12] Loaded plugin: homebridge-alexa Aug 31 17:31:12 homebridge homebridge[24030]: [2018-8-31 17:31:12] Registering platform 'homebridge-alexa.Alexa' Aug 31 17:31:12 homebridge homebridge[24030]: [2018-8-31 17:31:12] --- Aug 31 17:31:12 homebridge homebridge[24030]: [2018-8-31 17:31:12] Loaded plugin: homebridge-config-ui-rdp Aug 31 17:31:12 homebridge homebridge[24030]: [2018-8-31 17:31:12] Registering platform 'homebridge-config-ui-rdp.config' Aug 31 17:31:12 homebridge homebridge[24030]: [2018-8-31 17:31:12] --- Aug 31 17:31:13 homebridge homebridge[24030]: [2018-8-31 17:31:13] Loaded plugin: homebridge-doorbird Aug 31 17:31:13 homebridge homebridge[24030]: [2018-8-31 17:31:13] Registering platform 'homebridge-doorbird.DoorBird' Aug 31 17:31:13 homebridge homebridge[24030]: [2018-8-31 17:31:13] --- Aug 31 17:31:14 homebridge homebridge[24030]: [2018-8-31 17:31:14] Loaded plugin: homebridge-edomoticz Aug 31 17:31:14 homebridge homebridge[24030]: [2018-8-31 17:31:14] Registering platform 'homebridge-edomoticz.eDomoticz' Aug 31 17:31:14 homebridge homebridge[24030]: [2018-8-31 17:31:14] --- Aug 31 17:31:14 homebridge homebridge[24030]: [2018-8-31 17:31:14] Loaded plugin: homebridge-fritz-platform Aug 31 17:31:15 homebridge homebridge[24030]: [2018-8-31 17:31:15] Registering platform 'homebridge-fritz-platform.FritzPlatform' Aug 31 17:31:15 homebridge homebridge[24030]: [2018-8-31 17:31:15] --- Aug 31 17:31:16 homebridge homebridge[24030]: [2018-8-31 17:31:16] Loaded plugin: homebridge-milight Aug 31 17:31:16 homebridge homebridge[24030]: [2018-8-31 17:31:16] Registering platform 'homebridge-milight.MiLight' Aug 31 17:31:16 homebridge homebridge[24030]: [2018-8-31 17:31:16] --- Aug 31 17:31:17 homebridge homebridge[24030]: [2018-8-31 17:31:17] Loaded plugin: homebridge-p1 Aug 31 17:31:17 homebridge homebridge[24030]: [2018-8-31 17:31:17] Registering platform 'homebridge-p1.P1' Aug 31 17:31:17 homebridge homebridge[24030]: [2018-8-31 17:31:17] --- Aug 31 17:31:17 homebridge homebridge[24030]: [2018-8-31 17:31:17] Loaded plugin: homebridge-thinkingcleaner Aug 31 17:31:17 homebridge homebridge[24030]: [2018-8-31 17:31:17] Registering accessory 'homebridge-thinkingcleaner.Roomba' Aug 31 17:31:17 homebridge homebridge[24030]: [2018-8-31 17:31:17] --- Aug 31 17:31:17 homebridge homebridge[24030]: [2018-8-31 17:31:17] Loading 7 platforms... Aug 31 17:31:17 homebridge homebridge[24030]: [2018-8-31 17:31:17] [Config] Initializing config platform... Aug 31 17:31:17 homebridge homebridge[24030]: [2018-8-31 17:31:17] [Config] Spawning homebridge-config-ui-rdp with PID 24051 Aug 31 17:31:17 homebridge homebridge[24030]: [2018-8-31 17:31:17] [P1] Initializing P1 platform... Aug 31 17:31:17 homebridge homebridge[24030]: [2018-8-31 17:31:17] [P1] homebridge-p1 v0.1.8, node v8.11.4, homebridge v0.4.44 Aug 31 17:31:17 homebridge homebridge[24030]: [2018-8-31 17:31:17] [MiLight] Initializing MiLight platform... Aug 31 17:31:17 homebridge homebridge[24030]: [2018-8-31 17:31:17] [MiLight] More than 4 fullColor bulbs added to a v6 bridge, enabling 8-zone support. May not work withall bridges/bulbs. Set the use8Zone property of the bridge config to either silence this message or disable this functionality. Aug 31 17:31:17 homebridge homebridge[24030]: [2018-8-31 17:31:17] [MiLight] Initializing platform accessory 'Vitrine Kast'... Aug 31 17:31:17 homebridge homebridge[24030]: [2018-8-31 17:31:17] [MiLight] Initializing platform accessory 'Serre Spots'... Aug 31 17:31:17 homebridge homebridge[24030]: [2018-8-31 17:31:17] [MiLight] Initializing platform accessory 'Serre LED'... Aug 31 17:31:17 homebridge homebridge[24030]: [2018-8-31 17:31:17] [MiLight] Initializing platform accessory 'Veranda Bar'... Aug 31 17:31:17 homebridge homebridge[24030]: [2018-8-31 17:31:17] [DoorBird] Initializing DoorBird platform... Aug 31 17:31:17 homebridge homebridge[24030]: [2018-8-31 17:31:17] [eDomoticz] Initializing eDomoticz platform... Aug 31 17:31:17 homebridge homebridge[24030]: [2018-8-31 17:31:17] [FritzBox] Initializing FritzPlatform platform... Aug 31 17:31:17 homebridge homebridge[24030]: [2018-8-31 17:31:17] [FritzBox] [INFO] ** Aug 31 17:31:17 homebridge homebridge[24030]: [2018-8-31 17:31:17] [FritzBox] [INFO] FritzPlatform v2.7.1 by SeydX Aug 31 17:31:17 homebridge homebridge[24030]: [2018-8-31 17:31:17] [FritzBox] [INFO] GitHub: https://github.com/SeydX/homebridge-fritz-platform Aug 31 17:31:17 homebridge homebridge[24030]: [2018-8-31 17:31:17] [FritzBox] [INFO] Email: seyd55@outlook.de Aug 31 17:31:17 homebridge homebridge[24030]: [2018-8-31 17:31:17] [FritzBox] [INFO] ** Aug 31 17:31:17 homebridge homebridge[24030]: [2018-8-31 17:31:17] [FritzBox] [INFO] start success... Aug 31 17:31:17 homebridge homebridge[24030]: [2018-8-31 17:31:17] [Alexa] Initializing Alexa platform... Aug 31 17:31:17 homebridge homebridge[24030]: [2018-8-31 17:31:17] Loading 1 accessories... Aug 31 17:31:17 homebridge homebridge[24030]: [2018-8-31 17:31:17] [Stofzuiger] Initializing Roomba accessory... Aug 31 17:31:18 homebridge homebridge[24030]: [2018-8-31 17:31:18] DoorBird is running on port 44811. Aug 31 17:31:18 homebridge homebridge[24030]: DoorBird is listening on port 5005 Aug 31 17:31:18 homebridge homebridge[24030]: [2018-8-31 17:31:18] [Stofzuiger] 1.0.106-310C-EU Aug 31 17:31:18 homebridge homebridge[24030]: [2018-8-31 17:31:18] [eDomoticz] Buiten Temperatuur Aug 31 17:31:18 homebridge homebridge[24030]: [2018-8-31 17:31:18] [eDomoticz] Regen meter Aug 31 17:31:18 homebridge homebridge[24030]: [2018-8-31 17:31:18] [eDomoticz] Room Setpoint Aug 31 17:31:18 homebridge homebridge[24030]: [2018-8-31 17:31:18] [eDomoticz] Room Temperature Aug 31 17:31:18 homebridge homebridge[24030]: [2018-8-31 17:31:18] [eDomoticz] Solar Aug 31 17:31:18 homebridge homebridge[24030]: [2018-8-31 17:31:18] [eDomoticz] UV Sensor Aug 31 17:31:18 homebridge homebridge[24030]: [2018-8-31 17:31:18] [eDomoticz] Wind meter Aug 31 17:31:18 homebridge homebridge[24030]: [2018-8-31 17:31:18] [eDomoticz] Successfully connected to MQTT broker. Aug 31 17:31:20 homebridge homebridge[24030]: [2018-8-31 17:31:20] [FritzBox] [INIT] Device initialized: FritzBox Aug 31 17:31:21 homebridge homebridge[24030]: [2018-8-31 17:31:21] [FritzBox] [INIT] Encrypted communication started with: FritzBox Aug 31 17:31:21 homebridge homebridge[24030]: [2018-8-31 17:31:21] [FritzBox] [INIT] Callmonitor connection established with: FritzBox Aug 31 17:31:21 homebridge homebridge[24030]: [2018-8-31 17:31:21] [FritzBox] [INIT] Configuring accessory from cache: FritzBox Aug 31 17:31:21 homebridge homebridge[24030]: [2018-8-31 17:31:21] [FritzBox] [INIT] Configuring accessory from cache: Callmonitor Incoming Aug 31 17:31:21 homebridge homebridge[24030]: [2018-8-31 17:31:21] [FritzBox] [INIT] Configuring accessory from cache: Callmonitor Outgoing Aug 31 17:31:21 homebridge homebridge[24030]: #033[0;37m[2018-8-31 17:31:21]#033[0m #033[0;36m[Config]#033[0m Using Form Authentication Aug 31 17:31:22 homebridge homebridge[24030]: #033[0;37m[2018-8-31 17:31:22]#033[0m #033[0;36m[Config]#033[0m Console v4.0.3 is listening on port 8080. Aug 31 17:31:22 homebridge homebridge[24030]: [2018-8-31 17:31:22] [FritzBox] [INIT] Platform initialization finished

[ebaauw]

I suspect the plugin finds the wrong USB serial port and is waiting indefinitely for the first message from the smart meter. Could you post the output of serialport-list -f json?

[RienduPre]

[{"comName":"/dev/ttyAMA0"},{"manufacturer":"FTDI","serialNumber":"P12B5OMM","pnpId":"usb-FTDI_P1_Converter_Cable_P12B5OMM-if00-port0","vendorId":"0403","productId":"6001","comName":"/dev/ttyUSB1"},{"manufacturer":"1a86","pnpId":"usb-1a86_USB2.0-Serial-if00-port0","vendorId":"1a86","productId":"7523","comName":"/dev/ttyUSB0"}]

[ebaauw]

It should connect to /dev/ttyUSB1. Could you check that, when you run homebridge -D, you see a message like:

[2018-8-31 17:41:10] [P1] listening on /dev/ttyUSB1

If not, try specifying "serialport": "/dev/ttyUSB1" in config.json.

If you do see the message, are you sure the cable is plugged into your smart meter? What meter do you have? What DSMR version does it support?

[RienduPre]

Tried that allready...

How do I check the DSMR version ?

[ebaauw]

I think it's on the yellow label: DSMR 2.2+. It seems to be the same meter as mine (or rather: the one they installed at my home), but with a different communication module. Mine says SMR 5.0 next to the green button.

I found the DSMR 2.2 spec. Looks like it uses a different baudrate (9600 instead of 115200) than 5.0 and no checksums. Also the payload is different, no timestamps, no support for 3-phase electricity, and some keys are different. And less frequent data delivery.

[ebaauw]

@RienduPre, I created a new beta version to try and capture the DSMR 2.2 telegrams. Could you please install v0.1.9-2 through npm -g i homebridge-p1@beta --unsafe-perm, and run homebridge -D, capturing the log file (see https://github.com/ebaauw/homebridge-hue#debug-log-file)? It should report an error, that no valid data has been received and allow homebridge to start.

Then, could you please add "dsmr22": true to config.json and capture another debug log file. I doubt the beta will expose your meter correctly, but it should at least dump the meter's telegram in the log file.

[RienduPre]

Hi Erik,

The update seems not to update to a new version

sudo npm i homebridge-p1@beta --unsafe-perm npm WARN saveError ENOENT: no such file or directory, open '/home/pi/package.json' npm WARN enoent ENOENT: no such file or directory, open '/home/pi/package.json' npm WARN pi No description npm WARN pi No repository field. npm WARN pi No README data npm WARN pi No license field.

• homebridge-p1@0.1.9-2 updated 1 package and audited 5120 packages in 13.721s found 0 vulnerabilities

Aug 31 23:05:56 homebridge homebridge[402]: [2018-8-31 23:05:56] [P1] Initializing P1 platform... Aug 31 23:05:56 homebridge homebridge[402]: [2018-8-31 23:05:56] [P1] config.json: warning: dsmr22: ignoring unknown key Aug 31 23:05:56 homebridge homebridge[402]: [2018-8-31 23:05:56] [P1] homebridge-p1 v0.1.8, node v8.11.4, homebridge v0.4.44

[RienduPre]

Deleted the 1.8 version completely and reinstalled beta version. Now it installed the 1.9.2 version

Got this error Aug 31 23:17:21 homebridge homebridge[2092]: [2018-8-31 23:17:21] [P1] /dev/ttyUSB1: no valid data received

Tested with and without the "dsmr22": true option, same results.

But the good thing is, HomeKit daemon is started now, but no P1 devices yet.

I will do the debug logging tomorrow.

[RienduPre]

Here is the debug logging

Sep 1 10:30:55 homebridge homebridge[5235]: [2018-9-1 10:30:55] [P1] warning: lastest version: homebridge-p1 v0.1.8 Sep 1 10:30:57 homebridge homebridge[5235]: [2018-9-1 10:30:57] [P1] ports: [{"comName":"/dev/ttyAMA0"},{"manufacturer":"FTDI","serialNumber":"P12B5OMM","pnpId":"usb-FTDI_P1_Converter_Cable_P12B5OMM-if00-port0","vendorId":"0403","productId":"6001","comName":"/dev/ttyUSB1"},{"manufacturer":"1a86","pnpId":"usb-1a86_USB2.0-Serial-if00-port0","vendorId":"1a86","productId":"7523","comName":"/dev/ttyUSB0"}] Sep 1 10:31:03 homebridge homebridge[5235]: [2018-9-1 10:31:03] [P1] /dev/ttyUSB1: no valid data received Sep 1 10:31:03 homebridge homebridge[5235]: Setup Payload:

[ebaauw]

No message listening on /dev/ttyUSB1 ?

[RienduPre]

Yes sorry I filtered out too much

Sep 1 11:51:23 homebridge homebridge[7508]: [2018-9-1 11:51:23] [P1] warning: lastest version: homebridge-p1 v0.1.8 Sep 1 11:51:24 homebridge homebridge[7508]: [2018-9-1 11:51:24] [P1] ports: [{"comName":"/dev/ttyAMA0"},{"manufacturer":"FTDI","serialNumber":"P12B5OMM","pnpId":"usb-FTDI_P1_Converter_Cable_P12B5OMM-if00-port0","vendorId":"0403","productId":"6001","comName":"/dev/ttyUSB1"},{"manufacturer":"1a86","pnpId":"usb-1a86_USB2.0-Serial-if00-port0","vendorId":"1a86","productId":"7523","comName":"/dev/ttyUSB0"}] Sep 1 11:51:25 homebridge homebridge[7508]: [2018-9-1 11:51:25] [P1] listening on /dev/ttyUSB1 Sep 1 11:51:30 homebridge homebridge[7508]: [2018-9-1 11:51:30] [P1] /dev/ttyUSB1: no valid data received

[ebaauw]

I set a timeout for 5 seconds, but the DSMR 2.2 sends a telegram only once every 10 seconds.

Could you try beta v0.1.9-3? Same install. This version will create excessive debug logging. Please attach the zipped logfile. If there's still no data, could you set "timeout": 120 in config.json?

[ebaauw]

Could you please attach the zipped logfile, see https://github.com/ebaauw/homebridge-hue#debug-log-file.

[RienduPre]

debug.zip

[ebaauw]

Thanks. It looks like DSMR 2.2 needs some other serial settings, see http://domoticx.com/p1-poort-slimme-meter-hardware/. Could you try v0.1.9-4? Sorry, it's a bit of trial and error - I cannot test this at home.

[RienduPre]

Logging seems the same,

Do I need to do something with the serial settings?

[ebaauw]

No, if you set "dsmr22": true in config.json, v0.1.9-4 should open the port using 9600 7E1. Does it still only report 00 bytes in the buffer, or are there other values?

[RienduPre]

Hi see debug1

I see a lot of data now.

No P1 devices however. debug1.zip

[ebaauw]

That's progress, I suppose. Could you try v0.1.9-5? It no longer logs the buffers, but hopefully logs the lines it receives.

[RienduPre]

debug2.zip See debug2

Some warnings and I have 2 p1 devices now :-)

[RienduPre]

[ebaauw]

This is more than I'd hoped for.

Sep  1 16:29:44 homebridge homebridge[3681]: [2018-9-1 16:29:44] [P1] line: /XMX5XMXABCE000063181
Sep  1 16:29:45 homebridge homebridge[3681]: [2018-9-1 16:29:45] [P1] line: 0-0:96.1.1(31333634303033302020202020202020)
Sep  1 16:29:45 homebridge homebridge[3681]: [2018-9-1 16:29:45] [P1] line: 1-0:1.8.1(32559.673*kWh)
Sep  1 16:29:45 homebridge homebridge[3681]: [2018-9-1 16:29:45] [P1] line: 1-0:1.8.2(36388.384*kWh)
Sep  1 16:29:45 homebridge homebridge[3681]: [2018-9-1 16:29:45] [P1] line: 1-0:2.8.1(00000.111*kWh)
Sep  1 16:29:45 homebridge homebridge[3681]: [2018-9-1 16:29:45] [P1] line: 1-0:2.8.2(00000.286*kWh)
Sep  1 16:29:45 homebridge homebridge[3681]: [2018-9-1 16:29:45] [P1] line: 0-0:96.14.0(0001)
Sep  1 16:29:45 homebridge homebridge[3681]: [2018-9-1 16:29:45] [P1] line: 1-0:1.7.0(0002.32*kW)
Sep  1 16:29:45 homebridge homebridge[3681]: [2018-9-1 16:29:45] [P1] line: 1-0:2.7.0(0000.00*kW)
Sep  1 16:29:45 homebridge homebridge[3681]: [2018-9-1 16:29:45] [P1] line: 0-0:96.13.1()
Sep  1 16:29:45 homebridge homebridge[3681]: [2018-9-1 16:29:45] [P1] line: 0-0:96.13.0()
Sep  1 16:29:45 homebridge homebridge[3681]: [2018-9-1 16:29:45] [P1] line: 0-1:96.1.0(3238303131303038333133313637353133)
Sep  1 16:29:45 homebridge homebridge[3681]: [2018-9-1 16:29:45] [P1] line: 0-1:24.1.0(03)
Sep  1 16:29:45 homebridge homebridge[3681]: [2018-9-1 16:29:45] [P1] line: 0-1:24.3.0(180901160000)(08)(60)(1)(0-1:24.2.0)(m3)
Sep  1 16:29:45 homebridge homebridge[3681]: [2018-9-1 16:29:45] [P1] line: (12006.444)
Sep  1 16:29:45 homebridge homebridge[3681]: [2018-9-1 16:29:45] [P1] line: !

This is what I wanted to see! The last two data lines (before the !) look a bit odd to me - need to double check the DSMR 2.2 spec to see what they mean.

Sep  1 16:29:54 homebridge homebridge[3681]: [2018-9-1 16:29:54] [P1] telegram:
Sep  1 16:29:54 homebridge homebridge[3681]: /XMX5XMXABCE000063181
Sep  1 16:29:54 homebridge homebridge[3681]: #015
Sep  1 16:29:54 homebridge homebridge[3681]: 0-0:96.1.1(31333634303033302020202020202020)
Sep  1 16:29:54 homebridge homebridge[3681]: 1-0:1.8.1(32559.673*kWh)
Sep  1 16:29:54 homebridge homebridge[3681]: 1-0:1.8.2(36388.384*kWh)
Sep  1 16:29:54 homebridge homebridge[3681]: 1-0:2.8.1(00000.111*kWh)
Sep  1 16:29:54 homebridge homebridge[3681]: 1-0:2.8.2(00000.286*kWh)
Sep  1 16:29:54 homebridge homebridge[3681]: 0-0:96.14.0(0001)
Sep  1 16:29:54 homebridge homebridge[3681]: 1-0:1.7.0(0002.32*kW)
Sep  1 16:29:54 homebridge homebridge[3681]: 1-0:2.7.0(0000.00*kW)
Sep  1 16:29:54 homebridge homebridge[3681]: 0-0:96.13.1()
Sep  1 16:29:54 homebridge homebridge[3681]: 0-0:96.13.0()
Sep  1 16:29:54 homebridge homebridge[3681]: 0-1:96.1.0(3238303131303038333133313637353133)
Sep  1 16:29:54 homebridge homebridge[3681]: 0-1:24.1.0(03)
Sep  1 16:29:54 homebridge homebridge[3681]: 0-1:24.3.0(180901160000)(08)(60)(1)(0-1:24.2.0)(m3)
Sep  1 16:29:54 homebridge homebridge[3681]: (12006.444)
Sep  1 16:29:54 homebridge homebridge[3681]: !

Again, this is what I wanted to see! I didn't think I changed anything to recognise the telegrams, but now they are?! I hope it's not a timing issue. Could you restart homebridge a couple of times and check that the telegrams are recognised each time?
Note the time lag between the ! line and the telegram. The telegram is only recognised at the receipt of the start of the next telegram (the / character). The default timeout for DSMR 2.2 should be long enough for two telegrams to be received (so 30 seconds is probably cutting it too tight).
Not sure what the #015 means. Maybe it's because of the *.rtf file? Are you on Windows? Could it be: octal 015 == decimal 13 == control-M == "\r".

Sep  1 16:29:55 homebridge homebridge[3681]: [2018-9-1 16:29:54] [P1] warning: unknown key: 0-0:96.13.1()

This should be easy enough to add.

Sep  1 16:29:55 homebridge homebridge[3681]: [2018-9-1 16:29:54] [P1] warning: unknown key: 0-1:24.3.0(180901160000)(08)(60)(1)(0-1:24.2.0)(m3)

Not sure about this one, see above. Looks like the next line is a continuation of the value. Does you gas meter indicate 12006.444 m3?

Looking at the parsed data:

Sep  1 16:29:44 homebridge homebridge[3681]: [2018-9-1 16:29:44] [P1] raw data: {
  "type": "XMX5XMXABCE000063181",
  "checksum": "",
  "id": "13640030        ",
  "consumption_low": 32559.673,
  "consumption_normal": 36388.384,
  "consumption_back_low": 0.111,
  "consumption_back_normal": 0.286,
  "tariff": "low",
  "power": 2320,
  "power_back": 0,
  "text": null,
  "d1_id": "28011008313167513",
  "d1_type": "gas"
}

id should be the serial number of the electricity meter; d1_id the serial number of your gas meter. Do the consumption fields match your electricity meter? I wonder why it reports the small numbers delivered back to the network. Did you just install solar panels?

Sep  1 16:29:44 homebridge homebridge[3681]: [2018-9-1 16:29:44] [P1] Electricity: set homekit total consumption from [object Object] undefined to [object Object] undefined

That's not good, but it does explains the 0,00kWh in the screenshot. The plugin incorrectly assumes id starts with E for the electricity meter and with G for the gas meter, as is the case with DSMR 5.0.

Sep  1 16:29:44 homebridge homebridge[3681]: [2018-9-1 16:29:44] [P1] Electricity: set homekit current consumption from 680 W to 2320 W

That's good.

[ebaauw]

Could you try v0.1.9-6? It should work, but still some excessive debug logging.

Don't you have a way to capture the output straight to file? I really need to see all the debug messages, also those before the Homebridge is running on port 51826 message.

[RienduPre]

Here's debug3 and a screenshot debug3.zip

[ebaauw]

Thanks. Could you check that the value for Last Updated for Electricity is updated?

The gas timestamp and consumption still aren't recognised (this is the last two lines from the telegram, which shouldn't have been split). I probably need to re-write the parser to cope with that...

[RienduPre]

Hi Erik,

What do you mean exactly with Last Updated for Electricity, I don't see that value or description in log or EVE app The 2 values for electricity are updated frequently

[ebaauw]

If you click on Electricity in Eve, you get a window with the service details, like consumption history, but also Last Updated.

[RienduPre]

Ah okay, yes that's being updated frequently

[ebaauw]

OK, just published v0.1.9, which should fully support DSMR 2.2+.

[RienduPre]

Thank you very much for your support, Erik.

Much appreciated.