Martin, is your docker instance of node-red running again & causing you to get confused with which instance of node-red is actually running?
Are you running node-red under node using n or nvm or some other way ?
No, i delete docker.
I don't know what is "n or nvm"
I asked you to post the output when you start node-red.
18 Jul 15:50:46 - [debug] C:\Users\Martin\node_modules\node-re
d-contrib-xbee
Note that is in the wrong folder, you have been installing modules from the Martin folder as well as .node-red. Remove the folder c:/Users/Martin/node_modules, and also the package.json and package-lock.json that you will probably find in the Marting folder. Then restart node-red again. If it still is wrong post the log again (the whole startup log this time please).
[Edit] I am assuming the node-red does not get installed into that folder on windows, if I am wrong there then just npm remove the node from that folder.
Have you possibly got two folders C:\Users\Martin, one with a trailing space or something else on the end?
No, i don't have
If your main node-red installation files are in "C:\Users\Martin " then it should NOT be there. When you follow the windows install guide node-red gets installed to the global npm folder. On windows, unless you change it, that is (in your case) "C:\\Users\Martin \AppData\Roaming\npm\node_modules\node-red"
Only when you launch node-red for the first time do you get the .node-red folder - in your case "C:\Users\Martin \.node-red"
All node-red contrib nodes MUST get installed inside the \.node-red\node_modules folder - no exceptions (unless you know what you are doing)
ISSUE!
Is your user folder REALLY "Martin " ← With a space at the end? This is probably messing some NPM nodes up.
Recommendations
- If there is a space in your user name, create a new account, log into that, install node-red again following the windows install TO THE LETTER
Well something is horribly confused, as you can see by the fact that the above appears to suggest that there is a folder with a space (and possibly more) and one without.
I remember you started off with your full name as the user name with a space in, are you sure that (or something related to it) is not still present?
I suggest you follow @Steve-Mcl's advice and start again.
There is no problem with my name folder.
I found the duplicate .node-red folder, delete it and solve the problem (in it was the xbee folder). I also find the "C:\\Users\Martin\AppData\Roaming\npm\node_modules\node-red", and in node_modules folder i found less sub-folders with nodes, compared to this directory .node-red folder "C:\Users\Martin\.node-red"
So, i suppuse there is no point to have both? So, what i have to do:
To copy one into other?
Or to reinstall NR?
Or something else?
It would be better to have all of the extra nodes you install to be under C:\Users\Martin\.node-red.
The fact you have some under C:\\Users\Martin\AppData\Roaming\npm\node_modules\node-red suggests you used the -g flag when running npm install and they have been installed as global modules.
First you should uninstall those global modules: npm remove -g <module-name>.
Then reinstall them in the .node-red directory - remember to not use the -g flag this time.
@knolleary do you understand how this output can be seen on starting node red when there is only one c:\Users\Martin* folder and it doesn't have a trailing or embedded space. The first line appears to suggest there is a space or unprintable character.
18 Jul 17:26:05 - [debug] C:\Users\Martin \node_modules\node-re
d-contribe-xbee-api
18 Jul 17:26:05 - [debug] Module: node-red-dashboard 2.21.0 *ignored due to loca
l copy*
18 Jul 17:26:05 - [debug] C:\Users\Martin\node_modules\node-re
d-dashboard
To be frank, no I don't. But nor do I, at this point, think it's worth pursuing.
We've been going in circles here trying to get Xbee working. The fact @Martin10 is back on a Windows machine when we spent a few days getting his RaspberryPi working is something I'm not going to spend any more of my time on.
1 Like
I know my questions sound stupid, but that is because i don't have enough experience.
After i reinstall, it seems like it work, but backward.
So, i have to write something in dashboard node, so i can see it in console -- debug node. Rather than vice versa.
That sentence means nothing to me. Please explain what you mean.
When i use the inject node to trigger the function node and send the ''hello'' message, i see this ''hello'' message in debug node (like in the pic), but not in the dashboard. But if i type some message (like ''XBBE'', in the pic) on dashboard, i can see it in the debug node (like in the pic).
That's make me wonder- how can i be sure, that the message i send are transmitted from one xbee-tx to the xbee-rx?
About the knolleary comment:
It was easier for me to test the Xbee-NR connection on Win first, because the xbee modules i use have drivers and libraries, that i don't know how to install on RPI. When i learn how to do it, i will try in RPI
In the screenshot of the flow you posted there does not appear to be a connection between the inject node and the dashboard node so there is no way anything will appear in the dashboard.
That is not possible as there is no connection between the dashboard node and any debug nodes.
For any further images you post please make sure that all debug nodes have names so that it is clear which node shows each message.
Yes, it is possible and it can be seen in the pic. Probably the code inside the function nodes make some connection.
I re-connect the nodes in variety of ways, but the results are almost the same...but not exactly
I connect debug node to all parts of the flow.
The results are in the pic (i can't understand everything in it, i uderstand only the xbee frame )
That is not the same flow you posted a few posts ago that you said had the problem. The new flow you post does obviously have such a connection.
Hey @knolleary, You are right !! this is a Node-red Forum, not a Xbee forum, have some respect @Martin10 for the great work these guys had put in to have a fantastic product as Node-Red!!
If its RPI related, I am will to advise as far I can, unfortunately, it seems you have a comms-related issue on the TX side.
