Thanks again for the replies. FWIW, I was looking for an excuse to install and try VirtualBox, and phenigma's suggestion finally got me over the line. Indications so far is that it works without a problem under VirtualBox, so if anyone's considering running / trialling it on virtual hardware, perhaps go for VirtualBox over VMware.
- Welcome to LinuxMCE Forums.
News:
Rule #1 - Be Patient - Rule #2 - Don't ask when, if you don't contribute - Rule #3 - You have coding skills - LinuxMCE's small brother is available: http://www.agocontrol.com
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages1
#1
Users / Re: Problems With Aeon Labs Z-Stick on VMware, Fails Most Times [Solved]
March 02, 2013, 11:42:13 PM #2
Users / Re: Problems With Aeon Labs Z-Stick, Fails Most Times
February 27, 2013, 12:33:44 PM
Thanks for the feedback. The plan is to run the 'production' version on dedicated hardware anyway, so for the moment I won't get too worried about it. Indeed with a bit of unplugging and re-plugging of the stick, bumping the virtual USB controller back to USB 1 and fiddling around along similar lines, it seems possible to get it to come alive okay, and once started correctly it works fine.
I'll report back if there's any continuing problems once it's running on hardware..!
I'll report back if there's any continuing problems once it's running on hardware..!
#3
Users / Problems With Aeon Labs Z-Stick on VMware, Fails Most Times [Solved]
February 24, 2013, 11:44:10 AM
Hi,
Firstly, thanks to the developers for the huge amount of work that has obviously been put into this project. The more you start to scratch the surface the more you can appreciate just how much has been done.
Unfortunately though, I've got a problem I'm struggling with and need to ask for help. My situation is that I'm currently setting up a very small Z-Wave network (one Z-Stick, and one light dimmer) as a proof of concept before I go nuts and automate the whole house - I'm not prepared to take the plunge without knowing whatever technology I use will be rock-solid, and I'm afraid I'm not there yet. The issue I have is that most times I start the LMCE core, the Z-Stick fails to initialise, and it simply doesn't work. It seems quite random though, and on rare occasions it will start correctly and work perfectly, same hardware, same software (more often than not it fails though). I'm running a 10.04 snapshot on a VMware virtual machine, and this is a sample of the log output:
== ATTEMPT FRESH START ==
1 02/24/13 20:01:16 /usr/pluto/bin/Spawn_Device.sh 53 (spawning-device) 11606 Dev: 53; Already Running list: 15,16,18,19,29,30,
== FRESH START ==
1 02/24/13 20:01:16 /usr/pluto/bin/Spawn_Device.sh 53 (spawning-device) device: 53 ip: localhost cmd_line: ZWave
0 02/24/13 20:01:16 53 (spawning-device) Entering 53
========== NEW LOG SECTION ==========
1 02/24/13 20:01:16 53 (spawning-device) Starting... 1
1 02/24/13 20:01:16 53 (spawning-device) Found /usr/pluto/bin/ZWave
01 02/24/13 20:01:16.635 TranslateSerialUSB pci0000:00/0000:00:11.0/0000:02:00.0+2.1 result /dev/ttyUSB0 <0xb773d6d0>
Return code: 255
3 02/24/13 20:01:18 53 (spawning-device) Device died... count=1/50 dev=53
Sun Feb 24 20:01:18 EST 2013 died
========== NEW LOG SECTION ==========
1 02/24/13 20:01:29 53 (spawning-device) Starting... 2
1 02/24/13 20:01:29 53 (spawning-device) Found /usr/pluto/bin/ZWave
01 02/24/13 20:01:29.289 TranslateSerialUSB pci0000:00/0000:00:11.0/0000:02:00.0+2.1 result /dev/ttyUSB0 <0xb77926d0>
Return code: 255
3 02/24/13 20:01:30 53 (spawning-device) Device died... count=2/50 dev=53
Sun Feb 24 20:01:30 EST 2013 died
...and it just keeps repeating until it hits 50 attempts and gives up.
Any suggestions would be appreciated!
Firstly, thanks to the developers for the huge amount of work that has obviously been put into this project. The more you start to scratch the surface the more you can appreciate just how much has been done.
Unfortunately though, I've got a problem I'm struggling with and need to ask for help. My situation is that I'm currently setting up a very small Z-Wave network (one Z-Stick, and one light dimmer) as a proof of concept before I go nuts and automate the whole house - I'm not prepared to take the plunge without knowing whatever technology I use will be rock-solid, and I'm afraid I'm not there yet. The issue I have is that most times I start the LMCE core, the Z-Stick fails to initialise, and it simply doesn't work. It seems quite random though, and on rare occasions it will start correctly and work perfectly, same hardware, same software (more often than not it fails though). I'm running a 10.04 snapshot on a VMware virtual machine, and this is a sample of the log output:
== ATTEMPT FRESH START ==
1 02/24/13 20:01:16 /usr/pluto/bin/Spawn_Device.sh 53 (spawning-device) 11606 Dev: 53; Already Running list: 15,16,18,19,29,30,
== FRESH START ==
1 02/24/13 20:01:16 /usr/pluto/bin/Spawn_Device.sh 53 (spawning-device) device: 53 ip: localhost cmd_line: ZWave
0 02/24/13 20:01:16 53 (spawning-device) Entering 53
========== NEW LOG SECTION ==========
1 02/24/13 20:01:16 53 (spawning-device) Starting... 1
1 02/24/13 20:01:16 53 (spawning-device) Found /usr/pluto/bin/ZWave
01 02/24/13 20:01:16.635 TranslateSerialUSB pci0000:00/0000:00:11.0/0000:02:00.0+2.1 result /dev/ttyUSB0 <0xb773d6d0>
Return code: 255
3 02/24/13 20:01:18 53 (spawning-device) Device died... count=1/50 dev=53
Sun Feb 24 20:01:18 EST 2013 died
========== NEW LOG SECTION ==========
1 02/24/13 20:01:29 53 (spawning-device) Starting... 2
1 02/24/13 20:01:29 53 (spawning-device) Found /usr/pluto/bin/ZWave
01 02/24/13 20:01:29.289 TranslateSerialUSB pci0000:00/0000:00:11.0/0000:02:00.0+2.1 result /dev/ttyUSB0 <0xb77926d0>
Return code: 255
3 02/24/13 20:01:30 53 (spawning-device) Device died... count=2/50 dev=53
Sun Feb 24 20:01:30 EST 2013 died
...and it just keeps repeating until it hits 50 attempts and gives up.
Any suggestions would be appreciated!
Pages1