Hi,
Thanks. Apologies if I am using the wrong terminology or making incorrect assumptions. I'm trying to infer from your responses the actual answers to my questions, and I think we are making progress in that regard. Let me know if what I've written below is correct.
First, I am guessing that "Envisalerts" is a cloud-based platform, while the "TPI" is used to directly access the EVL4 on the LAN. If that is the case, then you are of course correct that the problem indeed cannot lie with Homeseer reaching out to a remote server, but exists in the socket connection between the Homeseer plugin and the EVL4 right on the LAN itself. That is very helpful to narrow the range of the problem. Thank you.
Second, socket communications obviously involve two-way communications, so either side could be "at fault". Whether or not the Homeseer plugin is properly formatting its communications to the EVL4, or whether the server on the EVL4 is not responding properly, is an issue that can only be resolved by the technical people on both sides talking to each other. I take it, from the tone of your prior post, that you have little interest in engaging in that discussion because you are convinced, perhaps with good reason, that the problem lies on the Homeseer side. I have no idea if you are right or wrong, by the way, only that you are disinterested in participating in finding the solution. If I have that wrong, please let me know; otherwise, I will work exclusively with the Homeseer folks to try to resolve the issue, as I have no other choice.
Third, I am inferring from your comment that I can simply cancel my Eyez-On account, that the EVL4 will continue top operate with Homeseer. The installation instructions that come with the EVL4 note prominently that one must set up an Eyez-On account before installing the EVL4, so I was concerned about cancelling it, but knowing that I can is very helpful. Thank you.
Fourth, I apologize for suggesting that something is wrong with anything regarding any of the Eyez-On products mentioned above.
I have no specific knowledge that any of the Eyez-On products have any problems whatsoever, and retract any accusation of product flaws that I made in prior posts.
Finally, in response to your request that I identify a single post on this issue there are, for the record, ten posts on this site discussing socket errors:
- by K-Man on Feb 02, 2017 at 3:03 pm
- by ptr454 on Feb 02, 2017 at 1:08 pm
- by vladb on Apr 06, 2016 at 2:40 am
- by dumbo25 on Jan 21, 2015 at 11:24 pm
- by mitalum on Sep 20, 2013 at 3:41 pm
- by K-Man on Thu Sep 05, 2013 at 1:55 pm
- by Z06jerry on Fri Aug 23, 2013 at 10:55 am
- by mitalum on Wed Jul 31, 2013 at 8:00 pm
- by mitalum on Tue Jul 30, 2013 at 8:29 pm
- by hypnosis4u2nv on Thu Sep 13, 2012 at 9:56 am
On the Homeseer site there is a post by the Envisalink plugin author that states "
This problem has been reported by other users, it looks like the envisalink board is stuck for some time before it can successfully communicate again. I reported the problem to Envisacor but I don't think they have ever figured it out." A search for "socket error" and "envisalink" on the Homeseer site returns more than 500 posts, though I'm sure not all of them relate to this error.
I suppose my point is that it was not ridiculous for me to inquire about a problem that I am experiencing nor to note that others seem to have experienced similar issues. I probably should not have opined on who was at fault, and for that I'm sorry. I realize supporting these types of products is often a labor of love and we all need to be grateful to the community for the efforts the experts put in to help us. You're obviously one of those experts, and your responses have been quite useful in helping me address this issue.
Thanks.