Thanks, I think I have it setup as far as I can until I get the Envisalink 4 installed tomorrow.
Great feedback guys - I have updated post #1 to reflect Option #1 (Native) and Option #2 (Redloro's smartthings-nodeproxy). I've also provided links to the ST thread as well as the native integration "refugees" thread.
If you have questions about the smartthings piece, please put them here.
I'll have to check next week as not at a place where I can test this.
1 Like
Hi Brian,
New user here wanting to integrate my DSC/Envisalink 4 with Hubitat for HA . Basically just want to tap into the sensor states (no need to arm or disarm since I handle that through the EyesOn app, keypads or Alexa...Alexa only for arming of course). Just for clarity, for DSC do I need to go with Option #1 only, or can Option #2 also handle DSC at this time (or is Option #2 strictly for Honeywell/Ademco/Vista panels).
Sorry for the noob question but I am concerned that @Doug left Hubitat native integration due to “stability” reasons and since others have said your integration (using rpi) has been solid, I was hoping to use your solution with my DSC panel. It also helps that support and development continues for Option #2 as well.
Any comments on how well the native integration works and problems with it (specifically stability and lag time) in comparison to your solution?
Also, if Option #2 has a driver for DSC, what model rpi are you using to run Smartthings Nodeproxy?
Thank you so such for any help you can give a noob!
I honestly don't know if Option #2 would support DSC, but from glancing at this thread I'm going to guess no.
I don't want to speak for @doug, but I believe his beef was with the Hubitat platform and the (still plaguing many) issue about hub slowness. I don't think there were any huge concerns with this integration, however, I cannot speak for if this integration may have caused his device to experience the sluggishness that caused him to leave. I do know people who don't run this still have sluggish devices. I do know that the native integration uses telnet and that the Envisalink device is super-chatty with it's communication.
My biggest concern at this time is getting as much processing as possible off of the Hubitat device itself and leave it to handle zwave, zigbee devices, run a few custom (but not resource-intensive apps). I don't consider Option #2 to be resource intensive and run this on my primary hub today. The other apps I run are things that interface directly with local services (some running on docker where the docker image is handling the heavy lifting) (Neosmart, Honeywell Option #2, Camect, Raincloud, Garage Doors Controller (ripped out MyQ Lite and my system got MUCH more responsive!)). The thought is to keep as much stuff off of the Hubitat device itself, but still keep it local (on my LAN). I'm also in the middle of moving many of my Rule Machine rules to Node-red to further compartmentalize things as to not impact CPU/Memory of the hub. It boggles my mind why Hubitat is continuing to release new devices with no apparent performance/rule processing upgrades. If there was a "pro" box or docker option, I'd keep everything there.
I think @doug had similar issues and went to go use Home Assistant. I like Hubitat and am more comfortable in Groovy, so I'm staying here. It also meets WAF much more so than HA.
Welcome to the club, hopefully I helped and haven't scared you away 
Sorry I haven't had a chance to look at this. I'll turn on debug logging to see if I can figure out what is causing it. I don't get a lot of chances to "play with the alarm" being stuck at home with other people, but I'll see if I can work some test time in.
Brian,
Thanks so much for your quick and detailed response! It’s members like you and others on this forum that also made me gravitate towards Hubitat due to your support over other hubs. Are you aware of any other Hubitat integrations that interface with a DSC/Envisalink combo that are NOT native to Hubitat in order to minimize Hubitat overhead? I could not find anything but I am of course new to all this. I really appreciate your contributions and support.
Glad to do it. I would try Option #1. Worst case scenario, you get slow-downs and you dedicate a Hubitat hub to your "things that slow down your main hub". I have an extra device specifically for this things like this. It may not impact your hub.
Also looks like there is an ST integration with AlarmServer that might work if you want to off-load the heavy lifting to another system. No idea if this works, but there might be someone on the ST forum that would have more info. If it does work, the code in that driver doesn't seem too complex, so it might port over without too much trouble.
UPDATE: You might try option 2 with DSC. I see code in the envisalink driver that mentions DSC. No idea if it works.
I checked tonight and there are no updates coming from envisalink when armed stay and there are motion events. In order to get them in Hubitat, the node proxy would have to see them and forward, but they aren’t there. Sorry.
1 Like
ah that was my fear as a layperson. Thanks for confirming. I'll see if I can't get a feature request (/ bug fix?) to the envisalink devs. Thanks!
So, I feel like a bit of an idiot because I must be doing something very obviously wrong here...
I have a DSC panel and Envisalink 3. I have installed the driver and the app and I have setup the app. Clearly my HE is connecting to the Envisalink because I see the IP address on the Envisalink page and I can arm and disarm the alarm through HSM.
However, I don't have any zones. I guess I kinda assumed that the zones would be created automatically while setting up the app, but there are none.
I have tried hitting the "Initialize" button and that reports back:
DeviceWatch-DeviceStatus : online
What am I missing please?
Thanks in advance, and thanks for developing this capability!
Jon.
Debug logs?
This is the log after pressing the "Initialize" button:
app:1642020-08-22 15:30:15.443 debugEnvisalink Integration: Connection Driver: Partition Ready LED On
app:1642020-08-22 15:30:15.429 debugEnvisalink Integration: Connection Driver: 10000001
app:1642020-08-22 15:30:15.405 debugEnvisalink Integration: Connection Driver: keypadLedState 81
app:1642020-08-22 15:30:15.388 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:15.374 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [51081FF]
app:1642020-08-22 15:30:15.350 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:15.336 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [8418D5]
app:1642020-08-22 15:30:15.311 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:15.298 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [8417D4]
app:1642020-08-22 15:30:15.272 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:15.257 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [8416D3]
app:1642020-08-22 15:30:15.232 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:15.219 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [8415D2]
app:1642020-08-22 15:30:15.193 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:15.180 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [8414D1]
app:1642020-08-22 15:30:15.154 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:15.141 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [8413D0]
app:1642020-08-22 15:30:15.115 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:15.102 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [8412CF]
app:1642020-08-22 15:30:15.077 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:15.061 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [8411CE]
app:1642020-08-22 15:30:15.033 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:15.015 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [6734D4]
app:1642020-08-22 15:30:14.984 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:14.966 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [6733D3]
app:1642020-08-22 15:30:14.933 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:14.917 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [6732D2]
app:1642020-08-22 15:30:14.892 debugEnvisalink Integration: Connection Driver: clearAllZones: Completed
app:1642020-08-22 15:30:14.871 debugEnvisalink Integration: Connection Driver: clearAllZones: called...
app:1642020-08-22 15:30:14.839 debugEnvisalink Integration: Connection Driver: partitionReady
app:1642020-08-22 15:30:14.823 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:14.810 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [6501CC]
app:1642020-08-22 15:30:14.773 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:14.757 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [61006431]
app:1642020-08-22 15:30:14.716 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:14.703 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [61006330]
app:1642020-08-22 15:30:14.660 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:14.646 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [6100622F]
app:1642020-08-22 15:30:14.607 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:14.594 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [6100612E]
app:1642020-08-22 15:30:14.558 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:14.544 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [6100602D]
app:1642020-08-22 15:30:14.508 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:14.495 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [61005935]
app:1642020-08-22 15:30:14.459 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:14.445 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [61005834]
app:1642020-08-22 15:30:14.409 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:14.396 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [61005733]
app:1642020-08-22 15:30:14.360 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:14.346 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [61005632]
app:1642020-08-22 15:30:14.308 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:14.291 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [61005531]
app:1642020-08-22 15:30:14.251 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:14.238 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [61005430]
app:1642020-08-22 15:30:14.202 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:14.186 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [6100532F]
app:1642020-08-22 15:30:14.147 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:14.133 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [6100522E]
app:1642020-08-22 15:30:14.095 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:14.081 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [6100512D]
app:1642020-08-22 15:30:14.045 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:14.031 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [6100502C]
app:1642020-08-22 15:30:13.980 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:13.967 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [61004934]
app:1642020-08-22 15:30:13.931 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:13.918 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [61004833]
app:1642020-08-22 15:30:13.882 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:13.865 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [61004732]
app:1642020-08-22 15:30:13.826 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:13.812 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [61004631]
app:1642020-08-22 15:30:13.776 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:13.762 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [61004530]
app:1642020-08-22 15:30:13.726 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:13.713 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [6100442F]
app:1642020-08-22 15:30:13.677 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:13.661 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [6100432E]
app:1642020-08-22 15:30:13.625 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:13.611 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [6100422D]
app:1642020-08-22 15:30:13.575 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:13.558 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [6100412C]
app:1642020-08-22 15:30:13.520 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:13.505 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [6100402B]
app:1642020-08-22 15:30:13.467 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:13.452 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [61003933]
app:1642020-08-22 15:30:13.413 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:13.398 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [61003832]
app:1642020-08-22 15:30:13.357 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:13.342 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [61003731]
app:1642020-08-22 15:30:13.302 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:13.287 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [61003630]
app:1642020-08-22 15:30:13.248 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:13.232 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [6100352F]
app:1642020-08-22 15:30:13.193 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:13.176 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [6100342E]
app:1642020-08-22 15:30:13.135 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:13.120 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [6100332D]
app:1642020-08-22 15:30:13.079 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:13.061 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [6100322C]
app:1642020-08-22 15:30:13.018 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:13.000 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [6100312B]
app:1642020-08-22 15:30:12.958 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:12.942 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [6100302A]
app:1642020-08-22 15:30:12.903 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:12.885 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [61002932]
app:1642020-08-22 15:30:12.844 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:12.830 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [61002831]
app:1642020-08-22 15:30:12.794 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:12.780 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [61002730]
app:1642020-08-22 15:30:12.743 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:12.727 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [6100262F]
app:1642020-08-22 15:30:12.687 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:12.669 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [6100252E]
app:1642020-08-22 15:30:12.623 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:12.607 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [6100242D]
app:1642020-08-22 15:30:12.567 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:12.551 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [6100232C]
app:1642020-08-22 15:30:12.511 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:12.495 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [6100222B]
app:1642020-08-22 15:30:12.455 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:12.439 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [6100212A]
app:1642020-08-22 15:30:12.398 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:12.353 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [61002029]
app:1642020-08-22 15:30:12.308 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:12.288 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [61001931]
app:1642020-08-22 15:30:12.242 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:12.223 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [61001830]
app:1642020-08-22 15:30:12.178 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:12.161 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [6100172F]
app:1642020-08-22 15:30:12.119 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:12.100 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [6100162E]
app:1642020-08-22 15:30:12.055 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:12.039 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [6100152D]
app:1642020-08-22 15:30:12.007 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:11.978 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [6100142C]
app:1642020-08-22 15:30:11.935 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:11.919 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [6100132B]
app:1642020-08-22 15:30:11.881 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:11.866 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [6100122A]
app:1642020-08-22 15:30:11.826 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:11.811 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [61001129]
app:1642020-08-22 15:30:11.770 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:11.753 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [61001028]
app:1642020-08-22 15:30:11.711 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:11.694 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [61000930]
app:1642020-08-22 15:30:11.650 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:11.633 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [6100082F]
app:1642020-08-22 15:30:11.594 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:11.576 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [6100072E]
app:1642020-08-22 15:30:11.498 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:11.483 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [6100062D]
app:1642020-08-22 15:30:11.440 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:11.425 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [6100052C]
app:1642020-08-22 15:30:11.383 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:11.366 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [6100042B]
app:1642020-08-22 15:30:11.324 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:11.306 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [6100032A]
app:1642020-08-22 15:30:11.258 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:11.237 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [61000229]
app:1642020-08-22 15:30:11.192 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:11.175 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [61000128]
app:1642020-08-22 15:30:11.147 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:11.130 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [50000126]
app:1642020-08-22 15:30:10.865 debugEnvisalink Integration: Connection Driver: sendTelnetCommand 00191
app:1642020-08-22 15:30:10.847 debugEnvisalink Integration: Connection Driver: cmdArray: 001
app:1642020-08-22 15:30:10.831 debugEnvisalink Integration: Connection Driver: generateChksum
app:1642020-08-22 15:30:10.814 debugEnvisalink Integration: Connection Driver: composeStatusReport
app:1642020-08-22 15:30:10.798 debugEnvisalink Integration: Connection Driver: StatusReport
app:1642020-08-22 15:30:01.047 debugEnvisalink Integration: Connection Driver: Login Successful
app:1642020-08-22 15:30:01.025 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:01.009 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [5051CB]
app:1642020-08-22 15:30:00.975 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:00.960 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [5000052A]
app:1642020-08-22 15:30:00.920 debugEnvisalink Integration: Connection Driver: Send Login
app:1642020-08-22 15:30:00.887 debugEnvisalink Integration: Connection Driver: sendTelnetLogin: user
app:1642020-08-22 15:30:00.871 debugEnvisalink Integration: Connection Driver: Connection to Envisalink established
app:1642020-08-22 15:30:00.852 debugEnvisalink Integration: Connection Driver: sendEvent([name:DeviceWatch-DeviceStatus, value:online])
app:1642020-08-22 15:30:00.833 debugEnvisalink Integration: Connection Driver: loginPrompt
app:1642020-08-22 15:30:00.808 debugEnvisalink Integration: Connection Driver: Panel Type: 0
app:1642020-08-22 15:30:00.789 debugEnvisalink Integration: Connection Driver: Parsing Incoming message: [5053CD]
app:1642020-08-22 15:29:28.500 infosubscribing
app:1642020-08-22 15:29:28.491 infoinitialize
app:1642020-08-22 15:29:28.488 infoupdated
app:1642020-08-22 15:29:26.955 debugEnvisalink Integration: getEnvisalinkDevice
app:1642020-08-22 15:29:26.950 debugEnvisalink Integration: getEnvisalinkDevice
Which integration did you use? #1 or #2 at the top? If it's #2, I'm not sure that works with DSC.
Thanks Brian, I used #1 since I wanted to implement fully native support.
Is my expectation of the functionality even accurate? I just assumed that it would initialize and create all the physical zones automatically, since that's how it worked when I was running a ST / Alarmserver combo...
That’s my assumption. Do you still have something running talking to the Envisalink? You can only have one integration running. So if you still have ST or Alarmserver talking to it, you need to turn that off first.
I didn’t write #1 (author left) and don’t use it, but I believe there is a thread that covers it’s use/issues unless it’s been deleted.
Probably not so much use to those using Envisalink with a Honeywell/Ademco panel but I just received my Hubitat C7 today and was excited to hook it up but was dismayed when I came upon this thread as I was hoping to use my alarm motion sensors in a similar manner. I haven’t actually set up the Hubitat yet but in preparation, I checked in the EyesOn app to see if Envisalink 4 was reporting motion on interior sensors (even though they are “disabled” when alarm is in Stay Armed status. At least with the DSC panel ( my ancient but trustworthy Power864) my Envisalink 4 reports motion to the Envisalink app so I’m hoping that it will report motion status to the Hubitat Integration app as well. I believe I have to use Brian’s update of Doug’s native app since my panel is a DSC. Hope this info is useful to someone (those with the Envisalink/DSC combo?). I’ll see if it works once I find time to get the Hubitat set up.
Unfortunately, as I have a DSC, although I wanted to use Brian’s Rpi solution to offload some of the processing load from the Hubitat, I am stuck using the native Envisalink integration. As I am only using the Hubitat to gain access to a few of the motion sensors (I am only interested in a few of the 64 zones I have set up), will mapping only those sensors help to significantly reduce the load on the Hubitat, or is the load primarily with how the link and data transfer is made with the Envisalink. In other words, does the Hubitat Integration app scan all the zones on the Envisalink (or receive all the chatter that the Envisalink sends out) whether all zones are mapped or not, or is telnet chatter reduced if only some of the zones have been mapped in the Hubitat. The reason this is important to me is that I want to minimize the risk of Hub slowing which seems to plague a number of users of the hub since I apparently can’t allocate some of the load to a Rpi .At the same time, I was not able to see if there was a way to add and subtract zones from the Hubitat once the integration app is loaded, or if it has to the deleted, reloaded and reprogrammed in its entirety every time there is a zone change.
As always, thanks for any answers to me nood questions.
Hey @moh! @brianwilson can probably better answer, but i don't believe this app puts much strain on the hubitat. from my observations, the envisalink / node server only send zone updates to hubitat when they happen, there's no constant chatter.
@brianwilson - had a quick chat with envisalink about the issue we discussed. it's an inherent issue / lack of functionality of the DSC panel itself 
guess i'll be getting some new motion sensors at least 
Hubitat will see the chatter anyway, even if the devices aren’t mapped. It’ll just ignore the chatter if you don’t configure everything. Might as well map everything.
