Pull Request sent.
I didn’t get far enough to make sure everything was functional. The only thing I noticed not working was the top left image wasn’t loading.
Maybe I am dead in the water after all since I have the Honeywell Vista Panel. I will stay up on this thread in case something comes out and thank you all for your time and efforts.
@joe64 If I bought the panel linked below and replaced my Honeywell Vista would your setup work for me?
Should work - Just check with Envisalink and make sure that panel is compatible. Thats actually what I did in my house when I bought it. It had an Ademco panel in it and I ripped that out and put in a used DSC 1616
Yeah they will sell me just the board for 48 dollars. That or I was going to PM you and offer you money to do my Vista up but Im thinking the board will be cheaper than your time by a long shot.
The app I wrote works with the DSC version of the envisalink controller. So as long as that PC1832 works with the envisalink the app i wrote should be able to talk to it. Let us know how it works out!
I figured out what was going on with both brian and my issues. Live logging said this
java.lang.NullPointerException: Cannot get property ‘value’ on null object @ line 60
i ended up clearing out the if statement completely to check for the SHM variable and was able to authorize and install the app.
i just found this thread and love it. glad to see another version popping up.
have you guys seen this thread also?
i run alarmserver on a raspberry pi, and setup takes very little time. it already does almost all of the features listed. I do love the new web interface you have here though, and alarmserver is very old looking.
Has anyone been successful getting this to work with there Vista panel?
sort of… i’m able to arm/disarm which i wasn’t able to do before. The problem is now for some reason it’s not reporting open/close zones properly or the status if the panel. this was working before, but i was unable to arm/disarm. I just need to revisit just haven’t had time.
@fishercs which code are you using? Are you using the j64 app or the python?
Big Webstas stuff with python alarmserver.
All,
Sorry for the long delay in response. I ended up getting fed up with my server stability and dismantled it. I rebuilt it with unraid instead of Windows and it is now extremely stable. Unfortunately, that means I had to redo my setup with Alarm Server.
Joe,
Really appreciate your work here! Instead of using my instructions, I decided to try out your new app and it is way easier to setup. I will say I tried putting it on CentOS and hit a wall with mono not supporting version 5 of ASP. With that, nothing would compile. I’m wondering if I just didn’t setup ASP correctly. I’m unfortunately not familiar with ASP, I’m a Java/JVM programmer, so I’m probably just doing it wrong. Anyway, I reverted to using Windows for now, and I hit zero roadblocks with your instructions. I would really like to switch back to Linux due to the resource load (I put this in a VM) and licensing challenges with Windows, so if you have any pointers on compiling it with Linux, let me know.
A Few things…
- You might add a section to your documentation on how to get this running with Windows on boot. I know how to do it, but others may not.
- Will this sync with a manual arm at the keypad?
- The last sentence after everything is setup states “your alarm system will NOT start syncing…”. I assume you mean “now”, correct? I had to take a double take to make sure you weren’t trying to tell me something about your code.
- If I hit “stay alarm” in your app, it will do an away alarm with the SHM. I have SHM to turn on my motion sensors if its set to away, so this causes a minor issue. Not a big deal as I’ve actually automated turning on/off the alarm using routines and SHM. I had this same problem with my app and it was due to envisalink not reporting stay vs away. You may need to sync the status directly from your device instead of the alarm.
Thanks @phiz118
I have been working on an app for the harmony hub/amazon echo so have not done much with the j64 alarm recently. I have been wanting to give linux a spin so will setup a VM when i have a little extra time.
I use a mac so have not really set this up on windows to auto boot when the machine turns on so am also curious how you would do it. I “think” you would just put something in the startup folder but am open to any thought you have.
Yes, it should. I just tested it in stay & away mode from mine and it synced with the app and also SHM. Let me know if this is not working for you.
I can’t find that sentence in my current docs, maybe i fixed that?
The stay vs. away works for me in SHM. There is a little bit of code in the smart app that must be having a problem in your setup. Is that ArmingMode being set wrong for you?
// Keep smart home monitor (SHM) in synch with the j64 alarm server
// We sync SHM with partition 1 in the alarm system since it does
// not support multiple partitions
if ("${Id}" == "1") {
if ("${IsArmed}".toLowerCase() == "false") {
setShmAlarmMode("off")
} else {
log.debug "check ArmingMode ${ArmingMode}"
if (ArmingMode == "Away")
setShmAlarmMode("away")
if (ArmingMode == "Stay")
setShmAlarmMode("stay")
}
}
this might actually be due to the behavior of DSC panel, rather than a problem with your code.
see this thread for the down and dirty details from the EVL guys themself, haha and phiz started this thread too I think:
http://forum.eyez-on.com/FORUM/viewtopic.php?f=6&t=2109&sid=422685197707ba1eb620e6fac77a1d43
we ran into similar problems a while ago with my fork of alarmserver (which also now supports syncing SHM, auto-device creation, etc, and probably also has this same bug as of now…, although i’ve made it an option to disable SHM sync since it’s not optimal for every situation)
if you don’t have any zones defined as zone type 05 or type 37 on your DSC panel, basically, stay/away zones, or night zones, then the DSC panel will never report itself as ‘stay armed’, no matter what. it will always report as “away”
for it to report as stay mode, there must be zones bypassed. normally it would automatically bypass the stay/away zones when you arm in stay mode, and the system will actually say that bypass is on when this happens, even though it’s not a *1 zone bypass, it still lights up bypass mode.
So, I’m guessing the problem is, some people have motion devices that are z-wave or what not - not part of the DSC system - they use those in SHM - but when the DSC panel arms, it’s going to want to set SHM back to away mode - even if you armed stay in SHM.
Another option would be to only sync SHM status in one direction for people who are in that situation…would be kinda unintuitive, but it would probably work. Or, slightly better, basically, add an option to make it “arm-mode-insensitive”, check the current SHM mode, and if it’s armed, and the new mode received is not ‘disarm’, just leave it, and don’t try to update when going to/from stay/away, only change SHM modes when going from armed / disarmed… I’ve actually decided to add this to my smartapp now as an option…and it seems to be working as expected, i think this successfully prevents the unexpected behavior…but i think it should most definitely be an option because it basically is disabling the full status synchronization for people who actually do have stay/away mode working properly on their DSC panel…but it does seem the option works as intended…the only thing you couldn’t do with the work around is arm SMH to stay mode from your actual alarm panel…there’s no way to work around that from the software side, but you could do my last and final option:
another-other option would be to add a dummy zone to your alarm panel so it actually arms in stay mode, if you had an extra wired zone available, just short it with a wire or resistor if you’re using SEOL, to just make an always-closed dummy zone on the panel, and set the zone type to 05, done. haha. even better would be to just add a real one, it could even be wireless if your panel supports that…ultimately getting the DSC panel to work with stay mode is the best option, since only then can you properly do full sync between DSC and SHM.
@joe64 I get this when I try to create the smart app
No signature of method: script14584912862161612228288.metadata() is applicable for argument types: (script14584912862161612228288$_run_closure1) values: [script14584912862161612228288$_run_closure1@3fe9cb32] Possible solutions: getMetadata(), getState(), setState(java.lang.Object), metaClass(groovy.lang.Closure)
NM copied the wrong file. So far the best feed back I can give is you leave a little of what some of you have as common knowledge off making it very difficult for the novice. I am getting there though and sincerely appreciate your hard work.
That message sounds like you are not copying in the full text in for the app or device type. The other possibility is that there have been a ton of ST platform issues over the last few days which are causing you an issue. I am working on an updated version of the app that will automatically install those smart apps & devices for you but that is a week or so away. If you want to talk over the phone I could probably walk you through the install. Just send me a private message with a time to meet.
@joe64 OK I am on step 5 and I am getting the following error in red letters but at the bottom it says 1 project built but only like 3 or 4 lines of text. Is this OK?
unable to locate project .json.
OK I see whats killing me. My DOS commands. I cannot seem to change to the src directory gimme a few minutes.
@joe64 I am almost there brother please dont get upset with me. I can restore the Web API in step 5 but I get a build fail from it. Below is a picture of my screen with the build fail.
[URL=http://s837.photobucket.com/user/Intimnasc/media/Mobile%20Uploads/14584949597052133629851_zps4u4eje9g.jpg.html]
[/URL]