Announcement

Collapse

Contacting HomeSeer This Week

HomeSeer is open and operational this week. All orders are being processed and shipped as usual. However, some staff are working from home. If you need to contact HomeSeer for support or customer service, please use our Email or Chat options. https://homeseer.com/contact-us/
See more
See less

(resolved) V1.5 Won't connect

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

  • (resolved) V1.5 Won't connect

    Hi Emotion,
    I had a previous version running, but I turned it off until I could spend the time configuring it. I upgraded to 1.5 and now it won't connect to my HS server. The users previously setup are gone. I have them both running on the same machine.
    HS version is 2.5.0.23
    I tried the "Remove plug-in" install option and re-installed it.
    What else can i try?

    Thanks
    Last edited by Emotion; July 10th, 2011, 12:30 PM. Reason: Resolved

  • #2
    Hi Chasem,

    Sorry for the late reply - I was not notified of your post for some reason - must check those settings!

    Versions prior to v1.5 store the user settings in a file called user.config in a location similar to C:\Users\Administrator\AppData\Local\Lailey_Limited\Emotion. exe_Url_wow0acu5c2yanyiovddzx3yvuy2juyjo\1.5.0.0

    If you copy your user.config from an old version (identified by directory name) to the latest 1.5.0.0 folder, you can restore your user settings that you have lost.

    Make absolutely sure the plugin is Enabled in HomeSeer. I know this sounds daft, but sometimes this setting gets toggled when Emotion is reinstalled and is easy to miss.

    Make absolutely sure you've got the full .Net Framework 4 installed (not the slimmed-down Client Profile version)

    Um, try removing HomeSeer username and password to see if that's an issue perhaps?

    Comment


    • #3
      Connected

      Thanks,
      Repair on dot net 4 install just in case and copied config from 1.2 folder to 1.5 folder seems to working now.

      Comment


      • #4
        Hi i am writing for help on getting emotion to connect to homeseer, I have both emotion and homeseer installed on the same machine. my current version of homeseer is 2.5.0.44. I have emotion configured to connect via localhost, with the web user name in homeseer "Emotion" and without a password.
        At the bottom of the emotion GUI for the connection status it says "Confirming connection to localhost", could this have any relation to my problem?
        Any help will be great - thanks
        Last edited by laurieg; December 21st, 2011, 11:56 AM.

        Comment


        • #5
          Hi Laurieg,

          Do you see any info in the HomeSeer logs, such as any connection attempts by remote client? If you do then this suggests Emotion is getting as far as HomeSeer and the message may lead you nearer to resolving the problem. If you get no entries in the HomeSeer log around the time Emotion is trying to connect then it's something else - you could try 127.0.0.1 or the IP address of your machine instead of localhost (but localhost should work).

          Normally, by default, HomeSeer doesn't expect usernames or passwords on the local subnet - you could try temporarily disabling this in HomeSeer - you'll know you've got this right as you won't have to login to the HomeSeer web interface. Emotion username and password should be set to the HomeSeer defaults of default and default. (HomeSeer web/setup/web users)

          Please let us know how you get on...

          Comment


          • #6
            Hi Emotion,

            Thanks for your responce. I have managed to amend the problem. It was interferance with a network bridge that was used by VirtualBox (Oracel Virtulization Platform), Once this bridge was removed Emotions functionality was restored. Could you suggest a method that would allows me to keep the functionality of Emotion as well as keeping the bridge installed?

            many thanks!

            Comment


            • #7
              Hi laurieg,

              This should be possible as it sounds similar to the virtual adapters that get created in VMware workstation.

              If HomeSeer and Emotion are installed on the same virtual machine, then you will need to supply the local virtual IP address of that VM's virtual adapter for the hostname in Emotion.

              If HomeSeer is installed on a separate VM to Emotion, then you'll obviously need to supply that IP address, but you will also need to at least install the HomeSeer speaker client on the Emotion VM as it requires the HomeSeer DLL's to function.

              In either case, you must ensure the network bridge is not blocking the remoting port (I think tcp 8737?)

              Comment

              Working...
              X