-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No commands received under Docker / Synology #109
Comments
The start-up handshake of the RFXCOM is not happening correctly. The node sends the handshake sequence starting at 10:57:57.613, but there is no reply: instead the RFX seems to disconnect (at 10:59:02.391). The node tries again to reconnect starting at 10:59:13.901 and this time it succeeds, so the message queue is started. But then at 10:59:32.931, the 'Copyright RFXCOM' message appears again, this time with a different message sequence number of 07. instead of 02 What happened to messages 03 to 06? They don't appear in the debug log. It's the RFX firmware that is generating these sequence numbers so it (presumably) sent the corresponding messages out, but they never reached Node-RED. Furthermore, the copyright message is the reply to the 'start receiver' command (first sent at 10:59:14.529) and the firmware should only ever send it in reply to such a command. So it looks like something in the USB Docker stack is going wrong - disconnecting oddly, missing and/or repeating messages, or something like that. But there also seems to be another problem, where the |
It sounds like it will be impossible to make it work under Docker ? |
If it is a Docker problem, I can't really help - sorry. Try the Docker and/or serialport package support channels. |
Hi Max I don't know if it is a docker problem. I changed an option reading channels : i changed the user and add it to dialout group with this option : -u node-red:dialout. When nodered starts, nodes are in yellow "Connecting...". Then i unplug the rfxcom module, and replug it. The nodes says "OK (v1025 ext 2)" in green. Then I can use a 433mhz light remote controller and it is working. I used it several time (hit buttons) until it stopped working, after receiving the "Copyright RFXCOM" message in logs here :
All commands like "Received: 0B,11,00,10,02,46,80,00,02,00,00,70" works and has an action on nodered. After the 2nd copyright message, nothing happens when i use the light remote controller Do you have an idea ? Regards Matz |
Any idea Max ? Maybe you need more info from me ? |
Sorry - I've been really busy lately. I intend to try simulating an unsolicited copyright message and seeing what happens (which is one part of the issue). |
I faced a problem similar to the logs shown above with erratic behaviour with Hass.io on raspberry 4 where I did install both the "rfxtrx integration" + "NodeRed Addon with node-red-contrib-rfxcom component". In my case the issue seems to be related to the fact that both the integration AND the addon want to access /dev/ttyUSB0 in parallel and it seems to confuse something, generating a conflict (Docker ? RfxComm module ? I don't know). This issue is talked about here. When I unplug the rfxcom module in that situation, it changes its port to /dev/ttyUSB1 when I plug it back and if I try to correct my configuration in NodeRed with /dev/ttyUSB1 it starts working just because the rfxtrx integration is dealing with the old /dev/ttyUSB0. I finally removed the rfxtrx integration from my configuration and now everything is OK with /dev/ttyUSB0 (after rebooting the OS to restore it from /dev/ttyUSB1 to /dev/ttyUSB0). Perhaps you should check on your system if nothings tries to access /dev/ttyUSB0 in parallel with your NodeRed configuration ? |
@zonk-git I don't think it is related. I have nothing on my system trying to access to /dev/ttyUSB0, and even if it were the case, I don't see why it could conflict with rfxcom node. |
Hi @maxwellhadley , I presume you are very busy, but do you think you will have time to check what's hapenning ? How can I help ? Regards Matz |
Finally got round to simulating the unsolicited copyright message. It doesn't cause any problems for me. It looks like the problem lies with Docker. When it hangs up, what is the displayed node status? (sorry this has all taken so long) |
I changed to running Node-RED in Docker a couple of days ago, and it work perfectly. This is my compose-file:
Edit: And as mentioned above, Home Assistant (https://www.home-assistant.io/) has an Node-RED add-on (https://community.home-assistant.io/t/home-assistant-community-add-on-node-red/55023), and all add-on's is Docker containers. So if this is a Docker issue, I would think you could find some solution in the HA forum. |
Hello
I'm using nodered under last image of Nodered Docker, in Synology. I created the container with the following command :
docker run -it --net=host -v /volume1/docker/nodered2/data:/data -v /volume1/docker/nodered2:/syno -v /etc/localtime:/etc/localtime:ro -v /etc/TZ:/etc/timezone:ro -d --restart always --privileged=true -e DSM_HOSTNAME=synology -e TZ=Europe/Paris --device /dev/ttyUSB0 -name nodered nodered/node-red
I used the parameter --device /dev/ttyUSB0 as indicated in the docker page of nodered, in order tobe able to access to the port.
I'm using last version of node-red-contrib-rfxcom (2.11.2, I upgraded the rfxcom to last fimrware (1025). Here is what i have :
I add a rfx-lights node, serial port / dev/ttyUSB0, with option "listen for commands sent to any address", I connect it to a debug node with complete msg object. I deploy. The node has this message under it : "OK (v1025 ext 2)". I push a button on a command, I can see the little yellow led light on then light off on the rfxcom, but nothing happens in nodered. When I push the same button when the rfxcom is plugged to my computer running windows, I see the message coming in rfxmgr.
Here is a grep rfxcom of the nodered logs :
Can you help me ?
Regards
Matz
The text was updated successfully, but these errors were encountered: