Premise What am I doing wrong?

[project_x]

I was looking for something to monitor my Honeywell IAQ remotely, and in my searching, I found Premise Home Control here.
Anyways, I 've read almost every thread here and in the Premise archive, + the help, and faqs,....

I've installed Premise on my server, setup the Thermostat in the builder. Services are running, builder reads t-stat communications, I made sure Automation Browser was checked. But I can't seem to access it from my Browser, either at localhost, or localhost:86, both come up as blank.
Do I have to "publish" something, or what? Any ideas? What have I missed?


Thanks,
Rob

 

[123]

Sounds like you've done everything correctly so we need to look outside of Premise.

First, let's confirm which port is being used by Premise's web server.

1. In Builder, click WebServer in the Shortcut Bar.
2. In the Explorer window, navigate to: WebServer > Sites > Default WebSite
3. In the Properties window, find the "CurrentPort" property. Its value represent the port number used by the web-server. Let's assume it is port 86.
4. Turn off Windows Firewall.
5. Using your browser, connect to http://localhost:86
6. If you establish a connection, the solution is to create an exception for port 86 in Windows Firewall.

If Windows firewall is not the culprit then we'll have to dig a little deeper.

 

[chucklyons]

You mentioned that you had set it up on 'your server'. If this is a box separate from your web browsing device, you'll need to use the ip address of the web server (http://xxx.xxx.x.x:86) to access it. 123's input also needs to be followed to make sure you have the Windows Firewall opened for port 86 for your web browsing device.

BTW, welcome to the cult!

 

[project_x]

You mentioned that you had set it up on 'your server'. If this is a box separate from your web browsing device, you'll need to use the ip address of the web server (http://xxx.xxx.x.x:86) to access it. 123's input also needs to be followed to make sure you have the Windows Firewall opened for port 86 for your web browsing device.

BTW, welcome to the cult!

This is in response to both Chuck and 123

No windows firewall
Went through the rest of 123s advise ( i think I had done all that before, but verified it.)
I am trying to view on my server pc (and i have tried from a client pc using the ip address of the server:86) and I the page cannot be displayed

Is there any way to ensure that the webserver is actually running? At what point does the builder update the files for the webserver?

 

[123]

Is there any way to ensure that the webserver is actually running?

To confirm the web server is operating:

1. Open Builder.
2. Click WebServer in the Shortcut Bar.
3. Click WebServer in the Explorer window.
4. Look in the Properties windows and find the "Status" property. It should be selected and indicate "Running".

In addition to the web server being active, the AutomationBrowser module must be loaded. This should have happened when you checked it during the Setup Wizard or via File > Addins. Click Modules in the Shortcut Bar and find AutomationBrowser in the Explorer window. It should be located just below the "Default" module. If it isn't, use File > AddIns > Modules > AutomationBrowser and give it a few seconds to load. When it appears in Modules, you're good to go.

If the web server is running and the AutomationBrowser is loaded, your browser should see something at http://localhost (or http://localhost:86). If all is well, your first connection to the web server will cause a message to appear asking for your permission to install an ActiveX object (SYSConnector).

Regarding "updating the files", there's no delay. All changes in the Home treeview (i.e. add or remove a thermostat or change its state) are instantly reflected in the browser.

 

[project_x]

Is there any way to ensure that the webserver is actually running?

To confirm the web server is operating:

1. Open Builder.
2. Click WebServer in the Shortcut Bar.
3. Click WebServer in the Explorer window.
4. Look in the Properties windows and find the "Status" property. It should be selected and indicate "Running".

In addition to the web server being active, the AutomationBrowser module must be loaded. This should have happened when you checked it during the Setup Wizard or via File > Addins. Click Modules in the Shortcut Bar and find AutomationBrowser in the Explorer window. It should be located just below the "Default" module. If it isn't, use File > AddIns > Modules > AutomationBrowser and give it a few seconds to load. When it appears in Modules, you're good to go.

If the web server is running and the AutomationBrowser is loaded, your browser should see something at http://localhost (or http://localhost:86). If all is well, your first connection to the web server will cause a message to appear asking for your permission to install an ActiveX object (SYSConnector).

Regarding "updating the files", there's no delay. All changes in the Home treeview (i.e. add or remove a thermostat or change its state) are instantly reflected in the browser.

I've got it! I was doing everything correctly, except my default browser Chrome. Once you mentioned the ActiveX object, I gave IE a try and up it came. That's the first issue I've had to date with Chrome.

Thanks for your help!

 

[123]

The browser must be capable of supporting ActiveX objects. Premise definitely works with IE and browsers based on IE's engine.

I'm glad to hear the problem is resolved. Welcome to the Premise community (a.k.a cult)!