RFXtrx on Synology will not be activated on a NAS reboot

Hardware
1

Hi,

Everytime I restart my NAS, the /dev/ttyUSB0 device (RFXtrx) will not be activated. It does not help to plug out and plug in to activate. Activate = be present in the system and visible to processes.
I’ve a Aeon 5 Z-wave stick inserted as well, and this will always be activated on a reboot of the nas.

I’ll think that the RFXtrx device stopped to be activated after I added the Aeon stick, but not sure since I normally not reboot the NAS so often.

The only way to get it activated, what I’ve learned, is to start up my old Domoticz instance and shut it down. After that it will be activated as /dev/ttyUSB0.

Anyone that had similar problem and solved it with something? I run my HASS instance as a Docker image.

Thanks,
Peter

2

Hello! I have the same problem and solve IT the same way as you. Did you find a better solution?

3

Nope, unfortunate. I do not know what causing it nor do I find time either to trace… Very irritating and frustrating that I cannot get the Docker be rebooted when Syno reboots and HASS to be working after a power failure or similar.

If anyone knows what to do or where to look, please let us know.

Thanks,
Peter

4

So, I’ve been doing one more round regarding this issue and think I’ve solved it.

It comes down to that two modules do not load automatic by the system, but it loads when you, for instance, start the Domoticz package.

The fils needed to be loaded is the two below (which exist in the system and works with the RFXCOM device, at least with latest DSM 6 version)

insmod usbserial.ko
insmod ftdi_sio.ko

After loading this run
dmesg

To be able to get automatic start when reboot a USBSerials.sh file need to be added in /usr/local/etc/rc.d folder as root (sudo).

Below an example of USBSerials.sh taken from jadahl start-stop-status script

#!/bin/sh

RUNAS="root"
    

case $1 in
    start)

    insmod /lib/modules/usbserial.ko > /dev/null
    insmod /lib/modules/ftdi_sio.ko >/dev/null	

if [ `/bin/get_key_value /etc.defaults/VERSION buildnumber` -ge "5004" ]; then
        # Create udev rules to set permissions to 666 
        # Doing this at package start so it gets done even after DSM upgrade.  
        ln -s ${INSTALL_DIR}/rules.d/60-jadahl.usbserial.rules /lib/udev/rules.d/60-jadahl.usbserial.rules
	udevadm control --reload-rules
    
fi
        exit 0
        ;;
    stop)
    
        exit 0
        ;;
    status)
        exit 0
        ;;
    log)
        exit 1
        ;;
    *)
        exit 1
        ;;
esac