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
While MQTT-Explorer is a great tool, the one annoying thing is that is occasionally tries to decode SparkplugB.
So if I send the message Slaapkamer1 to homeassistant/status/reset MQTT-Explorer tries to decode this as SparkplugB, resulting in {} as message. If I send Keuken to the same topic, the decoder stops working and just shows my message.
SparkplugB is sadly not fixed in beta6 but deactivated. There where disscussions and suggestions about enhancing the detection. I am not aware of the current state of implementation.
While MQTT-Explorer is a great tool, the one annoying thing is that is occasionally tries to decode SparkplugB.
So if I send the message
Slaapkamer1
tohomeassistant/status/reset
MQTT-Explorer tries to decode this as SparkplugB, resulting in{}
as message. If I sendKeuken
to the same topic, the decoder stops working and just shows my message.From what I can tell, SparkplugB should only be send in this format
spBv1.0/Group ID/Message Type/Edge Node ID/Device ID
(source: https://corsosystems.com/posts/mqtt-and-sparkplug-b-simplified)So would it be possible to improve/disable the SparkplugB detection.
Note: I am at MQTT-Explorer 0.4.0-Beta4.
The text was updated successfully, but these errors were encountered: