For those who also use a Hubitat hub with the Smartthings hub: There is now an excellent (post groovy) solution available to sync the status of devices between the two hubs called HubiThings Replica.
Using @TAustin’s Envisalink Edge driver and the HubiThings Replica app in HE (with the dedicated driver for the Envisalink card) on the Hubitat side, one is able to sync all the info/capabilities of TAustin’s drivers between Smartthings and Hubitat. HubiThings create and identical device in Hubitat which can be used as any other device in automations. The status of the “linked” devices is synced in both directions between the two hubs.
1 Like
My alarmserver stopped working and luckily I found your new approach. However, I have the same problem like BobR and I could not arm/disarm from the panel (zone sensors do report open/close/motion). What’s the solution?
Thank you very much!
Sounds like maybe you don’t have the right alarm code configured?
How many characters are in yours?
Thanks for the quick help…It’s a 4-digit code for arm/disarm.
What happens exactly when you try to arm or disarm from the app?
The Arm Stay/Arm Away buttons won’t respond to finger touch before I posted here, now they are working for some reason:-)
The titles inside Panel still show “partionstatus2”, “partitionCommand2” and “dscselectswitch2” though but it does not seem affect anything.
Really appreciate your help.
hi there just got my EVL-4EZR all configured with my Honeywell WA3000.
Followed the link, installed the driver, scanned and installed the app, edited the settings with IP, password etc but the smartapp wont connect. Ive tried a few times but wont connect at all… i can log onto the envisalink board locally with no issues just can get it into smartthings
edit: i see some ppl mention logs… where do i pull or view the logs
Hi - This driver only works with DSC systems. You want a different driver here.
oh man… thanks. i was inquiring about that one and he said i may need this… i’ll try that one thanks.
In the last week, PartStatus has been duplicated about 5 seconds later, which is messing up my setting of variables in SharpTools. Device history screenshot:
The “Armed-Stay” before “Arming Stay” seems to be the erroneous report. Also I see Switch On is reported twice, but I don’t use it, so that’s not causing me trouble.
Is the driver doing this, or the Envisalink?
It looks like the bug where SmartThings is generating duplicate notifications to the driver. I get this every once in a while (for multiple Edge drivers), and I have to reboot my hub to fix it.
I’ve reported it multiple times, provided hub logs, etc.
OK, ill give that a try, thanks.
If that doesn’t fix it, I may need you to get me some driver logging output with the CLI.
1 Like
The reboot didn’t fix the problem, but I’ve worked around the problem for now by using Security Mode – which is not duplicated – instead of PartStatus.
That’s odd. If you ever want to diagnose it any further, we’d need some logs from the SmartThings CLI to see what may be causing it. It’s possible it’s coming directly from the DSC. Not sure what else could be causing it…
1 Like
TAustin:
Thanks again for your work on this driver. I was wondering if you have any update on my request back in November for some enhancements (repeated below):
- The Eyezon app reports the user name of who arms or disarms the DSC system. User number 1, 2, 3, etc. have their own unique user codes to arm/disarm the system with user 40 being the “Master” code. On the Eyezon web portal, you enter a label for each user number, the label being the name associated with that user number, say user 1 is “John Smith”. The Eyezon app reports the username arming or disarming the system via email and it appears in the event log. This is very useful to know who is in your house. Could your Edge Driver make this information available to ST? You would need to enter the user name for each user number similar to how you enter a zone label, but once available to ST a routine could generate a notification specific to which user disarmed the system or take other user specific actions.
- When the system is in “trouble” the Eyezon app reports the specific trouble (low battery, bell circuit, AC failure, etc.). Could this be added as a field on the DSC Primary Panel display?
- Add PGM1, 2, 3 and 4 as a Partition Command that can be enabled in a routine. I would like to use a virtual switch to enable PGM1 which is hardwired to an external device. This was previously requested (Sep 9).
Thank you for your work on this and your other drivers.
Reply
Hello and thanks very much for your feedback and excellent suggestions. I hope to have a driver update by the end of the year, so will take all of these into consideration.
Hi there. My apologies for the delay. Due to the sensitive nature of this particular driver, I do not updated it often. That said I do intend to include some of your suggestions in the next one, which will be a new driver, rather than an update to the existing one. I do this to minimize any disruption to current users and give you more control over when/if you want to make the change. Some of the changes I need to make to the device capabilities wouldn’t lend themselves to upgrade existing devices.
Please look for a new driver release by mid-May. If you are willing to be an early tester, let me know and that would help me out immensely.
No need to apologize. The driver has been completely stable, so I understand you wanting to minimize updates.
I would be happy to help with any testing, just let me know what you need me to do.
1 Like
So my integration has been offline since last night for some reason. Nothing has changed. I can log into the Envisalink card. Not sure what is going on… Tried rebooting the hub from the IDE but no change.
1 Like
Fixed it… Rebooted the envisalink card. Problem solved. Odd.