Synology upgrade to DSM 5.2-5644 – Service ZWave not connected

Free domotica! Forums Report a bug Synology upgrade to DSM 5.2-5644 – Service ZWave not connected

This topic contains 16 replies, has 7 voices, and was last updated by  conichonhaa 1 year, 7 months ago.

Viewing 15 posts - 1 through 15 (of 17 total)
  • Author
    Posts
  • #1567

    guillaume
    Participant

    Hello,

    My Synology DS212j DSM was automatically upgraded to the latest version DSM 5.2-5644 released on 28/10/2015. Afterward I was not able to control my Z-Wave modules. Looks like the Z-wave plus USB stick cannot connect. See log below from Pulse-Station Zwave service.
    Please advise

    2015-10-31 09:39:01.681 Always, OpenZwave Version 1.3.0 Starting Up
    2015-10-31 09:39:01.683 Info, mgr, Added driver for controller /dev/ttyACM0
    2015-10-31 09:39:01.740 Info, Opening controller /dev/ttyACM0
    2015-10-31 09:39:01.741 Info, Trying to open serial port /dev/ttyACM0 (attempt 1)
    2015-10-31 09:39:01.741 Error, ERROR: Cannot open serial port /dev/ttyACM0. Error code 13
    2015-10-31 09:39:01.741 Error, ERROR: Failed to open serial port /dev/ttyACM0
    2015-10-31 09:39:01.741 Warning, WARNING: Failed to init the controller (attempt 0)
    2015-10-31 09:39:06.750 Info, Opening controller /dev/ttyACM0
    2015-10-31 09:39:06.750 Info, Trying to open serial port /dev/ttyACM0 (attempt 1)
    2015-10-31 09:39:06.750 Error, ERROR: Cannot open serial port /dev/ttyACM0. Error code 13
    2015-10-31 09:39:06.750 Error, ERROR: Failed to open serial port /dev/ttyACM0
    2015-10-31 09:39:06.750 Warning, WARNING: Failed to init the controller (attempt 1)
    2015-10-31 09:39:11.760 Info, Opening controller /dev/ttyACM0
    2015-10-31 09:39:11.760 Info, Trying to open serial port /dev/ttyACM0 (attempt 1)
    2015-10-31 09:39:11.760 Error, ERROR: Cannot open serial port /dev/ttyACM0. Error code 13
    2015-10-31 09:39:11.760 Error, ERROR: Failed to open serial port /dev/ttyACM0
    2015-10-31 09:39:11.760 Warning, WARNING: Failed to init the controller (attempt 2)
    2015-10-31 09:39:16.770 Info, Opening controller /dev/ttyACM0
    2015-10-31 09:39:16.770 Info, Trying to open serial port /dev/ttyACM0 (attempt 1)
    2015-10-31 09:39:16.770 Error, ERROR: Cannot open serial port /dev/ttyACM0. Error code 13
    2015-10-31 09:39:16.770 Error, ERROR: Failed to open serial port /dev/ttyACM0
    2015-10-31 09:39:16.770 Warning, WARNING: Failed to init the controller (attempt 3)
    2015-10-31 09:39:21.781 Info, Opening controller /dev/ttyACM0
    2015-10-31 09:39:21.781 Info, Trying to open serial port /dev/ttyACM0 (attempt 1)
    2015-10-31 09:39:21.781 Error, ERROR: Cannot open serial port /dev/ttyACM0. Error code 13
    2015-10-31 09:39:21.781 Error, ERROR: Failed to open serial port /dev/ttyACM0
    2015-10-31 09:39:21.781 Warning, WARNING: Failed to init the controller (attempt 4)
    2015-10-31 09:39:21.801 Warning, WARNING: Tried to write driver config with no home ID set
    2015-10-31 09:39:21.801 Info, mgr, Manager::WriteConfig completed for driver with home ID of 0x00000000

    G

    #1568
    Mika
    Mika
    Keymaster

    Hi,

    I just upgrade the package normally…

    Mika.

    #1569

    RoyalTaz
    Participant

    Hello !

    It’s ok for me with the 1.2.2.
    Just upgrade, reboot the Syno…and run 😉

    Thx !

    #1571

    K.Rens
    Keymaster

    Error code 13 means that the key is found, but that you do not have access rights to it.

    After this update I had to execute following command via ssh:
    chmod 777 /dev/ttyACM0

    Kind regards,
    K.Rens

    #1575

    coldbringer
    Participant

    Great idea. But the result is:

    chmod: ttyACM0: Operation not permitted

    #1576

    K.Rens
    Keymaster

    That’s strange.
    Are you not logging as root via ssh?

    Kind regards,
    K.Rens

    #1579

    coldbringer
    Participant

    I logged in as admin. What’s the root password?! ‘root’ doesn’t work, blank also doesn’t.

    And is it true that I need to do the chmod after each restart?

    #1580

    K.Rens
    Keymaster

    It’s the same password as the one you use to login to DSM.
    For me it’s the same as admin.
    But user admin has limited rights, user root has all rights.

    Normally you don’t need to do that after every restart, but it all depends on how it’s implemented.

    Kind regards,
    K.Rens

    #1584

    coldbringer
    Participant

    Hey, it worked. Many thanks for your help!

    #1613

    coldbringer
    Participant

    But unfortunately: After restarting the DiskStation the problem is back. Do I need to automate the chmod command or what else can I do?

    Thx

    #1623

    coldbringer
    Participant

    Any help regarding my last question would be really appreciated.

    #1626

    RoyalTaz
    Participant

    What’s your version of DSM ?
    Mine is 5.2-5644, and just an upgrade of pulsestation and a reboot must be necessary.

    #1638

    coldbringer
    Participant

    I am on the same DSM version, but I have a PulseStation beta. Maybe that is the reason

    #1649

    RoyalTaz
    Participant

    Where do you see “beta”, if it’s in the package section, mine is also in beta

    In my side, when the problem appear, i’ve just upgraded PulseStation, in the package section of Syno, reboot my Syno.

    If it’s KO for you, try to uninstall Zwave plugin in PulseStation admin interface
    reboot your Syno and reinstall the Zwave plugin. (if i’m right, it reinstall the driver at same time)

    #1761

    Coyote
    Member

    Hi,

    I’m with the last release of PulseStation 1.2.2 and DSM 5.25644, and I’ve problem with ZWave service too.
    My stick is the Aeotec ZStick Gen5.

    There are two problems when I have to reboot the Syno :
    – The stick always changes (switches) the port at each reboot. If it was on the /dev/ttyACM0, it reboots on the /dev/ttyACM1… And I have to modify the parameters in the ZWave service.

    – I always have the ‘Error 13’ code in my log, and need to log on my Syno to make a ‘chmod 777’ of my port..

    Any ideas to solve this problem ?

    I just find something special… Since the last update (1.2.2), my interface says that I’m on 1.2.1 (But 1.2.2 on DSM interface), and my core service is ticked as stopped (But still running)…

    Thanks

    JMarc

Viewing 15 posts - 1 through 15 (of 17 total)

You must be logged in to reply to this topic.