EVL4(MAX) Pre-Purchase Questions
Posted: Fri Mar 28, 2025 1:42 pm
Hi, new forum member here. Private DIY'er. In the past I set up & ran an Ademco Vista BPT128 panel using Alarmdecoder hardware interface + OpenHAB for semi-"smart" features, LAN-enabled reporting, etc., so I have a good familiarity with the ins and outs of DIY'ing.
I have reviewed the most recent ~20 pages of the forums here to glean a basic understanding of the EVL4 & related issues, features, etc. I still don't understand certain things:
1) Eyezon remote/cloud monitoring vs. local TPI LAN and/or HTTP interface: Is it possible to have full activation & use of both of these features at the same time, or does it have to be one or the other? I want my local OpenHAB or HomeAssistant server to be able to interact fully with the EVL4 while also subscribing to Eyezon remote/cloud monitoring.
2) Long-term fall back to permanent stand-alone operation? In the event I don't want to associate my EVL4 with Eyezon or any other remote monitoring service, does my EVL4 have to be manually "released" or "unlocked" by Eyezon before I have full control over it again? Or do I always have full administrative control over the device at all times? (Assume that I've covered the polling by creating a local LAN server to reset the polling timer via TPI interface to prevent the EVL4 from rebooting.)
3) Comprehensive written documentation of all of the EVL4MAx'es current feature set in one document?
I have gathered these bits and pieces by sifting through hundreds of forum posts but still have no confidence that I understand the full scope of the EVL4.
• There's some kind of private Eyezon-only API which Eyezon uses to manage the device remotely.
• There's a local LAN http/web control panel of some kind, accessible to the end user for configuring various settings.
• There is a rudimentary but ?? undocumented http:// or https:// interface exposed to the local LAN which can be used to harvest certain status info?
• There's a local-lan SYSLOG capability.
• There's a local-lan TCP-socket (TPI) interface but it is only for use by programmers, not usable interactively via telnet. --> Where is the list of 3rd party developer libraries or packages that are tailored to allow higher-level access to the features offered through the TPI?
• ?? Am I missing anything else?
4) The EVL4"Max" is "identical" to the EVL4, except it isn't, it actually has much more available memory, potentially allowing it to be carried forward with ongoing feature expansions and enhancements that the EVL4 and earlier cannot due to memory restrictions? How can I ensure that I am getting an EVL4Max board vs. an EVL4 if I am ordering from Amazon or eBay etc?
I have reviewed the most recent ~20 pages of the forums here to glean a basic understanding of the EVL4 & related issues, features, etc. I still don't understand certain things:
1) Eyezon remote/cloud monitoring vs. local TPI LAN and/or HTTP interface: Is it possible to have full activation & use of both of these features at the same time, or does it have to be one or the other? I want my local OpenHAB or HomeAssistant server to be able to interact fully with the EVL4 while also subscribing to Eyezon remote/cloud monitoring.
2) Long-term fall back to permanent stand-alone operation? In the event I don't want to associate my EVL4 with Eyezon or any other remote monitoring service, does my EVL4 have to be manually "released" or "unlocked" by Eyezon before I have full control over it again? Or do I always have full administrative control over the device at all times? (Assume that I've covered the polling by creating a local LAN server to reset the polling timer via TPI interface to prevent the EVL4 from rebooting.)
3) Comprehensive written documentation of all of the EVL4MAx'es current feature set in one document?
I have gathered these bits and pieces by sifting through hundreds of forum posts but still have no confidence that I understand the full scope of the EVL4.
• There's some kind of private Eyezon-only API which Eyezon uses to manage the device remotely.
• There's a local LAN http/web control panel of some kind, accessible to the end user for configuring various settings.
• There is a rudimentary but ?? undocumented http:// or https:// interface exposed to the local LAN which can be used to harvest certain status info?
• There's a local-lan SYSLOG capability.
• There's a local-lan TCP-socket (TPI) interface but it is only for use by programmers, not usable interactively via telnet. --> Where is the list of 3rd party developer libraries or packages that are tailored to allow higher-level access to the features offered through the TPI?
• ?? Am I missing anything else?
4) The EVL4"Max" is "identical" to the EVL4, except it isn't, it actually has much more available memory, potentially allowing it to be carried forward with ongoing feature expansions and enhancements that the EVL4 and earlier cannot due to memory restrictions? How can I ensure that I am getting an EVL4Max board vs. an EVL4 if I am ordering from Amazon or eBay etc?