Announcement

Collapse
No announcement yet.

Homeseer Pro100 SII - Sound Driver Needed

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Homeseer Pro100 SII - Sound Driver Needed

    I have a Homeseer Pro100 SII (specs below) that I loaded using a Dongle with HomeTroller (that I am quite sure I purchased from Homeseer).

    I am not getting the sound to work except through my Way2Call and I can add a usb Sound card (which makes the way2call speak very slooooooow).

    What is the sound driver I need for my Pro100 Series II. Any help is appreciated.

    Thank you,
    Chris.

    #2
    Pro100 Specs

    Meant to post the specs:

    System Information
    Current Date/Time: 5/1/2016 4:24:32 PM Eastern Daylight Time
    HomeSeer Version: HS3 Pro Edition 3.0.0.280 (Windows)
    HomeSeer: Is Registered
    Operating System: Microsoft Windows XP Professional - Work Station
    OS Version: 5.1.2600 Service Pack: 3.0
    System Uptime: 6 Days 23 Hours 40 Minutes 27 Seconds
    User Name and Access Level: xxxxxx
    LAN IP Address: xxxxxx
    Client IP Address:
    External IP Address: xxxxxxx
    Network Adapter: Realtek RTL8139 Family PCI Fast Ethernet NIC #3 - xxxx
    Network Adapter: Adapter -> Realtek RTL8139 Family PCI Fast Ethernet NIC #2 - xxxxx
    Network Adapter: Loopback Address (localhost) IP: 127.0.0.1
    Web Server Address:Port: xxxxx
    Number of Devices: xx
    Number of Events: xx
    Event Last Ran: Automation : Sunrise, Ran at 5/1/2016 6:10:00 AM
    Number of unique event scripts used: 0

    Connected Speaker Clients: HOMETROLLER (127.0.0.1)EFAULT
    Plug-Ins Enabled: Z-Wave:,X10:,BLLAN:
    Processor Type and Speed: x86 Family 6 Model 13 Stepping 8 at 1.49 GHz
    Modules/Threads: 154 Modules, 74 Threads
    Available Threads: 100
    System Processes/Load: 33 Processes, 2% Load
    Free / Total Physical Memory: 537.14 MBytes / 0.97 GBytes (54% free)
    Free / Total Virtual Memory: 1.96 GBytes / 2.00 GBytes (98% free)
    HomeSeer Memory Used: 122 Mbytes
    Plug-In Memory Used: 3 EXE Plug-Ins using 74 Mbytes

    Comment


      #3
      Using the original stuff your sound should work.

      Shut down Homeseer.

      Go to control panel, system, hardware tab, device manager and sound, video and game controllers. Post a picture of what you see here.

      Here is an example of one Touchscreen running XP embedded on an Atom.

      Note here do not have a Way2Call controller plugged in to my Homeseer 3 client.

      You should also see a little speaker icon on the right hand bottom side.
      Attached Files
      - Pete

      Auto mator
      Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
      Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro
      HS4 Lite - Ubuntu 20.04 / VB W7e Jetway JBC420U591
      Fanless IntelĀ® Celeron N3160 SoC 8Gb
      HS4 Pro - V4.1.18.1 - Ubuntu 20.04/VB W7e 64 bit Intel Kaby Lake CPU - 32Gb
      HSTouch on Intel tabletop tablets

      X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Smartthings hub, Hubitat Hub, and Home Assistant

      Comment


        #4
        Thank you for the help.

        I do not see the speaker in the lower right. I use to see it before (on my old Pro100 Series I running HS2).

        As I said I currently have the Way2Call and a single USP Sound stick. I am not sure why 3 USB show up. I was thinking the Multiimedia Audio Controller might be what I was missing.

        Attached is the screenshot.
        Thank you,
        Chris
        Attached Files

        Comment


          #5
          Yup; looks like the motherboard video / audio drivers are not installed.

          Do you have a disk for them? Or do you have a MFG/model number of the motherboard?

          The way2call device has it's own sound stuff.

          Somewhere here a few weeks back I posted a link for the MFG of the motherboard.

          Looks like it could be the Celeron version versus the VIA version.

          Just a guess here. It could be these drivers from Lex.

          Lex

          Note that it isn't Homeseer 3 software that provides the base audio drivers. Rather it is the OS that provides the hardware drivers for the motherboard.

          While doing this also validate SAPI in the control panel such that Homeseer speaker works with Wintel SAPI. Do this after the base audio driver stuff.
          Last edited by Pete; May 4, 2016, 07:19 AM.
          - Pete

          Auto mator
          Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
          Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro
          HS4 Lite - Ubuntu 20.04 / VB W7e Jetway JBC420U591
          Fanless IntelĀ® Celeron N3160 SoC 8Gb
          HS4 Pro - V4.1.18.1 - Ubuntu 20.04/VB W7e 64 bit Intel Kaby Lake CPU - 32Gb
          HSTouch on Intel tabletop tablets

          X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Smartthings hub, Hubitat Hub, and Home Assistant

          Comment

          Working...
          X