Comments

13 comments

  • Avatar
    Sergey Yuldashev

    Hello Harry,

    There is no such capability at the moment.
    I moved your post to the "New Feature Ideas" topic.

    Our design team member will likely contact you here to collect more detailed feedback.

    0
    Comment actions Permalink
  • Avatar
    Tagir Gadelshin

    Hi, Harry!

    First of all -- thanks for the feedback!

    We've been discussing customizable events and actions in our product team. For now, we decided to postpone this. Do HTTP request is enough for most of our users and scenarios. Currently, we are working on extending parameters proxying from events to actions (e.g., {resource.name})

    May you elaborate what kind of scenario do you have and what is your goal? Why HTTP Request is not suitable for you (usage instruction: https://support.networkoptix.com/hc/en-us/articles/222669328-Action-Do-HTTP-Request)

    0
    Comment actions Permalink
  • Avatar
    Hamb Anet

    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.

    MQTT would be a great option as well. Also useful for integrating with Home Assistant and other systems (e.g. ESP devices).

    0
    Comment actions Permalink
  • Avatar
    Hamb Anet

    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 actions can be reconsidered?

    Or, MQTT put on the roadmap? 

    MQTT's smaller size and delivery guarantees would be powerful for integration with other systems.

    0
    Comment actions Permalink
  • Avatar
    Tagir Gadelshin

    Hamb Anet

    We'll consider adding a plain-text field in the Event Rules for the HTTP headers.

    But we have plenty of things in our Event Rules roadmap, so I'm not sure if it will make it in 4.2.

    MQTT action is also a good idea, but we'll keep it in the ideas section for now
    basically, it means that we won't do this until "HTTP headers" is released. 

     

    Internal: FDBK-207

    0
    Comment actions Permalink
  • Avatar
    Norman Graafsma

    Hi Hamb Anet,

    Please check out https://my.networkoptix.com/#/integrations and search for 'MQTT' and find the solution our valued partner Stefaan Joos submitted. 

    Most likely it is useful for you as well. 

    0
    Comment actions Permalink
  • Avatar
    Tagir Gadelshin

    Norman Graafsma 
    If I'm not mistaken, this integration is more like an MQTT event, not like MQTT action. It directs any incoming MQTT as a Generic Event in Nx Witness. Hamb Anet needs an MQTT action

    I think there are some services or integrations that will re-route outgoing HTTP requests (Do HTTP request action) as MQTT, but I can't recommend any specific ones. They call them HTTP to MQTT bridge 

    0
    Comment actions Permalink
  • Avatar
    Stefaan Joos

    Hi All,

    Sergey Yuldashev it does exist, i use it, not inside nx, but in the integration

    Tagir Gadelshin you are correct, we created an MQTT broker where you could publish an action and that action will go to NX as an generic event

    Doing the other way around is also possible, we created a tool with softbuttons that is useable in NX and can publish MQTT messages.

    I also played around with openHAB and you can integrate an openHAB webpage in NX, that can also publish MQTT messages.

     

    All fun! With NX and smart integrations, anything is possible.

    2
    Comment actions Permalink
  • Avatar
    Hamb Anet

    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 in notifying not just Hassio, but a large number of other systems as well (e.g. ESP devices, Grafana). For example, at my location, I have ESP8266 based devices that are MQTT connected. With MQTT, NX motion events can turn on lights via Hassio. In the event Hassio is down, the ESP devices can include fallback logic, so they still function as expected. With MQTT, there is so much more flexibility and it scales easily. Opens a lot of new doors.

    0
    Comment actions Permalink
  • Avatar
    Evgeny Balashov

    This is officially my favorite thread in the entire community!

    2
    Comment actions Permalink
  • Avatar
    Hamb Anet

    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 HTTP (Bearer) relay would work as well, at least until a native HTTP header is an option. Thanks Tagir.

    0
    Comment actions Permalink
  • Avatar
    Stefaan Joos

    it seems that i'm the only guy that thinks that http request actions are not the best way to approach external action, http request is a start, so i'm happy with that.

    0
    Comment actions Permalink
  • Avatar
    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-in architecture, this would be the ideal option so developers can contribute actions as needed.

    But for now, HTTP requests are a good first option because of the ubiquity of REST APIs and generic HTTP endpoints.

    0
    Comment actions Permalink

Please sign in to leave a comment.