I re-did all the icons, so now everything has icons that make sense. You can see the fun I had tracking down what are the available icons here:
We should all push smartthings to make it easier to pick icons! This is just crazy! Anyway, I think all the new icons make a lot of sense, it looks a lot better now.
I also used no break spaces for things like “No Trouble” and “No Chime” as well as “Sensor Reset” Hopefully those spaces work well for everyone! For me, it means the text doesn’t get wrapped onto another line and get cut off, which is what it was doing before and it looked bad. It’s looking much better for me, hopefully it works for everyone else too. If it didn’t work, you might see some crazy characters like Sensor\u00A0Reset, if you see something crazy like that (while in the smarthings app…), let me know, but so far it seems to be working well.
Anyhow, please try out the latest stay/away panels - they look much better now I think.
Gonna work on the new contact/motion/etc devices later…got another cool surprise coming up too!
I have wireless smoke and CO2 devices, I take it there are no support for them yet? I have just set them to 4 wire smokes for now but not had a chance to see of they actually report ok yet.
I’m gonna make a CO device which should act the same as 4wire smoke but just show up as a CO detector in smart things capabilities. But 4wire smoke should work for now, or even zone contact…
it’s only 2-wire smokes that are funny. the 4-wire smokes and co detectors mostly act like anything else, we’re just re-mapping the states to the smartthings devices so smartthings thinks they are actually smoke detectors instead of just thinking it’s an open/closed contact, which it still basically is ,but yeah…
if you think it’s nice now, just wait til you see what i’m doing now…
we’re gonna have a zone bypass slider where you can slide to select zone 1 - 64, then hit a submit button to send the bypass…that’s actually pretty much already done and working…I’m also implementing the 8 status LED’s that are reported as part of event code 510…this is so you can actually see that zones are bypassed. It’s not 100% but it’s getting there. it was a lot more annoying to implement than i thought since it doesn’t send a partition number - event 510/511 is ALWAYS partition 1, and rather than sending a partition number it sends a 2 byte hex status code which i have to interpret to convert it into the 8 status LEDs (yes 8…though my actual panel only has like 3-4…i think some of the other stuff shows up as items on the LCD rather than actual LEDs)
Updates look great. I have one basic question however… Sorry I missed it if it was already covered. Why do we need both the away and the stay panels? It seems that we can make most settings changes and see status changes on both panels. Thx for the quick education.
EDIT: I think Imfigured it out… Re reading the install instructions. Basically each provides a switch formuse in routines. Right? So if I dont use the commands in routines then I may only need one of the pannels? Just curious.
did you enable the extra event codes in alarmserver.cfg for the chime statuses?
and no i hadn’t seen that - i guess yet another version is popping up? I guess its written in some kinda .net or whatnot…well, i am not about to start learning that, lol. but interesting none the less…would be nice to make a frontend to setup the smartthings api some day, that’s definitely a huge usability thing. but i mean, most of us have this working already so it’s not a huge deal.
wait til you see the new panels i’m working on though, probably will have more features than anything you’ve seen to date…
after seeing that and a few other panels though - makes me think it might be worth making custom icons…seems it’s the only way to make it look nice.
but i’ve got a lot more coming…get ready for zone bypassing and all 8 led statuses. I ended up having to redo the code for that - my initial implementation would send all 8 statuses every time it came in and it was causing it to slow down the app significantly, i refactored the code a bit and it’s almost ready, just a few more minutes i hope
yeah if you go wireless, those are your only option.
if you go wired, you can use anything. I used all system sensor in my basement since they seemed nice, I used a co1224 which is nice because its got a built in supervisory relay, so no extra relays are needed. i haven’t bought any wireless co’s yet, but i was planning to get those…
OK latest code is up…bypass slider/switch should hopefully be self explanatory but you basically just drag it to where you want and then hit bypass. the big box will show the value the slider is set to to make it easier. the status leds are also pretty explanatory, make sure eventcode 510 (AND 511) is enabled in alarmserver.cfg…this will need new new dsc integration + alarmserver + panels.
you just run it again on the same zone, or, you can arm and disarm, it will unbypass after you disarm
and yes the slider just lets you pick the zone to bypass…
also I noticed i missed eventcode 511 - you also need this enabled in alarmserver.cfg for the flashing status led.
i also just found an issue where it kind of takes a while to activate the bypass - it’s waiting for a timeout on the terminal. I need to make it send a # character so it bypasses immediately. It seems this does actually improve the speed, so I’m gonna try to add it to all the 071 commands, some more updates coming soon i guess!
OK. I found a bug where if the hex value sent is real low that it would generate only partial binary values, i needed to pad it out to 8 characters, but now it’s working wayyy better.
new alarmserver + stay/away + dscintegration is needed again
Apparently if you send “00” as the bypass, it will remove all bypasses, which is handy. I’ve adjusted the slider so it lets you go down to 0. Now we can just drag the slider to 0 and hit bypass, and it will remove all bypasses. Nice.
There’s some other stuff you can do as well:
Additional Bypass Commands:
Bypass Recall: Press [99]. The keypad will recall the last group of zones that were bypassed
Clear Bypass: Press [00]. The keypad will clear the bypass on all zones.
Save Bypass: Press [95]. The keypad will save which zones are manually bypassed.
Recall Save: Press [91]. The keypad will recall the bypassed zones that were saved.
Not sure I care about those right now - but it might be worth making buttons to individually press those rather than trying to use the slider for all of it…if anyone actually cares about those i can add them…but for now i think it’s good
yeah i’m pretty happy with this now. I can be upstairs in my bedroom and have the window open, bypass it, and arm the system, all from upstairs.
Edit: I also just had another thought. I could probably add bypass buttons inside the zone devices too…if only i had a way to show bypass status per zone…my dsc panel can show it, but i’ve not found a way via EVL to get it…I’m going to look into doing that once i revamp the zone devices, maybe tonight. I think I may also move more of the logic for the LED status lights into alarmserver just to see if it helps speed things up any…also, that said, I think if i’m gonna put bypass buttons in all the zones i need to move the IP/Port config to the smartapp instead of the stay/away panels, now you’ll only have to define that once for everything, but in the smartapp. So be aware you’ll have to define this in a new place when you update the app! Though it’s kind of nicer now…i’m still testing the changes now, hopefully updates soon…
the more i look into it, the more it seems like we’re supposed to have the smartapp add/setup the devices, kinda like that new integration in the other thread was doing. i may actually try to do that. meaning, no more adding all the zone/panel devices manually - alarmserver would basically add them when it starts up. In fact - that means we’d need to specify the zone types again in alarmserver, so that means i may go back to that old alarmserver config format i had tried long ago where its like [zone1] with various attributes under it…kinda funny we might be moving back to that again…but you would never have to setup devices or name them manually in smartthings - we can have alarmserver create them & pick their device type based on the string in alarmserver now…so one place to define it all…i’ve already got some code in the works now, but this is gonna be a huge change so it might take me some time…
i guess if I can get that going then we’re not even that far apart from that other alarm server - if anything i probably have it beat on panel features already…its kinda a matter of preference, web gui vs config file - i probably prefer just editing the config file because i can do it faster and generate it easily via various text manipulation tools…infact converting the text file from the old format to the new one i was able to do completely via search and replace - can’t do that with a web gui…anyway, i digress.
Either way I’m on board. I like the Linux box because I can leave it on all the time. Other than when it crashes or gets out of sync with evl I have no problems. I guess the best result would be if st could talk directly with evl.
for (def i = 0; i < 8; i++) {
def name = ledMap."${i}"
** def status = (zoneorpartition[i] == '1') ? 'on' : 'off'**
if (notifyEvents && (notifyEvents.contains('all') || notifyEvents.contains('led'+name+status))) {
sendMessage("${opts[0]} 1 ${name} led in ${flash}${status} state")
}
pretty sure that’s the issue i fixed already last night, try updating to latest version
also make sure you’re using latest alarmserver
i switched some of the string conversion to happen there so if you didnt update both it will break
I spent a while last night working on the new version though - where it creates the alarm devices for you automatically, and i have it mostly working - there’s some weird bugs in smartthings where deleting devices seems to only partially take effect, I’ve managed to work around it but it’s odd
