Hi Flukso People,
Our Flukso is located on the first floor of a building, where the attached Dutch smart meter is located a floor below, on ground-level. Ground floor is rented. The owner, who lives on the first floor, sends a electricity bill to the renters. Now he has to inspect the meter from time to time to see its digits, but we hoped that Flukso would help us with that, so he could get the values of the meter 'realtime' from his Flukso.
Is it possible to extract the raw P1 telegrams from the Flukso by its Api or any other way? Would be great, because that's why we bought our Flukso.
Kind regards;
Gerard
If the P1 is attached to the FLM then it is "just another sensor", thus readings are posted realtime via MQTT as "gauge" and "counter" values. I don't exactly get what you mean by "raw" data; would passing on "raw" data mean someting like "pipe it to the WLAN"? How would you decode it afterwards?
Regards, Markus
See https://www.flukso.net/content/mqtt-mq-telemetry-transport and https://www.flukso.net/content/mqtt-nicely-designed-gauges for MQTT related discussions.
Thank you Markus,
What i meant with "Raw data" is the data the P1 port sends to the FLM, according to the "P1 Companion Standard". There are two values i'm interested in: 1-0:1.8.1.255 (Meter Reading electricity delivered to client (low tariff)) and 1-0:1.8.2.255 (Meter Reading electricity delivered to client (normal tariff)).
If i can get these values out of the FLM, for example with a program (maybe C#) running on a windows computer connecting to the FLM, than that would be fine. The program can create the electricity bill with these values. These values should be readable in plain text, so no need to decode.
As i understand, MQTT should be the way to get this data? Is there a commandline example how to read these values?
Command line example --> https://www.flukso.net/content/mqtt-mq-telemetry-transport --> post from Thu, 26/09/2013 - 17:15
I succeeded in getting data out of the FLM using MQTT, but i'm not sure how to translate this to P1 telegram data. This is what i see:
/sensor/xxxxxxx/gauge [1393876676,0,"L/day"]
/sensor/yyyyyyy/counter [1393876676,6606073,"Wh"]
/sensor/yyyyyyy/gauge [1393876676,1080,"W"]
Where xxx and yyy are my sensor-id's.
However, P1 telegram data should look something like this:
/ISk5\2MT382-1000
1-3:0.2.8(40)
0-0:1.0.0(101209113020W)
0-0:96.1.1(4B384547303034303436333935353037)
1-0:1.8.1(123456.789*kWh)
1-0:1.8.2(123456.789*kWh)
1-0:2.8.1(123456.789*kWh)
1-0:2.8.2(123456.789*kWh)
...
where "1-0:1.8.1" stands for the meter digits "electricity delivered to client (low tariff)" and "1-0:1.8.2" stands for the meter digits "electricity delivered to client (normal tariff)".
The above data is sent from the P1 port of the smart-meter to the FLM, but is seems that the FLM is not displaying any of this data on its MQTT broker. Or maybe i'm in the wrong direction?
Kind regards,
Gerard
Any other solutions?
No; actually I don't really see the use case to pipe telegrams; but maybe help yourself - the relevant code is around \flm02\openwrt\package\flukso\luasrc\fp1.lua
Sorry, I am also "just" a user with some affinity to the topic...