Hallo,
I'm new to this and have v 0.21.0 installed. I'm using CC2531 connected to official nodered docker.
I needed to add --privileged -v /dev/ttyACM0:/dev/ttyACM0 to the docker command to map the serial port.
In addition, it took me half day to figure out why zigbee-herman was not starting (either permission of serial port or /dev/ttyACM0 not accessable). ...so I also needed to apply the patch from #160.
Now its starting and working.
BUT, as soon as I change something in the flow and hit Update in nodered, than I again get the error message with permission of serial port. So I suppose that during update the zigbee node does not fully clean up the serial port binding and when restarting, the port is still blocked.
The only action which helps here is to reeboot the entire docker image.
So can someone please help me and tell me what I need to do to avoid rebooting the entire nodered docker image ?
Is it a bug in nodered zigbee package or is it something on my side?
Hallo, I'm new to this and have v 0.21.0 installed. I'm using CC2531 connected to official nodered docker. I needed to add --privileged -v /dev/ttyACM0:/dev/ttyACM0 to the docker command to map the serial port. In addition, it took me half day to figure out why zigbee-herman was not starting (either permission of serial port or /dev/ttyACM0 not accessable). ...so I also needed to apply the patch from #160. Now its starting and working.
BUT, as soon as I change something in the flow and hit Update in nodered, than I again get the error message with permission of serial port. So I suppose that during update the zigbee node does not fully clean up the serial port binding and when restarting, the port is still blocked. The only action which helps here is to reeboot the entire docker image.
So can someone please help me and tell me what I need to do to avoid rebooting the entire nodered docker image ? Is it a bug in nodered zigbee package or is it something on my side?
Mayn thanks DRS