EyezOn Forum

I don't think he has gotten around to enabling that feature..

Right, I don't have it yet but it's in the pipeline. Do you mind if I ask if you have thoughts on how you'd like to see this supported? I'm considering a long press on the partition to select it, and directing all keypad related functions to the current partition.

Mike

(sorry for the delay in responding & in getting to this function, I've been on the road the last few weeks)

I was finally able to get the UI configurable so that it fits most (all I hope!) of these situations with multiple zones. You should see a refresh in the next 24hrs from google market.

Next up will be configurable buttons and selectable partitions.

Any further feedback is much appreciated - the suggestions here have been really excellent. Thank you!

Mike

Wanted to mention that I've published a companion DscServer app to go along with this DscKeypad app. This server runs on a dedicated tablet or phone as a front end to the envisalink TPI interface. You configure the DscKeypad(s) to contact it instead of envisalink card directly.

I've just added to the DscServer a key capabiility - it provides encryption so that it's safe to use the DscKeypad outside of your encrypted and firewalled internal network. There are a few other functions provided, check out my website for details and to find the apps: http://sites.google.com/site/mppsuite/.

Remember, it's not safe to expose the envisalink API or on card webpage outside of your encrypted network! Use the EYEZ-ON cloud service if you don't use the DscKeypad/DscServer.

Mike

One suggestion which would be great - use some web scraping techniques (or maybe one of the guys from eyezon can make a simple machine readable page for this in some standard form like xml or csv), have the app hit the user's portal page where all their zone and partition definitions are already available for editing and sync up the app with them every so often or on demand.

If someone has half a dozen keypads going its much simpler to just make the changes on the portal page and then sync all the client apps to that.

The GrandWizard mentioned a web service interface to eyez-on (on the first page of this thread), I think it's discussed in another thread - if I can get the specs something like that might be easy to add.

Mike

I asked about that in the other thread but no answer yet - there are the zone names but not the partition names although the numbers are there, not sure if its a typo or they are actually missing.

I also asked about sending the partition in the api since its missing too for the api as published, and no answer on that yet either.

Still nothing on making the service meta data available to us yet.

No worries, I filled my time by adding support for multiple partitions and to allow the definition of custom programmable keys (ala the DSC Keypad) to my keypad app. It should be available in the usual place on google play for updates (or it'll be done automatically if you've configured that way).

Also added a feature to the server app to watch for alarm changes and let you tell it to get/put/post to a URL, launch another app on the phone, or change your thermostat for away/occuppied temps if you have a CT-30 and my CT-30 app.

Mike

I haven't seen anything on the metadata yet.

In the mean time I'm continuing to add function to what I already have - a non-android version of my server, it's ready now as version 0.5.0:
http://sites.google.com/site/mppsuite/d ... scserver-2.

The server will run on any system with java 1.5 or newer, and provides the ability to hook mutiple DscKeypad apps to it at once - so you can have more than one DscKeypad widget running and access it from more than one phone at the same time.

The server and unencrypted access from the DscKeypad is free, and includes custom zone and partition labelling. For version 1.0 there will be a (modestly priced) app to configure it to send emails and to allow encrypted DscKeypad remote access.

Logging is coming, and if there's enough interest I'll add a REST API for automation controllers and perhaps a web front end. And if there's support for "Installers Mode" enabled for the envisalink I'll try to add that too.

Mike

Old thread, but I just finished some updates to my android apps for envisalink in case they're of interest:

DscKeypad (free) used for local access to your envisalink - there were a few requests for bigger buttons and an easier way to see open zones. I added scrolling to the various views which allows the keys to be larger. Along with the ability to customize the layout it should be more convenient.

DscServer (paid) used as a proxy server for the envisalink for remote access, multiple devices (like home automation systems, etc). I've added some additional events and actions, but more importantly (for home automation) you can now send android intents to the DscServer and it will pass them on to the DSC system. You can customize the SMSs, eMail, or UDP messages sent that will allow them to trigger home automation systems as well.

I'm still trying to find a decent automation app for android to fully leverage my automation servers (suggestions welcome!); but even the basic functions are competitive with Rogers (Canadian) home automation for a lot less expense (as in a dedicated pay-as-you-go phone account and a low end android phone is all you need).

Mike