You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I have a modbus kWh meter. A Raspberry Pi collects it's data and sent it to a online broker (HiveMQ). That broker is bridget with my HA broker.
Every now and then I get a strange value of the energy, corrupting my energy dashboard in home assistant. I have to remove the strange value from my statistics.
First I thougt this value came from the raspberry pi but then I start logging both MQTT brokers with the MQTT explorer..
At that point, I noticed a very peculiar thing. When I closed the MQTT explorer logging the HA mqtt broker, and started it again, I got a corrupt data point in the broker and also in Home Assistant.
The upper part is HA mqtt. the lower is bridget HiveMQ. It is visible the first datapoint, at 10:18:04 is 924,4.
The following datapoint are 293,xxx.
How is this posible?
I am able to reproduce, every time I start mqtt explorer on this broker, this happens.
The text was updated successfully, but these errors were encountered:
Hi,
I have a modbus kWh meter. A Raspberry Pi collects it's data and sent it to a online broker (HiveMQ). That broker is bridget with my HA broker.
Every now and then I get a strange value of the energy, corrupting my energy dashboard in home assistant. I have to remove the strange value from my statistics.
First I thougt this value came from the raspberry pi but then I start logging both MQTT brokers with the MQTT explorer..
At that point, I noticed a very peculiar thing. When I closed the MQTT explorer logging the HA mqtt broker, and started it again, I got a corrupt data point in the broker and also in Home Assistant.
The upper part is HA mqtt. the lower is bridget HiveMQ. It is visible the first datapoint, at 10:18:04 is 924,4.
The following datapoint are 293,xxx.
How is this posible?
I am able to reproduce, every time I start mqtt explorer on this broker, this happens.
The text was updated successfully, but these errors were encountered: