Node-RED enhancement to the lynx-server config node

rejas

I have been working with Node-RED in my home this weekend. I have a proposal for the lynx-server node that I want comments on.
Today you can enter Name, URL, Broker and API-Key. This works very well but it doesn't work that well for access to a local Edge Client.
Maybe we should have two "modes" for configuration. One simple with only Name, URL and API-key that suits the most use cases. And then one for "local broker" that adds the following:

Broker: Address (and optional port)
Username and Password (if authentication is used)
Local (Yes / No) (If local it will not add client_id to topics)
Then it should be possible to have a local Node-RED (on or near the edge-client) that will only need connection to Lynx when configuring. Local flow will still work without internet. Of course with some limitations like get status and add meta.
A good idea?

Jesper

I think this could be a good option if we include NodeRED inside the docker edge client as well. Should add this to the to-do list for future development.

gushed

Bumping this, I have a huge amount of conf files from mosquitto and thus I do not really know my Username and Password or where to look. But I've found the function I'm looking for in nodered. I know I want to use a MQTT in and subscribe to a single topic. That way I can setup an alarm when a device has not been active for the amount of time I want. Such a node would be very useful in the Lynx palette for Nodered. Cheers!

Jesper

I think this is two separate nodes, but one of them could work with the other.

The function you are looking for already exist built into the platform and is called Metric Monitor. This can be used together with another application called Metric Notifier that can send notifications when Monitor detects too old data.

gushed

Oh yes, thank you. It is these functions I was thinking of developing further with nodered!