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.
Thank you both for the information. I have mapped all the zones into the native app and the Envisalink was not only recognized by the Hubitat, but in addition, the zones I designated were also picked up and discovered by Alexa via the Hubitat Alexa Skill. However, the zone status is not updating (I have polling intervals set up to the shortest interval of one minute). The debugging log shows repeated failures to acquire telnet communication and the error message “TPI password required”. I’m using the password (per another thread) that is used to sign onto the Envisalink in the direct web ui (not the one used to register with Envisalink. Not sure what to use for “device name” however. Is this the same as the “user name” or do I leave it on the Hubitat default of “Envisalink”? Or, is the device name my email address used as the “user name” when logging into the Envisalink web UI? Although the password can be easily changed in the Hubitat Integration App, the app does not allow for changing the “device name” once it is set up.
In summary, I’m not sure what I’m supposed to use for the “device name” and the “password” to enable telnet access. Also, IIRC, I think in setting up the app, that it asked for a telnet code or something like that? I looked in both the Envisalink web ui for my device (using the ip of the device) and the device info on the EyesOn app, and I did not see any reference to a telnet or communications code.
Again, any and all help is greatly appreciated. You guys are great! I so want this to work. Thanks.
Just to update (and sorry as I realize this thread is for the Honeywell/Ademco/Vista crowd but I wanted to also thank everyone who has tried to help me here) as I posted in the DSC/Envisalink discussion group, in Doug’s native app, even if you use the correct telnet PW (the one used to connect directly to the Envisalink board), it appears that the PW is limited to 6 characters. After spending hours playing with this (and with help from this group) I reset the pw on my EVL4 to 6characters and telnet connected and I finally got rid of the TPI pw required telnet comm error. Also, I know its a bit late for a previous poster, but in the native app, you do have to either manually map each of the zones, or manually have to set the integration app to discover the zones and populate the zone mapping for you. It is not automatic as in ST. Again, thanks for everyone’s help.
1 Like
Thanks for the port over to Hubitat, works great. Had not problems converting from Smartthings.
Have you given any thought to creating any additional zone types, such as Carbon Monoxide, Low Tempture, Water Leak, Panic Button, Heat Detector. Coming from the alarm industry these are very conman zones that would be on a security panel.
No plans to add anything like this. I'm guessing most of the items you mention - minus panic button - could be setup as a motion, contact or break glass and it would work the same. Assuming you get this to work, feel free to send your changes and I can add them.
Hi, I'm new to Hubitat coming from ST. I was able to successfully get the envisalink working with Hubitat but I found an issue and maybe I did something wrong. I can't see my only one motion sensor (Virtual Motion Sensor) in the list of motion sensors in the "Simple Automation Rules" App. I can see the virtual motion sensor device in the device list tab in Hubitat. Anybody can help me with that?
Can you take a screenshot of the device page for it? Maybe also look at the driver for that device and link to the ImportURL for it so I can see which one you’re using? Which method are you using #1 or #2?
Thanks a lot for your quick reply. I'm using method #1 (direct connection to envisalink). This is the driver I'm using: https://raw.githubusercontent.com/bdwilson/hubitat_envisalink/master/hubitat_envisalink_connection_driver.groovy
Screenshoots:
I see my devices and I'm using the same driver. Are you sure you're setting the device you want to control first, then the trigger? I'm actually using the Zone Driver for the #2 integration above, and not the one on #1, so I can't say for sure that's it, but the one I'm using has motion capabilities and showing up.
I can't change the type because is grayed out but it seems you can. Do you know why?
No idea. I guess it’s the integration with #1. I don’t think that’s the issue.
