Ghost metrics

[kriskillerz]

The problem encountered

The integration of the TICMeter was flawless with the new firmware, but now in Home Assistant (HAOS Core)

Home Assistant Version :

• Core : 2024.6.4
• Supervisor : 2024.06.0
• Operating System : 12.4
• Interface utilisateur : 20240610.1

Firmware version

V3.2.7

Steps for reproducing the error

Waiting on the dashboard to see metrics dissappear, with different timing.
Looking into Dev. State to see a new metrics with same name but ending with _2.
Example : sensor.ticmeter_53b730_sinsts_2
Looking with MQTT Explorer to see the metric, and i see that information is not receive all minute but randomly.
Looking at the log in MQTT.

If you need anything else, i can made some more stuff you need for invetigation.

Thanks

What I've already tested

Resetting the TICMeter without success.
Resetting the TICMeter and forcing the mode to STANDARD without success.
Restarting HAOS Core

Relevant log output

2024-06-22 16:55:41: New connection from 192.168.2.193:57737 on port 1883.
2024-06-22 16:55:41: New client connected from 192.168.2.193:57737 as TICMeter_53B730 (p2, c1, k120, u'xxxxxxxxxx').
2024-06-22 16:55:42: Client TICMeter_53B730 disconnected.
2024-06-22 16:56:40: New connection from 192.168.2.193:57738 on port 1883.
2024-06-22 16:56:40: New client connected from 192.168.2.193:57738 as TICMeter_53B730 (p2, c1, k120, u'xxxxxxxxxx').
2024-06-22 16:56:40: Client TICMeter_53B730 disconnected.
2024-06-22 16:57:40: New connection from 192.168.2.193:57739 on port 1883.
2024-06-22 16:57:40: New client connected from 192.168.2.193:57739 as TICMeter_53B730 (p2, c1, k120, u'xxxxxxxxxx').
2024-06-22 16:57:40: Client TICMeter_53B730 disconnected.
2024-06-22 16:58:39: New connection from 192.168.2.193:57740 on port 1883.
2024-06-22 16:58:39: New client connected from 192.168.2.193:57740 as TICMeter_53B730 (p2, c1, k120, u'xxxxxxxxxx').
2024-06-22 16:58:39: Client TICMeter_53B730 disconnected.
2024-06-22 16:59:38: New connection from 192.168.2.193:57741 on port 1883.
2024-06-22 16:59:38: New client connected from 192.168.2.193:57741 as TICMeter_53B730 (p2, c1, k120, u'xxxxxxxxxx').
2024-06-22 16:59:38: Client TICMeter_53B730 disconnected.
2024-06-22 17:00:37: New connection from 192.168.2.193:57742 on port 1883.
2024-06-22 17:00:37: New client connected from 192.168.2.193:57742 as TICMeter_53B730 (p2, c1, k120, u'xxxxxxxxxx').
2024-06-22 17:00:37: Client TICMeter_53B730 disconnected.

[acontios]

Bonjour,

I also have the same behaviour (Tic version 3.2.13).

It seems that the TICMeter reboots in loop, as it intermittently pings (and makes its DHCP requests each time it seems to be booting up):

acontios@puisard:~$ ping 100.100.100.24
PING 100.100.100.24 (100.100.100.24) 56(84) bytes of data.
From 100.100.100.252 icmp_seq=1 Destination Host Unreachable
From 100.100.100.252 icmp_seq=2 Destination Host Unreachable
(...)
From 100.100.100.252 icmp_seq=10 Destination Host Unreachable
From 100.100.100.252 icmp_seq=11 Destination Host Unreachable
From 100.100.100.252 icmp_seq=12 Destination Host Unreachable
64 bytes from 100.100.100.24: icmp_seq=13 ttl=64 time=1751 ms
64 bytes from 100.100.100.24: icmp_seq=14 ttl=64 time=727 ms
64 bytes from 100.100.100.24: icmp_seq=15 ttl=64 time=23.2 ms
From 100.100.100.252 icmp_seq=23 Destination Host Unreachable
From 100.100.100.252 icmp_seq=24 Destination Host Unreachable
From 100.100.100.252 icmp_seq=25 Destination Host Unreachable
From 100.100.100.252 icmp_seq=26 Destination Host Unreachable
(...)
From 100.100.100.252 icmp_seq=64 Destination Host Unreachable
From 100.100.100.252 icmp_seq=65 Destination Host Unreachable
64 bytes from 100.100.100.24: icmp_seq=67 ttl=64 time=1521 ms
64 bytes from 100.100.100.24: icmp_seq=68 ttl=64 time=497 ms
From 100.100.100.252 icmp_seq=77 Destination Host Unreachable
From 100.100.100.252 icmp_seq=78 Destination Host Unreachable
(...)

[acontios]

Bonjour,

Se pourrait-il que ce soit un problème de réception Wi-Fi ?
Cela fait de sacrés trous dans les graphes :-)