Hamb Anet

Stefaan Joos I agree with you, and I’m sure others do as well. Eventually, other methods like MQTT will bring greater flexibility and performance. If NX were able to modularize actions into a plug-...

Sergey Yuldashev Tagir Gadelshin Any update to this? Really want the ability to more easily integrate NX with other systems. At the very least, a custom HTTP header field, which should be trivial t...

Sergey Yuldashev Any further development on this subject (custom action)?

Additional information: Noticed some client debug log entries that might be relevant to the issue: 2020-10-17 08:22:06.791 4e50 DEBUG nx::vms::discovery::ModuleConnector::Module(0x1be022e7bd0, 1674...

Tagir Gadelshin This is fine. Thank you!

Evgeny Balashov Happy to hear this isn't just noise. :) Tagir Gadelshin Circling back to your comment about an HTTP to MQTT bridge. This exists and works. Likewise, an HTTP (no-auth or basic) to HT...

Stefaan Joos Thanks for the reply. And that's a great project. I'll certainly keep it in mind. What I'm looking for currently is an MX event action that can dispatch an MQTT message.

Tagir Gadelshin That's great. Having this extra field makes the action usable with Hassio. And, that is correct. I'm looking to have events dispatched from NX as MQTT messages. This would be useful...

Are you able to add a field for custom HTTP headers? It's a small change that would add flexibility, including enable Bearer token authentication. And, perhaps a plugin architecture / API for actio...

Hi Sergey and Tagir! I would like to integrate NX Witness with Home Assistant. HTTP requests would work (best) if a header field were added as Hassio prefers a header token for authentication. MQ...