I've very disappointed that HomeSeer is dropping SSL support. I don't want to use myHS. I want a direct, secure connection to my HS machine and don't want to rely on a 3rd party service let alone give said 3rd party access to my HS machine. Bad choice IMHO. Very frustrating to hear. I understand the usefulness of myHS for those who don't want to hassle with port forwarding and dynamic IPs and such, but I think most of us who are into home automation want that level of control and don't want to sacrifice on that for the sake of simplicity. That's one reason I won't use IFTTT right now as it requires 2 3rd party services and requires allowing unauthenticated LAN access to HS3.
That said, your solution sounds interesting. I really wish I didn't have to run another server to get a proper, direct SSL connection. Are you running Apache on Win 8.1? I'm somewhat familiar with Apache but not so much on Windows machines, let alone getting HS to run through a 3rd party server. Can you describe in more detail how you accomplished this or post links to some threads that explain this? If you post your own step-by-step it would probably deserve its own thread.
Thank for caring about this issue!
That said, your solution sounds interesting. I really wish I didn't have to run another server to get a proper, direct SSL connection. Are you running Apache on Win 8.1? I'm somewhat familiar with Apache but not so much on Windows machines, let alone getting HS to run through a 3rd party server. Can you describe in more detail how you accomplished this or post links to some threads that explain this? If you post your own step-by-step it would probably deserve its own thread.
Thank for caring about this issue!
Comment