Closed tomav closed 1 year ago
I am running on an esp8266, you can have a look at my config here: https://community.ch2i.eu/topic/1369/wemos-teleinfo-et-esp-home. it will require small adjustment for esp32, but from what I've read in the past, issues can occur with the uart bus, or the GPIO you chose.
You can check hardware with some examples of LibTeleinfo such as passthru or stats.
@tomav did you ever solve this? I have a very similar setup to you (Board off Tindie, ESP32 S2 mini), but my Linky is Historical mode. I'm getting the same errors:
[E][teleinfo:038]: bad crc: got 72 except 32
[E][teleinfo:038]: bad crc: got 44 except 60
No data seems to get received by HomeAssistant
Hi @harrygr, sadly nope, so I moved quickly to https://github.com/fairecasoimeme/Zlinky_TIC Works great with MQTT, and nice form factor, no need of an external 5v.
@tomav thanks for the response. I did get it working in the end, albeit with still a few bad crc
errors. However the metrics I'm interested in are getting recorded and injested by HomeAssistant.
Turns out I had to carefully read the Teleinfo datasheet to figure out which tag names work for my Linky setup. I ended up with the following (for single-phase, single rate, historical):
sensor:
- platform: teleinfo
tag_name: "BASE"
name: "Usage"
device_class: energy
unit_of_measurement: "kWh"
state_class: "total_increasing"
accuracy_decimals: 3
icon: mdi:gauge
filters:
- multiply: 0.001
- median:
window_size: 5
send_every: 4
teleinfo_id: linky
- platform: teleinfo
tag_name: "IINST"
name: "Current"
unit_of_measurement: "A"
icon: mdi:current-ac
teleinfo_id: linky
- platform: teleinfo
tag_name: "PAPP"
name: "Apparant Power"
unit_of_measurement: "VA"
icon: mdi:flash
teleinfo_id: linky
Hi @hallard, thanks for the wemos teleinfo board, I got mine from Tindie. It works but I got these errors:
Same in historical or standard mode. I use ESPHome, with an ESP32 (lolin s2 mini).
Here's my config, nothing too fancy.
Any idea of what could be the issue? Any way to check if it's the teleinfo esphome module or the hardware? Same kind of errors were observed here: https://github.com/esphome/issues/issues/2060#issuecomment-882589485
Thanks for your help!