Custom ptvo device with UART spams MQTT with retained Home Assistant trigger config messages #23436
ondras12345
started this conversation in
Devices
Replies: 1 comment
-
I have generated a new firmware using ptvo-2024-10-01, set a custom model and generated a |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I have a custom CC2530-based device that receives UART messages (every 30 seconds) and forwards them via zigbee. Whenever a UART message is received, zigbee2mqtt sends (among others) a MQTT message like this:
(
50,48,50,52,48,55,50,55,84,49,55,52,57,50,49,90,9,32,32,32,32,32,50,55,49,52,56,9,32,51,52,46,32,54
is the content of the UART message represented as a series of ASCII values.)Presumably, this is is configuration for an MQTT device trigger in Home Assistant. However, Home Assistant does not seem to offer me such a device trigger -- and even if it did, I don't need that. Each UART message will be different (it contains a timestamp), so this just spams my MQTT broker with useless messages with retain flag set.
How can I prevent this?
For now, I have created a Home Assistant automation that subscribes to
homeassistant/device_automation/0x00124b000cbe08e1/#
and erases the messages by sending an empty retained message to the same topic. However, this is just a temporary solution.Edit - related message from Home Assistant log:
Beta Was this translation helpful? Give feedback.
All reactions