how do i keep FRED Nodes Connected
I have a raspberry pi3 collecting information and pushing to a cloud hosted instance on FRED. I am using a cellular modem as there is no wifi at the location. The cell service has to reconnect at times when connections are lost. I have that configured to happen automatically but now I am having trouble keeping the FRED Nodes connected. They will get disconnected and will try to reconnect 3 time and then lock out. How do I set them up to go back and look again after a set period of time or do I need to set it up another way. Thanks for your help
node-red
add a comment |
I have a raspberry pi3 collecting information and pushing to a cloud hosted instance on FRED. I am using a cellular modem as there is no wifi at the location. The cell service has to reconnect at times when connections are lost. I have that configured to happen automatically but now I am having trouble keeping the FRED Nodes connected. They will get disconnected and will try to reconnect 3 time and then lock out. How do I set them up to go back and look again after a set period of time or do I need to set it up another way. Thanks for your help
node-red
add a comment |
I have a raspberry pi3 collecting information and pushing to a cloud hosted instance on FRED. I am using a cellular modem as there is no wifi at the location. The cell service has to reconnect at times when connections are lost. I have that configured to happen automatically but now I am having trouble keeping the FRED Nodes connected. They will get disconnected and will try to reconnect 3 time and then lock out. How do I set them up to go back and look again after a set period of time or do I need to set it up another way. Thanks for your help
node-red
I have a raspberry pi3 collecting information and pushing to a cloud hosted instance on FRED. I am using a cellular modem as there is no wifi at the location. The cell service has to reconnect at times when connections are lost. I have that configured to happen automatically but now I am having trouble keeping the FRED Nodes connected. They will get disconnected and will try to reconnect 3 time and then lock out. How do I set them up to go back and look again after a set period of time or do I need to set it up another way. Thanks for your help
node-red
node-red
asked Nov 22 '18 at 3:45


Robert VanHofwegenRobert VanHofwegen
1
1
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The short answer is that you should use MQTT, not the FRED node.
The FRED node has known issues with reconnecting after the connection drops. They won't likely be addressed in the FRED node because MQTT is a far better approach.
If you subscribe to FRED, you can use the MQTT service provided. If not, you can use any of a number of free MQTT services available. There's a list on GitHub here and a Tutorial on using MQTT with Node-RED
Finally, if you don't want to lose data when the connection drops, Sense Tecnic has contributed a MQTT node which uses a local in memory database to cache data, then will continue sending data when the connection is restored. mqttdb node
This is very helpful. Ill check this out. Thx
– Robert VanHofwegen
Nov 24 '18 at 19:16
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53423580%2fhow-do-i-keep-fred-nodes-connected%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The short answer is that you should use MQTT, not the FRED node.
The FRED node has known issues with reconnecting after the connection drops. They won't likely be addressed in the FRED node because MQTT is a far better approach.
If you subscribe to FRED, you can use the MQTT service provided. If not, you can use any of a number of free MQTT services available. There's a list on GitHub here and a Tutorial on using MQTT with Node-RED
Finally, if you don't want to lose data when the connection drops, Sense Tecnic has contributed a MQTT node which uses a local in memory database to cache data, then will continue sending data when the connection is restored. mqttdb node
This is very helpful. Ill check this out. Thx
– Robert VanHofwegen
Nov 24 '18 at 19:16
add a comment |
The short answer is that you should use MQTT, not the FRED node.
The FRED node has known issues with reconnecting after the connection drops. They won't likely be addressed in the FRED node because MQTT is a far better approach.
If you subscribe to FRED, you can use the MQTT service provided. If not, you can use any of a number of free MQTT services available. There's a list on GitHub here and a Tutorial on using MQTT with Node-RED
Finally, if you don't want to lose data when the connection drops, Sense Tecnic has contributed a MQTT node which uses a local in memory database to cache data, then will continue sending data when the connection is restored. mqttdb node
This is very helpful. Ill check this out. Thx
– Robert VanHofwegen
Nov 24 '18 at 19:16
add a comment |
The short answer is that you should use MQTT, not the FRED node.
The FRED node has known issues with reconnecting after the connection drops. They won't likely be addressed in the FRED node because MQTT is a far better approach.
If you subscribe to FRED, you can use the MQTT service provided. If not, you can use any of a number of free MQTT services available. There's a list on GitHub here and a Tutorial on using MQTT with Node-RED
Finally, if you don't want to lose data when the connection drops, Sense Tecnic has contributed a MQTT node which uses a local in memory database to cache data, then will continue sending data when the connection is restored. mqttdb node
The short answer is that you should use MQTT, not the FRED node.
The FRED node has known issues with reconnecting after the connection drops. They won't likely be addressed in the FRED node because MQTT is a far better approach.
If you subscribe to FRED, you can use the MQTT service provided. If not, you can use any of a number of free MQTT services available. There's a list on GitHub here and a Tutorial on using MQTT with Node-RED
Finally, if you don't want to lose data when the connection drops, Sense Tecnic has contributed a MQTT node which uses a local in memory database to cache data, then will continue sending data when the connection is restored. mqttdb node
answered Nov 23 '18 at 7:45


Rob MuirRob Muir
1
1
This is very helpful. Ill check this out. Thx
– Robert VanHofwegen
Nov 24 '18 at 19:16
add a comment |
This is very helpful. Ill check this out. Thx
– Robert VanHofwegen
Nov 24 '18 at 19:16
This is very helpful. Ill check this out. Thx
– Robert VanHofwegen
Nov 24 '18 at 19:16
This is very helpful. Ill check this out. Thx
– Robert VanHofwegen
Nov 24 '18 at 19:16
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53423580%2fhow-do-i-keep-fred-nodes-connected%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown