Thanks for reporting. I’ll check it out.
Yes, I deleted all previous devices, uninstalled the driver, and unenrolled from the beta. I tried installing and removing the new driver several times. I also tried rebooting the hub a couple of times. The driver continued to install without an issue. Every time I would “Add device / Scan nearby” the log I posted above would capture and nothing else.
I decided to uninstall the new driver and go back to the beta. The panel installed without issue on the first try. I can see that the log should have kept going after clicking “Add device / scan nearby”. It just…wasn’t.
Well that’s awfully frustrating. I wish everyone was having the same problem - at least then it would probably be easier to find the cause. I’m suspecting something related to device profiles, but one would think it would be a problem for everyone…
Hi Josh - I found the problem and have made the fix. I’m looking into a couple other issues that I’d like to get solved before I push out an update, so give me a chance to look into those if you don’t mind. Thanks.
I’m still thinking about what could have gone wrong. One thing that doesn’t many any sense is that based on your log, you shouldn’t have seen any Panel device in your mobile app, since according to the log, it didn’t get added or initialized. So it’s really confusing to me that you said you could go into the panel device settings and try to configure your zones. It’s almost like the panel was some sort of zombie device that was half alive and half dead!
This one’s going to really bother me until I can figure it out…
Yes, the panel device does appear in the app. However, to your zombie analogy, the log does not show anything no matter what I try to do in the device settings. I can only delete the panel and try again.
Hi TAustin, great to hear you fixed the issue. It’s not a feature I use often but thought I’d let you know. I’ll keep an eye out for future driver updates.
I have another hub at a different location that only has a few devices (and no DSC system…yet). I thought I’d try to install the new driver there and see if it works. It does. I can’t test it out completely of course, but everything seems to log correctly and devices are added as would be expected. Finally, I did notice that when I removed the panel, this was logged as well.
On my main hub, nothing is logged when I remove the zombie panel that is created by the new driver. Obviously, there must be something specific to my main hub, but I haven’t figured out what it might be yet.
Ahhh very interesting. This might require some diagnosis from SmartThings support.
One other thought I had - and maybe you’ve already looked at this - but have you used the CLI to inspect the installed drivers list and the devices inventory, just to see if maybe there is something unexpected there?
smartthings edge:drivers:installed
smartthings devices
Thank you TAustin for this awesome Driver. I am trying to setup an automation to turn on lights when unarmed. I have tried using the trigger Security Mode Disarmed but it doesn’t work. I looked at the panel history and it doesn’t register a Disarmed event.
Is there a way to add an Entry-delay to the Partition Status triggers?
“Security Mode” values are only useful if you are using STHM to trigger arm/disarm. If you’re not using STHM then you need to trigger based on “Partition Status”.
I’m not sure there is an easy way to do what you want, since disarm is not on the selectable list. You’d need some way to trigger when the Partition Status value changes away from Arm-stay or Arm-Away. I think webCoRE allows that kind of logic, but unfortunately not automation routines. Not sure if you could accomplish it in Rules.
Nevertheless you’ve exposed a limitation that I need to address. Let me look at this and see what I can do.
Todd I have ‘Configure dashboard button’ set to Arm Stay, but when I press the power button on the security panel in the room nothing happens. I’m I misunderstanding the meaning of ‘Configure dashboard button’ ?
I just replaced my Radionics D6112 with a DSC 1832, every window/door (hardwired) and 3 motion sensors are on it’s own zone. I purchased the panel and keypad RFK5500 (wireless capability) DSC is discontinuing this keypad but, not the wireless panel. I don’t need wireless but, got in case. I also went ahead and got alarmsystemstore’s programming option. I decided to minimize the learning curve and have it running quicker. I also got the EVL4. Got everything running. Can’t help with the wireless since mine are all wired sensors. I have zwave for automation, mostly switches and additional smokes. Satisfied with the help from alarmsystemstore.
Hi- There was a bug with that and I haven’t sent out the fix yet. I will do so within the next few days, as I also want to address the limitation with creating automations based on disarm actions.
I found this thread today after finding the whole edge platform. Been running alarmserver for several years and today, turmed it off… deleted everything in ide, even the old app. I installed your 2.1v and i get the dsc panel but no other devices show up
I am having similar issues as @Delgreco007…
I feel pretty sad as i cant seem to figure out how to access or load the st cli. Like the most basic info…
Open command prompt on windows, or has to be done on linux or mac… im pretty savvy but feel pretty stupid on this front lol.
Hi there; I’m happy to help get you going.
A couple questions:
-
When you say that no other devices show up, I assume this means when you are defining the zone types within the Settings options?
-
Regarding CLI, do you have a windows machine you can install it on? If so, you can follow my step-by-step instructions that I provided in this post. If you have any questions or need further help, don’t hesitate to DM me.
Also, I’m about to push out a new driver update see below.
New Driver Update!
I’m pushing out an update to the driver which includes these changes:
-
Fix to dashboard button bug. Prior issue was that sometimes the dashboard button would not result in any action. This should work better now! (@NickA, @Josh_Eamon)
-
Added ability to create automations based on additional Partition Status values of “Disarmed” and “Entry Delay”. As a reminder, be sure to use the “Partition Status” attribute when testing for conditions. Only use the “Security mode” attribute if you want to test specifically for the STHM state (see my comment below regarding STHM linkage). (@dirtdiglord)
-
Hopefully, this update also fixes an issue for webCoRE users where the “setPartitionCommand” option was not showing up as selectable when creating pistons using the primary or secondary panel devices. (@949BFN)
New driver version is 2022-03-21T20:58:20.227208
Additional Notes
-
If you are not seeing the new “Disarmed” and “Entry Delay” Partition Status options when creating an Automation routine, you may be forced to delete your devices and re-creating them. I apologize for this, but this is sometimes necessary for this kind of change. What you can do is this: First make sure you have the new Driver version. Then manually delete all your zone and partition devices using the mobile app. Once you’ve deleted all devices, you can run an Add device / scan nearby devices and a new primary panel device will be created. Before you recreate your zones and finish configuration, try creating a new Automation Routine for the new panel device and confirm that the new options are showing up for selectable Partition Status values. If it looks good, then proceed to create your zone devices and finish configuration. Don’t forget that it’s best to set the Envisalink IP address last.
-
There have been reports that STHM security mode changes are not getting sent to drivers that are ‘subscribed’ to receive them. And indeed I have seen this case myself with this driver. The symptom here is that you have the STHM synch enabled for this driver, but your alarm system arm and/or disarm aren’t being triggered when STHM mode changes. This appears to be a random SmartThings issue. Changing the STHM mode manually using the mobile app seems to always work, however. I apologize for this issue, but there’s not a lot I can do about it until it gets resolved by SmartThings. In the meantime, if you are having this problem, I would recommend rather than relying on the STHM synch feature, that you create an explicit Automation routine to check for STHM mode and set the DSC Partition Command accordingly. This may be a more reliable way to go for now. Just remember to set the 'Set arm mode from STHM" option to ‘No auto-synch’.
Thanks for the reply @TAustin!
I have defined all the zones, 1 extra partition, code, ip:port, password. I can see the primary panel connecting and am able to arm/disarm the panel from ST.
I am using ST Hub v3 (2018), Envisalink 4, turned off alarmserver integration (LXXero).
FYI, I deleted the v2.1 driver and installed your beta v2.0 driver and all the zones I added (as a test) showed up in ST.
I will follow the tutorial on cli from the link you sent me and am willing to help troubleshoot with logs if thta will help narrowing down the issue. I will not delete the beta driver until I hear back from you with further instruction/suggestions/recommendations to troubleshoot.
Thanks!
Edit2: i logged in to IDE and noticed the webapp “DSC Integration” app was still there. Also noticed that all my (new zones created with Beta driver) zones are still “cloud”. I thought I deleted all instanced of this integration, but will now delete this app in IDE and try to install the new driver. KYP.
So to make sure I understand: you are working ok with the v2.0 driver, but you can’t create devices using the 2.1 driver? I’m not sure I’m clear here… It’s also important to understand that you can’t have both drivers installed at the same time. You would not be able to get the devices created since they would conflict.
It would be great if you could get the CLI working, since that will help tremendously in diagnosing any problems you are having.
The IDE still shows Edge drivers as cloud for some reason; you can ignore that.