Yea, I’m really sorry about that! Right now I’m trying to finish up multi-partition support. After that I can start to look at what it will take to have a Honeywell version, if no one else can volunteer to have a go at it. It would probably be pretty difficult for me to do it without having an actual system to test.
I have EVL 3 and been running alarm server. Had this 3-4 years. 8 zones. Only motion and contact. Would love to test it.
Hi - I’d love to have you test out the latest driver! I’ve been working with someone to test the multi-partition support, so I want to give you that version to try. Should be fine with one partition too.
Can you install the CLI first so that we can diagnose any issues?
LINK: SmartThings Developer CLI
1 Like
This is pretty awesome!
What does the GUI look like?
How many panels does it create?
One for each partition (no more separate stay/away panels)
1 Like
Ok. Will get to this shortly so I can test it with you.
1 Like
@TAustin - Can this be put in a docker container so I can test it on my unraid server?
This runs entirely on the SmartThings hub.
A quick update for those interested in this topic.
With tremendous thanks to @949BFN for testing and feedback, I’m happy to report that multi-partition support is now complete and ready for additional users to try out if there are other folks out there who need it.
Partitions and Zones can now be configured up to the maximum possible, which is 8 and 64 respectively.
Also at the request of @949BFN, I have improved the ability to control the DSC panel from webCoRE. Partition panels are now listed as available in the ‘refreshable devices’ list, and webCoRE can issue various partition commands including arm, disarm, and other controls. Automations and Rules are the preferred approach, but this is an accommodation to webCoRE users with complex pistons that can’t yet be migrated.
I’m looking for a couple more testers before I make this driver generally available to everyone, so please DM me when you are ready (please have the CLI installed) and I will provide a shared testing channel for the driver.
1 Like
Great. I’ll DM you once I figure out how to get CLI installed.
1 Like
@TAustin thanks for all your help on this project!
Thanks to you I have successfully tested this running with my contact zones and motion zones.
It works great in WebCore as well.
However, only the motion zones can be added to ActionTiles, not the contact zone devices.
@949BFN have you had luck adding contact zones to ActionTiles? That’s very important for my setup on the tablets I have running DSC around the house.
1 Like
@KB111 No, sorry, I have not. I only make use of motion sensors.
@TAustin
Can you apply the Refresh capability to your edge device definition for your Zone Sensors?
This is the reply from my friends at ActionTiles:
“Thank you for bringing this issue to our attention. This may become more common as more people switch to Edge drivers. It will take several weeks to apply a patch to the ActionTiles connector SmartApp to add device selector for Contact Sensors.
Are you able to modify the Edge driver to add the Refresh capability? If the driver could be updated, then your devices will be available for inclusion right away.”
Yes, I can do that. Strange that contact sensors cause a problem but not motion??
I’ll try to have that done by this evening U.S. time. Updates like this may or may not get dynamically applied to existing devices. Sometimes you have to delete the device and recreate it for the change to take affect. So once I make the change, give it 12 hours to see if those devices update (and they are recognized by ActionTiles); if not you will have to recreate them (sorry for that).
Will let you know when I’ve made the change.
Sounds good! On standby.
OK, driver update has been pushed out to the testing channel. Let me know if this fixes the issue.
I only added the refresh capability to the contact device and not the smoke, co, or water devices. Wasn’t sure if ActionTiles would have problems with those as well, but I guess we’ll see if someone reports it.
Great work @TAustin
I had to delete the existing contacts zones/devices in the app then add them back one at a time. All working in WebCore and in ActionTiles
Another thing for you… The main DSC Panel device is also not showing up in ActionTiles. I assume it needs to have the on/off “Switch” capability. (of course, I’m not sure that if you set it to ON whether it sets itself to Alarm Away or Alarm Home status for the alarm)
Can you give it the switch capability and then I’ll test that out?
I’m surprised to hear about the DSC panel not showing up. @949BFN said he got that working. In fact the Panel devices have the refresh capability included already.
@949BFN How did you add the main DSC Panel in ActionTiles? I see it listed as a device in the ios smartthings smartapp, but it won’t let me add it to any actiontiles panels. It’s not listed as an option.
@KB111 - The main panel doesn’t show up in ActionTiles. A possible workaround would be to create a virtual switch for the panel, and use webCore to check the status and turn the virtual switch on/off according to the panel status.
I’ve been unable to try his yet, because my webCore Dashboard has been refusing to load for the past two days. (I’ve been having this issue frequently recently. Usually, it sorts itself out after a few days.)