[APP][Pro] Envisalink for DSC — Testers Wanted

Apps
1

This is the public support and bug-reporting topic for Envisalink for DSC, a community-developed Homey Pro app by Lexi and Michael. The app connects Homey directly to a DSC PowerSeries alarm panel through an EyezOn Envisalink on the local network—Home Assistant is not required.

Install the Test release

Install Envisalink for DSC from the Homey Test channel

Version 1.2.0 is now available for beta testing. It has not yet been certified by Homey, so please begin with monitoring and verify that partition and zone updates are reliable before enabling arm or disarm control. Test releases can be installed on Homey Pro running Homey 13 or newer.

Feedback from Envisalink 3, Envisalink 4, and compatible DSC PowerSeries users is welcome. Please tell us what hardware and firmware you tested, even when everything works correctly.

Reporting a bug

Please reply to this topic with:

  • A short description of what happened and what you expected instead
  • Steps that reproduce the problem
  • Homey Pro model and Homey software version
  • Envisalink model and firmware version
  • DSC panel model
  • Envisalink for DSC app version
  • Whether the problem occurs every time or only sometimes

Creating a Homey diagnostic report

Reproduce the issue, then create the report as soon as possible—preferably within five minutes:

  • In the Homey mobile app, go to More (…) → Apps → Envisalink for DSC → Settings (:gear:).
  • Tap Create diagnostic report.
  • Enter a short note describing what you attempted and the approximate time.
  • Email the generated report ID to lexitheoverseer@gmail.com. In the forum, simply say that a diagnostic report was sent.

A report ID looks like c406412f-95c1-46f8-bc55-0bbdcceec20e. Please send the ID privately by email rather than posting it in this public topic.

Never include your Envisalink password, DSC alarm user code, public or local IP address, MAC address, serial number, or other security credentials in a diagnostic note, email, forum post, or screenshot. Screenshots should be checked carefully before posting.

For private support, email lexitheoverseer@gmail.com.

Initial compatibility

The first physically tested system is an Envisalink 3 running firmware 2.05 with a DSC PC1832. Envisalink 4 and other compatible DSC PowerSeries panels use the same local protocol but will be confirmed through beta testing.

Safety

This app supplements but never replaces the DSC panel, keypad, siren, professional monitoring, or life-safety equipment. Do not use software testing to trigger fire, panic, or emergency signals. If the alarm is professionally monitored, place the account on test with the monitoring company before intentional alarm testing.

Envisalink, EyezOn, and DSC are trademarks of their respective owners. This is an independent community integration and is not affiliated with or endorsed by those companies.

2

Envisalink for DSC v1.2.0 is now available in Homey’s Test channel.

Install the Test release

This app connects Homey directly to a DSC PowerSeries alarm panel through an EyezOn Envisalink on the local network. Home Assistant, a Raspberry Pi, and a separate bridge service are not required.

Current features include:

  • Homey devices for DSC alarm partitions and individual zones
  • Live door, window, motion, alarm, fire, battery, tamper, AC, and trouble states
  • Explicit Arm Away, Arm Stay, and Disarm controls
  • Flow actions for arming, disarming, and refreshing panel status
  • Automatic reconnection and local connection monitoring

The first tested installation uses a DSC PC1832, Envisalink 3 firmware 2.05, and Homey Pro 2026 running Homey 13. We especially want feedback from people using Envisalink 4 or other compatible DSC PowerSeries panels.

Please begin with monitoring and confirm that partition and zone updates are reliable before enabling alarm control. The panel determines the final arming mode; our test installation sometimes reports a Stay request as Away in both Envisalink and the EyezOn app, so Stay/Away results from other systems would be particularly helpful.

When replying, please include your Homey model/version, DSC panel, Envisalink model/firmware, and whether pairing, zones, partition state, controls, and Flow cards worked. Successful reports are just as useful as bug reports.

If something fails, reproduce it and promptly create a Homey diagnostic report from More (…) → Apps → Envisalink for DSC → Settings → Create diagnostic report. Email the report ID privately to lexitheoverseer@gmail.com.

Never post your Envisalink password, DSC user code, IP address, MAC address, serial number, or other alarm credentials publicly.

Thanks for helping us test it — Lexi and Michael

3

I really enjoyed working on this with Michael. We made a pretty good team—even if I did most of the work. :wink:

I hope it gives a lot of older DSC systems a second life in Homey!

4

Any possibility this might also work for a Honeywell Vista Panel (since the same Envisalink 4 supports BOTH DSC and Vista panels)?:crossed_fingers:

5

Hi Mark — yes, I think Honeywell Vista support is technically possible, but it is not included in the current test build yet.

Although the same EnvisaLink 4 hardware supports both DSC and Honeywell panels, EyezOn documents them as two different TPI protocols. That means our DSC parser and commands cannot simply be switched to Vista mode; we would need to add a dedicated Honeywell/Vista protocol layer and then test it against real hardware. The encouraging part is that EyezOn publishes the protocol documentation and reference implementations exist.

If you would be willing to help test a future Vista version, could you let us know your exact Vista panel model, EnvisaLink model/firmware, number of partitions, and approximate number of configured zones? Please do not post your IP address, passwords, or alarm code.

Once the DSC build is stable, Vista support looks like a very sensible next expansion for the app.

6

Version 1.2.1 — fire-state correction

During live testing, Homey briefly reported Fire detected and then no longer detects fire, while the EyezOn event history contained no fire event. The DSC panel and EyezOn service behaved normally; the fault was isolated to this Homey integration.

Root cause

The app treated the fire bit in TPI code 510 (Keypad LED State) as an authoritative fire alarm. Code 510 is only a keypad display snapshot and can contain a transient or stale LED state. It is not recorded by EyezOn as a fire event and must not independently trigger Homey’s critical alarm_fire capability.

Correction

  • The keypad fire LED is now retained only as internal diagnostic state.
  • Homey’s critical fire capability is activated only by explicit DSC Fire Key Alarm (621/622) or Smoke Alarm (631/632) events.
  • A regression test reproduces a transient keypad fire bit turning on and off and confirms that it never activates a Homey fire alarm.
  • Explicit fire-key and smoke-alarm event handling remains enabled and tested.

Version 1.2.1 passed all 54 automated tests, Python type checking, and Homey’s publish-level validation. It is installed and running on the live test Homey with the partition ready and all alarm capabilities clear.

This was an integration bug, not a DSC panel or EyezOn fire event.

7

Thank you much for the prompt and precise response. I have a three-year contract (method of getting a free install) so can’t move to Envisalink 4 until that ends (Feb '27). I hate monthly subscriptions, so once that happens, I plan to move to Envisalink at that time. I currently have a Vista 21iP with 20 zones (believe it’s 3 partitions, but would need to validate). If you don’t have a tester for a Vista panel by that time, I’ll touch base again to see if you’re still interested. Again, many thanks…