This section provides solutions for some commonly encountered issues.

Windows Azure Dependencies

For remote storage of logs and configuration data, HomeOS uses Microsoft Sync Framework Azure technology to write this data to the cloud. Therefore it's important that you have the Microsoft Sync Framework 2.1 Redistributable Packages (x86) installed. Otherwise you may encounter exceptions complaining about lack of StorageClient object or not finding Sync components.

Windows Azure SDK - You will need the binaries from any of these versions of the SDK: 2.12.2, 2.3 (Note: if you only have 2.4 and up, you will not be able to build). To get the version 2.3 of the SDK for Visual Studio 2013 | for Visual Studio 2012  

WebFaultException Thrown During Debugging

When you try to run Dashboard in Debug mode you may see the following exception:

WebFaultException

This exception is expected when running under the debugger. Throwing this exception is part of the authentication logic. It's fine to hit continue. If you don’t want to see this exception repeatedly just uncheck the Break when this exception type is user-unhandled checkbox.

Z-Wave Device Won't Pair

When attempting to add a Z-Wave device, the process times out or the error "Device not found" is displayed. Sometimes when a device is removed from the platform it can still remain registered on the system. Try these things to remove the Z-Wave device so that you can add it again.

**Run removezwavenode **

  1. With the platform running, in the dashboard console enter the removezwavenode command.
  2. Immediately press and hold the Program button on the Z-Wave device.
  3. Confirmation will be displayed in the console.

Perform a hard reset

  1. Stop the platform.
  2. Navigate to Hub\output\binaries\Pipeline\AddIns\HomeOS.Hub.Drivers.ZwaveZensy s_4_55.
  3. Run ZWaveController.exe.
  4. Under Node, click the icon with the red "x", then click the Program button on the device to unpair.

Z-Wave PC Controller

Remove and reconnect the Z-Wave controller

  • If a Z-Wave device is not being recognized, unplug the Z-Wave controller (dongle) and plug it back in.

Why isn't my driver running?

There are a few potential causes for driver issues. First, ensure that the scout for the driver is running. Each device driver (with the exception of the provided Z-Wave driver) requires its scout to be running so that HomeOS platform can discover a new device. For more information, see HomeOS Software Architecture.

  • For your own driver(s), check that the scout component is running. Verify that Hub\output\binaries\Scouts\HomeOS.Hub.Scouts.YourScoutName exists
  • Make sure that Scouts.xml (\Hub\output\Configs\Config) has an entry of the scout you want to run. For example, by default we ship with this entry in the Scouts.xml, so the web cam scout is always running:

    <Scout Name="HomeOS.Hub.Scouts.WebCam" DllName="HomeOS.Hub.Scouts.WebCam.dll"/>

The Platform is in a Weird State

If the platform becomes non-responsive or exhibits other unwanted behavior, take these steps to reset the platform:

  • Clear your browser cache.
  • Reset the platform by running the reset command.
  • Delete the output directory and then rebuild the solution.

View the log files

By default in startplatform.bat, the platform is started without the -l switch:

binaries\Platform\HomeOS.Hub.Platform.exe -c %configDir%  

This means that the log file will go to the default location: \Hub\output\Data\Platform\homeos.log You can change it by changing the LogFile entry in settings.xml. You need to restart the platform for the change to take effect.

Known Issues Related to Cloud Data Storage

Invalid HomeID causing invalid Container name

Unhandled Exception: Microsoft.WindowsAzure.StorageClient.StorageClientException: One of the request inputs is out of index.. System.Net.WebException: The remote server returned an error: (400) Bad Request.

You may see the above exception when a blob container name violates the following naming rules:

  • Blob container names must start with a letter or number, and can contain only letters, numbers, and the dash (-) character.
  • Every dash (-) character must be immediately preceded and followed by a letter or number
  • All letters in a container name must be lowercase.
  • Blob container names must be from 3 to 63 characters long.

If your HomeID (in settings.xml) has character(s) that might break the rules above the exception will be thrown.

Build errors related to SmartCam app and WebCamLib binaries 

It should only affects VS2013. When you load the solution for the first time, Visual Studio 2013 will prompt you upgrade the VC++ compiler in order to work with some dependencies required for the SmartCam and the WebCamLib projects.

 VC++ compiler update prompt for VS2013

 You need to check both and press OK.

If you don't update, you may see the following message 

Error1error MSB8020: The build tools for Visual Studio 2012 (Platform Toolset = 'v110') cannot be found. To build using the v110 build tools, please install Visual Studio 2012 build tools.  Alternatively, you may upgrade to the current Visual Studio tools by selecting the Project menu or right-click the solution, and then selecting "Upgrade Solution...".C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.Cpp.Platform.targets645WebCamLib...

If you dismiss the dialog by mistake, you can manually update these two projects in Visual Studio:

In the Solution Explorer: Highlight, right click and select Upgrade VC++ Compiler and Binaries for these two projects

\Hub\Apps\SmartCam\SmartRecorder

\Hub\Common\WebCam\WebCamLib

 

Last edited Sep 12, 2014 at 12:20 AM by dannyh206, version 5

Comments

No comments yet.