![aeon labs z-stick plus aeon labs z-stick plus](https://media.ldlc.com/r1600/mkp/62e01511f4144ab8b6aa7359617adba4.jpeg)
- #Aeon labs z stick plus install
- #Aeon labs z stick plus serial
- #Aeon labs z stick plus driver
- #Aeon labs z stick plus full
cdc_acm 3-2.4:1.0: ttyACM0: USB ACM deviceīased on my experience and of others recommending the above commands, Synology said I should create a task on task manager to run on boot with these commands: /sbin/modprobe usbserialĪnd the best part is that they said, and I quote them: cdc_acm 3-2.4:1.0: This device cannot do calls on its own. The system log messages when recognizing the stick are now different, no more errors logged as before, and so far the stick has been running flawless, notice the specific cdc-acm messages: usb 3-2.4: new full-speed USB device number 6 using etxhci_hcd-170202
#Aeon labs z stick plus install
I had read here in this forum that some people couldn’t even see the stick on VMM and they needed to run these commands to install 3 packages upon system boot: modprobe usbserialĪlthough I could see it, and Synology said I shouln’t need them if I was to run the stick on VMM, I decided to give it a try and include them on my host system startup (DS916+). USBSerial and ftdi-sio are unnecessary for Z-Stick Gen5 connection.” “ The primary module that you need is the cdc-acm.ko from kernet. I also contacted AEOTEC support to make sure I was not asking for something from Synology I shouldn’t or needed to.įrom Synology they first gave me the reasoning behind the step back on device support, that I won’t go into details here, mainly to do with security and OEM support for all those devices.įrom AEOTEC they confirmed that the only thing we need on Linux based operating systems is the package cdc-acm.ko and nothing else: I was precisely to come here this weekend and share some good news, or so it seems to be the case.ĭuring the last 2 weeks I’ve been exchanging messages with Synology Support, and managed to get up to the Product Management team. (/usr/src/node_modules/zwave-js/src/lib/commandclass/MultilevelSwitchCC.ts:323:33)Īt tValue (/usr/src/node_modules/zwave-js/src/lib/node/Node.ts:798:14)
#Aeon labs z stick plus driver
Z-Wave error ZWaveError: The driver is not ready or has been destroyedĪt Driver.ensureReady (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1518:10)Īt ndMessage (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:2581:8)Īt ndCommand (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:2787:28)Īt ndSupervisedCommand (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:2848:27)Īt ySendCommandSupervised (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:2880:16)Īt t (/usr/src/node_modules/zwave-js/src/lib/commandclass/MultilevelSwitchCC.ts:173:47)Īt Proxy.MultilevelSwitchCCAPI.
![aeon labs z-stick plus aeon labs z-stick plus](https://cdn.shopify.com/s/files/1/0062/7287/6655/collections/eonsmoke_1200x1200.jpg)
#Aeon labs z stick plus serial
I might have a defective stick, but that is so unlikely I prefer to dwell into the software part.Īnd again… T17:12:14.240Z DRIVER Serial port errored: The serial port closed unexpectedly!Įrror in driver ZWaveError: The serial port closed unexpectedly!Īt SerialPort. I’ll restart the VM this time with USB 2.0 instead of 3.0, although this is silly, using 3.0 never was a problem till now, most certainly it won’t help.Īny help from Linux/Synology expert users would be very welcome on this. Is there any log hidden in the HASS operating system, Synology operating system, or VM internal logs that might help diagnose what is going on? I have searched the logs on DSM7 gui as well and can’t find anything, neither at the VMM log nor at the DSM log itself, so I’m baffled with this.ĭoes anyone here have a clue of what might be happening?
#Aeon labs z stick plus full
Is there any way via bash on the container or whatever method to get the full log and not just the tail of it as it appears on HASS gui? The only logs I have are on HASS side on Z-Wave add-on that stated something like “Error in driver ZWaveError: The serial port closed unexpectedly.”.īy the way, side question: the log is far too long now with many events after the hour when it gave the error and I can’t rollback to that specific message. This is what I see when I open the edit window on the running VM:Īnd this is what was supposed to be there (it was there when the VM started):
![aeon labs z-stick plus aeon labs z-stick plus](https://cdn1.planete-domotique.com/media/catalog/product/cache/1/image/9df78eab33525d08d6e5fb8d27136e95/a/e/aeo_zw100_2_1.jpg)
After running HASS on DSM7 for almost 2 months without any isssue whatsoever on the ZWave front, over the last 24h I’ve had 2 exactly identical incidents where my zwave stick suddenly disappears/dismounts from VMM.