We just purchased an enterprise gateway and 2 bidirectional pressure/temp sensors.
I have node-red programmed and connected to Blynk. If my gateway is connected to the internet via ethernet (ETH0), everything works fine and my data shows up on my Blynk dashboard. I am sending the temp and pressure once every 10 seconds. If I disconnect the ethernet and allow the gateway to connect to the internet via my hologram sim card, the gateway connects to the internet and the device shows as online in Blynk, but my data no longer streams.
Can someone from NCD reply to my issue here? I need to get this resolved.
Some additional info.
When I switch from LTE to ethernet by simply plugging in the ethernet cable, the gateway prioritizes the ethernet connection, connects to the internet and to Blynk, but doesn’t start streaming data, I have to then reboot the gateway in order for it to stream data.
If I then disconnect the ethernet and allow the LTE to connect, it connects to the internet and to Blynk, but doesn’t stream, so I then reboot, but it still does not stream.
One thing I noticed monitoring the web management page in the gateway, the modem initially connects GPRS but then changes to LTE. Not sure if that makes any difference.
It looks like there are undeployed changes on your flow.
Is this screen capture of Node-Red from when the gateway is connected over Cellular? If you restart the gateway while its not connected to internet over ETH0 do the MQTT nodes still show connected?
On the MQTT nodes what is the QoS set to?
Can the gateway send an http request to google.com and get a response while the issue is occuring?
I ran a series of tests with Blynk support, switching from ethernet to LTE. Blynk looked at the connection logs and concluded:
“It seems the connection fails to establish after switching to LTE. It appears to be a device-level issue. The connection appears to stall, causing no data to be transmitted to the server.”
Try setting that to 1 and see if that resolves your issue.
I’m not sure what blank will default to, but a value of 1 will expect a response when data is sent and should trigger a reconnect. I’m guessing that the network switch causes a dropped connection, but with a value of blank the MQTT doesn’t do any integrity checks.
Hard to say, the error message is pretty clear about the error, but what’s causing it I’m not entirely sure. If I had to guess its the handling of retained messages sent after reconnect.
Blockquote
“For the initial MQTT API release, only clean sessions are supported. In particular, the client will not receive any undelivered QoS 1 messages that were queued for it while it was disconnected. The Blynk team is working on Persistent Session support.”
You could try setting QoS to 0 and see if the base issue is just that it wasn’t set.
So with QoS of 0, no ethernet connected, and a reboot of the gateway can you confirm that no data is going to Blynk over MQTT through the cellular connection? Wanting to test that its not a network change that’s causing the issue. Does Node-Red have the ability to access the internet? The easiest way to check is to have node-red send an http request to google.com
Can you send a screenshot of your cellular configuration? You can find it through the Network Management UI > Interface > Cellular as well as its status (tab along the top of that page)?
These pages should look similar to this (minus the sim not connected message):
So with QoS of 0, no ethernet connected, and a reboot of the gateway can you confirm that no data is going to Blynk over MQTT through the cellular connection?
Correct. It shows connected on the MQTT node, and shows as ONLINE in Blynk, but no data streaming.
TEST: Gateway connected through LTE. Sent request to google.
