SYNOLOGY Ds209+ [SOLVED]

[Stevanovich]

Hello,
Il installed domoticz from source repo.
Z-wave device USB stick does not appear in device popup to add.
There is no z-wave device an no openzwave device available .
The last domoticz software seem to be compiled for ds209+ nas. Need last dsm 5 but mine is 4.
I tried to compile it but i meet some error.
How can i check if my USB z-wave stick is recognised ?
Why z-wave or openzwave does not appear in manual device list to add.
Thanks for help
Best regards.

[Stevanovich]

I found a post about something like my trouble :
viewtopic.php?f=47&t=7087&start=20&hilit=DS209

I tried to install beta domotics from jahdal links , but are not compatible with my DS209+ , because i cannot get last DSM on it !

So , i have to try to upgrade manually DSM, or , to compile manually domoticz for my syno , very hard for me !

What is the best way?

Thanks for any reply.

[jumbotroll]

I found a post about something like my trouble :
viewtopic.php?f=47&t=7087&start=20&hilit=DS209

I tried to install beta domotics from jahdal links , but are not compatible with my DS209+ , because i cannot get last DSM on it !

So , i have to try to upgrade manually DSM, or , to compile manually domoticz for my syno , very hard for me !

What is the best way?

Thanks for any reply.

Sorry, but DS209+ arch-ppc853x with older DSM 4.2 and DSM 4.3 does not have OpenZwave support.
It's some problem compiling OpenZwave for older DSM.

[Stevanovich]

C'est quoi le problème ? (where is the problem ?)

So with domoticz v2.212 from synology community rep , no z-wave or openzwave device in the popup list

with domoticz V2.3823 from Jahdal , no z-wave or openzwave device in the popup list

Also tried UsbSerialDrivers_3.0.2.spk and UsbSerialDrivers_3.0.5.spk with no differences
- stop domoticz services, install driver, reboot and start domoticz

I'm sad and crying ...

[Stevanovich]

Sorry, but DS209+ arch-ppc853x with older DSM 4.2 and DSM 4.3 does not have OpenZwave support.
It's some problem compiling OpenZwave for older DSM.

Ok,
if i try to install DSM 5, i will get some result ?

Thanks

[niki_lauda]

When you have a an "older" DS like me a DS209, you can't upgrade to dsm 5.
Synology supports the dsm 5 year after release off the diskstation.

[Stevanovich]

Yes , i confirm that DS209+ does not support at all DSM5 ...
Now, I've got a syno-bricks ... at home

I tried to downgrade to DSM4 , but it is another problem.
I hope i can repear it .

Come back as soon as repair .

[jumbotroll]

I have made a test build Domoticz stable v2.3530 for DS209+ DSM 4.3 (arch=ppc853x) and OpenZvave.
Should also work on DSM 4.2.
http://www.jadahl.com/domoticz_stable/?arch=ppc853x
http://www.jadahl.com/domoticz_stable/p ... 3530-7.spk

[Stevanovich]

I have made a test build Domoticz stable v2.3530 for DS209+ DSM 4.3 (arch=ppc853x) and OpenZvave.
Should also work on DSM 4.2.
http://www.jadahl.com/domoticz_stable/?arch=ppc853x
http://www.jadahl.com/domoticz_stable/p ... 3530-7.spk

Hello,
Thanks for reply, i can't remember if i have tested it, not downloaded , not tested ...
i will try as soon as i repair my Syno DS209+ ...
I followed a german tutorial for upgrade it to DSM5 , i failed it and brick my syno.
At this time , i am backup all my precious files on my DS207 with an external disk , happy to have another one

I hope to have finish saturday .
Thanks for all

[Stevanovich]

Unbricked my DS209+ !!!
Really thanks to this :
http://www.huubmons.nl/multimedia/nas/1 ... gy-unbrick
and this :
http://www.synology-forum.de/showthread ... erschossen
and my arduino usb ttl device !

I'm writting a french blog about it, maybe not alone in this case .


Really thanks to jadahl :
domoticz_ppc853x-4.3_2.0.3530-7.spk works for me !

Openzwave device appear in the dropdwon list now .

Can i try to install another spk (latest) and go back after ?

best regards

[jumbotroll]

No, you can not update.
domoticz_ppc853x-4.3_2.0.3530-7.spk is the only version I have manage to compile with openzwave.
You can always test another versions and uninstall if it's not working and reinstall domoticz_ppc853x-4.3_2.0.3530-7.spk

[Stevanovich]

Hello,
Now i meet a new problem ,
I plug AEON Stick on my Synology
Is there any easy way to know what is it's usb device mounted name (usb0 , usb1?),

domoticz01.JPG (34.06 KiB) Viewed 5157 times

When i want to manage it nothing appear, what i get wrong ?

domoticz02.JPG (84.88 KiB) Viewed 5157 times

here is lsmod and dmesg |grep usb

Code: Select all

Module                  Size  Used by    Tainted: P  
ch341                  10820  0 
pl2303                 17487  1 
cp210x                 14577  0 
ftdi_sio               33370  0 
usbserial              28790  6 ch341,pl2303,cp210x,ftdi_sio
cifs                  213600  0 
udf                    83070  0 
isofs                  31447  0 
loop                   14892  0 
usbhid                 27720  0 
hid                    40835  1 usbhid
input_core             24002  2 usbhid,hid
usblp                  13170  0 
usb_storage            41243  0 
ohci_hcd               22406  0 
ehci_hcd               38572  0 
ppc85xx_synobios       31446  0 
skge                   41500  0 
synoacl_ext4           16683  0 
synoacl_vfs             8648  0 
hfsplus                75000  0 
fuse                   58743  0 
vfat                   12814  0 
fat                    50456  1 vfat
i2c_mpc                10320  0 
of_i2c                  4658  1 i2c_mpc
i2c_core               19323  3 ppc85xx_synobios,i2c_mpc,of_i2c
cryptosoft             15693  0 
ecryptfs               90327  0 
sha512_generic         12013  0 
sha256_generic         12560  0 
sha1_generic            5095  0 
ecb                     5269  0 
talitos                26523  0 
authenc                 9366  0 
rng_core                6346  1 talitos
cryptodev              15358  1 
ocf                    21290  2 cryptosoft,cryptodev
crc32c                  5774  0 
ansi_cprng              6937  0 
aes_generic            30578  0 
cpufreq_stats           5933  0 
freq_table              5346  1 cpufreq_stats
dm_snapshot            25975  0 
crc_itu_t               4411  1 udf
crc_ccitt               4403  0 
quota_v2                7169  2 
quota_tree             10166  1 quota_v2
usbcore               123446 11 ch341,pl2303,cp210x,ftdi_sio,usbserial,usbhid,usblp,usb_storage,ohci_hcd,ehci_hcd
sg                     26254  0 
psnap                   5089  0 
llc                     6464  1 psnap
raid456                58235  0 
raid10                 26936  0 
raid0                  12020  0 
linear                  9202  0 
async_raid6_recov       8066  1 raid456
async_pq                6885  2 raid456,async_raid6_recov
raid6_pq               78043  2 async_raid6_recov,async_pq
async_xor               6029  3 raid456,async_raid6_recov,async_pq
xor                    10517  1 async_xor
async_memcpy            4486  2 raid456,async_raid6_recov
async_tx                5410  5 raid456,async_raid6_recov,async_pq,async_xor,async_memcpy
dm_mod                 61733  1 dm_snapshot
ipv6                  238191 38 

Code: Select all

[   17.270650] usbcore: registered new interface driver usbfs
[   17.294731] usbcore: registered new interface driver hub
[   17.305965] usbcore: registered new device driver usb
[   27.543971] usb usb1: configuration #1 chosen from 1 choice
[   27.760982] usb usb2: configuration #1 chosen from 1 choice
[   28.082240] usbcore: registered new interface driver usb-storage
[   28.232998] usbcore: registered new interface driver usblp
[   28.522189] usbcore: registered new interface driver hiddev
[   28.541073] usbcore: registered new interface driver usbhid
[   28.546670] usbhid: v2.6:USB HID core driver
[   30.923079] usb 2-1: new full speed USB device using ohci_hcd and address 2
[   31.086703] usb 2-1: configuration #1 chosen from 1 choice
[   52.051872] usbcore: registered new interface driver usbserial
[   52.057750] usbserial: USB Serial Driver core
[   52.122666] usbcore: registered new interface driver ftdi_sio
[   52.208197] usb 2-1: lock for hub EH
[   52.354067] usb 2-1: reset full speed USB device using ohci_hcd and address 2
[   52.493458] usb 2-1: device firmware changed
[   52.497756] usb 2-1: unlock for hub EH
[   52.504367] usb 2-1: cp210x converter now attached to ttyUSB0
[   52.531532] usb 2-1: cp210x converter now attached to ttyUSB1
[   52.540401] usbcore: registered new interface driver cp210x
[   52.559088] usb 2-1: USB disconnect, address 2
[   52.777089] usb 2-1: new full speed USB device using ohci_hcd and address 3
[   52.976597] usb 2-1: configuration #1 chosen from 1 choice
[   53.131334] usb 2-1: pl2303 converter now attached to ttyUSB0
[   53.308192] usb 2-1: pl2303 converter now attached to ttyUSB1
[   53.391220] usbcore: registered new interface driver pl2303
[   53.540833] usbcore: registered new interface driver ch341
[   57.277543] Modules linked in: ch341 pl2303 cp210x ftdi_sio usbserial cifs udf isofs loop usbhid hid input_core usblp usb_storage ohci_hcd ehci_hcd ppc85xx_synobios(P) skge synoacl_ext4(P) synoacl_vfs(P) hfsplus fuse vfat fat i2c_mpc of_i2c i2c_core cryptosoft ecryptfs sha512_generic sha256_generic sha1_generic ecb talitos authenc rng_core cryptodev(P) ocf(P) crc32c ansi_cprng aes_generic cpufreq_stats freq_table dm_snapshot crc_itu_t crc_ccitt quota_v2 quota_tree usbcore sg psnap llc raid456 raid10 raid0 linear async_raid6_recov async_pq raid6_pq async_xor xor async_memcpy async_tx dm_mod ipv6 [last unloaded: i2c_core]
[   57.412628] [be789d40] [c30b8538] serial_open+0xe4/0x140 [usbserial]

[Stevanovich]

Hello,
Some news here, i still try to plug my AEON Stick gen5 , with UsbSerialDriver V3.0.9

Domoticz001.JPG (68.54 KiB) Viewed 5101 times

and Fail to open usb port

Domoticz001.JPG (68.54 KiB) Viewed 5101 times

I think there is a problem with detect AEON Stick ?

Thanks for help

[Stevanovich]

Hello,

I followed this post from :

http://www.openremote.org/display/docs/ ... ents=false

4) Permission OpenRemote service account to allow the creation of OS locks. This will be needed to ensure a resource lock is created when communicating the serial port of the USB device.

For this:

Add a new group using the standard add group admin screen in synology. Review section 3 of How to create user accounts and groups on Synology NAS. Add a group called: uucp
Add the openremote user to the newly created uucp group
Verify that the group is setup correctly in a shell session:
> more /etc/group
You should see something like:
uucp65548:openremote
Ensure new group can access write to /var/lock folder:
> chown -R root.uucp /var/lock
5) Permission openremote to the USB port device.

Add a new group using the standard add group admin screen in Synology. Review section 3 of How to create user accounts and groups on Synology NAS. Add a group called: dialout
Add the openremote user to the newly created dialout group
Verify that the group is setup correctly in a shell session:
> more /etc/group
You should see something like:
dialout65549:openremote
Ensure new group can access write to /dev/ttyUSB0 device:
> chown -R root.dialout /dev/ttyUSB0
The example here uses ttyUSB0, but the device assigned is what you'll observe in step (6) in the Installation of Linux Serial Drivers.

I shut down domoticz, uninstall domoticz, reboot my synology, réinstall domoticz

Now, work prefectly, my device is /dev/ttyACM0 , so apply this to previous post