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
Originally posted by proddy July 6, 2024
Thinking of adding a small new feature to output notifications.
The command would be called message, and the data would be any string. When invoked, it writes it to the log (so also syslog) and publishes an MQTT Topic called message.
Combined with the new powerful condition logic in the Scheduler this could be used to trigger other events. For example Home Assistant or NodeRed would respond to an incoming MQTT message.
The text was updated successfully, but these errors were encountered:
Discussed in #1848
Originally posted by proddy July 6, 2024
Thinking of adding a small new feature to output notifications.
The command would be called
message
, and the data would be any string. When invoked, it writes it to the log (so also syslog) and publishes an MQTT Topic calledmessage
.Combined with the new powerful condition logic in the Scheduler this could be used to trigger other events. For example Home Assistant or NodeRed would respond to an incoming MQTT message.
The text was updated successfully, but these errors were encountered: