yourselffasad.blogg.se - Homeseer update failed

Then I take the first 10 characters, which turned out to be unique enough (at least for DSMR version 5) from each line and use a switch…case statement to figure out what it is. I ignore every line that does not start with 0 or 1 to make sure it’s an OBIS code.Ģ. On the other hand it doesn’t seem to make sense to invest a lot of time in developing for HS3 with HS4 coming up.ġ. My intention is to turn it into a plugin, but being new to C# I’m still trying to make sense of all the plugin examples. In the mean while I have written a small C# application to read my smart meter. My Landis+Gyr meter only has 1 entry in the failure log, which is 000101010000W (2000 January 1st 01:00:00) and seems to be some sort of test/default value, considering how exact it is and DSMR being non-existent back then.

Although I agree a Linux timestamp would make more sense than what they’ve implemented here (I hate it when timestamps are still not Y2K proof).Īs I understand these DSMR timestamps are in the following format: YYMMDDhhmmssX, where X is an indicator of Daylight Saving Time (DST) – It’s either S for summer/DST or W for Winter/no DST. With the first script run, the virtual devices will be created automatically and can be shown like this: When this is done, Homeseer needs a restart as well. My.(save_telegram, data & ControlChars.CrLf, False, )īe aware of the comment to add the mentioned “ScriptingReferences”: it’s can be used to see what data is in the actual telegram. This feature is not mandatory for running the script. It’s possible to save the telegram to a local file in the Homeseer HTML folder. With the start of Homeseer, the com port will be opened and with every telegram update from the smart meter, the script will be run in Homeseer.Īt lines 19-21 an extra comment is visible. In the first place, nothing has to be changed in the script. Read the below text first, before restarting Homeseer. To have the settings fired up, a restart of Homeseer is necessary. In this case, the com port will be closed when Homeseer will be stopped. If you want to do it right, you should add a statement in “Shutdown.vb” script as well, corresponding to the earlier used com port:

“Main” is the name of the Sub statement in the “P1smartmeter.vb” script.

“P1smartmeter.vb” is the name of the script that can be downloaded at the bottom of the page.

Where “3” is the number of the com port.

To be sure the comport is not already open, the comport will be closed first.

The following line, has to be added at the bottom of the script, but before the “End Sub” statement:ĭim e=hs.OpenComPortTerm(3,”115200,N,8,1″,1,”P1smartmeter.vb”, “Main”, “!”) The file will run at every start of Homeseer. To arrange this an “open comport statement” has to be added to the “Startup.vb” file from Homeseer. Check your device manager for the corresponding port number:įor a stable connection to the P1 USB cable, I’ll keep the com port open all time. Because I don’t have solar panels, the smart meter don’t receive power.īecause of the frequent telegram update, a stable connection is necessary. Some objects are not provided by the meter, so the values will be zero, like “ 1-0:2.7.0(00.000*kW)”.

1-0:1.7.0 = “Actual electricity power delivered (+P) in 1 Watt resolution,”.

I’ll explain an example from the telegram here: All objects are based on the “P1 Companion Standard”, which is documented in the P1_Companion_Standard.

My smart meter send every ~3 seconds a telegram update. In this case, I’m able to use a P1-to-USB cable, and the exact type in my case is “ NTA8130-P1 – P1 Converter Cable v2“, which can be bought in The Netherlands for around 20 euro.

The Plugwise Smile P1 can’t be used anymore with this newer type of smart meter, but the benefit here it that my home automation server is installed next to the smart meter. This smart meter has also the famous P1 port. More information about this meter can be seen here. I did this before in my previous house and I want to have the old meters replaced here as well. A few months ago I asked (again) for a priority installation for a new smartmeter.