So I have figured out you can't "start" the HSProxyService if you have connected already via command prompt using "node proxy.js <ip address> <port>" and vice versa, if the service is "started", you get the error in your original post when trying to connect via command prompt.
It seems it can only be "open" in one instance, either command prompt or "started" through the computer management console.
Announcement
Collapse
No announcement yet.
can't figure out the install...
Collapse
X
-
It sounds like you are going through my steps. I had the exact thing as well. I ended up deleting everything from the HSMetro folder and starting over. This time before creating the service, I updated the require.config.js file first with the IP addresses and port. Then started adding the node, nssm, etc.
But I am still working out some kinks myself.
Leave a comment:
-
-
Correct. You don't need to specify port 11000 when running the proxy since it defaults to that automatically. The port # you specify is the one you will be broadcasting on and the one that HSMetro will be listening on.
Leave a comment:
-
Actually looking at your ports, maybe you have 11000 in wrong place unless you have modified the ASCII port within homeseer. The port under the ASCII should be 11000 and the service should be something else, 6512 default, 8000 for me.
Leave a comment:
-
-
I had this same issue and I believe I restarted Homeseer to get it to work.
Leave a comment:
-
can't figure out the install...
I've been at it for over an hour now...ready to throw in the towel.
got the service up and running but can't get anything to work.
Attached a couple of screenshots below. One of the error when testing the service and one of my registry. Please let me know if I can provide anything else.
Thanks.Tags: None
Leave a comment: