inControl ZWave service stopping periodically

  • 255 Views
  • Last Post 29 August 2016
arichter5 posted this 28 August 2016

A few months ago, I moved my setup from a WinXP pc to a Win10 Intel ComputeStick pc.  In general, all is working fine.  Even the NEST plugign that stopped working on XP is working.  HOWEVER, periodically the service stops for no apparent reason.  The setup is at a remote location, so this was problematic.  My first workaround was to set the PC to reboot once a day.  That worked for the most part.  But it was not perfect.  So, my next workaround was to set up a batch file to run hourly to start the service,  If the service had stopped, this would get it going again.

The best solution would be to figure out why the service is stopping, but I don't know where to start.  Has anyone else had this problem and solved it?  If not, where should I begin the troubleshooting process?

Order By: Standard | Newest | Votes
cowinger posted this 28 August 2016

In the tools, options, misc for axial (incontrol) there is a selection you can tick called "Run as a Service". Select that box and if the computer reboots it will automatically start up axial so all of the scenes will run. If you access the computer from afar then you can double-click the Axial icon and it will load the GUI.

Hope that helps.

arichter5 posted this 28 August 2016

Thank you for the reply.  I already have it running as a service.  When ghe PC boots up, the service starts fine.  Then, at some seemingly random time later (hours/days), the service stops.  If I restart the service (or reboot the pc) it again works, until the next service stop.

cowinger posted this 29 August 2016

The only other thing I can think of is if there is more than one thing you might have that is being started at reboot they could be messing with each other. I had to do this for my laptop that I use as a server. I went into task manager and clicked on the Services tab. From there I scrolled down and I right clicked on "InControl ZWave Service" and selected "open services". Scroll down again and find the same "InControl ZWave Service" and right click. Select "Properties" and change startup type to "Automatic Delayed Start" and OK. Close out all windows. This will cause the InControl Service to be delayed by 2 minutes after all other Services have been loaded.

I wonder if the failure of the startup of InControl could be related to windows doing an update and re-booting the computer and maybe that is messing with the timing of the startup of the InControl Service. Putting a delay may help or it may not.

It might be worth a try. Hope this helps.

rscott posted this 29 August 2016

Could you check your windows application event logs and see if there are any errors being logged in there? If it's a crash, they will be reported to that log list and it might give us an idea of what's going on.

Change Language
Categories
Search
Popular Tags
Hot Topics
Close