
#SOFTWARE DOWNLOAD ACTIVEHOME PRO CM15A INSTALL#
When the announcement was made that the cm15a had been added I built a test machine to install a fresh build on before I committed my main machine to the build.
#SOFTWARE DOWNLOAD ACTIVEHOME PRO CM15A SOFTWARE#
If the software is the problem that may not be enough. Tue Mar 9 21:58: ShutdownWill try to remove it and add again. Ġ5 03/09/10 9:01:55.604 Note: Device manager has attached a device of type 37 that this has no custom handler for. I installed the OS last evening and lmce before 8am this morning.Ĭode: = NEW LOG SECTION =ġ 03/09/10 09:01:48 41 (spawning-device) Starting.
I can remember taking most of the day and over night to install everything and that did not include the OS install. It is a lot faster to install lmce though. Now I only have one light added to the interface but there is no restarting of the interface and no locking up. Ok I installed lmce on another computer that I have and so far I am not seeing what you are. This would seem to happen each time the router would need to be reloaded due to additions. This would kill both the zwave and cm15a interfaces until I rebooted.

I also had a problem I found with hardware where the usb ports on the MB I was trying to use would quit working. I have had my cm15a running from beyond the beginning and other than a time in January when there seemed to be a major problem with the installation of the system I have had good results. How long has it been since you did a fresh install? If you have the hardware laying around you might want to build a system to see if the problem follows. Once the package was corrected the cm15a seemed to work fine. Then later the template downloaded and installed with the rest of the installation but the package was incorrect. I had to create a template and do an apt-get install pluto-cm15a to get it to work. When the cm15a was first added to the build there was no template for it(at least that was my case). Ġ5 03/08/10 12:47:55.288 Note: Device manager has attached a device of type 37 that this has no custom handler for.

Ġ5 03/08/10 12:37:28.672 Note: Device manager has attached a device of type 37 that this has no custom handler for.
