New Feature Requests
Moderators: EyezOnRich, GrandWizard
-
- Posts: 2273
- Joined: Tue Nov 16, 2010 4:08 pm
New Feature Requests
With the recent addition of the Enivsalink IP100D to the list of Eyez-ON supported devices, we're looking for input on what users want in terms of features on the portal. Modifications to the actual IP100D firmware is less flexible but will also be considered.
Enjoy the new features!
Enjoy the new features!
Re: New Feature Requests
Although I understand that the firmware-related stuff is more difficult to address than the portal, here's a couple of things to consider:
1. It would be advantageous is the option was available to arm the system in Away mode instead of Stay mode, which is the default when arming by user code. You can get around this by sending a bypass code of "1" using the portal after the system is armed in Stay mode. Using the intranet (envisalink local network mode) this is not possible. Two things, consider adding the bypass capability to the envisalink network (local) page and/or present a "mock" keypad on the portal and the intranet version so that Away and Stay can be selected by the click of a button.
2. Neither the local network page nor the portal grabs the name of the user from the User Code page. The events page only displays the position that the user code is programmed into (ie., 2, 40, etc.). I would think this should work similar to the zones page, where the text for the zone is used (Garage Entry Door vs. zone 3).
3. Although this is a long-shot, it would be absolutely outstanding if you would somehow integrate the ability to be able to make programming changes using the DLS software into the portal. I don't know how this would be done, but you'd sure give the TL150/250 cards a run for the money.
Thanks for your consideration.
1. It would be advantageous is the option was available to arm the system in Away mode instead of Stay mode, which is the default when arming by user code. You can get around this by sending a bypass code of "1" using the portal after the system is armed in Stay mode. Using the intranet (envisalink local network mode) this is not possible. Two things, consider adding the bypass capability to the envisalink network (local) page and/or present a "mock" keypad on the portal and the intranet version so that Away and Stay can be selected by the click of a button.
2. Neither the local network page nor the portal grabs the name of the user from the User Code page. The events page only displays the position that the user code is programmed into (ie., 2, 40, etc.). I would think this should work similar to the zones page, where the text for the zone is used (Garage Entry Door vs. zone 3).
3. Although this is a long-shot, it would be absolutely outstanding if you would somehow integrate the ability to be able to make programming changes using the DLS software into the portal. I don't know how this would be done, but you'd sure give the TL150/250 cards a run for the money.
Thanks for your consideration.
-
- Posts: 2273
- Joined: Tue Nov 16, 2010 4:08 pm
Re: New Feature Requests
Thanks Hwkdrv
In response
1. Yes, we know this is a problem and it revolves around how the panel does arming. The IP100D acts as a virtual keypad so it is just like if you were in your home arming the system. If you arm the system with a code and do not trip an exit zone, it will assume you are home and it will arm in ARM STAY. There are ways around this, just not very slick.
2. The local page will never reference the user/zone labels due to memory constraints. It will require a hardware change to do something like that. But... it should all be working on the Portal side. Could you describe where you aren't seeing user labels?
3. It can't happen with the IP100D due to hardware issues and how DLS works. There is a new version of IP100 that will support DLS but its not even beta yet. I don't even have one
The plan is to first support local DLS (you need to be on the same LAN) and then open it up to anywhere DLS (which is a requirement for pro installs).
In response
1. Yes, we know this is a problem and it revolves around how the panel does arming. The IP100D acts as a virtual keypad so it is just like if you were in your home arming the system. If you arm the system with a code and do not trip an exit zone, it will assume you are home and it will arm in ARM STAY. There are ways around this, just not very slick.
2. The local page will never reference the user/zone labels due to memory constraints. It will require a hardware change to do something like that. But... it should all be working on the Portal side. Could you describe where you aren't seeing user labels?
3. It can't happen with the IP100D due to hardware issues and how DLS works. There is a new version of IP100 that will support DLS but its not even beta yet. I don't even have one
![Smile :-)](./images/smilies/icon_e_smile.gif)
Re: New Feature Requests
Actually, I'm not seeing user names on the portal side or the local network side. Instead, I'm seeing the position the user code is entered into, ie., "...User Code 2" or "...User Code 40". I do see the zone label being displayed, just not the user name that I have entered for a user code. It's not that big of a deal for me, but I thought you might want to know.
Basically, what I'm saying is that I have (in the portal side) a code of (for example) 1234 and a user name entered. What I see in the summary of events list is the position the code 1234 is entered in the system itself, whether is be position 1, 2 or 40 (master). Let me know if you need other details.
Basically, what I'm saying is that I have (in the portal side) a code of (for example) 1234 and a user name entered. What I see in the summary of events list is the position the code 1234 is entered in the system itself, whether is be position 1, 2 or 40 (master). Let me know if you need other details.
-
- Posts: 2273
- Joined: Tue Nov 16, 2010 4:08 pm
Re: New Feature Requests
Ah, I see what you're doing wrong. When you enter a User Label, the user number is the actual user number (1-99 - depends on your panel), not the password PIN. So for user 40 (master user), you would enter 40, not the password.
Maybe that's not clear on the website, I'll log a note for the Portal folks.
Maybe that's not clear on the website, I'll log a note for the Portal folks.
Re: New Feature Requests
Oh. I see. Didn't think of that. Thanks.
Re: New Feature Requests
A new feature request for both the Eye-Zon portal and the Envisalink (local) webpage...
Every night I set the home alarm system using the (*9 + usercode)= "No-Entry Delay Arm", this turns all zones to instant and disables motion detector.
This (*9 + usercode)= "No-Entry Delay Arm" currently doesn't work very cleanly on the portal and not even an option to do it on the local webpage (preferred). The Portal work around right now is to input in the PIN field (*9 + usercode)... But the PIN field has a bunch of preinstalled "...." dots in the box; that must be deleted prior to use. This may be a Droid-X Android smartphone Web Browser save form data issue? This doesn't happen on a desktop IE8. The main Eye-Zon webpage Account Login has these fields populated with dots that must be deleted.
SUGGESTION
Preferred Option: Add a quick link like the portal buttons "ARM AWAY", "ARM STAY". to add " *9 No-Entry Delay Arm" with no code entry.
Appreciate your time and great system...
Every night I set the home alarm system using the (*9 + usercode)= "No-Entry Delay Arm", this turns all zones to instant and disables motion detector.
This (*9 + usercode)= "No-Entry Delay Arm" currently doesn't work very cleanly on the portal and not even an option to do it on the local webpage (preferred). The Portal work around right now is to input in the PIN field (*9 + usercode)... But the PIN field has a bunch of preinstalled "...." dots in the box; that must be deleted prior to use. This may be a Droid-X Android smartphone Web Browser save form data issue? This doesn't happen on a desktop IE8. The main Eye-Zon webpage Account Login has these fields populated with dots that must be deleted.
SUGGESTION
Preferred Option: Add a quick link like the portal buttons "ARM AWAY", "ARM STAY". to add " *9 No-Entry Delay Arm" with no code entry.
Appreciate your time and great system...
-
- Posts: 2273
- Joined: Tue Nov 16, 2010 4:08 pm
Re: New Feature Requests
Mighty wrote:A new feature request for both the Eye-Zon portal and the Envisalink (local) webpage...
Every night I set the home alarm system using the (*9 + usercode)= "No-Entry Delay Arm", this turns all zones to instant and disables motion detector.
This (*9 + usercode)= "No-Entry Delay Arm" currently doesn't work very cleanly on the portal and not even an option to do it on the local webpage (preferred). The Portal work around right now is to input in the PIN field (*9 + usercode)... But the PIN field has a bunch of preinstalled "...." dots in the box; that must be deleted prior to use. This may be a Droid-X Android smartphone Web Browser save form data issue? This doesn't happen on a desktop IE8. The main Eye-Zon webpage Account Login has these fields populated with dots that must be deleted.
SUGGESTION
Preferred Option: Add a quick link like the portal buttons "ARM AWAY", "ARM STAY". to add " *9 No-Entry Delay Arm" with no code entry.
Appreciate your time and great system...
As its been mentioned before, we have no way of updating the local firmware on the IP100D so we cannot make changes to the local webpages (right now). But on the portal, we can add this feature as it has come up before.
Re: New Feature Requests
Sounds like I'm not the only one interested in having this feature added.
Appreciate on your next revisions to the portal that you add the (*9 + usercode)= "No-Entry Delay Arm" mode.
Thanks Again for your time and great service.
Appreciate on your next revisions to the portal that you add the (*9 + usercode)= "No-Entry Delay Arm" mode.
Thanks Again for your time and great service.
-
- Posts: 134
- Joined: Wed Nov 17, 2010 11:53 am
Re: New Feature Requests
Done! It is also available on the mobile portal.