Support for UNO-IP

[deliverer33]

Anyone know if this code will work with Eyezon and their board/envisalink combo, UNO-IP? Or does it require the a Honeywell or DSC panel?

[slaygirlz]

my idea too

[deliverer33]

I called Eyezon and they stated the UNO panel is based on the Honeywell TPI so maybe it will work? I would feel more comfortable getting someone to confirm they have got it to work previously before I make my purchases.

[ufodone]

Someone else was asking about Uno support here. You might follow up on that discussion to see if anyone else has a unit that they've tried the integration with.

[jaybug624]

I did just install the UNO took 40 minutes while on a conference call (I used to have DSC and EnvisaLink 3). I originally tried to use the old integration and it did not work, now I am thinking it was because I still had it set to DSC not Honeywell. I did get it setup and can confirm it did pull it in and detected all my zones. It discovered it as Honeywell. The only issue I am having right now is the panel is beeping every so often, I think it is the keep alive but I need to do some more testing tomorrow (Wife did not appreciate the constant beeping LOL).

I also plan to add the sidekick (LTE backup) will be interesting to see if it is able to pull in anything in regards to that. I would love to trigger some automation if it fails over to the LTE.

Side Note: In speaking to Eyezon they did say it is basically EnvisaLink 4 under the hood. I will also say I spoke with Eyezon at length and they seem like a really great company. I told them about home assistant as they had not heard of it before. The guy I spoke to (head of sales I think) was very interested in it and wanted to know if it still worked. It might be worth it for the developer to reach out they might hook you with some test gear.

[ufodone]

I've actually been in contact with Envisacor recently regarding a different issue and that led to a conversation about the UNO.

While the UNO does use the Honeywell TPI interface (which this integration relies on), I'm told that there are differences. From what they told me, I suspect that the stock integration (included with HA) currently has a higher likelihood of working. This is due to some changes made in this version to work around issues with zone updates on real Honewell panels. Based on what they've told me, I also suspect that most of the information available in the keypad entity will not be available (which it looks like may be the case in the screenshot you provided).

That being said, they are looking for beta testers and open to adding in any missing functionality. I don't have one of these devices so have no way to test. But if there are others interesting in testing, then I can attempt to add the needed changes to make this work (as well as work with Envisacor on missing features). It may be a lengthy process though given my current available time.

[slaygirlz]

I did just install the UNO took 40 minutes while on a conference call (I used to have DSC and EnvisaLink 3). I originally tried to use the old integration and it did not work, now I am thinking it was because I still had it set to DSC not Honeywell. I did get it setup and can confirm it did pull it in and detected all my zones. It discovered it as Honeywell. The only issue I am having right now is the panel is beeping every so often, I think it is the keep alive but I need to do some more testing tomorrow (Wife did not appreciate the constant beeping LOL).

I also plan to add the sidekick (LTE backup) will be interesting to see if it is able to pull in anything in regards to that. I would love to trigger some automation if it fails over to the LTE.

Side Note: In speaking to Eyezon they did say it is basically EnvisaLink 4 under the hood. I will also say I spoke with Eyezon at length and they seem like a really great company. I told them about home assistant as they had not heard of it before. The guy I spoke to (head of sales I think) was very interested in it and wanted to know if it still worked. It might be worth it for the developer to reach out they might hook you with some test gear.

you have the uno? can you make a video that shows the panel how you installed it and the keypad and programing :)

[jaybug624]

I've actually been in contact with Envisacor recently regarding a different issue and that led to a conversation about the UNO.

While the UNO does use the Honeywell TPI interface (which this integration relies on), I'm told that there are differences. From what they told me, I suspect that the stock integration (included with HA) currently has a higher likelihood of working. This is due to some changes made in this version to work around issues with zone updates on real Honewell panels. Based on what they've told me, I also suspect that most of the information available in the keypad entity will not be available (which it looks like may be the case in the screenshot you provided).

That being said, they are looking for beta testers and open to adding in any missing functionality. I don't have one of these devices so have no way to test. But if there are others interesting in testing, then I can attempt to add the needed changes to make this work (as well as work with Envisacor on missing features). It may be a lengthy process though given my current available time.

I would be more than happy to aid in this. Let me know how I can help, maybe dm or discord?

[deliverer33]

I will also contribute if we think we can get the uno working once my house is completed. @jaybug624 just to confirm it’s working minus the keypad?

[ufodone]

Adding @pileofkyle who was also enquiring about the UNO a while back.

I won't be able to get to this right away as I've got a few other things in the queue first.

@jaybug624 Since you've already configured your system, a good place to start would be if you could enable debug logging for the integration, startup HA, trip some zones, and to arm/disarm, etc. and then send me the log. That will give me a sense of how compatible the UNO is with the existing Honeywell implementation.

You can enable debug logging by adding something like the following to your configuration.yaml:

logger:
  default: info
  logs:
    custom_components.envisalink_new: debug

Thanks.

[pileofkyle]

I'm exploring alternatives since DSC has discontinued their Power Series panels. My experimentation included using an EnvisaLink 4 with UNO Standalone firmware, although I'm uncertain if this is identical to the newly released full UNO IP panel. This setup involved Honeywell, but I encountered issues with constant spamming of a keypad panic or similar error, rendering it unusable. Additionally, I've found the zone status updates from Honeywell to be disappointingly slow. Interestingly, the UNO IP panel's webpage mentions compatibility with DSC keypads, suggesting it might use DSC firmware. I plan to conduct further testing with the EnvisaLink 4 in Standalone mode and will share my findings and logs.

[ufodone]

I received the following from Envisacor when I was discussing UNO support with them:

Yes, the UNO864 panel, and the other "UNO"s (now called StandAlone), all support the same TPI which is modelled after the Honeywell TPI as it is pretty simple. It already has support for everything except the virtual keypad update.

He also confirmed that while the UNOs use the Honeywell TPI, they will not suffer the same problem with slow zone updates. Both partition and zone updates will be real-time.

The current envisalink_new integration no longer uses the zone updates from the Honeywell TPI because of the slowness you mentioned. It instead tries to do a better job of zone updates based on the virtual keypad updates. For this reason, I wouldn't expect much to work with the UNO and this version of the integration right now. But given there is interest, I'll try and get things working with these UNO panels.

[ufodone]

The devices modelled after the Honeywell TPI:

UNO Panel

EVl4MAX - SA (Standalone)

EVL4 - SA

DUO - SA

[deliverer33]

One question I have is the uno supposedly supports the DSC keypad. Would the integration work differently if I made an investment in the uno with DSC keypads or is it irrelevant to this conversation?

[ufodone]

The integration currently knows nothing about the type of keypads attached to a panel so my guess would be that it should be irrelevant what physical keypads you use. If you are worried though I'd suggest asking EyezOn. They likely won't know anything about Home Assistant but should be able to confirm whether or not the keypad type has any impact on how the TPI works.

[jaybug624]

A bit of information I have gathered from my environment. ( I should track down model numbers, so will update as I find them)

Original System:

• I had a DSC system installed when we built our house 7 years ago.
• I have two DSC keypads as well.
• I have both wired and wireless devices (Wireless: Motion and glass break)
• I had a envisalink 3 hooked to the system
• I also had the DSC network connection (call me paranoid as I had both monitoring the system LOL)
• I had been using the original integration to connect it to HA.

Updated System:

• UNO IP Alarm
• I also got the LTE backup (have not hooked it up as I am missing a cable)
• All other hardware is the same (DSC Panels, wired and wireless sensors)
• Original integration did NOT work, which is how I found this new integration (more on this latter)

Upgrade path:

• The upgrade was really easy, it is just moving wires from the DSC board to the new one. They are labeled the same and in essentially to same spot.
• Once it was powered on I went to the EyezOn portal and went through the new device setup which was putting in the MAC of the device then labeling the zones.
• For me it auto discovered the two wireless devices I had, it sounds like my panels had the information at that's why.
• One thing I did have to enable in the settings of UNO 'Normally Closed Contacts (OFF - EOL Resistors)'
• All configuration is done via the web portal so it is really easy.
• Side Note: Speaking with EyezOn they said they are still rolling out updates to give you even more configurations capabilities via the web. They also said programing via a panel is very limited right now but more updates are coming for that and they are planning to release their own panel for even more functionality. (sounded like its in production right now.) Though I have only found one thing I cant do right now (See below for open issues)
• Once I had the system setup I went to update the IP Address in HA and thats when I realized it did not work.
• I originally tried switching to version 4 to see if that made a difference, it did not.
• I then found this integration and ran through the setup, it looked to have worked. (Not fully though)
• This is when I noticed during the discovery process it detected it as a Honeywell system.
• I tried going back to the old integration but configured it for 'Honeywell' and that looked to have also worked mostly. (See Open Issues)

Open Issues:

• Uno System: For me at night time we would arm the alarm with no entry delay (9 + Code) and then once in bed enable the motion sensors (1). You can not currently do this from the panel. You can do *9 through the web but not through the app. There is also no way to arm the interior outside of doing the 'AWAY; button but you get the countdown and still have the exit delay. Speaking with EyezOn, they asked for me to send that in as a feature request so they can add it to their backlog. This may not be a feature for everyone and still not enough for me to NOT recommend the UNO system, I still like the system and not having to pull out the book to figure out how to program it and instead having a nice web interface is worth it.

• HA integration: (The reason we are all here :) ) It appears both new and old integrations have similar issues, though I think the old worked a bit better as @ufodone suspected. It is clearly sending commands to the system that it is not expecting. Noticed that panel beeps every so often and sometimes has the 'Memory' label on it. This is where I now will run the debug and send the logs for @ufodone to take a look at. It seems like it is 90% the way there which is good. I will also see if I can track down anything to help him out. I will also test some of the responsiveness (it seems quick from the limited testing.) I will notify the monitoring company as I am worried I might trip it and dont want an unwanted knock on my door.

[fxl90]

I’m also available for testing. Just installed the UNO IP today. As @jaybug624 mentioned, it was a relatively simple install.

[ufodone]

I've passed along to Envisacor the additions I think I'll need to get the UNO panels working. I don't have an ETA on when they will be able to make the additions.

It may be possible to get some functionality working with the current firmware but I'll need debug logs from someone who has an UNO panel before I can do anything.

[Enoche21]

Hello All, I thought I would share my experiences installing and setting up the UNO-IP and DSC PTK5507W with hopes of this helping the update and support of the product. Currently the system (UNO & DSC) are up and running successfully with hardwired sensors on doors and windows. I can arm, disarm, and the alarm triggers properly.

Integrating with HA:

• I followed the HA //Envisalink integration page as per Eyezon's customer support
• Added the example text to my configuration.yaml
• DSC doesn't work but Honeywell does as a panel_type:
• Eyezon said to treat it as evl_version: 4
• Added my zones as I have them in Eyezon web config
• Restarted HA

Initial Results:

• HA recognized all my door and window sensors
• Tested each and HA registers open and close

Automation:

• Based on these results I set up auto triggers to tell me when each door opens via my Google minis
• Tested and it all worked great

Secondary Results:

• This is when I started noticing issues
• Wife and I are sitting down watching tv at 9pm and Google chimes in and says "front door is open"! But it ain't.
• Wife not happy.
• Then 2 hrs later, "Mudroom door is open", but it ain't...
• I disable all the voice notifications and start looking at logs and such

Investigation:

• First thing I notice is that the Eyezon web portal has no record of the doors opening or closing
• I look at the HA history and I can see the doors opening and closing in the history
• I also note that the time from open to close in all instances is exactly 30 seconds, which I find odd but draw no conclusions
• I then notice as I am near my DSC panel that it is beeping regularly even though no doors or motions are being triggered
• I look at the Eyezon web portal app again and notice Personal Emergency is being triggered every 30 +/- seconds! Fortunately I have not set up external monitoring yet...

As Far As I Got:

• So I start a trial and error approach to see if I can figure out what is going on.
• I change config options, and try different HA addons, etc.
• All that I have been able to narrow it down to is the top part of the config yaml. With the entire Envisalink config section rem'd out, no Personal Emergencies, no random open doors. If have just have from host: down to timeout: , not even listing any of the zone info, I get the Personal Emergency alert.

I stopped there since I can not get past the Personal Emergency trigger. I contacted Eyezon and they sent me to this specific page. Not sure if any of this helps but I really would love to automate this UNO-IP.

[ufodone]

I won't be able to do anything here without some debug logs as I don't own an UNO system myself. Thanks.

[pileofkyle]

I picked up an UNO IP Panel, latest firmware. Tried both the core (set to HONEYWELL + EVL4) and Envisalink_new integrations. No zone updates, the arm disarm buttons will "beep" the keypad. Keypad will send a "Personal Emergency" every 60 seconds.

Thanks for the help!

Envisalink_new UNO debug.log Envisalink core intergration debug.log

[ufodone]

@pileofkyle Thank you for the logs. It would appear that the Personal Emergency events you and @Enoche21 are seeing are likely triggered when the integration sends a command to the panel. From you logs I see CID events indicating Personal Emergency immediately following when a command or keystroke is sent to the UNO.

@Enoche21 : I assume the results you posted were with the stock/core envisalink integration rather than envisalink_new? From what I've been told about the panels and based on how envisalink and envisalink_new differ, I wouldn't expect envisalink_new to register zone open/close events.

I'll see what I can find out from Envisacor as to why it is triggering the Personal Emergency events.

[Enoche21]

Thanks @ufodone . I switched to the envisalink_new and will test for random door alerts today. With the envisalink_new I still get the Personal Emergency alerts, same as pileofkyle. What I have noticed is that if I go to Integration Entries and click configure, under Advanced it gives you the Options panel specific to Panic. If I change the Keep-alive interval it changes the duration between Personal Emergency alerts (60 vs 120 vs 240). For now I am keeping it at a huge number to keep it for filling the log (though I am guessing it is keeping the alert on).

[Enoche21]

Also, with the Envisalink_new setup, HA does not recognize changes in the entities. When a door or motion is triggered HA does not register it. It seems to recognize the entities / zones but not the change in state. Not sure if I am doing something wrong.

[slaygirlz]

mudroom door keeping your mud in a room interesting

[ufodone]

I have published a pre-release v0.9.0-alpha-uno1 which should make the zone and partition update work. I expect there is still plenty of work to be done though.

I'm told that the Personal Emergency issue should be fixed in firmware version 1.0.72 so please be sure to update to that.

Just a reminded that I do not own one of these devices nor do I currently have any documentation on the interface so everything is "best guess" based on what I've been told and the logs provided. Please be sure to include full debug logs when reporting issues.

[ufodone]

You will need to enable the "Show Beta Versions" (under "Redownload") in order to see this version showing up.

[pileofkyle]

@ufodone Thanks for support on this! Personal Emergency issue is fixed. Keypad partition state is working, I can arm and disarm. No zone updates though.

Envisalink_new_uno.log

[ufodone]

@pileofkyle Thanks for the update.

The logs explain why you aren't seeing any zone updates: the UNO panel isn't sending any. I had a look back again at the other log you previously posted and it didn't have any either. I'll have to check with Envisacor to see what's up with that.

I see a REDACTED in the log where it's printing the MAC address. I assume that's you manually redacting the value? I don't need to see it but wanted to be sure that the code is, in fact, able to obtain the MAC address as that is important in generating the unique ID for the device that HA requires.

[ufodone]

@pileofkyle I checked with Envisacor and they have indicated that the zone updates should be sent. They shared a log of their own system showing this. It is also in line with what @Enoche21 saw when using the stock envisalink integration.

Are you sure that you faults some zones with your test? I don't believe the UNO will currently send a "current state" for zones on initial connection so if no zones changed state while you did the test, that would explain why I'm not seeing any of the zone state updates (%01) in your logs.

[Enoche21]

@ufodone I have updated to V.0.9.0 and have firmware 72. Looks like the Personal Emergency is indeed gone. But have the same issue as @pileofkyle - not registering faults. Screen shot shows that I have opened doors and triggered motions, even left a door open, and no faults registered. Refreshed screen.

Where do I find the log(s) to share?

Could it be because I am not using resistors?

[ufodone]

Are either of you able to provide me the MAC address of your UNO devices? Envisacor is asking if I can get those - I suspect they are able to check setup on their end (if you are connecting your system to their service).

[pileofkyle]

Sounds good, it’s 001C2A400418 Thanks!

On Feb 27, 2024, at 7:37 PM, ufodone @.***> wrote:

Are either of you able to provide me the MAC address of your UNO devices? Envisacor is asking if I can get those - I suspect they are able to check setup on their end (if you are connecting your system to their service).

— Reply to this email directly, view it on GitHub https://github.com/ufodone/envisalink_new/issues/77#issuecomment-1967972569, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWCYJDYYS6LRGFXWZ37EIPDYVZ35DAVCNFSM6AAAAABBJHZVLSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRXHE3TENJWHE. You are receiving this because you were mentioned.

[ufodone]

@pileofkyle Here's the response I got based on that MAC address:

That unit isn't even programmed. It's listed as "lab" and has two zones that are not connected to anything. It will never generate %01 because they are ALWAYS faulted.

You might want to check with EyezOn support regarding this.

@Enoche21 Given the screenshots that you shared, it certainly looks like you system is "programmed" but if you can provide your MAC address I can check with them.

Could it be because I am not using resistors?

Probably not but if that is the case, I'd say that's probably a bug in the firmware.

Where do I find the log(s) to share?

You'll need to enable debug logging by adding something like this to your configuration.yaml:

logger:
  default: info
  logs:
    custom_components.envisalink_new: debug

and then restart HA. Once you've tried faulting a few zones, you can download the logs from Settings->System->Logs and there is a button at the bottom of the page to download full logs.

[pileofkyle]

@ufodone I realized the UNO panel programming was defaulted to N/O with resistors, I was manually bypassing the zones before through EyezOn web portal to test arming and disarming. This is just a test setup so I only enabled a few zones, but the system is programmed. I tried configuring to N/C, no resistors to see if that made any difference, I can confirm I see the zones opening and closing via the EyezOn web portal, but still no zone updates in Home assistant.

Here's the latest log output:

home-assistant_2024-02-29T15-55-24.680Z.log

Thanks

[pileofkyle]

@ufodone It works! After wiring an Uno 8 expansion module to the system, which added zones 9-16. I only had z9 enable (as well as zones 1-8) on the EyesOn web zone programming. When I tripped z9, I noticed z8 would activate. I went back to the web programming and enabled all zones from 1-16 as instant and now they all work.

So a note to other users, you must add all the zones on the EyesOn web zone programming (see photos) even if you're not using a zone in order for things to work.

Lastest log output:

home-assistant_2024-02-29T16-41-33.434Z.log

[Enoche21]

So a note to other users, you must add all the zones on the EyesOn web zone programming (see photos) even if you're not using a zone in order for things to work.

I do have all 8 available zones setup and HA does not register faults. BUT I did notice you have your zones set at "Instant" where mine are set to "Entry/Exit Zone" and "Interior Zone (Stay)" which may be the problem. Testing now.

[Enoche21]

@Enoche21 Given the screenshots that you shared, it certainly looks like you system is "programmed" but if you can provide your MAC address I can check with them.

@ufodone Is there any way to send that privately? Don't see a private message option in GitHub. I have also modified my yaml to begin logging. Thanks.

[Enoche21]

So a note to other users, you must add all the zones on the EyesOn web zone programming (see photos) even if you're not using a zone in order for things to work.

I do have all 8 available zones setup and HA does not register faults. BUT I did notice you have your zones set at "Instant" where mine are set to "Entry/Exit Zone" and "Interior Zone (Stay)" which may be the problem. Testing now.

Changing to instant did not fix HA not registering faults. No difference. I also made sure Zone 4 was in HA and Eyezon AP even though it is not used. No change.

Here is my first log data dump:
home-assistant_2024-02-29T17-53-28.251Z.log

[Enoche21]

@Enoche21 Given the screenshots that you shared, it certainly looks like you system is "programmed" but if you can provide your MAC address I can check with them.

@ufodone Is there any way to send that privately? Don't see a private message option in GitHub. I have also modified my yaml to begin logging. Thanks.

Nevermind. MAC is in log anyways. 001c2a40048d

[pileofkyle]

@Enoche21

[ufodone]

@Enoche21 Thanks for the logs. It looks like you system IS sending the required updates but that the code is parsing them incorrectly. I'll try and have a look a fixing that tonight. It doesn't look like you should need to make any additional setup changes to your system.

Given you were getting zone updates with the stock envisalink integration, I also suspect that your original configuration working working as well.

[Enoche21]

Given you were getting zone updates with the stock envisalink integration, I also suspect that your original configuration working working as well.

Yes, my system worked with the original integration, just gave me rouge door opens and personal emergency alerts.

[ufodone]

I've posted a new version which should fix the zone update issue.

[Enoche21]

I've posted a new version which should fix the zone update issue.

@ufodone - Oh, it is a beautiful thing... Thank you so much!

[fxl90]

Awesome, also have my zones and panel arming working! @ufodone What should the Panel Chime switch be doing?

[ufodone]

The Panel Chime switch will toggle whether the panel will chime when a zone is faulted (assuming the zone it setup this way). It just sends the <code>9 keypresses to the panel for Honeywell (and now Uno) systems. I don't know whether the Uno systems support this key sequence.

[Enoche21]

@ufodone , just to confirm, everything is up and running. Tested automations (google mini text to speech) and no false positives. Everything is all good. Is this just a hobby or is there a way I could "tip" you? Very much worth it. Thank you so much.

[deliverer33]

Thanks everyone for helping with the logs I second @ufodone for your efforts here. Any idea if/when this code will be merged back into the main code? I’ll report back once my system is up but I’m a couple of months away from being able to do that.

[ufodone]

Thanks for the updates and glad to hear things are working now.

Any idea if/when this code will be merged back into the main code

I need to get detection working before that can happen so the integration will be able to properly differentiate between Honeywell and Uno systems. I think there's a way to do that with what's available in the firmware today but I just haven't had a chance to get to it yet.

[524248]

Been lurking here for a while, as I used to have a DSC Power 832-based system, consisting of DSC PC5010 main board, 2 PK5501Z LCD keypads, a PC5132-433 wireless module with two 4-button key fobs, and an EVL4 as a local IP interface. The canned HA Envisalink integration via configuration.yaml worked well with this setup for some time. I recently replaced the PC5010 board and EVL4 with an Envisalink UNO-IP and saw HA could no longer access the alarm system.

I ran across a posting about "EnvisaLink Refactored" and ended up here reading this thread. I've loaded the HACS/EnvisaLink_New integration, and after restarting HA, commented out the old configuration.yaml EnvisaLink stuff. Restarted HA again for good measure.

Went through the device and entities cleanup (naming etc), and created a couple new dashboards. HA complained that it couldn't find keypad_1 (it doesn't even mention 2nd keypad or the 5132-433 wireless unit, so I guess those aren't part of the EnvisaLink inteface). Zones weren't updating and the arm/disarm functions didn't seem to work. I saw there was an update for 0.90_uno2, read the warning and did the update with little to lose.

After the update, my zone entities in HA responded to changes in the sensors, both door and motion, as expected. and I think HA now sees the keypad, but I don't know which of the two it is (not really an issue, they're redundant).

Device Info: EnvisaLink 0: UNO by eyezon, Firmware 01.00.77

I left default "Alarm" as the name, so my 11 entities are:

• sensor.alarm_partition_1_keypad
• binary_sensor.alarm_zone_1 [ door ]
• binary_sensor.alarm_zone_2 [ door ]
• binary_sensor.alarm_zone_3 [ door ]
• binary_sensor.alarm_zone_4 [ motion ]
• binary_sensor.alarm_zone_5 [ motion ]
• binary_sensor.alarm_zone_6 [ motion ]
• binary_sensor.alarm_zone_7 [ motion ]
• binary_sensor.alarm_zone_8 [ Not Used ]
• switch.alarm_panel_chime [ chime on-off ]
• alarm_control_panel.alarm_partition_1 [ states: arm_home, arm_away and arm_night ]

When I toggle the Panel Chime on-off, it triggers ARM / DISARM commands. When the system is ARMed this way, alarm_partition_1 state goes from flashing "Pending" to "Armed", as expected. When I DISARM the system by toggling the chime,the state goes back to DISARMED. There is no effect by toggling the chime on the keypad Chime beep when a door is opened (the toggle isn't changing the keypad Chime state).

Is anyone else getting this behaviour, or have I fat-fingered my setup?

I also noticed that there are a LOT of "Attributes" associated with alarm_partition_1_keypad (ie. AC present, armed bypass, entry delay, etc). Are these not available for display as entities? I know I can do some yaml-fu to surface them, but ...