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
The MQTT Agent currently appears to have no support for publishing messages with MQTT's RETAIN flag feature, which directs the MQTT broker to keep a copy of the last message for new subscribers to a topic.
ruby-mqtt does support RETAIN by sending an additional argument to the MQTT::Client#publish function, and editing mqtt_agent.rb to force RETAIN does appear to work for my use case:
I suspect not everyone would be content with every MQTT agent publishing only with RETAIN, so this issue is to suggest adding a configuration option on an agent-by-agent basis. Based on some of the discussion in #1289, this may not be as simple since there's complications due to MQTT QoS level.
The text was updated successfully, but these errors were encountered:
The MQTT Agent currently appears to have no support for publishing messages with MQTT's
RETAIN
flag feature, which directs the MQTT broker to keep a copy of the last message for new subscribers to a topic.ruby-mqtt does support
RETAIN
by sending an additional argument to the MQTT::Client#publish function, and editing mqtt_agent.rb to forceRETAIN
does appear to work for my use case:huginn/app/models/agents/mqtt_agent.rb
Line 112 in 4d17829
I suspect not everyone would be content with every MQTT agent publishing only with
RETAIN
, so this issue is to suggest adding a configuration option on an agent-by-agent basis. Based on some of the discussion in #1289, this may not be as simple since there's complications due to MQTT QoS level.The text was updated successfully, but these errors were encountered: