Open ludrao opened 4 months ago
I have an even worse situation: the value is sometime reported as 0 (again randomly) Output of mosquito_sub as mentioned above
3767421
3243171
865199
698963
491408
174437
3767421
3243204
865199
698963
491408
174437
3767421
3243214
865199
0
491408
174437
3767421
Reading the source code I found out that the are logs on the serial port. Unfortunately my linky meter is outside in the street, so I cannot let a laptop connected to it until it reproduces, especially in rainy days :sweat_smile: .
I upgraded TICMeter to v3.2.9 and will try again so see if the prb still occurs
Hello, For me the new firmware don't solve the issue.
Same for me V3.2.9 does not solve the issue, I still have values set to 0:
An example of my dashboard on 3.2.9 :
Hello, I have just updated my TICMeter with 3.2.10 firmware and now i have only few metrics. I put some screenshots of my dashboard and of MQTT Explorer for information. If you look at my screenshots some metrics are in MQTT Explorer but not on HAOS. Regards
Hello, This afternoon i have all lot of metrics, some of them are in "unknow" but these seems to be correct, without doing anything. Regards
Hello, I updated to latest (v3.2.12) and still have bug (Energy Indexes that randomly(rarely) reported as zero). This breaks Home Assistant stats as the index is not "always increasing" I also noticed that the device reboot several times, is this a normal thing? See the uptime graph:
The problem encountered
Note: this may be related to #20 Using MQTT mode + Home Assistant.
Some value seem truncated, e.g. 324206 instead of 3242060 (missing the last digit) for EASF0x energy indexes This screws home assistant statistics since it thinks the index looped...
Firmware version
V3.2.7
Steps for reproducing the error
Nothing specific this seems to happen randomly, a couple of times a day
What I've already tested
I captured what is reported to mosquito server using this command:
mosquitto_sub -u ha-client -P "XXXXX" -t 'TICMeter/545520/EASF01' -t 'TICMeter/545520/EASF02' -t 'TICMeter/545520/EASF03' -t 'TICMeter/545520/EASF04' -t 'TICMeter/545520/EASF05' -t 'TICMeter/545520/EASF06' -p 1883 > mqttsub.log
Thus taking Home Assistant out of the equation.This is the output I got (truncated file, greped on "324" to list the same index value)
As you can see the TICMeter reported truncated value 324200 and 324206 (3rd and 10th line from the end)
This is confirmed from the data view in home assistant:
Relevant log output
No response