syberalexis / linky-exporter Goto Github PK

Maybe the daemon could not try to read the serial device each time we request http://localhost:9101/metrics ?
As it is a slow device, should be better the daemon decide when he read the device and give a cached result ?

I got:

With the following Promotheus config:
scrape_interval: 30s
scrape_timeout is default so 10s ?

Hello

First, thanks to you for this project!

I added a support to the standard mode of the TIC, you could be interested : https://github.com/hugocollignon/linky-exporter.
I didn't create a pull request because code is not perfectly finalised (have to see how to integrate both modes).

Hey,
Thanks for your work, did you have or plan to have a Grafana dashboard ?

Thanks

Thanks a lot for this perfect exporter!

Would you mind adding a parameter to allow op to choose serial parity? I first tried the linky-exporter as-is and didn't get anything usable. Switching to serial.parityEven solved the issue.

Fyi, I'm using such kind of device : https://www.planete-domotique.com/compteur-teleinformation-usb-rail-din.html which require an even parity. I'm not enough qualified in Golang to submit a PR :/

Hello,
Would you mind setting up an automatic build workflow on docker hub so that a docker image is automatically built as you update your code?
Let me know if some help is needed.

Hello,
To begin, thanks a lot for your exporter, it's very usefull for myself !

When using --standard flag, I get this output :

level=error msg="Failed to read standard serial : Serial port busy"
level=error msg="Unable to read telemetry information : Serial port busy"

When using --historical flag, there is no problem.

Is there a problem with my configuration or my Linky isn't able to send "all standard" telemetries and the error message is wrong ?

Hi,
On compiled linky_exporter v2.0.1 on OpenBSD
/usr/local/bin/linky_exporter -d /dev/cuaU0 -p 9101

I got messages like open /dev/cuaU0: device busy

cu or minicom on this device is working

Hello,

I successfully ran linky-exporter release 2.0.0 for a few years. I wanted to try your release 3, but it seems it does not work for me.

Here's the command that I launch in 2.0.0

/usr/local/bin/linky-exporter --device=/dev/ttyUSB0 --baud=1200 --size=7 --parity=O --stopbits=Stop1

In 3.0.0

It seems the stop bit can't be set to 1.

root@rasp-6:/home/tom# /usr/local/bin/linky-exporter --device=/dev/ttyUSB0 --baud=1200 --size=7 --parity=O --stopbits=Stop1 --debug --historical
INFO[0000] Debug mode enabled !
DEBU[0000] Parse parity O
DEBU[0000] Parse Stop Bits Stop1
INFO[0000] Beginning to serve on port :9901
DEBU[0001] Read serial with config device:/dev/ttyUSB0 baudrate:1200 framesize:7 parity:1 stopbits:0
DEBU[0001] Read serial data...
DEBU[0007] Read serial with config device:/dev/ttyUSB0 baudrate:1200 framesize:7 parity:1 stopbits:0
DEBU[0007] Read serial data...

^C
root@rasp-6:/home/tom# /usr/local/bin/linky-exporter --device=/dev/ttyUSB0 --baud=1200 --size=7 --parity=O --stopbits="Stop1" --debug --historical
INFO[0000] Debug mode enabled !
DEBU[0000] Parse parity O
DEBU[0000] Parse Stop Bits Stop1
INFO[0000] Beginning to serve on port :9901
DEBU[0005] Read serial with config device:/dev/ttyUSB0 baudrate:1200 framesize:7 parity:1 stopbits:0
DEBU[0005] Read serial data...
^C
root@rasp-6:/home/tom# /usr/local/bin/linky-exporter --device=/dev/ttyUSB0 --baud=1200 --size=7 --parity=O --stopbits="1" --debug --historical
INFO[0000] Debug mode enabled !
DEBU[0000] Parse parity O
DEBU[0000] Parse Stop Bits 1
INFO[0000] Beginning to serve on port :9901
DEBU[0005] Read serial with config device:/dev/ttyUSB0 baudrate:1200 framesize:7 parity:1 stopbits:0
DEBU[0005] Read serial data...
DEBU[0008] Read serial with config device:/dev/ttyUSB0 baudrate:1200 framesize:7 parity:1 stopbits:0
DEBU[0008] Read serial data...
DEBU[0010] Read serial with config device:/dev/ttyUSB0 baudrate:1200 framesize:7 parity:1 stopbits:0
DEBU[0010] Read serial data...

Could you advise ?

Thanx

Thomas