Good evening Jerome
Is the transmitter Node connected to Node Red (the small green square)? If yes, redo your setup on the transmission side of your Mega
Have you tested with an injection node?
Yes, properly connected. It receives the info because the LED blinks on the Arduino Mega.
Do you have any idea how to test the transmitter otherwise?
Hello Jérôme
If you tinker a bit, you can try this (Cloner une télécommande Radio Fréquence (433MHz) – Part 1 – Acquisition | StefTech)
At the beginning of Gladys 3, this is how I checked if it worked. You connect your receiver to your PC line input (with a jack plug), you visualize the received signals with the Audacity software. You generate a frame with the Mega and you see if it arrives on your PC.
Hello everyone,
I have an issue with Node-RED:
On each restart of Gladys the port of my Arduino RFLink changes
hello @gaetanb76
look in the Node-RED RFLink tutorial I talk about it there
does it change the port between RFLink and the Zigbee USB stick?
No, the Zigbee dongle remains on ttyUSB0
In the tutorial there’s this:
docker run -d \
--log-opt max-size=10m \
--restart=always \
--network=host \
--name node_red \
-u node-red:dialout \
--device=/dev/ttyUSB0 \
--device=/dev/ttyUSB1 \
--label com.centurylinklabs.watchtower.enable=false \
-v /var/lib/node-red:/data \
nodered/node-red
which I adapted during installation to:
--device=/dev/ttyUSB0 \
--device=/dev/ttyACM1 \
If I do that
That’s strange,
the node-red container ID has changed and its name too.
c1772a1d78ab nodered/node-red \"./entrypoint.sh\" 44 seconds ago Up 43 seconds (healthy) 1880/tcp nervous_keldysh
Previously the ID started with bfc5d463b
If I run docker run… again, here’s the error:
docker: Error response from daemon: Conflict. The container name "/node_red" is already in use by container "bfc5d463b…". You have to remove (or rename) that container to be able to reuse that name.
I’m not very familiar with the subject — my problem was that at startup the Rflink was on port ttyUSB0 and the dongle on ttyUSB1, and at each startup they would swap. At first I swapped the wiring and it worked again. Since then it’s been working with those two lines you mention (thanks to Vonox). What do you have on the other ttyACM port?
There is nothing at the other port.
[quote="
No, actually, there’s only one with docker ps …
That’s strange,
In a situation like that I have a radical solution: since I’m not very familiar with it, I’ll completely reinstall Node-RED.
Try adding this line:
--device=/dev/ttyACM0 \
Maybe this will fix the ACM ports
Already done.
The problem is that I can no longer run docker start node_red because it no longer finds the ttyACM1 port.
Each time I rerun the docker run command, it creates a new container for me.
Are you deleting all of Node-RED?
No, I don’t want to delete my flows.
I might be able to make a copy of the files flows.json and flows_cred.json before removing Node-RED.
For sure, you need to make a copy of your flows
You just need to, in Node-RED, export your flows, which you’ll find in your PC’s Downloads folder (I’m on Windows)
However, you’ll need to configure one of the MQTT nodes
But I can’t access Node-RED since I can’t start it 
I copied the files with WinSCP.
I hope that’s enough