@TAustin , to clarify, I started off the bat with v2.1 drivers after presumably deleting all artifacts of alarmserver integration in IDE. Since no devices were being created when the zones were setup in v2.1, I deleted v2.1 and installed from your beta repo v2.0, and the devices are now being created after setting up the zones in the primary panel. Not using any drivers concurrently.
OK thanks for the clarification. Once you get the CLI running and can do logs, we’ll want to make sure both drivers and all devices are deleted, then start fresh with the 2.1 driver. Then before you start creating the zone devices, fire up the logger and we’ll see what’s going on.
Thank you so much for the update~ I have followed the steps and removed the original DSC Panel and Zones. I believe uninstalled the old Driver and installed the new one. I have added a new DSC Panel but after I setup the zones, they are not automatically added to ST. I have confirmed the new DSC Panel is using the new driver and I can see the new Partition Statuses. When I click into the new DSC Panel, It doesn’t have a Partition Status although it says it is connected. At times, the DSC Panel tile is showing a parameter as attached.
Ugh - It sounds like you are having the same problem as others have reported - that the zone devices are not being created for some reason.
As I understand it, you did have this all working with the prior driver version, correct?
I can’t understand why these zone devices are not getting created, but I’m hoping that @d33pa can get the CLI working so we can see what is in the logs (he seems to be having a similar problem).
One question: Assuming you had this working with the prior driver version, did you try and just let the driver update normally without deleting anything? This should be the default - you normally should not have to start from scratch - those instructions were only for the case where you weren’t seeing the new Partition Status options after the driver update.
Yes, the prior version was working perfectly. I wasn’t aware that the new driver would update on its own so unfortunately, I did start from scratch. I did check the prior version DSC Panel to see if the new Partition Status was up but they were not.
Any chance you’d be willing to install the CLI tool? If you have a windows machine it’s quite easy to do.
@TAustin , i was about to start deleting the devices, then I saw your reply
Blockquote
One question: Assuming you had this working with the prior driver version, did you try and just let the driver update normally without deleting anything? This should be the default - you normally should not have to start from scratch - those instructions were only for the case where you weren’t seeing the new Partition Status options after the driver update.
Blockquote
FYI, i couldnt delete the old v2 driver, kept telling network error, Hub showed connected and is hard wired ethernet… rebooted, no go, so then I tried to add v2.1, then tried to delete 2… no go.
So, i now deleted v2.1 (as i had both drivers installed)
deleted all devices
now i was able to delete v2
I will be starting the logging shortly and try to install v2.1, then see where that takes us with device detection after the zones are classified, etc.
Stay tuned…
T ,
Havent updated since my initial install…
What is the process to update?
Chet
Starting from scratch, after having deleted all devices under v2 then deleting the driver, installed v2.1, setup primary panel with prereq’s (partitions/alarm code/password/lan address and zones), this time it magically added the devices!!
Now only thing I can chalk this to is that i missed deleting the old alarmserver app in my apps in IDE. or there is some dependency from v2 that sticks and lets v2.1 work as expected.
I did logcat the whole device addition, but not sure it will help as it worked as expected; also, I would have to parse the data to remove any sensitive info… but in the name of debugging, I will do it if you need @TAustin .
Happy camper here! Thanks TAustin 
Sorry I only have a Mac. I did manage to get it working. I uninstalled and unenrolled the edge driver and deleted the DSC Panel it created. I then enrolled and installed the newest driver. To my surprise, it started adding all of the zones and it is working perfectly now.
I’m relieved to hear you’re all working. Thanks for letting me know. No need for the log then.
That’s good! It’s a strange issue that I don’t quite understand the cause, but am glad you got it working.
Edge is still in beta and I guess we have to tolerate these things.
Thanks for your patience!
Hi Chester - No need to do anything if you were already on the 2.1 version. Normally Edge driver updates should happen silently and without problems. What will happen is that your driver will automatically get updated in the background and the driver will restart. Envisalink connection will get re-established and your devices should then continue work normally.
You can confirm the current driver version by going into your panel device details screen, tapping the three vertical dots in the upper right corner, and tapping ‘Driver’. You can then check the driver version.
Thank you so much for working on adding the functuality to automate when disarmed. I’m sure everyone will enjoy having their lights turn on when the alarm is disarmed.
Thank you!
New driver works great! Thank you TAustin for your hard work.
Todd, I think it should be “Exit Delay” not “Disarmed”
Additional Notes
- If you are not seeing the new “Disarmed” and “Entry Delay” Partition Status options
