I am attempting to set up my micro gateway using Node-Red, and I continue to run into an issue with connectivity. Im not sure what the issue is, as I installed the VCP drivers from FTDI and have verified I set the correct serial port in node-red. I continue to get either the “TypeError: Cannot read properties of undefined (reading ‘on’)” or the error I’ve attached below.
I am trying to follow along with the Getting Started with NCD Wireless Sensors and Node-Red YouTube video, but I keep getting stuck when I should be seeing the green ready symbol, I continue to get failures to connect.
Hi @jtob can you please provide details on your setup? Are you running Node-Red on a computer and attempting to connect it to this gateway:
If so the MQTT WiFi Micro Gateway was not developed to work with Node-Red. If you want to run Node-Red on a computer and connect it to an external Modem I would recommend this modem instead of the MQTT Gateway:
A more concise setup however, which I would recommend, would be our Enterprise Lite Gateway here which runs Node-Red on board meaning it replaces the modem and computer with a single hardware device:
Thanks Travis, unfortunately that’s what I was attempting to do. I have a few wireless sensors I was hoping to connect to the MQTT micro gateway through node-red. So there is no way to do this, I would have to order a modem as well?
Our MQTT Gateway wasn’t designed to work with our node-red library, but its technically possible to get the data into node-red using a package like this that acts as an MQTT broker in Node-red that the MQTT Gateway can connect to: node-red-contrib-aedes (node) - Node-RED and then just using MQTT in/out nodes. I haven’t tested that module so I cannot guarantee it plus there’s firewall concerns if you’re on Windows.
You could also use an MQTT broker like HiveMQ and get the sensor data that the MQTT Gateway can publish to HiveMQ using the built-in MQTT nodes in Node-Red.
The MQTT Gateway was designed to accept sensor data over the wireless network and publish it to an MQTT broker without the need of any other local software, just an MQTT broker somewhere to connect to.
In general I wouldn’t recommend using it to get data into a local node-red instance as it adds an additional layer of tech (mqtt broker + client configuration, incoming network connections/firewall) into the mix of getting data into node-red unnecessarily. If you’re within the 30 day window we do offer refunds or if you’re past that 30 days I believe we generally offer store credit that you can use for a Modem or an Enterprise Gateway. Shipping isn’t covered under the refund policy though. You can find the RMA form at: https://ncd.io/contact-us/product-returns/
Backing up a little bit. We have several IoT sensors were hoping to use as a monitoring system for some structures we have. We’re using the PR52-33TS Tilt/Inclination Sensor, the PR55-61E Vibration Sensor, and the PR55-1G_C1D2 door sensor. We want to publish the data collected by these using the MQTT micro gateway. We were initially trying to do this within node-red, but it sounds like the main functionality of our gateway doesn’t use node-red to begin with, and if we configure our gateway using the wifi and MQTT broker information, we can achieve our goal without the use of node-red. Is this correct?
Currently I am in the configuration page for the MQTT micro gateway, and I have our vibration sensor on trying to connect. I am in a constant state of “Configuring Now…” on the devices page and I have received the following errors.
[{“problem”:“Failed to fetch device list”,“message”:{“message”:“Non 200 response”,“err”:0,“data”:“”}},{“problem”:“Failed to fetch device list”,“message”:{“message”:“Non 200 response”,“err”:0,“data”:“”}},{“problem”:“Failed to fetch device list”,“message”:{“message”:“Non 200 response”,“err”:0,“data”:“”}}]
