I had the same thought. I created a Virtual Switch yesterday to try this as a workaround.
Just haven’t figured out how to implement a WebCore piston rule to check both the Panel changes as well as the Virtual switch on/off and not get caught in a loop.
@TAustin can you update the DSC Panel so that it has a “Switch” as it’s capability? I think you already have it set as “Refresh” too?
If adding a switch allows the device to be recognized by ActionTiles, would ActionTiles even allow you to do anything with it? If it doesn’t support custom capabilities, then you probably couldn’t display any attributes or do any commands. Maybe I’m wrong?..
Let me ask them. BTW, what does an “On” command do to the DSC Panel. Does it turn it to On Home? On Away? (I’d prefer On Home and be happy)
Not sure where you are seeing that. Webcore maybe?
In Automations, there is an on/off command you can set for either the Arm Stay button or the Arm Away button: on=arm, off=disarm.
Thanks. I thought of that too, but the Virtual Device switch doesn’t have a “partStatus” capability like the real DSC Panel one does. Just On/Off.
Did you figure it out differently?
You will use webCore, testing for the Panel status as in the screenshot above, to turn the virtual switch for the Alarm On/Off. So, when the alarm arms, webCore turns the virtual switch on. You will also set up the reverse in webCore, i.e. when turning the virtual switch On/Off, webCore will arm/disarm the panel.
Thanks @949BFN In WebCore, I have it working well when doing the phycial Panel changes, to update Virtual Switch (used in ActionTiles) like this:
However I can’t find the right command or value to use for “SetPartStatus” to change the main Panel Arm-stay or Disarmed when I click the Virtual Switch On or Off In ActionTiles. This doesn’t work right:
Hi - Don’t use setPartitionStatus for any commands. Use setPartitionCommand. The valid arguments (commands) are as follows:
armstay
armaway
disarm
panicfire
panicamb
panicpolice
instantarm
toggleinstant
togglenight
togglechime
refresh
reset
I would highly recommend you try to move away from webcore and use Automations or Rules unless you really need a specific function of webcore. The piston you posted is pretty simple and can easily be handled by Automations. The new platform devices (like Edge devices) and their states and commands are more straight forward to access and use. I know Rules are a bit too esoteric for most folks, but Automations is quite easy.
NOTE: The above guidance is for the latest testing version of the driver from my testing channel only!
Todd - Regarding your comment about running in parallel w Alarmserver, is that a potential workaround to support Honeywell Vista boards or no? I was looking through your code on github wondering how hard it would be to adapt it for Vista. Did you have to reverse-engineer the EVL codes/commands etc, or is there some developer support?
Hi there - Did you see this recent post?:
I did not, but that sounds like great news! I will give it a shot and let you know how it goes!
@TAustin Most of my stuff in webcore is too complex for ST app automations.
If I try to rewrite my webcore pistons above in ST Automations it will be multiple ones. And then the Rules functions seem way to complex without a nice GUI
Based on the announcement Samsung made at their recent online developer event, the web-based interface to Rules is ready for beta. Hopefully it will be made available soon!
But I do appreciate the point about needing the webcore piston functionality.
Thank you !
This is how I arm the Panel in webCore:
To execute a piston when the alarm is armed:
To Test which of the Zones triggered the Alarm (Note: Single “!”):
To execute a piston when the Alarm is triggered (Note double “!!”):
@taustin the “disarm” command is not working when I use it. “armstay” works fine, just not “disarm”. It doesn’t do anything
Does using the mobile app buttons to disarm work?
No it doesn’t work… Can’t disarm thru the app. Have to disarm manually through the panel.