domoticz in synology as package! Available now.

[Beaupigny]

Hi jumbotroll

A 6.2 version exist because I succeed installing domoticz_88f6281-6.2_3.0.9483-7 on my old 211J and it works very well.

I need a version with Python to install Zigate plugins, it doesn't exist for 88f6281 ?

Best regards

Jean luc

[Beaupigny]

Hi jumbotroll,

i known that your are very busy, and I am very sorry to trouble you but i am not able to find a solution by myself.

as i tell you a need a Domoticz version with Python plugins for my old DS 211 j Synology to install Zigate plugins.

I succeeded in installing domoticz_88f6281-5.2_3.0.8849-7. with Python plugins, but it doesn't want to launch.

what can i do, is there a suitable version for 88f6281 Ds 211 j ?

Best regards

[supergroover]

Hi Jumbotroll,

When you have some spare time, could you build a new package voor de Armadaxp dsm 6.2 beta with python?
There is a problem with blockly and dzVents link to topic.
This problem is solved in V4.10445.

Thanks!

[jumbotroll]

Hi Jumbotroll,

When you have some spare time, could you build a new package voor de Armadaxp dsm 6.2 beta with python?
There is a problem with blockly and dzVents link to topic.
This problem is solved in V4.10445.

Thanks!

Done and uploaded

[supergroover]

Hi Jumbotroll,

When you have some spare time, could you build a new package voor de Armadaxp dsm 6.2 beta with python?
There is a problem with blockly and dzVents link to topic.
This problem is solved in V4.10445.

Thanks!

Done and uploaded

Thank you very much!

[poldim]

Hi @jumbotroll,

I'm getting the following in my log:

Code: Select all

[  193.400079] usbcore: registered new interface driver usbserial
[  193.426258] usbcore: registered new interface driver ftdi_sio
[  193.434111] usbserial: USB Serial support registered for FTDI USB Serial Device
[  193.511698] usbserial: version magic '4.4.59 SMP preempt mod_unload ' should be '4.4.59+ SMP preempt mod_unload '
[  193.574980] ftdi_sio: version magic '4.4.59 SMP preempt mod_unload ' should be '4.4.59+ SMP preempt mod_unload '
[  193.636414] cp210x: version magic '4.4.59 SMP preempt mod_unload ' should be '4.4.59+ SMP preempt mod_unload '
[  193.660063] pl2303: version magic '4.4.59 SMP preempt mod_unload ' should be '4.4.59+ SMP preempt mod_unload '
[  193.728309] ch341: version magic '4.4.59 SMP preempt mod_unload ' should be '4.4.59+ SMP preempt mod_unload '
[  193.791661] ti_usb_3410_5052: version magic '4.4.59 SMP preempt mod_unload ' should be '4.4.59+ SMP preempt mod_unload '

Here's what I just did:

1. Used this page to find out which architecture my Synology uses. Turns out it is Broadwellnk as uname -a shows Linux Hyperion 4.4.59+ #23824 SMP PREEMPT Tue Dec 25 18:27:57 CST 2018 x86_64 GNU/Linux synology_broadwellnk_3018xs.
2. Downloaded the Broadwellnk driver file.
3. Installed this file as a manual package in the Synology package center, it's showing as running status.
4. Pulled the USB stick in + out and got nothin. No ttyUSB*, ttyAMA0, or ttyACM0.
5. As you mentioned in a previous post, I've tried renaming usbserial.ko in /lib/modules to usbserial.ko.old and reboot to no avail.
6. I did notice a copy of the UsbSerialDrivers folder was placed in /usr/local/ in addition to the standard /volume1/@appstore/UsbSerialDrivers. The installation did not copy the driver files to /usr/lib/modules.

Code: Select all

lsusb -t
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M
    |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M
    |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M
    |__ Port 3: Dev 4, If 0, Class=Vendor Specific Class, Driver=, 12M
    |__ Port 3: Dev 4, If 1, Class=Vendor Specific Class, Driver=, 12M
    |__ Port 4: Dev 5, If 0, Class=Mass Storage, Driver=usb-storage, 480M

Keep in mind, I'm trying to get GoControl HUSBZB-1 Combo Stick to work.



Any thoughts on what else to try?

[jumbotroll]

Hi @jumbotroll,

Here's what I just did:

1. Used this page to find out which architecture my Synology uses. Turns out it is Broadwellnk as uname -a shows Linux Hyperion 4.4.59+ #23824 SMP PREEMPT Tue Dec 25 18:27:57 CST 2018 x86_64 GNU/Linux synology_broadwellnk_3018xs.
2. Downloaded the Broadwellnk driver file.
3. Installed this file as a manual package in the Synology package center, it's showing as running status.
4. Pulled the USB stick in + out and got nothin. No ttyUSB*, ttyAMA0, or ttyACM0.
5. As you mentioned in a previous post, I've tried renaming usbserial.ko in /lib/modules to usbserial.ko.old and reboot to no avail.
6. I did notice a copy of the UsbSerialDrivers folder was placed in /usr/local/ in addition to the standard /volume1/@appstore/UsbSerialDrivers. The installation did not copy the driver files to /usr/lib/modules.

Keep in mind, I'm trying to get GoControl HUSBZB-1 Combo Stick to work.



Any thoughts on what else to try?

I will update the drivers in broadwellnk packages tonight with 4.4.59+ SMP drivers, this is a known problem...
I think your device GoControl HUSBZB-1 Combo Stick use the CP210x drivers, but I have not tested this device on synology.
The UsbSerialDrivers package for arch-broadwellnk is updated and the domoticz beta packages is updated
BTW the UsbSerialDrivers don't move to /lib/modules folder, they are insmod in the usr/local/... folder

[poldim]

I will update the drivers in broadwellnk packages tonight with 4.4.59+ SMP drivers, this is a known problem...
I think your device GoControl HUSBZB-1 Combo Stick use the CP210x drivers, but I have not tested this device on synology.
The UsbSerialDrivers package for arch-broadwellnk is updated and the domoticz beta packages is updated
BTW the UsbSerialDrivers don't move to /lib/modules folder, they are insmod in the usr/local/... folder

Thanks for your help. I believ the stick does use the CP210x driver from what I've found online.

I installed the new drivers and rebooted. Then tried unplugging and replugging the USB stick. Here's the log. Do I need to try renaming usbserial.ko in /lib/modules to usbserial.ko.old and reboot? I did notice a difference in output of lsusb before and after installing your SPK.

Code: Select all

dmesg | grep usb
[  191.770374] usbserial: version magic '4.4.59 SMP preempt mod_unload ' should be '4.4.59+ SMP preempt mod_unload '
[  191.896894] ftdi_sio: Unknown symbol usb_serial_handle_sysrq_char (err 0)
[  191.905984] ftdi_sio: Unknown symbol usb_serial_generic_open (err 0)
[  191.915217] ftdi_sio: Unknown symbol usb_serial_handle_dcd_change (err 0)
[  191.929166] ftdi_sio: Unknown symbol usb_serial_deregister_drivers (err 0)
[  191.947584] ftdi_sio: Unknown symbol usb_serial_generic_unthrottle (err 0)
[  191.957625] ftdi_sio: Unknown symbol usb_serial_handle_break (err 0)
[  191.972912] ftdi_sio: Unknown symbol usb_serial_generic_get_icount (err 0)
[  191.981022] ftdi_sio: Unknown symbol usb_serial_generic_tiocmiwait (err 0)
[  191.989776] ftdi_sio: Unknown symbol usb_serial_generic_throttle (err 0)
[  192.000370] ftdi_sio: Unknown symbol usb_serial_register_drivers (err 0)
[  192.047605] cp210x: Unknown symbol usb_serial_generic_open (err 0)
[  192.055745] cp210x: Unknown symbol usb_serial_generic_close (err 0)
[  192.063595] cp210x: Unknown symbol usb_serial_deregister_drivers (err 0)
[  192.075107] cp210x: Unknown symbol usb_serial_register_drivers (err 0)
[  192.225075] pl2303: Unknown symbol usb_serial_handle_sysrq_char (err 0)
[  192.232528] pl2303: Unknown symbol usb_serial_generic_open (err 0)
[  192.239462] pl2303: Unknown symbol usb_serial_generic_close (err 0)
[  192.246498] pl2303: Unknown symbol usb_serial_handle_dcd_change (err 0)
[  192.253988] pl2303: Unknown symbol usb_serial_deregister_drivers (err 0)
[  192.261525] pl2303: Unknown symbol usb_serial_handle_break (err 0)
[  192.268467] pl2303: Unknown symbol usb_serial_generic_tiocmiwait (err 0)
[  192.276003] pl2303: Unknown symbol usb_serial_register_drivers (err 0)
[  192.435947] ch341: Unknown symbol usb_serial_generic_open (err 0)
[  192.442812] ch341: Unknown symbol usb_serial_generic_close (err 0)
[  192.449768] ch341: Unknown symbol usb_serial_handle_dcd_change (err 0)
[  192.460634] ch341: Unknown symbol usb_serial_generic_resume (err 0)
[  192.474320] ch341: Unknown symbol usb_serial_deregister_drivers (err 0)
[  192.483634] ch341: Unknown symbol usb_serial_generic_tiocmiwait (err 0)
[  192.497387] ch341: Unknown symbol usb_serial_register_drivers (err 0)
[  192.570676] ti_usb_3410_5052: Unknown symbol usb_serial_deregister_drivers (err 0)
[  192.580500] ti_usb_3410_5052: Unknown symbol usb_serial_generic_get_icount (err 0)
[  192.589341] ti_usb_3410_5052: Unknown symbol usb_serial_generic_tiocmiwait (err 0)
[  192.605445] ti_usb_3410_5052: Unknown symbol usb_serial_register_drivers (err 0)

[jumbotroll]

Thanks for your help. I believ the stick does use the CP210x driver from what I've found online.

I installed the new drivers and rebooted. Then tried unplugging and replugging the USB stick. Here's the log. Do I need to try renaming usbserial.ko in /lib/modules to usbserial.ko.old and reboot? I did notice a difference in output of lsusb before and after installing your SPK.

Yes it's look like you have an old usbserial.ko driver in your system and maybe it's the /lib/module/usbserial.ko the t make some problem.
In my package the usbserial.ko is updated and insmod.
You can always try to rename the file and reboot...

[poldim]

I got it working!! Thank you!

Here's what I did:

Code: Select all

cat /usr/lib/modules/usbserial.ko

about halfway through the file I found this line:

Code: Select all

license=GPLdescription=USB Serial Driver coreauthor=Greg Kroah-Hartman <[email protected]>depends=usbcoreintree=Yvermagic=4.4.59+ SMP

Then I compared it with the other file:

Code: Select all

cat /usr/local/UsbSerialDrivers/modules/usbserial.ko
license=GPLdescription=USB Serial Driver coreauthor=Greg Kroah-Hartman <[email protected]>depends=usbcoreintree=Yvermagic=4.4.59 SMP

Noticing that /usr/lib/modules/usbserial.ko had the + after 4.4.59, I decided to try to place it into your folder:

Code: Select all

sudo mv /usr/local/UsbSerialDrivers/modules/usbserial.ko /usr/local/UsbSerialDrivers/modules/usbserial.ko.original
sudo cp /usr/lib/modules/usbserial.ko /usr/local/UsbSerialDrivers/modules/usbserial.ko

Code: Select all

sudo reboot now

Code: Select all

dmesg | grep tty
[  188.836041] usb 1-3: cp210x converter now attached to ttyUSB0
[  188.848238] usb 1-3: cp210x converter now attached to ttyUSB1

So now that I have it working, do I basically have to not perform DSM upgrades for fear of them breaking this driver compatibility? Or how can I learn to make these drivers for the correct DSM version on my own?

[spider2]

Hi,

I have a problem with the last beta Domoticz v4.0.10548-8. Now the notification is not working at all. .
My synology is armada370 213J type.
In the log shiw only this: 2019-03-18 12:03:26.995 Error: Telegram:
2019-03-18 12:04:08.577 Error: Pushbullet:
2019-03-18 12:04:34.728 Error: Pushbullet:
2019-03-18 12:09:17.496 Error: Pushbullet:
2019-03-18 12:09:26.331 Error: Telegram:
2019-03-18 12:09:31.341 Error: Telegram:
2019-03-18 12:09:33.158 Error: Telegram:
2019-03-18 12:15:54.242 Error: Telegram:
2019-03-18 12:15:56.785 Error: Telegram:

[spider2]

still not working and cant go back older beta because the synology package manager manual install not accept older beta domoticz.

2019-03-20 14:29:22.528 Notification sent (telegram) => Failed
2019-03-20 14:29:22.570 Active notification Subsystems: pushbullet, telegram (2/13)
2019-03-20 14:29:22.475 Status: Notification: Domoticz test
2019-03-20 14:29:22.527 Error: Telegram:

[schumi2004]

Today I updated to version 4.0.10570-8 and it seems to run but i don;t have a GUI to connect to.
Is this a know issue?

[jumbotroll]

Today I updated to version 4.0.10570-8 and it seems to run but i don;t have a GUI to connect to.
Is this a know issue?

Working fine here.
Try to clear your browser, if that don't work, manually download 4.0.10570-8 and reinstall and check that http port is 8084 in wizard.

[schumi2004]

Today I updated to version 4.0.10570-8 and it seems to run but i don;t have a GUI to connect to.
Is this a know issue?

Working fine here.
Try to clear your browser, if that don't work, manually download 4.0.10570-8 and reinstall and check that http port is 8084 in wizard.

A manual reinstall did the trick, thanks for your help

[bnlhv]

I installed the pre-compiled Domoticz package on my DS215j but Domoticz is not started at reboot of my NAS.
How do I configure automatic startup I can not find the script domoticz.sh anywhere.
Thanks for you help

[jumbotroll]

I installed the pre-compiled Domoticz package on my DS215j but Domoticz is not started at reboot of my NAS.
How do I configure automatic startup I can not find the script domoticz.sh anywhere.
Thanks for you help

Domoticz start automatic on Synology. no need for edit startup.sh.
You have maybe installed the python plugin version and if you don't have Python 3 package from synology installed, the domoticz will not start.

[schumi2004]

@jumbotroll
Since i upgraded to version 4.10602 i see a issue with python plugin iDetect
(https://www.domoticz.com/forum/viewtopic.php?t=20467)

2019-04-19 13:26:56.629 Error: (iDetect Wifi presence detection) Aborting plugin initialization because SSH client could not be found
2019-04-19 13:27:06.779 Error: (iDetect Wifi presence detection) Plugin initialization did not complete successfully. Check the (debug) log for startup errors.

For some reason it can't find SSH client but it always worked and nothing has changed to the Synology system, no DSM upgrade or anything like that.
SSH still workes like before so no noticeable changes there either.
I can't downgrade easily because Synology doesn't let you.
Any ideas?

[jumbotroll]

@jumbotroll
Since i upgraded to version 4.10602 i see a issue with python plugin iDetect
(https://www.domoticz.com/forum/viewtopic.php?t=20467)

2019-04-19 13:26:56.629 Error: (iDetect Wifi presence detection) Aborting plugin initialization because SSH client could not be found
2019-04-19 13:27:06.779 Error: (iDetect Wifi presence detection) Plugin initialization did not complete successfully. Check the (debug) log for startup errors.

For some reason it can't find SSH client but it always worked and nothing has changed to the Synology system, no DSM upgrade or anything like that.
SSH still workes like before so no noticeable changes there either.
I can't downgrade easily because Synology doesn't let you.
Any ideas?

Nothing changed in the package only updated domoticz from latest source.
Maybe something went wrong when you updated?
I have build the latest domoticz 4.10603 Alpine you can test or if that not work, maybe try to reinstall the plugin.

[waaren]

I have build the latest domoticz 4.10603 Alpine you can test or if that not work, maybe try to reinstall the plugin.

Can you please also build this version with Python for Braswell- DSM 6.2. I want to test dzVents' domoticz.triggerIFTTT on my Synology 916+
Many thanks !