Eliz
Forum Replies Created
-
AuthorPosts
-
Eliz
ParticipantThank you for the explanations! I ran the ftp command from the terminal and now I understand a lot better how the conduit handles the node red information and ftp site.
January 20, 2017 at 1:36 am in reply to: Conduit, Node red and Lora interconnection and storage confusion #16416Eliz
ParticipantHi Jeff
Thank you so much for your answers – they clarified a lot of my uncertainties and confusion!Eliz
ParticipantHi
I know this post was pretty long ago but I am sitting with the same initial problem – wanting to ftp a file from the conduit to the ftp server. Before it got very technical 🙂 I saw you said that one can use mqtt to transmit the file? How does one do that? Also you spoke of a FTP client program already installed on the conduit? How does one use and access that within node red?
Eliz
ParticipantHi all
thanks for the advice. I managed to install the node I wanted in the end! A few things that happened to me that might help someone –
1. I tried installing a package/node that I only realized had a pre-requisite for node red 0.14.0 after a few hours
2. When using npm install while in the /opt/node-red/node_modules directory it did’t work but when installing in /opt/node-red/nodes it worked and the node also then appeared in the config file and under node_modules
3. I was rebooting node red endlessly cause I misread originally – you actually have to reboot the conduit!Eliz
ParticipantJeff
thanks for the advice – I was busy rebooting node red until I was blue in the face but didn’t reboot the conduit – I think that was one of my problems.
Eliz
ParticipantI understand – thanks Jeff!
Eliz
ParticipantWill upgrading the AEP firmware upgrade nodejs and node red as well or not?
Eliz
ParticipantHi
I have tried to install the new node module in /opt/node-red and three things happened:
1. I can actually see the node-red-new-node module under node_modules
2. I also went to check that json config file that should update with a conduit restart but there is no /var/config/app/install/development/.config.json file there.
3. After restarting the conduit – still no new nodes were added to the palette.Does anyone have any advice or idea why this happens?
Update: The config.json file is in fact there, but does not update when the conduit restarts – does anyone know why?
-
This reply was modified 8 years, 1 month ago by
Eliz.
Eliz
ParticipantHi Jeff
Thank you for the answer. I have been playing around with this installation and trying to install in /opt/node-red and it is still not showing up in my palette. 🙁 Is there someplace I can maybe get the necessary prefix needed? What I mean is how do I know what the prefix should be?
Eliz
ParticipantJeff, thank you for the answer – it helped clear up my confusion.
Eliz
ParticipantBit of an update from my side – I went back to basics and came upon 2 sentences in that said that one could communicate with the conduit by using the linux commands if one installs cygwin or by using terra term or putty with ssh on port 22. I definitely missed this previously. So, as soon as the root@mtcdt:~# appeared after logging in I typed npm install node-red-my-new-node. This appeared to install successfully – at least there were no errors in the terminal displayed. I then also restarted node-red from the conduit UI.
However, my new nodes have not appeared in Node Red. Advice?
Eliz
ParticipantI am going to ask a very stupid question, also regarding the installation of additional nodes… these commands:
cd /opt/node-red/nodes
npm install node-red-contrib-the-new-node
/var/config/app/install/development/.config.jsoetc.
Where are you typing them? In what program? And under which directories? I am using the AEP model for the conduit. Is this mlinux? Or, I have connected the conduit via USB to my PC and am typing these programs via a terminal program? Is this correct? The outputs are very confusing and I am also getting the same errors as Martijn had originally. I would appreciate it if someone could please point me in the right direction?
Eliz
ParticipantMy mistake – a missing semi-colon – thanks again for the answer.
Eliz
ParticipantThanks for the answer – it clears up a lot of my uncertainty!
Unfortunately when I used the code with my own eui and payload substituted in, the debug terminal diplays – syntax error: unexpected token ILLEGAL. I am very much a newbie in javascript syntax and can’t seem to find the error?
-
This reply was modified 8 years, 1 month ago by
-
AuthorPosts