ejn1

I agree. Not linking this to C4 accountability at all. The driver is 3P as well. 15 secs was the shortest timing my integrator could get without it missing the signal. My integrator basically said the same thing as you as the soundbar is the slow link but once again I don't think my setup is that unique so it may be valuable for others to know. But all in all this was one of the lesser issues in my list, the door chime link works great and is instant. Bottom line though is unless you have C4 touchpads with video capability, then the value of paying for the 3P driver goes down greatly in my opinion. I just bought a T3 touchpad but havent installed yet but will test the driver out in that capacity as i soon as I have installed.

All, I thought I would post a few experiences with my Doorbird D202. Likes: Very Professional Look and clean installation High build quality Good Camera quality and audio quality Limited noise / interference when 2-way communication with the Doorbird When someone presses the doorbell, it takes a clean pic and saves in the app Dislikes: First and most important is around the clumsiness of the remote access via IOS and the quality and speed of the connection. I have very strong Cellular LTE connection much of the time but yet almost NEVER is the connection to the device quick enough for me to actually answer the doorbell before someone walks off. The lag via IOS cellular connection is awful thus negating one of the primary reasons on bought the device. When the Doorbird APP rings on my Iphone i get a notification pop up on main screen but the iphone is usually locked. To answer, I cant just tap the notification, i have to unlock the phone, scroll to the app, open it and then in most cases it lags for a very long time to connect and sometimes never connects. Not sure if this is because doorbird is in Germany and the intercom call are routed their via cloud ? The Doorbird "Birdchirp" chime is very difficult to hear outside when someone presses the button. You cannot change the outside chime or volume at the doorstation. I have the Control4 houselogix driver and that is disappointing as the lag to get the ring through my audio speakers is almost 15 sec. After trying this for a few days, i disabled this in C4 and just hardwired the Doorbird to my door chime inside the house which works instaneous. I understand that if you have a C4 amp to speakers, the lag can be reduced but i have it going to a soundbar connected via HDMI to my C4 controller and the lag is too long to be useful. All and all, the lag to the IOS and the frequent inability to connect real time, and the clumsiness of connecting of IOS App is making for a not so positive experience but there is hope i guess for future doorbird improvements. A tad too big in the design but can live with that...

Yes, i have the HS2064. Currently, i have about 11 hard wired zones so I added a DSC zone expander card to accommodate. For some reason, the Control4 GUI does not show the zones outside of the 8 on the board itself opening and closing. They work perfectly on the keypads and actually got pulled into C4 to show the zone labels but only the ones on zones 1-8 show opening and closing on the C4 gui. Its the only quirk i have found so far with the C4 driver. I tested everything known on the TL280 card and panel and it is all set up properly per DSC tech support. Its not a big deal as the critical functionality is working great with C4 but hopefully something that will be worked out in a next driver version.

Here it is... DSC PowerSeries NEO PCL422 Communicator Remote Mounting Module

i think there is an extension you can purchase to position it away from the panel.

It wasn't that as the Ubiquiti Edgeswitches dont share a port with the SFP port. I haven't investigated yet as I had several gremlins appear in my C4 system when I changed switches so for the time being i switched back to my TP-Link SG2424P switch. I really like the Ubiquiti switches so will try to learn more about their installation tweaks. The SFP port connection was live on the Ubiquiti switches and it did enable devices onto the network across the switches but for some reason, devices that needed to communicate with each couldn't be on different switches even though they were connected.

I've got it to work now... The issue was I installed 2 new switches and patched together via SFP fiber and the alarm panel was on one switch and the other was on the other switch and they were not talking for some reason. WHen i moved to same switch it worked.

My TL280 card is version 5.01

I can go look but I have the latest version i know as I had to use updated subsections versus what was in the C4 instructions... I found this out by calling DSC and they said i have the latest version of the card.

Hi all, I've just installed a DSC NEO alarm panel and I have added the TL280 internet communicator and the C4 driver. I followed the c4 instructions to the letter and the alarm setup seemed to go fine and then added the alarm credentials to the driver in composer HE. For some reason, i cannot get C4 to see the alarm. I have a clear IP address for the DSC that I can ping just fine. Appreciate if anyone has any words of wisdom or tricks to make this driver work. Thanks!

...

Many thanks all, Got it to work now. Much appreciated!

All, would great appreciate if someone could post a pic of where the IR bud location needs to be on the UBD-k8500... I have tried locations reported on net to no avail. Thanks in advance.