domoticz in synology as package! Available now.

[Marselaar]

Maybe check if the Domoticz version in the Synocommunity might be an alternative:

Perhaps if they update it? Seems like an old version.

[francouai]

Don't upgrade to DSM7.0 then you will loose definitely Domoticz.
No USBSERIAL driver to connect your RFXcom will be updated so... stuck!
I migrate to Raspberry Pi1 and it works better than the Syno install.

[Gravityz]

migrated to docker some time ago
everything working
i decided to reboot to test if serialports were still working, they were not.(zwave was up but RFXcom was not)

i installed the the jadahl usb 6.2 package(did not need it before) and everything is working again

quick question.
will these drivers get loaded on the next reboot?

i know how to do this by putting a startup script in /usr/local/etc/rc.d but it looks like the jadahl package is taking care of this since it is installed in a seperate UsbSerialDrivers directory

thanks

still afraid of going to DSM7 because it might break domoticz (although we seem to have the 7.0 drivers)

[JackD]

I use the latest DSM 6.2.4-25556 Update 2 and also the jadahl usb 6.2 package.
On my system the serial drivers from the jadhal package get loaded when I do a reboot (both cold and warm reboot).

Just like a lot of people I am hesitant to go to DSM7. I wail until I see more people having Domoticz running on DSM7, and by doing it on a "easy and reliable way". For now I stay on DSM6 with the jadahl usb 6.2 package and Domoticz on Docker, works fine for me.............

[Gravityz]

thanks.

i am on 6.2.3 (probably save to go to 6.2.4)

i discovered info on how to load the usb drivers for DSM 7.0 but this info is 5 minutes old. better wait a while. for people who upgraded and are stuck try this

DSM7 by default does ship with the appropriate kernel modules, but does not load them at startup. It also ships with systemd, so there's no need to make any scripts, just a well placed text file:
(as a root) create /etc/modules-load.d/user.conf (the directory modules-load.d does not exist, create it; the file can be named whatever you like, but it must end with .conf).
put just these lines there:(or other drivers you need but they need to be present)
usbserial
cdc-acm
ftdi_sio

after that reboot

to load the drivers to test (after reboot they will be gone)

/sbin/modprobe usbserial
/sbin/modprobe ftdi_sio
/sbin/modprobe cdc-acm

stop the docker container and start it again to see it recognizes the ports